The Engineering Manager's Guide to 1:1 Meetings
Your 1:1 is the only meeting where the agenda belongs to your report, not to the project. Get that right, and everything else about managing gets easier: trust builds, problems surface early, and careers move forward.
Most managers do not have a 1:1 problem. They have a trust problem that shows up in the 1:1 – status updates you could have read in Jira, silence where there should be signal, feedback saved for review season. This guide rebuilds the practice from first principles: cadence, structure, questions, feedback, notes, and remote adaptations that make 30 minutes a week the highest-leverage time on your calendar.
1:1s catch drift, not tickets
Engineering work is complex, invisible, and ambiguous. People hit blockers, feel stuck, or quietly disengage long before it shows up in velocity or code reviews. The deploy pipeline everyone hates but nobody escalates, the unclear ownership between two teams, the senior silently carrying on-call – none of that appears in Jira. It appears in a 1:1, if you have built the kind of 1:1 where it is safe to say it.
For engineering specifically, 1:1s do three things no other meeting can: surface system friction early, build technical growth through tradeoff and design conversations, and keep you honest about what kind of manager you are actually being. Skip them or treat them as optional and you pay later in attrition, low engagement, or preventable project failures.
The report owns the agenda, you own the space
The single most common mistake new managers make is treating the 1:1 as their meeting. The moment you show up every week with project status and deadline pressure, you have converted a trust channel into a project check-in with better branding.
The fix is simple to state and hard to hold under deadline pressure: they bring the topics in whatever order matters that week, and you bring a short list you are tracking – a career thread you promised to revisit, a commitment you made last time – but you hold it until they are done. If they show up with “nothing,” do not fill the silence with status questions. Hold it, or offer one real question from section 05.
Weekly, 30 minutes, same time
Thirty minutes is enough if both people prepare. Protect the slot ruthlessly – cancel twice in a row and you have sent a message whether you meant to or not. If you must move it, move it within 48 hours. Never let it slide two weeks in a row.
If a senior engineer says they do not need it, keep 30 minutes on the calendar and finish early when there is nothing to discuss. You need the channel open more than you need the full slot filled.
A loose container, not a script
Use just enough structure that the conversation can breathe. Keep a shared running document – Google Doc, Notion page, Linear note – where both of you add topics between meetings. Spend 10 minutes before each 1:1 reviewing last time’s notes, recent PRs or design docs, and 2–3 questions based on what you observed.
Questions that actually open something up
“How is it going?” gets you “fine.” Specific, low-stakes, open questions lower the activation energy for an honest answer. Keep one good question handy rather than interrogating through ten.
Adapt to the person: new hires need clarity over autonomy, senior engineers need influence over tasks, a struggling engineer needs observation over judgment, and a future lead needs delegation plus coaching on people problems, not just technical ones.
Feedback that actually lands
Vague praise and vague criticism both fail. Prefer concrete observations – Situation, Behavior, Impact – and deliver them close to the event, not saved for review season: “In the design review on Tuesday, you interrupted three times while Alex was presenting. It made it harder for the group to follow the proposal.” Then ask what was going on for them. That fourth step turns one-way feedback into coaching.
The harder discipline is listening more than you talk. Before giving advice, ask: “Do you want ideas, feedback, or just to think out loud?” Engineers become managers because they are good at solving problems – resist fixing everything immediately. Silence after a real question is not a problem. Let them think.
Be supportive without becoming a therapist. When someone shares a personal difficulty, appropriate boundaries still apply: “I am sorry you are dealing with that. Let me know what support you need from a work perspective.” Empathy, not treatment.
Notes are memory, follow-through is trust
Keep lightweight notes – agreed actions, career goals, commitments, topics to revisit – not a transcript. Review them for five minutes before each 1:1. That prep alone puts you in the top tier of managers, because following up unprompted six weeks later (“You wanted platform on-call exposure – how did that rotation go?”) lands differently than any generic check-in.
Where this goes wrong is when notes become a private performance log the engineer never sees. If you would not want your own manager keeping a file like that on you, do not keep one on your reports. If it is worth writing down as a concern, it is worth having said out loud first.
Remote makes 1:1s more important, not less
Distributed teams lose hallway conversations and ambient signal, so the 1:1 becomes a lifeline. Default to video – hesitation, discomfort, and fatigue do not survive audio-only. Rotate the awkward hour instead of letting the same person always take 7am or 9pm. Protect the first five minutes for rapport instead of skipping straight to substance because time feels scarce.
Use the manager portion to share context remote engineers get late – strategy shifts, reorgs, budget realities – and watch for isolation signals directly: connection to the team, visibility into decisions, whether context arrives in time to decide well.
Five habits that quietly kill the meeting
How you know it is working
You will know the 1:1s are effective when people raise problems early, feedback flows both ways without drama, and you are rarely surprised by performance or attrition. The meetings feel useful to both sides rather than obligatory.
- They bring hard topics first, not last – trust is high
- They reference past conversations – continuity, not transactions
- You leave with more clarity, not more weight – and so do they
- Cancellations are rare on both sides – the slot has earned its keep
The ultimate test: if you stopped doing 1:1s, would the team notice and miss them? If the answer is no, reset the format – weekly, their agenda, better questions, visible follow-through – rather than adding more meetings.
Popular questions about engineering 1:1s
Q1How long should a 1:1 actually be?
Thirty minutes weekly is the right default. Shorter rarely gets past status; longer eats the week for reports who do not need it. Let specific conversations run over occasionally rather than defaulting every slot to 45–60 minutes.
Q2What do I do when my report says “I have got nothing this week”?
Do not rush to fill it with status. Sit with it for a beat, then offer one specific question from section 05. “Nothing” usually means “nothing prepared,” not “nothing going on.”
Q3Should I take notes during the meeting itself?
Brief notes, yes – mainly commitments and follow-ups, not a transcript. Typing continuously while someone discusses something hard reads as distraction, not diligence.
Q4What if a 1:1 turns into a performance conversation?
Let it, if that is genuinely what the moment needs – but say so plainly rather than letting it happen by stealth. Anything serious enough to affect a review should never be a surprise by review time.
Q5Do skip-level 1:1s replace my own?
Neither replace nor duplicate – they catch what a direct relationship can miss, including problems with the manager. Keep them rare enough not to feel like an audit and frequent enough not to feel like an event.
Q6What if someone says they do not need 1:1s?
Keep 30 minutes on the calendar and finish early when there is nothing to discuss, or move a stable senior to biweekly. Do not remove the channel – you do not want to learn someone is unhappy from a resignation letter.
Q7How do I handle confidential or compliance-adjacent disclosures?
Listen first, then be honest about what you can keep confidential and what you cannot – conduct and compliance issues almost always fall in the second bucket. Follow up visibly within days, not at the next scheduled 1:1.
Great 1:1s do not feel productive in the moment. They feel like two people actually thinking together.
The productivity shows up two quarters later, when the team ships calmly, tells you hard truths early, and grows people who want to stay. You do not manage Jira tickets. You manage people.
The version worth building sits in the same place as the rest of this series: a team that makes good decisions whether or not you are in the room – built one honest 1:1 at a time, not one grand policy change.