Skip to content

Lesson · Behavioral Interview Preparation

Behavioral interviews for first-line engineering managers

For people interviewing as a first-line engineering manager who leads one team of engineers. Covers feedback, performance, hiring, conflict, delivery and growing engineers, with original questions and worked examples.

13 chapters1 table

A first-line engineering manager leads one team of engineers who are individual contributors. Most of the job happens through other people: one-to-ones, feedback and performance conversations, hiring and onboarding, sorting out conflict on the team, and answering for what the team delivers and how it works with the product and business partners it serves. You may still review designs or write some code, but this Lesson is not about that. Your influence comes from the expectations you set, the decisions you make about people and priorities, and how you behave when either goes wrong.

Behavioral questions for this role tend to listen for specific actions with specific people: what you said, when you said it, what you wrote down and what happened next. Interviewers are usually checking that hard conversations were fair and clear, that you separated the person from the problem, that delivery trade-offs were visible to the people who had to make them, and that the team, not only you, came out better. This is an editorial summary of how behavioral questions are commonly used for first-line management roles, not a description of any particular company's process.

Two habits from individual-contributor interviews work against you here. The first is solving the problem yourself. A story in which the manager stepped in, wrote the fix and rescued the launch says little about managing a team, and can suggest the opposite. The second is the answer made of values. "I believe in open communication and psychological safety" is a statement of intent; the interviewer wants the conversation you actually had with one engineer, and what changed afterwards. There is no single right script for a people situation either. Two good managers can handle the same case differently and both be fair. What is being weighed is your reasoning, and whether the outcome was fair to the person and to the rest of the team.

These stories are about real people who are not in the room. Describe them by role rather than name, leave out health and personal circumstances even if you knew about them, and give enough detail to make your own decisions clear and no more. How you talk about the people on your team is part of the evidence.

Choosing a level. Pick the Lesson that matches the scope of the work the role will expect and the examples you can honestly give, not your current title. Employers name and divide these roles differently, and "manager" covers very different jobs, so treat this Lesson as a description of scope. It is for people interviewing to manage one team of engineers directly. If the role leads through technical direction rather than people management, for example a tech lead with no direct reports, the SDE-3 or SDE-2 Lesson in this Track is a closer fit even if the title says "lead". If the role manages other managers, runs several teams or owns an organization's strategy, this Lesson covers only the first-line part of it; those interviews are outside what this Track covers. The four Lessons are alternatives, not a ladder. Managing a team is a different job from senior individual contribution, not the step after it.

The answers below use the structure in Structuring behavioral interview answers with STAR⁠: Situation, Task, Action and Result, with Reflection where it adds something. In management stories the Task often deserves a sentence more than usual. Say what you were responsible for as the manager, which is usually different from what the team was building, so the interviewer can judge your actions against it.

What fits at this level#

AspectFits a first-line manager storySounds like an individual contributor's answerBeyond this Lesson
Whose workYour team's work, delivered through the engineers on itYour own code or design, with the team in the backgroundSeveral teams, or managers who report to you
PeopleA specific conversation with one of your engineers, what was agreed and what changedHelping a colleague as a peerDesigning an organization's career framework or performance process
EvidenceExpectations written down, check-ins that happened, a plan for either outcomeStatements about what you believe in as a managerOrganization-wide measures claimed as your result
HiringDecisions for your own team's roles, and what you learned from themSitting on an interview panel with no decision to makeHiring plans or standards across a group
StakeholdersYour team's priorities negotiated with a partner, with capacity made visibleAccepting priorities as given and working harderCompany roadmap or organizational strategy

The notes under each question describe what to look for in your own experience. They are not a template for one correct story, and different stories, or different tellings of the same one, can answer a question equally well.

Feedback that was hard to hear#

The question: "Tell me about a time you gave one of your engineers feedback that was hard to hear."

What the interviewer is assessing

Directness with care: whether you can say something specific and uncomfortable to someone who reports to you, in a way they can act on, and then follow up to see whether anything changed.

What strong evidence sounds like

What the feedback was, close to the words you used, and the observations it rested on. Why it needed saying, and why then rather than at a review. How you said it: privately, soon after the behaviour, about the work and its effect rather than about the person. How they responded, including if they disagreed, and anything you learned from their side that changed what you asked for. What you agreed and how you checked on it later. A result that was partial, or took more than one conversation, is credible. The first worked example below answers this question.

