Rebuilt two portals
InsideBCG and the Survey portal, rebuilt in React and Next.js and connected to Outlook, Slack and a central People API running on Go microservices and AWS Lambda.
React, Next.js, Go, AWS Lambda
Fade in:
Naman Bhatt in
The wholeproduct.
A software engineer's story in six reels: backend, web, mobile and real-time systems, told from the beginning.
Download résumé
Scroll at your own pace, or press K to play and pause.
This is how I went from studying machines to owning every layer of a product: the database, the API, the web app, the phone in your pocket, and the tests that keep all of it honest.
Reel 1
Int. Delhi Technological University — 2020
The wrong degree
I enrolled to study machines. But all around me, my seniors were building websites, and they started showing me how you make things on the web. It was a lot more interesting than nuts and bolts.
The first real thing I built was a registration portal, with those same seniors. I learned what I needed from YouTube and took on the front end. Then came freelance projects, and with them my first money from code.
- Drawn by
- Naman Bhatt
- Degree
- B.Tech, Mechanical Engineering
- School
- Delhi Technological University
- Years
- 2020 – 2024
- CGPA
- 8.00
- Sheet
- 1 of 6
On paper it was the wrong degree.
It wasn't.
Code let me help people and help myself, and be creative instead of fixing machines or worrying about placements. It gave me freedom. It still does.
Reel 2
Int. Three internships, still in college — 2023
Side quests
Before I graduated I'd already shipped software real people relied on, for three very different businesses. Each one taught me a layer.
Reel 3
Int. Boston Consulting Group — 2024
The big machine
Junior Software EngineerJul 2024 – Jul 2025
My first full-time role put me inside a global firm, building the sites, portals and AI tooling its consultants use every day. When your software serves seventy offices, you learn to be careful.
Sitecore XM Cloud
One platform, about seventy offices.
Twenty-plus micro-sites, each maintained on its own.
One managed content platform, serving about seventy offices.
- micro-sites migrated to Sitecore XM Cloud
- 20+
- BCG offices served by those sites
- ~70
- lift in portal adoption
- 15%
- less manual post-migration work
- 50%
The moment I'm proudest of
Presenting my team's quarter at BCG's annual internal meet. We'd hit a big migration target inside a tight window, and the room applauded. Part of the reason was my PowerShell automation, running across five or six repositories: it took the manual cleanup off people's plates, so they could be put on more valuable work.
AI Portal components
AI-assisted components for BCG's internal AI Portal, wiring LLM APIs into real-time content generation and personalisation.
LLM APIs, React, TypeScript
Kept the migration honest
Selenium and Cucumber regression coverage over every migrated site, PowerShell automation for the cleanup, and more than thirty production issues resolved along the way.
Selenium, Cucumber, PowerShell
Two product rotations
A month each embedded with two internal AI product teams, NAVI and Findability, learning how they scoped, tested and shipped AI features.
Reel 4
Int. Edock, a small product team — 2025
The whole thing
Senior Software Engineer, DecodesSoftware Architect, EdockSep 2025 – 2026
Then I joined Decodes as a senior software engineer and was assigned to Edock as its software architect: a product small enough that one engineer could own all of it. So I did.
Edock was an ed-tech product.
It became an event-first community platform.
The product changed direction while I was there, and every layer of the codebase had to change with it.
Six repositories, one owner
- Schema
- Backend
- Web
- Mobile
- Admin
- Tests and deploy
~48%
of every pull request the organisation opened in eleven months was mine: 200 of 412.
I also wrote the platform's architecture and onboarding guide, so the next engineer doesn't need me in the room.
Ticketing and payments
Bringing ticketing on-platform gave Edock its first revenue path. Money is where optimism goes to die, so the design assumes everything goes wrong: two buyers race for the last seat, a webhook arrives twice, a buyer walks away mid-checkout.
Node.js, PostgreSQL, Prisma, Razorpay, Redis
Pick a scenario to walk through it.
- A buyer opens checkout for an event.
- A payment attempt is created with a TTL, so it can't stay open forever.
- Razorpay confirms the payment through a webhook.
- Inside one database transaction, remaining capacity is checked again.
- There's still room, so the ticket is confirmed.
Simplified model of the production flow.
Now try to break it
One seat left. Send three buyers for it at the same moment, replay a payment webhook, then switch the safeguards off and try again.
- Buyer AWaiting
- Buyer BWaiting
- Buyer CWaiting
- Never sell more seats than exist
- Holding0 of 1 seat sold
- One outcome per payment
- HoldingEvery payment settled once
- Server log. Send the buyers to start.
Testing as a merge gate
127tests failing
I inherited a suite with 127 failing tests across 72 files. People had learned to ignore it.
I repaired it without changing product behaviour and split CI into critical and normal tiers. Now 3,800+ tests run green on every merge.
Each square is a test file; each dot, a failing test.
Along the way I closed XSS, SSRF and auth-gating gaps, and blocked a migration that would have dropped three live production columns.
Flutter app, iOS and Android
From first commit through TestFlight to the stores: chat parity with web, push that deep-links to the right screen, a share extension, Apple and Google sign-in, and guest mode, shipped behind seven CI workflows with fastlane match signing.
Flutter, Dart, FCM / APNs, fastlane, GitHub Actions
Events and community
Bookings, threaded event chat, WebRTC voice, read state synced across devices, and Vault, one home for event photos that used to scatter across WhatsApp and Drive. Private communities laid the groundwork for a B2B offering.
Socket.IO, WebRTC, React, Next.js, AWS S3
Beyond the code
Not all of it was code. I worked with clients directly: onboarding them, and helping them find collaborators for their events. I brought in stakeholders and investors, and worked as the product's growth person too, gathering a lot of its early adopters and users.
Reel 5
Ext. Nights and weekends — 2025 – 2026
Nights and weekends
Freelance builds alongside my full-time roles, each one live in production. These are the ones I designed and built myself.
Adonai Reserve
Fashion e-commerce, 2026
Storefront for a monochrome streetwear label: a 3D monogram rendered in WebGL over a shader-driven smoke backdrop, an editorial catalogue served from its own product API, and cart through checkout.
Next.js, React Three Fiber, GLSL, Vercel
Design and full-stack build
adonaireserve.com (opens in a new tab)
Beelia
AI marketplace, 2026
Marketing site for a marketplace where people discover and subscribe to AI tools: separate journeys for users and creators, in English and Spanish. I also built the business and revenue models behind the launch.
Next.js, React, i18n
Landing pages, business and revenue models
beelia.ai (opens in a new tab)
Alora Vacations
Travel, 2025
Site for an India tour operator, built end to end: destinations, tour packages, services and an enquiry flow, with a video-led home page.
Next.js, React, Vercel
Design and full-stack build
aloravacations.com (opens in a new tab)
Reel 6
Int. Editing room — later
What stuck
Cut everything else and this is what's left.
Own the whole path.
I'd rather carry a feature across schema, API, web and mobile than hand it off at a boundary. Fewer handoffs means fewer places for a product decision to get lost.
Be paranoid where money moves.
Payments get transactions, state machines and idempotency keys, never optimism. Concurrent buyers, replayed webhooks and failed refunds are designed for up front.
Green is the only way to merge.
A red suite people have learned to ignore is worse than none. I fix it, tier it, and make passing tests the gate.
Write the system down.
An architecture guide means the next engineer doesn't need me in the room. I was the sole author of Edock's, along with its onboarding guide.
Written, directed and engineered by
Naman Bhatt
- Supporting cast
- DecodesBoston Consulting GroupJRD ConsultancyCrazy LearnersAlkras Online Services
- Featuring
- Adonai ReserveBeeliaAlora Vacations
- Languages
- TypeScriptJavaScriptDartSQL
- Frontend and mobile
- ReactNext.jsReduxTailwind CSSFlutter for iOS and Android
- Backend and cloud
- Node.jsExpressPrismaPostgreSQLRedisAWS: EC2, S3, RDS, Lambda, Cognito, CloudFront, ECR, SES
- Real time and systems
- Socket.IO and WebSocketsWebRTCDockerGitHub Actionsfastlane
- Quality
- JestPlaywright
- Payments and messaging
- RazorpayFirebase (FCM and APNs)OpenAI API
- Motion and 3D
- GSAPthree.jsWebGL shaders
- Education
- Delhi Technological UniversityB.Tech, Mechanical Engineering
- Off screen
- Music producer, seven years and countingAn album in progress
- Favourite film
- War Dogs
- Filmed on location in
- New Delhi, India
- This site
- Next.js, GSAP, Lenis and three.jsScore synthesised live with the Web Audio API
To be continued.
The next chapter is a senior engineering role on a team that wants the whole product built well. If that's your team, or you need a product built end to end, I'd like to hear about it.
Your ticket
Every screening comes with a stub. This one's yours to keep. Turn it over for the fine print.
Admit one
The Whole Product.
Starring Naman Bhatt
- Audience
- –
- Date
- –
- Showtime
- –
- Seat
- –
- Watched
- –
- Ticket
- –
Redeemable for one conversation: namanbhatt.dev@gmail.com
–