In this article
Before you start
Developing a team is one part of the people-management loop in the engineering manager interview questions.
Why interviewers ask this
A manager who coaches badly loses engineers in quiet ways: people stall, stop asking for help, or leave. The question tests whether a candidate has a method, not only good intentions.
The manager matters. Google analyzed over 10,000 data points about its managers and found that teams with highly effective managers were more likely to achieve better results, be happier and have lower turnover. "Be a good coach" is the first behavior on Google's list of ten, and "Have key technical skills" is also on that list. Gallup reports that managers account for about 70% of the variance in team-level engagement.
A weak answer says "I mentor people and give feedback." A strong answer shows a method: a shared goal, a style that fits the person, questions before answers, and a routine. The wider people management round tests the same habits from other angles.
Coaching and developing engineers from first principles
- GROW model
- The GROW model is a coaching framework that structures a conversation in four stages: Goals, Reality, Options and Will (the way forward). It is a conversation structure, not a script, so a conversation can move back and forth between stages.
- Situational Leadership II
- Situational Leadership II (SLII) is a leadership model that matches a manager's style to a person's development level on a specific task, using four styles: directing, coaching, supporting and delegating. The style changes with the task, so one engineer can need different styles in the same week.
In plain words
Think of a running coach. For a beginner she shows the stride. For a veteran she asks what felt off in the last race. She never runs the race for them. A good manager does the same with engineers: the work is theirs, and the manager shapes how they grow.
The analogy breaks in one place. A manager also assigns the work and writes the review, so engineers may hold back what they do not know. Coaching only works when the engineer trusts that honesty is safe.
In one precise sentence, developing a team means giving each engineer a clear goal, the right amount of direction for the task, and regular conversations that build their own judgment. The growing engineers guide goes deeper on the career side.
Step-by-step description
- The engineer helps set the goal.
- Direction follows skill on the task.
- Goals, reality, options, will.
- Weekly one-on-ones keep it going.
- Coaching starts with a goal that the engineer helped set.
- A coaching conversation moves through four stages: goals, reality, options and will.
Step 1: Agree the goal and what is expected
Coaching starts with a goal that the engineer helped set. Google's list of manager behaviors includes supporting career development and discussing performance, which starts from a shared view of what is expected.
Gallup reports that when employees are included in goal setting, 76% strongly agree they know what is expected of them, against 47% when they are not, a gap of 29 percentage points.1
Input: the engineer's current level, what they want in a year, and what the team needs from them. Output: one or two written goals, the expectations for their level on the career ladder, and a date to review. Ask about both sides, their wishes and the team's needs. You now have a target to coach toward.
Step 2: Match your style to the engineer's level on the task
The right amount of direction depends on the person and the task, which is why one fixed style fails. A development level is how skilled and how motivated a person is on one specific task, and the model matches the style to it. A secondary explainer maps it so: development level D1 calls for directing, D2 for coaching, D3 for supporting and D4 for delegating. The SLII Coaching style (S2) means high directing and high supporting: it explains and redirects. In SLII the most question-led style is Supporting (S3); the S2 Coaching style still explains and redirects.
Illustrative example, one engineer in one week: on a first on-call shift they need directing, a walk through the runbook and when to escalate. Two weeks into learning the new build system, they still break the pipeline and are frustrated, so the SLII Coaching style (S2) fits: explain again, redirect and encourage. On a design they have done twice but doubt, supporting (S3) fits: ask how they would approach it and offer backup. On a service they built, delegating fits: agree the outcome and step back.
Explainers note that the original version of the model used other labels (telling, selling, participating, delegating), so check which version an interviewer means.
Text description of the diagram
- Development level D1 calls for directing, D2 for coaching, D3 for supporting and D4 for delegating.
- Coaching means high directing and high supporting.
Step 3: Coach with questions, not answers
A coaching conversation moves through four stages: goals, reality, options and will, the order of the GROW model. At the options stage, the guide uses a question such as "What options could you consider?" Plain questions work at the other stages too: what the engineer wants, what is happening now, and what they will do first.
The aim of the options stage is to encourage new ideas, not to give set answers. The guide also says conversations often move between stages as new insights arise.
Input: an engineer with a goal or a problem. Output: an action the engineer chose and said aloud. If the engineer has no experience of the task, that is the signal from Step 2 to direct first and ask later.
Step 4: Make it routine with one-on-ones and growth work
Development happens in a routine, not in one big talk. Use the one-on-one for coaching conversations, code review for specific feedback, and stretch assignments for growth.
Time is the first cost. With eight engineers and a thirty-minute one-on-one each (illustrative), that is 240 minutes, four hours a week, a tenth of a forty-hour week; with twelve engineers it is six hours, or fifteen percent.1
Gallup says the best managers are performance coaches who take a positive, future-focused approach to developing talents into strengths. A candidate who describes a routine has something concrete to say. Check progress against the Step 1 goal, not against how much you talked.
Worked example: one coaching conversation
Illustrative composite, written in third person. An engineer's design documents keep coming back for rework.
- Goal: the manager asks what the engineer wants from next week's design review. The engineer says they want fewer late objections.
- Reality: asked what is happening now, the engineer says they write the document after building, so objections arrive late.
- Options: the engineer proposes sharing an outline first and showing the riskiest part early. Only then does the manager add one option of their own, a one-page outline circulated beforehand, and asks whether it fits.
- Will: asked what they will do first, the engineer commits to send an outline on Wednesday.
At the next one-on-one the manager asks what happened. The engineer chose every action, and the manager's only contribution was one added option.
Knowing it is half the job. Saying it is the other half.
Interview Clozo is an AI interview copilot for real interview rounds: it hears the question and puts a strong answer on your screen, and you say it in your own words. See the features or how it works.
Start Free Trial →The Staff-level answer
How do you coach and develop your engineering team?
I start by agreeing a goal with each engineer, because people who help set their goals are more likely to know what is expected of them. Then I match my style to their skill on the task: more direction for someone new to it, more questions and delegation for someone experienced. In one-on-ones I ask before I tell, in four steps: goal, reality, options, then what they will do.
For example, an engineer whose design docs kept being reworked chose to share an outline first. I judge it by their progress against the goal, not by how much I talked. If someone stays stuck, I give more direction first; if a gap against expectations remains, I move to a clear performance conversation.
What makes it Staff-level: it names the style change by task, gives a concrete example where the engineer made the choice, and marks where coaching ends and a performance conversation begins. Link it to your management philosophy in one sentence.
The rubric
| Dimension | Weak answer | Strong answer | Staff answer |
|---|---|---|---|
| Correctness | "I mentor and give feedback." | Agrees goals, coaches with questions, holds one-on-ones. | Adds that style depends on skill and motivation for each task. |
| Depth | Vague on how a conversation runs. | Describes a four-stage question structure. | Says the structure bends and is not a script. |
| Trade-offs | No mention of cost or limits. | Notes the time cost of one-on-ones. | Notes when direction beats questions and when coaching is the wrong tool. |
| Communication | Generic, no example. | One concrete example. | Example with the engineer's choice, the manager's one option and a follow-up. |
| Follow-up readiness | Stuck when asked "does it work?" | Names a measure tied to the goal. | Separates coaching from performance management and escalates correctly. |
Three variants of this question
How do you develop an engineer who does not want a promotion?
Ask what they want from the work, because development is wider than promotion. Agree a goal such as deeper ownership, a new skill or better craft, and coach toward it with the same steps. The career-ladder expectations still apply, so be clear about them.
How do you coach an engineer who is stuck on a task right now?
Check their level on that task first. If they are new to it, the model's directing style fits: show the approach and say when to escalate, then ask questions on the next attempt. Questions alone from a beginner feel like being quizzed.
How would you coach a senior engineer who is better technically than you?
Coach on goals, judgment and communication, not on code. Google's list places key technical skills eighth, and the list's order is not presented as a ranking. Ask questions about options and trade-offs, and delegate with a clear outcome.
Common mistakes
- "I coach everyone the same way." (wrong) Style should follow the person and the task. (right) "I direct someone new to a task and delegate to someone experienced in it."
- "Coaching means telling people what to do." (wrong) The aim of the options stage is new ideas, not set answers. (right) "I ask first, and offer one option of my own after theirs."
- "A good engineering manager must be the best engineer on the team." (wrong) Coaching is first on Google's list and technical skill is one item on it. (right) "I need enough technical skill to follow the work, and I coach on growth."
- "I jump to my solution as soon as they describe the problem." (wrong) It shuts down the engineer's own thinking and leaves them nothing to own. (right) "I ask what is happening and what they have tried before I suggest anything."
- "Gallup proves coaching raises engagement by 18% on engineering teams." (wrong) Gallup reports that teams led by managers who completed strengths-based manager development improved engagement by up to 18% more and had 21% to 28% less turnover, but that is a cross-industry program, not coaching training for engineers. (right) "Research links manager development to better engagement; I treat it as an association."
Follow-up questions
How do you know your coaching is working?
Check the engineer's progress against the goal you agreed in Step 1, and ask them what has changed. If a goal has not moved, change the style before concluding the engineer cannot do it. The team health question covers measuring at team level.
How often should you hold one-on-ones with your engineers?
A weekly slot is one common choice, and regularity matters more than length. With eight engineers at thirty minutes each, it costs four hours a week.1
Is the GROW model a script you follow in order?
No. The guide says the steps are shown in order but conversations often move between stages as new insights arise, so treat GROW as a structure for the conversation, not a script.
What if the engineer disagrees with your view of their level?
Treat it as information. Ask what they have done on this kind of task, agree what evidence would change your view, and review it at the next one-on-one.
How does coaching differ from performance management?
Coaching builds capability toward a goal; performance management deals with a gap against expectations. When coaching does not close the gap, move to the process in handling a low performer and managing team performance.
How does coaching differ from mentoring?
Coaching is the manager asking questions so the engineer finds their own next step. Mentoring is usually advice and experience shared by someone who has done the job, often outside the reporting line. An engineer can have both, and a manager can borrow from either.
- Coaching starts from a goal the engineer helped set.
- The right style depends on the engineer's skill and motivation on each task.
- Ask before you tell, but direct when the engineer is new to the task.
- A routine of one-on-ones and growth work does the developing.
- Report engagement research as an association, not a promise.
Sources
- Following the data: The research behind great managers — Google re:Work, 1 Aug 2025
- The GROW Model: A Complete Guide — Performance Consultants, 24 Jun 2026
- Employee Engagement and Productivity: Gallup's Research — Gallup (page undated; read 2026-10-26), 26 Oct 2026
- How Managers Impact Team Productivity — Gallup, 30 Sep 2026
- Situational Leadership Theory: the Blanchard and Hersey model — LEADx (secondary explainer; page undated, read 2026-10-26), 26 Oct 2026
