vishal patel
Sr Tech Lead · Technical & Solution Architect · Engineering Manager

Vishal Patel designssystems, and leads theteams that ship them.

15+ years in software, 8+ leading engineering teams. I own platform capabilities end to end — HLD and LLD, versioned API contracts, implementation and production — on multi-tenant SaaS serving 500+ enterprise tenants.

1 mo → 1 wk
developer onboarding, via an AI agent-based setup system
5 h → 1 h
production issue resolution, via logging, alerts and dashboards
500+
enterprise tenants on the platform I led features for
50+
technical interviews run; mentored a team of 8

// 01 · case studiesSelected work

01 — 06 · all →

// Core development

Platform capabilities and engineering tooling I designed and led.

release v2· entry/home· entry/pricing· asset/herofallbackchecken-usfr-frde-deja-jp
Tech lead · Contentstack platform01

Stopping unintended locale publishing: cross-locale release items

Enterprise customers were publishing content into markets it was never localised for, via master-locale fallback. I led the design that enforces the rule in the release service without breaking a single existing client.

Rule enforced for every client (UI, API, SDK, CLI) — not just the UI
maincompare-branchGET merge job · per-item details+content_type/blogadded~entry/homepagemodifiedglobal_field/seodeleted
Tech lead · Contentstack platform02

Making branch merges explainable: per-item merge job details

Users merging content branches couldn't see what a merge actually changed, so they exported entire branches via CLI to diff them. I led the design that adds a per-item breakdown to the merge job API.

Per-item visibility: added / modified / deleted, strategy and status
POST /branches environments: ["development","staging"]main3 envsfeature-x2 envsdevelopmentstagingproduction// omitted → clone all (backward compatible)
Tech lead · Contentstack platform03

Branch creation API: controlled environment cloning

Creating a branch cloned every environment's publish configuration, whether you wanted it or not. I worked on an explicit, validated control that's still backward compatible.

Explicit control: clone all, none, or a chosen list
$ cms setupagentRAG60+services configured
Tech lead · builder04

AI-augmented engineering: setup agent, RAG knowledge app and LLM migration tooling

Three AI builds that removed real friction: a Claude-driven local setup agent for 60+ microservices, a RAG app over internal engineering docs, and an LLM pipeline that turns a legacy website into a CMS import package.

Local environment for 60+ services provisioned by typing "cms setup"

// 02 · careerExperience

Oct 2021 – Aug 2026
Senior Technical Lead
Contentstack

Led core multi-tenant SaaS platform capabilities — Taxonomy RBAC, Variants and Branches Env — from HLD/LLD through release and production support, for 500+ enterprise tenants.

Node.js · TypeScript · MongoDB · Kafka · Kubernetes · AWS
Mar 2018 – Oct 2021
Senior Software Engineer II, Technical Solutions
Raw Engineering

Moved deliberately from project management back into hands-on engineering: end-to-end CMS and platform solutions for enterprise clients; led a team of 3.

Node.js · React · Next.js · MongoDB · REST
Jun 2014 – Feb 2018
Application Project Manager
DNEG

Led a team of 8 engineers delivering application programs for a global VFX studio, and streamlined release processes to shorten project cycles.

ASP.NET · C# · SQL Server · MySQL · PHP
Dec 2011 – Jun 2014
Application Developer
Prime Focus World

Built and maintained internal applications supporting VFX production pipelines.

ASP.NET · C# · SQL Server · MySQL
Jun 2010 – Dec 2011
Senior Software Engineer
Zobble Solutions

Built enterprise web applications, including reusable reporting frameworks that stayed in use long after the projects wrapped up.

ASP.NET · C# · SQL Server
Jul 2009 – Jun 2010
Software Engineer
Ascentech

Delivered 8+ production applications, including INS Shivalik (Indian Navy) and the ICICI Prudential mock test platform.

ASP.NET · C# · SQL Server

// 03 · skillsExpertise

Architecture
HLD / LLDAPI-first & versioningMulti-tenant SaaSEvent-drivenMicroservicesRBAC & authorization
Backend
Node.jsTypeScriptExpress / NestJSREST / GraphQL / gRPCReact / Next.jsPython
Data
MongoDBRedisElasticsearchSQL ServerMySQLOracle
.NET (previous stack)
ASP.NETC#SQL ServerMySQLPHP
Cloud & DevOps
AWSAzureGCPDockerKubernetesKafka / RabbitMQGitHub Actions
AI Engineering
Claude / Claude CodeCursorRAG & PineconeAgents & MCPOllama
Leadership
Team of 8MentoringHiring (50+ interviews)Code & design reviewAgile / Scrum

// 04 · writingLatest post

all posts →

API Series, Part 2: Why MCP when we already have APIs?

MCP doesn't replace APIs. APIs are built for applications; MCP gives AI agents a standard way to discover tools, resources, prompts and existing services. Application → API, AI agent → MCP → APIs / tools / data.

#apis #mcp #ai-architecture #system-design

// 05 · learning in publicKnowledge hub

open the hub →
// visual cheatsheetsall 19