A 1:1 meeting is the highest-leverage tool an engineering manager has — and the most commonly misused. Run well, it's where you surface problems before they become resignations, build the trust that makes feedback land, and create the conditions for an engineer to stay and grow. Run as a status update, it wastes 30 minutes and costs you the relationship.
This guide covers structure, cadence, question templates, and what to do when the 1:1 stops working.
Why Engineering 1:1s Fail (And Cost You Engineers)
The pattern is consistent: a manager schedules weekly 1:1s with the best intentions, the meetings become status reports by week three, and by month two both parties are going through the motions. The engineer stops bringing real concerns. The manager stops having signal on how the engineer is actually doing. Six months later, there's an unexpected resignation.
The reason 1:1s become status reports is structural: without a defined format, the manager defaults to "what are you working on?" — because it's safe, it produces information, and it fills the time. But the engineer gets nothing from it except the feeling that their manager is checking up on them rather than investing in them.
Understanding why developers quit reveals that poor management quality — specifically the absence of real 1:1s — is the third most common driver of developer attrition. And unlike compensation issues, this is entirely within the manager's control. Retention metrics for engineering teams that track engagement over time often show a correlation between 1:1 quality and voluntary attrition rate.
Key insight: Engineers who report having quality weekly 1:1s are 3x less likely to be actively job searching than engineers with monthly or no 1:1s (Gallup Workplace Research, 2024).
Structure and Cadence: What Actually Works
Cadence
Weekly, 30 minutes minimum. Not biweekly. Not "monthly deep dives." Weekly, even if some sessions are short.
The argument for biweekly is always efficiency. The reality is that biweekly breaks the relationship maintenance loop — issues that would have been flagged in a weekly session at an early, manageable stage compound for an extra week before surfacing. By the time they surface, they're harder to address.
Extend to 45–60 minutes for:
- New hires in their first 90 days (see the 90-day developer onboarding framework)
- Engineers in a performance conversation
- Engineers returning from leave
- Any period of significant team change or uncertainty
Ownership
The engineer sets the agenda. The manager's role is to create space for the engineer's concerns, not to drive the conversation toward the manager's topics.
In practice, that means: at the start of every session, ask "what's the most important thing we should talk about today?" and use the answer as the starting point — not the manager's pre-prepared list of project updates.
Shared Document
Every engineer-manager pair should have a shared running document (Google Doc, Notion, Linear note — format doesn't matter). Structure:
## [Date]
**Engineer agenda:**
- [item 1]
- [item 2]
**Manager agenda:**
- [item 1]
**Action items:**
- [ ] [What] — [Who] — [By when]Both parties add items before the meeting. After the meeting, action items are added with owners. The shared doc creates mutual accountability and serves as a relationship record.
1:1 Question Bank by Situation
Opening the Session
- "What's the most important thing we should talk about today?"
- "What's been on your mind since our last session?"
- "Is there anything you've been wanting to bring up but haven't found the right moment?"
Surfacing Blockers
- "Is there anything in your way right now that I could help remove?"
- "Where are you spending time that feels like it's not moving the needle?"
- "Is there anything about the current project structure that's making your work harder than it needs to be?"
Growth and Development (connect to developer mentorship program)
- "Where do you want to be in 12 months — technically and in terms of scope?"
- "What's something you want to learn this quarter that we haven't talked about yet?"
- "Are there problems you wish you had more exposure to that I could route your way?"
- "Is there a project or initiative where you'd benefit from more visibility?"
Engagement and Wellbeing
- "On a scale of 1–10, how energized are you about your current work? What would move it toward a 10?"
- "Is there anything going on outside of work that I should be aware of — just so I can be supportive?"
- "When was the last time you did work here that felt genuinely challenging in a good way?"
Feedback
- "Is there anything I've done recently that's made your work harder?"
- "What could I do differently to be a more effective manager for you specifically?"
- "Is there a decision I've made that you'd want to push back on or understand better?"
These questions feel uncomfortable because they genuinely invert the power dynamic. That discomfort is the signal they're working.
1:1 Templates for Three Scenarios
Template 1: Regular Weekly 1:1
Agenda (engineer sets first):
- What's on your mind
- Current work: any blockers or escalations
- One growth/development item (rotates)
Manager topics (if any after engineer's agenda):
- Any upcoming org changes, decisions, or context
- Feedback (if specific and timely)
Close: action items + preview of next sessionTemplate 2: 30-Day Onboarding Check-In
Context: 30 days in, this is a structured reflection session
Manager asks:
- What's working well in how we've set up your first 30 days?
- What's the biggest unresolved friction point?
- Do you feel clear on what success looks like at 90 days?
- What would make the next 30 days more effective?
Engineer asks:
- Where am I working well, from your perspective?
- Where do you want to see more progress by day 60?
- Is there anything about how I'm working that you'd flag early?
Close: Updated 90-day plan with specific day-60 markersTemplate 3: Retention Conversation (Run Proactively, Quarterly)
Open: "This is a conversation about your future here, not a performance review."
Questions:
- What would make the next year here feel like the right call for you?
- What's the one thing that, if it changed, would make the biggest difference?
- Where are you on your growth trajectory — are you moving at the pace you want?
- Is there anything you've been wanting that I haven't been able to provide?
Manager commits to:
- [Specific action 1] by [date]
- [Specific action 2] by [date]
Close: Written summary sent async within 24 hoursWhen 1:1s Stop Working
Four scenarios where 1:1s become ineffective, and what to do:
The Status Report Drift
What happens: Manager defaults to project questions; sessions become check-ins instead of relationship conversations.
Fix: Reset the format explicitly. "I want to change how we're using this time. I have standups and status updates for project visibility — this time is yours. What would be most useful to you?"
The Engineer Who Cancels Repeatedly
What happens: The engineer deprioritizes the sessions — a signal of disengagement, overload, or finding them unhelpful.
Fix: Don't make them optional. Reach out async: "I noticed we've missed the last two sessions. Is there a better time or format?" Then genuinely adapt based on the answer.
The Surface-Level Answers
What happens: Every question gets a fine, things are good, no blockers. The engineer has stopped sharing anything real.
Fix: This is a trust deficit, usually built over months. Address it directly: "I've noticed our sessions have been pretty surface-level. I want to make sure this is actually useful to you — what would make you feel safe bringing real concerns here?"
The Over-Busy Manager
What happens: The manager cancels 1:1s when stressed. The sessions become the first thing cut when the schedule compresses.
Fix: Never cancel a 1:1 without immediately rescheduling within the same week. For the engineer, a cancelled 1:1 is a signal that they're not a priority. Developer burnout signs often correlate with periods of repeated 1:1 cancellations — the absence of the check-in removes the safety valve.
How Nextmantra AI Approaches This
Stronger hires make 1:1s more productive. When an engineer's actual working style, communication patterns, and learning orientation are documented from the interview process — not inferred from CV keywords — the manager can make first 1:1s more targeted and meaningful from day one.
Nextmantra AI's structured evaluation report identifies how candidates communicate when blocked, how they take and apply feedback, and how they approach ambiguity. A manager who starts the first 1:1 with that context builds a faster, more accurate picture of how to support the new engineer — and spends less time in the first 90 days doing retrospective discovery of things that could have been known before the hire started.
See how Nextmantra AI handles this
Frequently Asked Questions
How often should engineering managers have 1:1s?
Engineering managers should hold 1:1s weekly with direct reports — 30 minutes minimum, 45–60 minutes for engineers who are new, in a challenging phase, or showing signs of disengagement. Monthly 1:1s are insufficient — by the time a problem surfaces in a monthly session, it's usually already progressed past easy intervention.
What should be discussed in an engineering 1:1?
A well-run engineering 1:1 covers: what's on the engineer's mind first (not a status report), any blockers to current work, feedback in both directions, one growth or development topic per session, and any upcoming changes or decisions that affect the engineer. What it should not cover: routine status updates, tactical project minutiae, or anything the manager could have communicated async.
How long should a 1:1 be for an engineering manager?
30 minutes is the standard baseline for a recurring weekly 1:1 with an experienced engineer working well. 45–60 minutes for new hires, engineers in a difficult performance situation, or any session where a substantive growth or retention conversation needs to happen. Resist shortening 1:1s during busy periods.
What questions should an engineering manager ask in a 1:1?
High-signal 1:1 questions: "What's the most important thing we should talk about today?", "Is there anything blocking you that I could remove?", "Where are you feeling most challenged right now?", "What's something you learned this week?", and "Is there anything I could do differently to make your work easier?"
How do you take notes in engineering 1:1s?
Use a shared 1:1 document — a running Google Doc or Notion page that both manager and engineer can see and edit. Structure it with date headers and two sections: engineer's agenda and manager's agenda. Add action items with owners and due dates after each session.
What do you do when an engineer cancels 1:1s repeatedly?
An engineer who repeatedly cancels is sending a signal: either overwhelm, finding the 1:1s unhelpful, or disengagement. Don't make them optional. Reach out async: "I noticed we've missed the last two sessions — is there a better time or format that would work for you?" Then listen to the answer.
How do 1:1s help with developer retention?
1:1s are the primary retention tool available to an engineering manager. Engineers who have regular, quality 1:1s report higher job satisfaction, more clarity on growth path, and significantly lower likelihood of passive job searching. The specific mechanism: 1:1s create the conditions for early problem identification while problems are still fixable.
Conclusion
The 1:1 is not a status meeting. It's the primary mechanism through which you maintain the manager-engineer relationship, surface problems before they compound, and create the conditions where capable engineers stay. Get the format right — engineer agenda first, shared document, weekly cadence, genuine questions that invert the power dynamic — and the retention value compounds over time.
Ready to hire engineers who make 1:1s work from day one? See Nextmantra AI in practice
Sources: Gallup State of the Global Workplace 2024; SHRM Workforce Analytics 2024; Stack Overflow Developer Survey 2025; Harvard Business Review Management Research 2024