Available for senior engineering roles
Ankit Patra.
I build work that ships.
Full-stack engineer
Senior full-stack engineer working on AI-powered systems, scalable cloud-native architectures, and motion-driven interfaces with React, Next.js, and TypeScript.
About
I think like a systems engineer and ship like a product designer.
6+ years across full-stack product engineering — from event-driven AI pipelines and serverless cloud architectures to design-systems, motion-rich interfaces, and Backend-for-Frontend patterns. I plan before I implement, prefer scalable boring tech to clever single-use code, and treat motion as part of the product, not decoration.
Senior Software Engineer · DocMind · One Convergence Devices
Building a scalable document-intelligence platform on Kubernetes microservices with an event-driven AWS pipeline (S3 → Lambda → Redis → workers).
Senior Software Engineer · Kasu.AI · One Convergence Devices
BFF on Next.js, real-time exception handling, CoPilotKit assistant. Cut AP approval cycle from 1–3 days to under 30 minutes.
Senior Software Engineer · DkubeX · One Convergence Devices
Re-architected MLOps platform UI for LLM/embedding deployment. Established Storybook, Jest + RTL, Tanstack Form + Zod foundations.
Senior Software Engineer · Rargus · One Convergence Devices
AppSync GraphQL over DynamoDB powering a typed React UI. Cognito auth, Lambda + API Gateway serverless, Fargate jobs.
Business Analyst (Frontend Engineering) · Deloitte Consulting India
Browser-based conversational agent (React + Node + Dialogflow) for US-hospital AR workflows. Later: React + .NET features at Deloitte App Studios.
B.Tech, Computer Science · VSSUT Burla
CGPA 8.36.
Work
Projects that shipped and mattered.
Four case studies from production — architecture decisions, tradeoffs, and what actually moved the needle.
Process
How I build with AI
Cursor and Claude Code are force multipliers — not replacements for engineering judgment. The leverage comes from knowing exactly where to apply them.
Write the spec before writing the prompt. If you can't describe the behavior in prose, the model can't implement it correctly.
Use AI for the first draft, your judgment for the second. Generated code needs the same architectural review as any other code.
Iterate in conversation, not in commits. Architecture decisions are cheaper to refine in a planning session than in a PR.
Know when to override. AI optimizes for plausibility. You optimize for correctness in your specific system — trust that.
Reading spec… ✓
Analyzing existing patterns… ✓
Writing lib/auth.ts… ✓
Done. 3 files modified.
Planning before prompting. Specs before code.
Principles
Engineering philosophy.
Six things I've found consistently true across every codebase I've worked in.
Plan before you code
Architecture decisions are cheaper in prose than in PRs. A 20-minute planning doc prevents a week of refactoring.
Maintainability over cleverness
The next engineer should understand it without you in the room. Clever is a liability; clear is an asset.
Event-driven where it counts
Decouple producers from consumers. When a system can scale its parts independently, it scales at all.
Product thinking
Every technical decision has a UX consequence. Engineering without product context is just expensive puzzle-solving.
Boring is good
Proven patterns over novel abstractions. The interesting part of the job is the problem, not the framework.
Observability first
If you can't measure it, you can't debug it in production. Tracing and structured logging are not optional.
Stack
Technologies I actually use in production.
No buzzword bingo. Every tool here has shipped something I'm comfortable being asked about in an architecture review.
Frontend
Backend & APIs
Cloud & Data
AI / ML Surface
Writing
Engineering articles.
Patterns, tradeoffs, and lessons from production — not tutorials.