Common pitfalls

  • Feedback saved for the performance review, where it arrives as a surprise.
  • So much cushioning that the engineer leaves without knowing what was asked.
  • Comments on personality ("not a team player") instead of observable behaviour.
  • No follow-up, so the story ends with the conversation.

Likely follow-ups

  • "What exactly did you say?"
  • "How did they react, and how did you respond to that?"
  • "What would you have done if nothing had changed?"
  • "How did you make sure it was fair to raise?"

An engineer whose work was below what the role needs#

The question: "Describe how you handled an engineer on your team whose work was consistently below what the role needs."

What the interviewer is assessing

Fairness and clarity in the hardest kind of management conversation: whether expectations were clear before you judged against them, whether you looked for the cause before acting, what support you offered, and whether you handled the outcome honestly whichever way it went.

What strong evidence sounds like

How you noticed, and what the gap was in observable terms. The first conversation and how early it came: by the time anything formal happens, the engineer should already have heard about the problem from you. What you learned about the cause, without speculating about anything they didn't tell you. The expectations you wrote down together, the support you offered and the check-ins you agreed. How you kept your own manager informed. If your organization has a formal performance process, when you used it and when HR became involved, described as what you did rather than as a general rule. The outcome: recovery, a move to work that fit better, or the person leaving. The first worked example below answers this question.

Common pitfalls

  • Labels instead of observations: "lazy", "not committed".
  • Months of letting it slide, followed by a sudden formal process.
  • Speculating about the person's private life, or sharing what you know of it.
  • Presenting your company's HR process as if it were how employment works everywhere.
  • A story that only makes sense because it ended well.

Likely follow-ups

  • "When did you first notice, and why did you wait as long as you did?"
  • "What did the rest of the team see, and what did you tell them?"
  • "What would you have done if it hadn't improved?"
  • "Which part of the problem was yours?"

A hiring decision you would make differently#

The question: "Tell me about a hiring decision you would make differently today."

What the interviewer is assessing

Calibration and self-awareness about how you judge people: what evidence you relied on, what the process missed, which of your own biases played a part, and what you changed in how you hire for your team.

What strong evidence sounds like

The decision, which can be a hire that didn't work out or a candidate you turned down and later regretted. The evidence you had and what you weighted too heavily or too lightly: a strong technical round that drowned out a concern about collaboration, or a quiet interviewer you read as less capable than they were. How you found out. What you changed in your own part of the process, such as writing down what the role needs before interviews start, asking your interviewers to submit written feedback before discussing a candidate, or using a work sample that resembles the actual job. How you treated the person if they were hired: someone who struggles in a role you hired them into is still someone you are responsible for supporting.

Common pitfalls

  • Blaming the candidate for a hiring mistake that was yours.
  • "I trust my gut", with nothing changed afterwards.
  • Describing the person who was hired in a way that would embarrass them.
  • Turning the answer into a redesign of the company's hiring process.

Likely follow-ups

  • "Which signal did you misread?"
  • "What did you do for the person once you realised?"
  • "How do you check for that bias now?"
  • "What does a hiring loop for your team look like now?"

Conflict between two engineers#

The question: "Describe a conflict between two engineers on your team. What did you do?"

What the interviewer is assessing

Mediation: whether you can separate what two people disagree about from how they now feel about each other, deal with the problem without taking a side by default, and help the working relationship recover.

What strong evidence sounds like

What the conflict was about, as specifically as discretion allows: who owns a component, how code reviews are written, how on-call work is shared. How you found out, and whether you had missed earlier signs. Talking to each person separately first, and what you learned that neither had said to the other. What needed a decision from you, such as who owns what, and what they needed to work out between themselves. How you brought them together, if you did, and what was agreed. Whether the relationship recovered, and if it only partly did, what you did to make it workable. Conflicts between engineers often expose something unclear that the manager was responsible for, such as overlapping ownership, and a strong answer says so when it happened.

Common pitfalls

  • Siding with the more senior or more vocal engineer by default.
  • Telling them both to "work it out" and stepping away.
  • Treating a real disagreement about the work as only a personality clash.
  • Discussing one person's faults with the other.

