How I work.

Six defaults I bring to every engagement, whatever the stack or the brief.

• 01

  Ship to production

  I optimise for software that runs, not slides that demo. Verifox, Vlon, and Prospetto are live products with real users — and that is the only bar that matters. A feature is not done until it is deployed, verified, and serving traffic.

• 02

  Own the full stack

  Frontend, API, database, auth, and deploy are one continuous problem, and I hold all of it. No throwing work over a wall, no gaps between layers where bugs hide. You get one person accountable from the schema to the pixel.

• 03

  Measure the outcome

  Adjectives are cheap; numbers are not. Sub-50ms API responses, 98.7% verification accuracy, 200M+ records served. I instrument what I build so we can both see whether it actually worked.

• 04

  Lead, don't just code

  As project lead on a 5-engineer team I scope the work, review the code, and ship alongside the team. I am comfortable owning the plan and the outcome, not just the tickets assigned to me.

• 05

  Build for scale

  Large-scale crawlers across 600+ sources, pipelines moving millions of records, AI features under real load. I design for the volume the product will actually hit, not the happy-path demo.

• 06

  Reliability first

  Edge cases, validation, error states, and tests are part of the job, not an afterthought. 60-character names, messy data, offline states, and 500s all get handled — so the thing holds up long after launch day.

Five steps from first conversation to a system you own — no black boxes in between.

1. 01

   Discovery

   Before any code, I get clear on the real problem, who it serves, and the constraints. A short, direct conversation beats a long brief — I ask the questions that change the build.

2. 02

   Scope & plan

   I break the work into milestones with a clear definition of done for each, flag the risky parts early, and agree on what ships first. You always know what is coming and when.

3. 03

   Build in the open

   I work in small, reviewable increments with frequent check-ins, not a three-week black box. You see progress on a real URL as it happens and can steer before things harden.

4. 04

   Ship & verify

   Deploy to production, test the real flows, watch the metrics. Shipping is a step in the process, not the finish line — I confirm it works for real users before calling it done.

5. 05

   Iterate & hand off

   Measure what shipped, pay down any drift, and document the system so the next person — including future you — can pick it up without me in the room.

• Communication

  Direct and low-noise. I tell you what is going well and what is not, with a reason. No status theatre, no surprises near a deadline.

• Cadence

  Frequent, lightweight updates on a real URL over long written reports. You can check progress any time, not just at milestones.

• Tools

  GitHub for the work, your channel of choice for the conversation (Slack, email, or call). I adapt to how your team already operates.

• Availability

  Based in Gurgaon, IN (UTC+5:30). Usually a reply within 48 hours, and I overlap with both EU and US mornings for live calls.