Katkat
Back

Resume Project Deep Dive: Tech Stack Choices, Trade-offs, Business Logic and Ownership

AmazonSoftware Engineer · Technical Screen
MediumSoftware EngineerTechnical ScreenBehavioral & Leadership

Last updated

Walk an interviewer through a project from your resume, explaining why the team chose its technology stack, which trade-offs those choices carried, how the business logic works, and exactly which part you owned. It tests depth of understanding, honest ownership boundaries and consistency under repeated probing.

The first 20 minutes of an SDE II phone screen went to a deep dive on a project from the candidate's resume, followed by two leadership-principle behavioral questions that the candidate did not record. This entry covers the project deep dive.

Pick one substantial project from your resume and walk the interviewer through it. Over the conversation you will be asked:

  • why the project uses the technology stack it does,
  • what trade-offs those technology choices involved,
  • how the business logic of the system works, and
  • exactly which part of the project you were personally responsible for.

Because this is a deep dive rather than a summary, expect each answer to be followed by "why?" or "what would have happened if you had done it differently?".

The same deep dive can also be run as a leadership round. In that version a bar raiser opens with a long introduction, then asks every question about the project as a leadership question (what you owned, a detail you had to dig into, a call you made with incomplete information, what you learned), interrupts often for more technical depth, and maps your answers to Amazon's Leadership Principles.

Clarifying Questions

  • Would you like the most recent project, or the one most relevant to this team?
  • Should the business logic be explained as the domain rules, or down to the code paths that implement them?
  • Would you prefer a short overview first and then choose where to go deep, or a walk through each area in order?

Hints

Hint 1

Pick a project you can defend line by line: Choose a project where you took part in the technology decisions and can explain the business rules in detail, even if another project on your resume sounds more impressive.

Hint 2

Separate "we" from "I" before the interview: Write down which components, decisions and incidents were yours alone, and where your part handed off to someone else, so the boundary comes out clearly when you are asked.

Follow-up questions

  • If you started this project today, which technology choice would you change, and why?
  • Which business rule was hardest to get right, and how did you find out that the first version was wrong?
  • Which part of the project that you did not own caused you the most trouble, and how did you handle that dependency?
  • What did the project measurably improve, and how was that measured?
  • Knowing what you know now, what would you do differently on this project beyond the technology? What did you learn from it, and in which later project have you applied that lesson?