Likely follow-ups

  • "What did each of them think was going on?"
  • "Which part of the cause was yours?"
  • "How did the rest of the team experience it?"
  • "How do they work together now?"

A commitment at risk#

The question: "Tell me about a time your team's commitment was at risk."

What the interviewer is assessing

Delivery through a team: whether you noticed the early signals, made the trade-offs visible to the people who could decide, and communicated honestly with stakeholders and with the team, rather than absorbing the problem through overtime.

What strong evidence sounds like

The commitment, who made it and who it was made to. The earliest signal and how it reached you: a planning check-in, a task that kept growing, an engineer mentioning a worry in a one-to-one. What you did in the first few days to understand the size of the gap and its causes. The options you put to stakeholders, each with what it gives up. What was decided, how you told the team, and how you kept the push sustainable. How it ended, including what slipped. The second worked example below answers this question.

Common pitfalls

  • Heroic overtime presented as delivery management.
  • Quiet scope cuts that the stakeholder discovers at the deadline.
  • A story about the manager coding through the final week.
  • Naming individual engineers to stakeholders as the cause.

Likely follow-ups

  • "When did you first know?"
  • "What did the team give up?"
  • "How did the stakeholder take it?"
  • "What do you do differently in planning now?"

Saying no to a partner#

The question: "Describe a time you said no, or renegotiated scope, with a product or business partner."

What the interviewer is assessing

Prioritization with stakeholders: whether you bring options instead of a flat refusal, ground the conversation in the team's real capacity, and keep the relationship working after a disappointing answer.

What strong evidence sounds like

What the partner wanted and what it was attached to, such as a customer commitment or a launch. Why it couldn't be done as asked, in terms of capacity and existing commitments rather than reluctance. The options you offered and the one you recommended, with your reasons. How you found out what the partner actually needed, which often makes a smaller first version possible. What was agreed, with dates, and whether you kept to it. How the partner felt about it, honestly, and how the relationship stands now. The second worked example below answers this question too.

Common pitfalls

  • "I protected my team" as the reason for a refusal with no options.
  • Agreeing to everything and paying for it with the team's evenings.
  • Treating the partner as an adversary.
  • Renegotiating without telling the team, or without telling your own manager when it affects commitments made to them.

Likely follow-ups

  • "What did the partner give up?"
  • "What would have made you say yes to the full request?"
  • "How did you explain it to your team?"
  • "How is that relationship now?"

Helping an engineer grow#

The question: "Tell me about helping an engineer grow into bigger responsibility."

What the interviewer is assessing

Developing people: whether you can see what someone is ready for, give them real responsibility with the right support, and let the success be theirs.

What strong evidence sounds like

The engineer's starting point and what they wanted, which may have differed from what you assumed they needed. The opportunity you found or made: leading a project, owning a component, running the team's design reviews, being the team's contact with another team. How you supported them without taking it back: what you covered in one-to-ones, where you stepped in and where you deliberately didn't. A moment that went wrong and how you handled it. Where they are now, with the credit given to them. Making their work visible to the people who decide on promotions counts too, where that is part of how your organization works.

Common pitfalls

  • The manager taking credit for the engineer's growth.
  • "Growth" that meant handing over work the manager didn't want.
  • Stretch with no support, so the story is really about someone being dropped in.
  • A general answer about mentoring the whole team, with no one person in it.

Likely follow-ups

  • "How did you decide they were ready?"
  • "Where did you step in, and was that the right call?"
  • "What did they want that you didn't expect?"
  • "What would you do differently for the next person?"

Onboarding someone onto the team#

The question: "Describe onboarding a new hire or an engineer who joined your team from elsewhere."

What the interviewer is assessing

Whether you give new people structure in their first weeks, make expectations clear early, and set up feedback in both directions so problems surface while they're small.

What strong evidence sounds like

What you prepared before they arrived: a first task that ships something real, a named teammate to go to with questions, access sorted out, the people they should meet. What you told them to expect at a few points, such as the end of the first month and the first quarter, and what you asked about how they like to work. How early feedback ran both ways, including what they told you about the team or about your onboarding. How it differed for an experienced engineer joining from another team, who usually needs context and relationships more than basics. How you knew it had worked, and what you changed for the next person.

