Run a mock round

Show that you have done homework and connect it to your goals. A strong answer has three parts:

1. Something specific about the company: product, engineering culture, recent launch, tech stack or mission.
2. How that matches your strengths and interests.
3. What you hope to contribute and learn.

Example: "Your team rewrote the checkout flow to handle flash sales without downtime, which is exactly the scale and reliability problem I enjoy. I have spent the last two years making our own payment service resilient under load, and I would like to bring that experience while learning your event-driven architecture."

Avoid generic praise, salary-only reasons, or saying you need any job. Reference concrete details you found in research.

Own it fully and show the learning. Use STAR but with the emphasis on accountability and change.

Example: "I shipped a database migration without a rollback plan and a missing index caused a slowdown during peak hours. I immediately opened an incident channel, reverted the change, and restored performance in 20 minutes. Afterwards I wrote the postmortem, added index checks to our review checklist, and made every migration dry-run in staging first. We have not had a repeat since."

What interviewers want: honesty, not blaming others, a concrete fix, and evidence the lesson persisted. Never claim you have never made a mistake.

Use a tight 60-90 second structure: Present, Past, Future.

• Present: your current role and the core value you deliver ("I am a full-stack engineer with four years building payment systems in a product team of eight").
• Past: two or three career highlights with concrete impact ("I led a migration to typed APIs that cut production incidents by 40%").
• Future: why this role and company are the logical next step ("I want to work on higher-scale systems, which is exactly what your platform team is doing").

Avoid a chronological life story, avoid personal trivia, and connect every sentence to the value you bring to the role. Practise out loud until it is natural, not memorised.

Show ambition that is compatible with the company and role.

Strong answer: "In the next year I want to fully own my area and hit measurable reliability and delivery goals. Within three years I would like to be a senior engineer who mentors others and leads a significant technical initiative. Longer term I am interested in staff engineer or tech lead track, deepening architecture skills while staying hands-on."

Key points:

• Ground it in depth and impact, not titles alone.
• Align with the company's likely growth path.
• Signal commitment and realistic expectations.
• Avoid clichés like "your CEO position" or a plan to leave and start a competing company.

Anchor on research, not on your current salary.

• Research the market range for the role, level and location (levels.fyi, Glassdoor, industry surveys, peers).
• Give a researched range rather than a single number: "Based on my research and four years in this stack, I am targeting 18-22 lakhs total, and I am open to the full package structure."
• If pushed before discussing scope, deflect politely: "I would rather understand the responsibilities first; if the role is a good fit, I am confident we can agree on a number."
• Consider total compensation: base, bonus, equity, benefits, flexibility and growth.
• Never inflate dishonestly; salary misrepresentation is easily verified and damages trust.

Be collaborative: state a range, justify it with value and market data, and show flexibility tied to the overall opportunity.