A disengaged senior engineer is one who shows up, does the work, and says nothing. No pushback, no suggestions, no investment in outcomes beyond their own ticket.
The questions that break this pattern dig into scope (is the work interesting?), ownership (does their input change anything?), and trajectory (is there a next thing they want?). Generic motivation talk rarely surfaces the real issue.
Key takeaways
- Ask what they wish they could be spending time on instead.
- Ask when they last felt like they had real influence over a technical decision.
- Name what you are seeing before you ask why: 'I have noticed you have been quieter in reviews lately.'
- Follow the energy in their answer, not just the answer itself.
Why it matters
Senior engineers disengage for concrete reasons: the work is too small, their opinions are not acted on, they have been passed over for something, or they have already decided to leave. Generic check-in questions will not surface any of these. You need questions that force a specific answer.
A 1:1 with a disengaged senior engineer is a diagnostic conversation. You are trying to identify which of four or five root causes is present. Each question you ask should help you rule something in or out. Once you have the root cause, you can act on it. Without it, you are guessing.
How it works in practice
A question sequence for a 1:1 with a senior engineer who has gone quiet
-
Name the pattern first
Open with: 'I want to check in specifically because I have noticed you seem less engaged in the last few sprints. What is going on from your side?' Do not ask a general 'how are you doing.' Name the specific observation.
-
Ask about scope
'What percentage of your week right now is work you would describe as genuinely hard? What would make that percentage higher?' This surfaces scope issues without asking whether they are bored, which invites a defensive answer.
-
Ask about influence
'When did you last feel like your technical opinion actually changed the direction of something?' If they have to think for a long time, you have found the issue.
-
Ask about trajectory
'What would make you feel like you were growing here in the next six months? Is there a project, a role, or a type of problem you want to get to?' This gives them a constructive direction to point toward instead of just naming what is wrong.
-
Ask about obstacles you might be creating
'Is there anything I am doing, or anything about how we work, that is making it harder for you to do good work?' This is the hardest question to ask and the most important. Say it last, after you have built enough trust in the conversation for an honest answer.
Common mistakes
Asking 'are you okay?'
This invites a yes or no. A disengaged engineer will say yes and the conversation ends. Ask specific, answerable questions instead.
Explaining their disengagement before asking about it
If you open with your interpretation, they will either agree to end the conversation or defend themselves. Get their account first, then share your read.
Treating it as a motivation problem
Motivation is downstream of conditions. Fix the conditions first. Asking someone to be more motivated without changing anything that is demotivating them is not management.
Not following up in the next 1:1
If you asked the questions and got real answers, you have made an implicit commitment to act on them. Silence after the conversation is worse than never having asked.
What it sounds like
Engineering manager Daniel is in a 1:1 with a senior engineer who has been quiet for two months.
Daniel: “I want to ask about something specific. Over the last couple of months you have been noticeably quieter in design reviews. I am not sure what is driving that, so I would rather ask directly.”
Merav: “Honestly, I don’t know that my input changes anything. I gave feedback on the auth refactor in March and we went a different direction anyway.”
Guy: “That is fair. Was there a moment where it would have helped to have a longer conversation about that decision before it was made?”
Questions managers actually ask
What if they say 'nothing is wrong' and shut down?
Name your observation more specifically: 'I noticed you did not comment on the three RFCs we circulated last week. That is unusual for you.' A specific observation is harder to wave off than a general check-in.
How do I know if this is a workload issue versus a growth issue?
Ask: 'On a scale of one to ten, how interesting is your current work?' Then ask what a ten would look like. Workload issues and scope issues produce different answers.
Should I bring up their performance data in this conversation?
Not in the first conversation. You are in diagnostic mode. Bringing performance data in too early shifts the conversation from collaborative to evaluative.
What if they tell me they are interviewing elsewhere?
Say: 'I appreciate you telling me that. Can I ask what they are offering that you are not getting here?' You now have a concrete retention conversation to have.
How often should I have this conversation if it happens more than once?
If you are having the same conversation every quarter, the issue is structural, not conversational. Something in how their work is scoped or evaluated needs to change.
What do I do if I suspect they are quiet because of a specific team conflict?
Ask directly: 'Is there anyone on the team you find it hard to work with right now?' Indirect questions rarely surface interpersonal issues.
See how Leap improves execution in your meetings
Leap sits in your meetings, captures decisions and owners in real time, and shows you where execution breaks down before the week is out.