Common pitfalls

  • Onboarding that amounts to a document and a laptop.
  • Expectations that only surface at the first review.
  • The same plan for a new graduate and an experienced transfer.
  • No feedback from the person who was onboarded.

Likely follow-ups

  • "What did they find hardest?"
  • "What did you change after hearing from them?"
  • "When did you know they had settled in?"
  • "What did the rest of the team do?"

When trust or morale dropped#

The question: "Tell me about a time trust or morale on your team dropped. What did you do?"

What the interviewer is assessing

Whether you notice when something is wrong with the team, listen before acting, separate symptoms from causes, and act on the cause, then check whether it helped.

What strong evidence sounds like

The signals you noticed: quieter retrospectives, one-to-ones turning guarded, people avoiding a part of the system, a change in who speaks up in meetings. The event behind it if there was one, such as a run of painful on-call weeks, a cancelled project or a well-liked teammate leaving. How you listened: one-to-ones, a retrospective run differently, asking an engineer you trust what they were hearing. What you concluded the cause was, which may include something you did. The actions you took, the ones that were outside your power, and how you explained the difference to the team. How you know whether things improved, stated modestly.

Common pitfalls

  • A team outing as the whole answer.
  • Morale described as a mood rather than as something with causes.
  • Fixing whatever the loudest person complained about.
  • Declaring that morale fully recovered, with nothing to show for it.
  • Widening the story into company culture, which is beyond one manager's reach.

Likely follow-ups

  • "How did you know morale had dropped?"
  • "What did people tell you that surprised you?"
  • "What did you try that didn't help?"
  • "What was outside your control, and how did you handle that part?"

A decision from above you disagreed with#

The question: "Describe a team-level decision from above that you disagreed with, and how you handled it with your team."

What the interviewer is assessing

Integrity in both directions: whether you disagree through the right channel and with reasons, then explain the decision to your team honestly, without disowning it or quietly working against it.

What strong evidence sounds like

The decision and how it affected your team: a project cancelled or handed to another team, a deadline set without your team's input, a change to how on-call works. Why you disagreed, and what you did with that: who you raised it with, with what evidence, and what you asked for. What happened, including if the decision stood. How you told your team: what you said about the decision, whether you mentioned that you had disagreed, and how you helped them work within it. What you did to reduce its cost to them.

Common pitfalls

  • "Management made us do it" as the explanation to the team.
  • Venting your disagreement to the team, or not carrying the decision out.
  • Agreeing silently upward and complaining downward.
  • Turning the story into a disagreement with organization-wide strategy.

Likely follow-ups

  • "Did you tell the team that you had disagreed?"
  • "What exactly did you raise, and with whom?"
  • "What would have made you push further?"
  • "Looking back, was the decision right?"

Worked example: the engineer whose output dropped#

Note

Illustrative example: a composite written for teaching, not a real candidate's experience.

The questions: "Describe how you handled an engineer on your team whose work was consistently below what the role needs." The same story also answers "Tell me about a time you gave one of your engineers feedback that was hard to hear."

Situation. A manager leads a team of seven engineers. At the start of a quarter the team's priorities change: work on a customer-facing feature area pauses, and the team takes on moving its services to a new deployment platform. One engineer, who had been dependable on the feature work, misses their commitments in each of the next two planning cycles. Two tasks carry over twice, and a teammate who was waiting on one of them mentions it in their own one-to-one. The manager has noticed too, but hasn't yet raised it directly.

Task. Understand what is happening before reaching a judgement, make expectations clear and offer fair support, be fair to the teammates affected, and protect the engineer's privacy, sharing only what the manager's own manager needs to know.

Action.

  • Before the conversation, the manager writes down what they have actually observed: the carried-over tasks, the dates, the teammate who was blocked. They leave out interpretations.
  • At their next one-to-one, the manager says they want to talk about the last two cycles, describes those observations, and explains why it matters: a teammate was blocked, and the platform move depends on these tasks. Then they ask how the engineer sees it, and listen.
  • The engineer says they hadn't been sure what was expected of them any more. Questions about the paused feature area were still coming to them, because nobody else had been named as its contact, and the platform work was unfamiliar enough that they didn't know what a good week looked like. The manager acknowledges that the first part was their own gap: they never reassigned the old area's support when priorities changed. They leave room for anything else the engineer wants to raise, and don't probe beyond what is offered.
  • Together they write a short shared note: what the engineer owns in the platform move, what done means for the next two tasks, and that questions about the old area now go to a named teammate. The manager tells that teammate, and the channel where the questions arrive, the same day.
  • They agree the support: a week of pairing with an engineer who has already moved a service, and a fifteen-minute weekly check-in for six weeks, alongside the regular one-to-one, to look at the note together.
  • When the blocked teammate asks again, the manager says they're aware of it and working on it, and nothing more.
  • The manager tells their own manager, in a sentence, that a performance conversation is under way and what the plan is, and keeps brief notes of each check-in.

