Hiring manager call: walk through your past work, interests and latest project

In a hiring-manager call that follows the technical screens, the manager asks you about three things: what you have built so far, what you are interested in working on, and the project you have worked on most recently. The manager then describes their own team. Prepare how you would answer each topic in a conversation where the manager can interrupt and dig into anything you say. ### Clarifying Questions - Does the manager want an overview of your whole career, or only of the most relevant roles? - How deep should the recent-project discussion go: architecture and trade-offs, or mainly the context and outcome? - If the most recent project is confidential, at what level of detail can you describe it? ### Part 1 — What you have built Give the manager an overview of the work you have done so far: the systems or products you built, what you personally owned, and what came of them. ```hint Pick a throughline Choose two or three pieces of work and the thread that links them, instead of walking through every job in order. ``` #### What This Part Should Cover - Scope and personal ownership for each piece of work - Concrete outcomes rather than lists of technologies - A narrative that connects the pieces and leads into your interests ### Part 2 — What you are interested in Explain what kinds of problems you want to work on next, and why. ```hint Ground it Tie each interest to something you have actually built, debugged or studied, so it reads as evidence rather than aspiration. ``` #### What This Part Should Cover - Specific problem areas rather than broad trends - Evidence from your own work that the interest is real - How the interest relates to the kind of work the role involves ### Part 3 — Your most recent project Walk the manager through the project you worked on most recently: the problem, your role, the key technical decisions, the outcome, and what you would do differently. ```hint Decisions, not tasks Organize the story around two or three decisions you made and the alternatives you rejected, and expect the manager to pick one and keep asking why. ``` #### What This Part Should Cover - The problem and why it mattered, stated briefly - Your contribution, separated from the team's - Technical decisions, their trade-offs, and the evidence behind them - The measured or observed outcome, and an honest lesson ### What a Strong Answer Covers - A concise structure that leaves the manager time to ask questions and describe the team - Consistent separation of "I" from "we" across all three topics - Technical depth on the recent project that holds up under several rounds of "why" - Interests that are specific, evidenced, and connected to the team the manager describes - Specific questions back to the manager about the team's work ### Follow-up Questions - What was the hardest trade-off in that project, and what new information would have changed your decision? - What went worse than planned in that project, and what did you do about it? - Now that I have described my team, which of your past projects is most relevant to it, and what would you want to know about our work?