The scouting report
This is how your resume reads from the other side of the table, in the ninety seconds before your name gets called. Every one of the eight attacks below will surface somewhere across your loop, and each has a good answer — if you prepare it now instead of inventing it in the room.
You own things end to end
"Technical owner of 4 client applications in production" is the line that gets you the interview. Most six-year candidates have owned features; you have owned releases. Lead with it.
Your stack is the hiring sweet spot
TypeScript on both ends, Next.js App Router, NestJS, Redis, Docker, GitHub Actions — in production, not in tutorials. That combination is in demand right now.
Every bullet has a number
Reads as an engineer who measures. It also creates attack 1 below.
You have set standards for others
Authoring the frontend and API standards, code review, mentoring. That is the difference between senior as a title and senior as a behaviour.
Forty percent fewer runtime errors. Thirty-five percent faster pages. Twenty-five percent infra saving. I will pick one at random and ask exactly how you measured it, over what window, and against what baseline. If you cannot answer that, every other number on the page turns from a fact into a claim — including the ones you can defend.
Prepare all ten. They are listed in R10.
Five thousand registered users and ten thousand monthly visitors is a small system. If I am hiring for traffic, I want to know whether you can think about ten times or a hundred times that.
The answer is not to inflate it. It is to be precise about what you have done — depth on delivery, reliability and architecture ownership — and then demonstrate in R8 that you can reason about scale you have not met. Those are different skills and interviewers know it.
No message queue, no background job system, no event bus anywhere on the page. Six NestJS services communicating with no async messaging means either tight HTTP coupling or something missing from the story.
The full answer is R5.4. Learn its shape: name the trade-off honestly, give the specific trigger that would change the decision, name the tool and why that tool.
"Structured logging" is where your monitoring story ends. No metrics, no tracing, no alerting, no error-tracking tool named. For someone who claims to own reliability after launch, that is the biggest genuine hole on the page.
Own it in the room: logs today, and here is the order I would add things — error tracking first, then p95 latency and error rate with alerts, then tracing last because it costs the most to instrument. That sequencing is the senior answer.
EC2, S3, IAM. No RDS, no ECS or EKS, no Lambda, no CloudFront, no load balancer, no auto-scaling group. It reads like a few VMs with Docker on them — which is completely fine, but say so before they work it out. R9.1 has the wording.
Jest appears under Prototion, five years ago, and nowhere in your two most recent roles — the ones where you own architecture. I will ask what your coverage looks like on the six services you designed.
Have a real answer. If the coverage is thin, say what is covered (the domain logic, the validation) and what is not (e2e), and what you would do first with a week.
Three roles, all client-delivery shops. The doubt is whether you can iterate on a single product, own its debt, and care about retention rather than handover.
Your "why leaving" answer in R1.2 is built to defuse exactly this — it names handover as the limitation and turns it into the reason you want their job. Use it early, before they form the doubt.
You are listed as Roorkee-based and remote. Every interviewer will quietly wonder.
Two resume edits to make tonight. First: change Roorkee, India · Open to relocation to Bangalore, India (relocated Sept 2026). You are physically there — say it in the past tense. This single edit measurably increases walk-in callbacks. Second: add one observability and one testing token to your skills line if they are true — Sentry, Winston, Supertest, e2e. If they are not true, spend one evening making one of them true on a side project so you can speak about it honestly.
Do not defend the gaps. Convert them into decisions.
"We did not add a queue" is a weakness. "At five thousand users with a p95 under two hundred milliseconds, a queue would have been infrastructure we had to operate for no measurable gain — the point where I would add one is when notification sends started blocking the request path" is an architect talking.
The gap is identical. The candidate is not.
Service & consulting walk-in same day · 3–5 hours
Two hundred people in a hall, a token number, a lot of waiting. Resume shortlist (2 min) → Technical 1, rapid-fire breadth (30–40 min) → Technical 2, projects and a light design question (40–60 min) → HR fitment (15 min).
How you win: answer fast and confidently, never say "I have not used that" without immediately saying what you used instead, have your notice period and joining date ready. The failure mode is over-explaining — they have ninety candidates left to see.
Series A–C product startup 5–10 days · 4–5 rounds
Recruiter screen (20 min) → Machine coding (90–120 min) → Technical deep dive (60 min) → System design (60 min) → Hiring manager (45 min) → HR close.
How you win: the machine coding round decides it and everything after is confirmation. Practise building a small CRUD feature with clean module separation in ninety minutes until it is boring.
Mid-size product & SaaS 2–3 weeks · 5 rounds
Online assessment (2 DSA problems) → DSA interview (60 min) → Frontend or backend deep dive (60 min) → System design with a real bar (60 min) → Manager and values, often scored against a written rubric.
How you win: do not walk into these cold. Give yourself the seven days first, spent mostly on DSA and design.
Agency & product studio 2–4 days · 2–3 rounds
Technical plus portfolio walkthrough (60 min) → take-home or pairing (often waived if your GitHub is convincing) → founder chat (30 min).
How you win: your client-ownership story is their exact pain. Talk about delivery, estimation and client communication more than about code — and push hard for fully fixed pay.