Result. The next task lands on time. By the end of the six weeks the engineer is meeting their commitments and has moved a service largely on their own, so the extra check-ins stop and the regular one-to-ones continue. Had the gap persisted past the agreed period, the manager's next step would have been a second, more explicit conversation: naming the gap against the written expectations and what would happen if it continued, then moving to the organization's formal performance process, which is where HR would become involved. The support would have stayed in place, and nothing in that process would have been the first the engineer heard of the problem.

Reflection. Part of the cause was the manager's. The change in priorities had been announced to the team, but what it meant for each person had not. The manager now goes through expectations with each engineer individually after any change in priorities, including who picks up the work being set aside.

Sample wording. One possible spoken version, offered as a sample to adapt rather than to memorise:

"Our team switched from feature work to moving our services onto a new platform at the start of a quarter. One of my engineers, who'd been really dependable on the feature work, missed their commitments two cycles running, and a teammate who was blocked mentioned it to me. I'd noticed as well and hadn't said anything yet, which I should have. Before talking to them I wrote down only what I'd seen: two tasks that had carried over twice, and the person who was waiting. In our one-to-one I described that, said why it mattered for the platform work, and asked how they saw it. It turned out they didn't know what was expected any more. People were still bringing them questions about the old feature area, because I'd never named anyone else for it, and the platform work was new enough that they didn't know what a good week looked like. The first part was my mistake, and I told them so. We wrote a short note together: what they owned, what done meant for the next two tasks, and who took the old questions. I set up a week of pairing with someone who'd moved a service before, and a short weekly check-in for six weeks. I kept it out of the team: when the teammate asked again, I just said I was on it, and my own manager got one sentence on the plan. It recovered. The next task landed on time, and by the end of the six weeks they'd moved a service mostly by themselves. If it hadn't, I'd have had a more explicit conversation against that note and moved to our formal process, but it wouldn't have come as a surprise. What I do now is go through expectations with each person after a priority change, not just announce it to the team."

Why it works. The manager starts from observations rather than a verdict, and asks before concluding. The cause they find is specific and partly their own, and they say so without turning the story into one about themselves. Expectations are written down together, the support is concrete, and the extra check-ins have an end date. Privacy is kept with the teammate who raised it, and the manager's own manager is informed. The answer also covers the path where things don't recover, which shows the manager would have been fair and clear either way. It stays with one engineer on one team, which is what both questions are about.

How a weaker version differs. A weaker version opens with a label, "they'd checked out", and goes straight to a formal plan, which tells the interviewer the manager judged before asking. Another waits for the review cycle, so the feedback arrives as a surprise. Another discusses the engineer with the rest of the team, or guesses at what might be happening in their personal life, which would be a serious misstep on its own. And a version that only works because the engineer improved, with no thought about what would have happened otherwise, leaves the interviewer unsure how the manager handles the harder case.

Worked example: two commitments, one team#

Note

Illustrative example: a composite written for teaching, not a real candidate's experience.

The questions: "Describe a time you said no, or renegotiated scope, with a product or business partner." The same story also answers "Tell me about a time your team's commitment was at risk."

Situation. A manager's team owns the account administration pages of a business software product. At the start of a quarter, the partner who runs the product's enterprise customer area asks for bulk user import by the end of the quarter, because several large customers have asked for it. The team has already committed to reliability work after a run of incidents in its notification-delivery service, a commitment made to the manager's own manager and to the engineers on call. One of the team's six engineers will be on planned leave for half of the quarter.

Task. Give the partner a truthful answer with real options, keep the reliability commitment credible, and avoid a promise the team could only keep through overtime.

