Engineering manager interview questions and how to answer them
Questions on the skills open engineering manager listings mention and on the core work of the role. For each: what the interviewer is checking, and a STAR answer outline with placeholders for your own example.
Based on 294 open engineering manager listings on ROLIVA as of . Each question below is about a term from ROLIVA’s skills vocabulary that appears in at least two of these listings, most-mentioned first.
01 Walk me through a Java service or component you worked on. What design decision are you most and least happy with?
Why this question: Java is mentioned in 89 of 294 listings.
What the interviewer is checking. Whether you can explain design trade-offs in a typed, object-oriented codebase and reflect honestly on your own decisions.
Answer outline (STAR)
Situation.[The system and your part in it].
Task.[The requirement or problem that shaped the design].
Action.[The decision you made, the alternatives you considered, and how you tested it].
Result.[How the design held up in production, and what you would change]. If there is no number you can support, say what changed as a result or what you learned.
02 Describe something you built or ran on AWS. Which services did you choose, and what went wrong at some point?
Why this question: AWS is mentioned in 76 of 294 listings.
What the interviewer is checking. Whether you understand the trade-offs behind the services you used, including security, cost and failure modes, rather than just naming them.
Answer outline (STAR)
Situation.[The system and what it did, e.g. an API, a data pipeline or a batch job].
Task.[Your part in building or operating it].
Action.[The services you used and why, how you handled permissions and cost, and how you dealt with the failure].
Result.[How the system ran afterwards and what you changed to prevent a repeat]. If there is no number you can support, say what changed as a result or what you learned.
03 Tell me about a stakeholder who disagreed with you or your team. How did you handle it?
Why this question: Stakeholder management is mentioned in 57 of 294 listings.
What the interviewer is checking. Whether you can understand another person’s interests, disagree constructively, and reach a decision without damaging the relationship.
Answer outline (STAR)
Situation.[The stakeholder’s role, what they wanted and why it conflicted with the plan].
Task.[What you were responsible for deciding or delivering].
Action.[How you understood their concern, the options you put forward, and how the decision was made].
Result.[The outcome and the state of the relationship afterwards]. If there is no number you can support, say what changed as a result or what you learned.
04 Tell me about a problem you diagnosed in a Kubernetes environment. How did you find the cause?
Why this question: Kubernetes is mentioned in 43 of 294 listings.
What the interviewer is checking. Whether you understand how workloads actually run (pods, resources, probes, networking) and can debug methodically under pressure.
Answer outline (STAR)
Situation.[The service and the symptom, e.g. restarts, failed deployments or slow responses].
Task.[Your role: on call, owner of the service, or helping another team].
Action.[The steps you took, e.g. events, logs, resource limits or probe settings, and the fix].
Result.[How the service behaved afterwards and what you changed to catch it earlier]. If there is no number you can support, say what changed as a result or what you learned.
05 Walk me through work you did on Azure. How did you handle identity, access and environments?
Why this question: Azure is mentioned in 38 of 294 listings.
What the interviewer is checking. Whether you can work safely in a cloud platform: least-privilege access, separate environments, and repeatable deployment instead of manual changes.
Answer outline (STAR)
Situation.[The system or migration and the Azure services involved].
Task.[What you were responsible for and the constraint, e.g. a compliance requirement].
Action.[How you set up access, environments and deployment, and any problem you solved along the way].
Result.[The result, e.g. a successful migration or fewer manual changes]. If there is no number you can support, say what changed as a result or what you learned.
06 Tell me about a machine learning model you worked on that was used for a real decision. How did you know it was good enough?
Why this question: Machine learning is mentioned in 38 of 294 listings.
What the interviewer is checking. Whether you frame the problem, choose a baseline and metrics that match the decision, and check for leakage and drift rather than reporting a single score.
Answer outline (STAR)
Situation.[The decision the model supported and the data available].
Task.[Your part: framing, features, modelling, evaluation or deployment].
Action.[The baseline, the model, how you evaluated it, e.g. a held-out set or an online test, and the risks you checked].
Result.[How it was used and how it performed after release]. If there is no number you can support, say what changed as a result or what you learned.
07 Tell me about something you built or automated in Python that other people relied on. What would you do differently now?
Why this question: Python is mentioned in 38 of 294 listings.
What the interviewer is checking. Whether you write Python that works beyond your own laptop: structure, error handling, tests or checks, and whether you can judge your earlier work honestly.
Answer outline (STAR)
Situation.[The task or problem, and who depended on the script, notebook or service].
Task.[What it had to do and any constraint, e.g. data size, run frequency or a deadline].
Action.[The approach and libraries you used, how you handled failures or bad input, and how you tested it].
Result.[What it replaced or made possible, and the one thing you would change today]. If there is no number you can support, say what changed as a result or what you learned.
08 Tell me about a time an Agile way of working was not helping your team. What did you change?
Why this question: Agile is mentioned in 31 of 294 listings.
What the interviewer is checking. Whether you understand the purpose behind Agile practices and adapt them to the team, rather than following ceremonies for their own sake.
Answer outline (STAR)
Situation.[The team and the practice that was not working, e.g. planning that never matched delivery].
Task.[What you were responsible for or chose to take on].
Action.[What you noticed, what you proposed, and how the team agreed to try it].
Result.[What changed in delivery or in how the team worked]. If there is no number you can support, say what changed as a result or what you learned.
Questions about the core work of a engineering manager
These follow from the work the role title describes, not from a count of listings.
09 Tell me about a time you managed an engineer whose performance was not meeting expectations.
What the interviewer is checking. Whether you give clear, early, specific feedback, look for causes you can address, document fairly, and follow through on the outcome without avoiding the hard conversation.
Answer outline (STAR)
Situation. Describe [the situation in general terms], without identifying the person.
Task. Explain [your responsibility as their manager and what expectations were not met].
Action. Walk through [how you raised it], [the support and clear goals you set], [how you checked progress], and [who else you involved, such as HR].
Result. State [the outcome: improvement, role change or exit], only as far as you can share it, and [what you would do earlier next time].
10 How have you balanced delivering roadmap work with paying down technical debt?
What the interviewer is checking. Whether you can argue for engineering health in business terms, make trade-offs explicit with product partners, and avoid both endless refactoring and neglect.
Answer outline (STAR)
Situation. Describe [the system and the debt, e.g. slow deploys or a fragile component] and [the roadmap pressure].
Task. Explain [what you were accountable for: delivery dates, reliability or both].
Action. Walk through [how you sized the cost of the debt], [how you agreed capacity with product], and [how you tracked it].
Result. Give [a result you can support, e.g. deploy frequency or incidents before and after]. If unmeasured, say [what the team could do afterwards].
11 Describe a hiring decision you got wrong, or nearly got wrong. What did you change in how you hire?
What the interviewer is checking. Self-awareness and process improvement: whether you can analyse a hiring miss without blaming the candidate, and make your process fairer and more predictive.
Answer outline (STAR)
Situation. Describe [the role you were hiring for] and [what went wrong or nearly did].
Task. Explain [your part in the decision].
Action. Walk through [what you found the process had missed], and [the change you made: structured questions, a work sample, a different panel].
Result. State [what changed afterwards, if you can support it]. If it is too early to tell, say [how you will know].
12 Tell me about a conflict between two people or two teams that you had to resolve.
What the interviewer is checking. Whether you listen to both sides, separate the people from the technical disagreement, help the group reach a decision, and make sure it sticks.
Answer outline (STAR)
Situation. Describe [the disagreement and its effect on the work], without naming people.
Task. Explain [your role: their manager, a peer manager or a mediator].
Action. Walk through [how you understood each side], [how you framed the decision and its criteria], and [how the decision was made and communicated].
Result. Give [the outcome you can support] and [what you did to stop the same conflict returning].
Using the outlines
One real example per answer. Replace every [bracketed] part with something you did and can talk about in detail.
Keep the situation short. Spend most of the answer on what you did and why.
Say “I” for your part. Name the team’s work as the team’s, and your own decisions as yours.
Results you can support. If there is no number, say what changed or what you learned. Never estimate a figure you cannot back up.
How these questions are chosen
Each open engineering manager listing’s description and stated skills are checked, on whole words, against the fixed skills vocabulary ROLIVA uses on its job pages, resume examples and monthly skills reports. A listing counts once per term. A mention is not a requirement, and the counts change as employers open and close roles. The questions and outlines are preparation prompts written for this role. They are not a record of what any employer has asked, and no employer’s process is described here.
Interview Studio prepares questions and STAR outlines for a real job from its description and the experience you have confirmed. No generative AI: when a detail is missing, it asks you instead of inventing one.