Field Manual — On Building Whole ProductsVol. 01Bengaluru, INSession live
A feature on Himanshu Agarwal · Founding Engineer
whoami --human
I turn messy operations into software that runs.
I’m a product engineer for the ambiguous middle — sharp domains, half-known workflows, and systems that still have to be correct. I’ve taken an exam engine, GST/TDS billing, a pharma ERP bridge, payments, and commerce from ambiguity to production — most of it as the only engineer on the system.
Prevented double-payouts by treating gateway failures by certainty: release funds only on a provable failure; keep ambiguous transfers pending until webhook, status reconcile, or admin review resolves them.
02
Timed exam engine100,000+ attempts
Resumable timed attempts, server-authoritative scoring, section-wise analytics, and disconnect recovery across 100,000+ attempts.
03
AI question workflowdays → ~30 min
Versioned prompts, multi-provider fallback, and batch generation/review workflows cut exam creation from days to ~30 minutes.
Founding Engineer · Mar 2023 — present
Four production apps for AfterBoards and AfterGrad on one 17-package monorepo: product surfaces, payments, mobile releases, content operations, and production recovery paths owned by one engineer.
Money has to be exactly right — settlement is idempotent and reconciliation-safe, not best-effort.
The AI pipeline is a system, not a prompt — versioned, multi-provider, with automatic fallback.
One Turborepo codebase carries web + React Native across both products.
Next.jsReact NativeMongoDBRedisAI · 4 models
”
The useful work starts where the workflow is messy and business-critical — then turns into software people can depend on every day.
The differentiator — breadth × ship-rate × domain-correctness
Sole engineer of two live exam-prep products on one Turborepo: payouts, real-time multiplayer, timed attempts, AI question workflows, Redis resilience, and solo quality gates.