Action.

  • With the tech lead, the manager writes down the team's capacity for the quarter in engineer-weeks, after leave, on-call duty and the usual interruptions, next to rough estimates for the reliability work and for the full import feature. Together the two need far more time than the team has.
  • Before proposing anything, they ask the partner what the date is attached to. Two of the large customers want to bring their staff onto the product next quarter, and both keep their user lists in spreadsheets. The partner had pictured a full self-service import screen, but that isn't what those two customers need first.
  • They lay out three options. First, the full import feature by quarter-end with the reliability work deferred, which leaves the incident risk and the on-call load where they are. Second, reliability first and the import feature next quarter, which misses the two customers. Third, a first slice by quarter-end, a file upload that the support team runs on a customer's behalf, with validation and error reports but no self-service screen; the highest-risk reliability items in the same quarter; and the self-service screen dated for the middle of next quarter, with the remaining reliability item kept on the team's tracked commitments and dated for the end of next quarter.
  • They recommend the third option and say why: it serves the customers behind the request, keeps the reliability fixes that matter most, and doesn't depend on the engineer who will be away.
  • They brief their own manager before the meeting, because the reliability commitment was made to them.
  • In the meeting, the partner pushes for the full feature. The manager holds to the capacity numbers, offers to revisit the date if the first slice lands early, and sends a written summary of the options and the decision afterwards.
  • They tell the team what was agreed, what won't be done this quarter, and that new requests during the quarter should come through the manager rather than straight to engineers.

Result. The partner accepts the reduced first slice with a dated follow-up. They are not pleased, say so, and tell their own leadership that the full feature has moved. The first slice ships before quarter-end, and both customers bring their staff on through it. The highest-risk reliability items land; the lowest-priority one stays a tracked commitment with its date in the next quarter, and the manager tells their own manager about the new date rather than leaving it to be discovered. The self-service screen ships on the agreed date, and the deferred reliability item lands on its date after it.

Reflection. The capacity picture would have been more useful at the start of planning than in answer to a request that already had a date attached. The manager now brings the team's capacity and existing commitments to quarterly planning with partners, before requests arrive.

Sample wording. A sample of how a candidate might say this, in their own words rather than these:

"At the start of a quarter, the partner who runs our enterprise customer area asked for bulk user import by quarter-end, because some big customers wanted it. We'd already committed to reliability work after a run of incidents in our notification delivery, and one of my six engineers was going on planned leave for half the quarter. Before answering, I worked out our real capacity with my tech lead, after leave and on-call, and the two pieces of work didn't fit. I also asked the partner what the date was really about. Two customers wanted to bring their staff on next quarter, and both had their users in spreadsheets, so what they needed first wasn't the full self-service screen. I took three options to the partner: the full feature with reliability deferred, reliability first and miss those customers, or a first slice where support uploads a file for the customer, plus the most important reliability fixes, with the self-service part dated for the middle of next quarter. I recommended the third and explained why. I'd briefed my own manager first, because the reliability commitment was to them. The partner pushed for the full thing. I held to the numbers but offered to revisit if we got ahead. They accepted the first slice and weren't happy about it, which was fair. Both customers came on through it, the self-service part shipped on the agreed date, and one lower-priority reliability item moved to next quarter with a date on it. I told my manager about that, and we did it on that date. Next time I'd bring the capacity numbers to planning before anyone asks for a date."

Why it works. The manager makes capacity visible instead of arguing about effort, and asks what the date is for before deciding what to offer, which turns a yes-or-no into a question about what to build first. The options are real, each with its cost, and the recommendation comes with reasons. The team is protected by the plan rather than by a refusal, and the people who need to know (the partner, the manager's own manager, the team) hear in a sensible order. The result is honest: the partner was disappointed, and a reliability item moved a quarter, but it kept a date and an owner rather than quietly disappearing. Everything stays within one team's commitments and one partner relationship.

How a weaker version differs. One weaker version refuses outright to "protect the team", leaving the partner with nothing and the customers unserved. Another says yes to everything and describes the team's long evenings as dedication, which tells the interviewer that the manager's capacity plan is people's personal time. A third describes the negotiation but skips how the team heard about the decision, or claims the partner was delighted, which invites a follow-up the candidate can't answer well.

Full outline of Behavioral Interview Preparation