Most managers run 1:1s with senior engineers wrong, and the engineers know it.
If your senior 1:1 is 25 minutes of “what are you working on, anything blocked,” you are using the most leveraged tool in management as a glorified Slack thread. You will produce a senior engineer who never feels heard, never gets coached, and starts looking at job listings on the third Tuesday of every month.
This guide is the 1:1 framework we use in our EM coaching pods. It’s specifically tuned for senior engineers — not new hires, not juniors. The mistake most managers make is using one 1:1 format for everyone; senior engineers need fundamentally different conversations than people who are still ramping.
Why Senior Engineers Need a Different Framework#
Three things are different about senior engineers that change what a good 1:1 looks like:
- They often know more than you do about specific technical domains. Mentoring (the implicit “I know, you don’t” mode) doesn’t fit.
- They are more likely to leave for environment than for compensation. A senior engineer who’s bored, blocked, or feels invisible will leave even if you pay them well. The 1:1 is your primary detection mechanism.
- Their highest-leverage contribution is decisions, not output. A senior engineer who makes one good architectural decision in a month is worth more than one shipping 30 features. The 1:1 should be where decisions get sharpened.
Status-tracking 1:1s ignore all three. The GROW framework, adapted for engineering, addresses them.
The GROW Framework, Engineering Edition#
GROW (Goal, Reality, Options, Will) was developed for executive coaching by John Whitmore in the 1980s. It’s well-suited to engineering 1:1s because it foregrounds the engineer’s thinking, not yours.
Stage 1 — Goal (5–7 minutes)#
Open with a question that puts the engineer in charge of the agenda:
“What’s the most important thing you want to leave this conversation having figured out?”
Variants:
- “What’s been on your mind this week that we should talk about?”
- “If we could only solve one thing in 30 minutes today, what should it be?”
Do not pre-load an agenda. If you arrive with a list of things you want to discuss, you’ve reverted to status mode. Your topics can come up in stage 4 (Will) — not at the start.
If they say “nothing in particular, things are fine,” dig once: “What’s the closest thing to ‘something not quite right’ on your mind?” Then accept the answer. Sometimes 1:1s are short. That’s fine.
Stage 2 — Reality (10–15 minutes)#
Once you have the topic, your job is to help them describe its current state in full. The trap here: managers often jump to interpretations or solutions (“Sounds like you’re frustrated with X”) within 90 seconds.
Useful Reality-stage questions:
- “Walk me through how this is showing up day-to-day.”
- “What have you already tried?”
- “What does the data say vs. what’s your gut saying?”
- “What’s the quietest version of this you’ve noticed?” (catches early signal)
- “What would have to be true for this to be a non-issue?”
The discipline: ask three Reality questions before offering any interpretation. Time yourself the first few times — most managers fail this.
Stage 3 — Options (10–15 minutes)#
Once the topic is fully on the table, your job is to help generate options before evaluating any of them.
Useful Options-stage questions:
- “What are 2–3 ways this could play out from here?”
- “If you didn’t have to choose one of those, what’s a third option?”
- “What would you do if you were 10 years more senior?”
- “What would [person they admire] do here?”
- “What’s the option you’ve been resisting because it’s uncomfortable?”
The discipline: generate at least 3 options before evaluating any. Most engineers will offer one preferred path and want you to validate it. Don’t. Even if their path is right, the practice of generating alternatives sharpens decision quality over time.
Stage 4 — Will (5–10 minutes)#
The conversation has produced clarity if it ends in a specific commitment.
Useful Will-stage questions:
- “What will you actually do, and by when?”
- “What would tell us it’s working in 2 weeks?”
- “What would tell us it’s NOT working, so we’d know to change course?”
- “What support do you need from me to make this happen?”
- “How will I know if you get stuck?”
Document the commitment in a shared 1:1 doc. Reference it next week — “Last week you said you’d talk to Anna about the migration plan; how did that go?” — without nagging.
A 50-Question Library#
We maintain a library of senior 1:1 questions, organized by purpose. A short selection:
Detecting attrition risk early#
- “On a scale of 1–10, how energized are you about your work right now? What would make it a 9?”
- “If you were going to leave in 6 months, what would have prompted it?”
- “What’s the most interesting thing you’ve worked on in the last 90 days?”
Surfacing technical disagreements they’ve stopped raising#
- “What’s a technical decision in the last quarter you would’ve made differently if you’d been the one deciding?”
- “Where do you think the team is over- or under-investing right now?”
- “What’s the tech-debt item you’d ship a fix for this weekend if you could pick one?”
Coaching toward staff-level impact#
- “What’s the project you’re working on that is most visible to leadership? What’s the one that’s least visible but might matter more?”
- “Who in the company has knowledge you need but don’t have access to? How do we fix that?”
- “What’s a decision the team is making that you wish you’d been consulted on?”
The full 50-question library is included in our EM coaching program materials. We’re happy to share a standalone copy on request.
Common Anti-Patterns#
In our coaching program we see five recurring failure modes:
- The status 1:1. “What are you working on” → “Anything blocked” → “Anything else” → end. This is not coaching, it’s a Slack thread with extra steps. Replace it.
- The vent 1:1. The engineer uses the 1:1 to complain about teammates or leadership; nothing changes; resentment compounds. Coaching transforms venting into commitment (“What will you do about this by next week?”).
- The over-prepared 1:1. Manager arrives with a 5-item agenda. Engineer’s actual concerns never surface. The agenda was the manager’s, not the engineer’s. Hold your topics until stage 4.
- The advice-giving 1:1. Manager hears the topic, immediately offers their own solution. Engineer leaves with a borrowed conclusion they don’t internalize and won’t sustain. Resist.
- The cancelled 1:1. Manager is busy, reschedules the 1:1, repeats. Engineer learns that the time isn’t sacred. Senior engineers especially read this signal — it’s a top driver of attrition.
Templates#
We maintain Notion templates for the 1:1 framework:
- The shared 1:1 doc — running document the engineer co-owns; section per week; commitments tracked.
- The GROW worksheet — for managers to use as scaffolding the first 4–6 times until the structure becomes intuitive.
- The retro template — quarterly 1:1 retrospective you run with the engineer to evaluate whether the 1:1 itself is working.
What Comes Next#
If you’re an EM running this framework with a senior engineer, you’ll start hitting the limits of what a 30-minute weekly conversation can do. That’s where structured mentoring comes in: Engineering Manager Mentoring Program: Cost, ROI & Setup.
If you’re a founder thinking about whether to manage senior engineers yourself or hire someone to do it, see From Founder to CTO: Scaling Tech Leadership Past 30 People.