Senior Staff Infra Hiring Manager Screen: Career Arc, Reasons for Leaving, Team Fit

This is a hiring manager conversation for a senior staff backend infrastructure engineering role. It is mostly behavioral and covers three things: a walk through your career over roughly the last ten years with a closer look at the most recent few, why you want to leave your current job, and how your experience maps to the technical challenges the manager describes on their team. Prepare an answer for each part. ### Clarifying Questions - How much time does the manager want the career walkthrough to take, and should it be chronological or organized around themes? - Does the manager want depth on one recent project or breadth across the whole period? - Of the challenges the manager describes, which are the most urgent for the team right now? ### Part 1 — Walk through the last ten years Summarize what you have done over roughly the past decade, then go deeper on the last few years: what you owned, the scale you worked at, and the decisions that were yours. ```hint Pick the through-line Ten years does not fit into ten minutes. Decide what single story about your growth the walkthrough should tell before choosing which roles get airtime. ``` #### What This Part Should Cover - A clear arc showing how scope and ownership grew to staff-level impact - Concrete technical depth in the recent years: systems owned, their scale, and your own decisions - Time discipline: brief on older roles, detailed on recent ones ### Part 2 — Why are you leaving? Explain why you want to leave your current role and why this team is the move you want to make. ```hint Pull, not push Think about what the new role offers that your current one structurally cannot, rather than what is wrong with your current employer. ``` #### What This Part Should Cover - A motivation framed around what you are moving toward - Honesty without disparaging your current employer or team - A link between that motivation and this specific role ### Part 3 — Map your experience to the team's challenges The manager describes the technical challenges the team faces, and they turn out to be close to what you work on now. Explain how your experience applies, where it does not, and what you would do first if you joined. ```hint Listen before you match Restate the challenge in your own words and check that you understood it before claiming you have solved it before. ``` #### What This Part Should Cover - Specific past work tied to specific challenges, with outcomes - An honest account of how your past context differs from theirs - A credible plan for the first months that starts with learning their system ### What a Strong Answer Covers - Staff-level signals throughout: scope across teams, setting technical direction, and influence without authority - Specific, checkable detail (systems, scale, results) instead of adjectives - Consistency between the career story, the reason for leaving, and the fit argument - Good questions back to the manager about the team's priorities and how success is measured ### Follow-up Questions - Which decision from the last few years would you make differently now, and what did it cost? - Describe a time you set technical direction for engineers who did not report to you. How did you get agreement? - If, after you join, the team's biggest challenge turns out to be different from what you expected, what do you do in the first month?