Developer recruiter questions: prepare your answers

Start with one shipped project

Choose a project you can explain without revealing confidential information. Write down who used it and which problem it addressed. Separate what reached production from prototypes, proposals, and work still in progress.

Then answer: “What did you personally build?” Name the components you owned, the decisions you made, and your collaborators’ responsibilities. “We shipped a scheduling system” describes a team outcome. “I built its Node.js API and reviewed database migrations” describes your contribution.

Add one technical trade-off: the options, the constraint, and why you chose your approach. List technologies you used directly separately from technologies another team managed. A stack list alone cannot explain your depth of experience.

Keep evidence beside each outcome

Record the baseline, measurement period, and source for any performance or business result you mention. Label team-wide results as team results. Do not turn a correlation into a claim that your change caused the outcome.

If nobody measured the impact, say so. You can still explain what shipped, how you tested it, and what feedback you received. Keep customer names, internal dashboards, credentials, and proprietary code out of anything you share publicly.

Amazon’s interview guide recommends specific situations, personal actions, results, and lessons. Use that structure to organize facts, not to manufacture an impressive number.

Prepare the practical follow-ups

These notes belong beside your project explanation. You can keep sensitive answers private or leave them unanswered.

• Job moves: Why did you leave, and what are you looking for now? Keep the explanation factual and professional.
• Next role: Which engineering problems, responsibilities, or team environments do you want? Distinguish preferences from requirements.
• Availability: What start date can you actually commit to? Mention a notice period only if it applies.
• Location: What remote, hybrid, on-site, or relocation arrangements would you consider? Do not publish your home address.
• Salary: Choose a range with currency and pay period, “open to discuss,” or no public salary answer.
• Limits: What have you not done, cannot verify, or cannot disclose? A clear limit is better than an unsupported answer.

Check the answers before sharing

Read your notes as someone who has never met you. Can they distinguish your contribution from your team’s work? Is each result supported? Are your job dates consistent with your resume?

Ask a colleague to flag unclear language, without sending confidential project material. When a question needs missing information, write “I haven’t provided that answer yet.” Add the fact only when you can verify it.

You can use this checklist with a plain resume or portfolio today. It does not require a chatbot or promise interviews.