Engineering Manager 1:1 Meetings - The Complete Guide

Why 1:1 Meetings Matter

If you manage engineers, the one-on-one meeting is the single most important recurring event on your calendar. The quality of your 1:1s will define the quality of your management. Everything else - sprint planning, retrospectives, architecture reviews - can function without you. The 1:1 cannot. It is the one space where your direct report has your undivided attention, and where the real work of engineering management happens.

Building Trust and Psychological Safety

Trust is the foundation of every productive engineering team, and trust is built in private long before it is visible in public. The 1:1 is where an engineer learns whether their manager genuinely listens, remembers what was discussed last time, and follows through on commitments. When you consistently show up prepared, give your full attention, and act on what you hear, you create a relationship where the engineer feels safe to be honest - about struggles with a project, tensions with a teammate, or doubts about their own performance. Psychological safety does not emerge from team-wide declarations; it is earned one conversation at a time.

This is particularly critical for engineering managers because the work itself is often complex and ambiguous. Engineers face trade-offs every day - should they refactor the legacy service or ship the feature on time? Should they speak up about a flawed technical decision from a senior colleague? Without a trusting relationship with their manager, they will default to silence and self-preservation, which harms the team and the product.

Retention and Engagement

Research consistently shows that people leave managers, not companies. A Gallup study found that managers account for at least 70% of the variance in employee engagement scores. When engineers feel heard, supported, and developed, they stay. When they feel ignored, micromanaged, or stagnant, they leave - often without warning, because the warning signs surfaced in conversations that never happened.

The 1:1 is your early warning system. An engineer who mentions feeling bored in week twelve is giving you a gift - a chance to intervene before they start interviewing elsewhere. An engineer who stops bringing topics to the 1:1 altogether is telling you something too, just less directly. Paying attention to these signals and acting on them is one of the best uses of time an engineering manager has.

Feedback Loops

Effective feedback is timely, specific, and delivered in a safe context. The 1:1 provides all three. Rather than waiting for a quarterly performance review to tell an engineer that their code reviews have been dismissive, you can address it within days - when the context is fresh and the behaviour is correctable. Equally, the 1:1 is the place where you can give reinforcing feedback: telling someone specifically what they did well and why it mattered, which is far more powerful than a generic "good job" in a team channel.

Feedback should flow in both directions. The 1:1 is one of the few spaces where a direct report can tell you what you could be doing better as a manager. Actively soliciting this upward feedback - and visibly acting on it - models a growth mindset for the entire team. It also gives you information you simply cannot get any other way. Your skip-level manager will not tell you that your standups feel like interrogations; your direct report might, if you have built the trust to make that conversation safe.

Early Problem Detection

Technical problems are usually visible in dashboards and incident reports. People problems are not. A brewing conflict between two engineers, a quietly overwhelmed new joiner, a senior engineer who has checked out mentally - these are the issues that derail teams, and they are almost always detectable in 1:1 conversations weeks before they become crises. The engineering manager who runs consistent, high-quality 1:1s is rarely blindsided because they have a continuous stream of qualitative data about how people are actually doing.

One-on-one meetings also surface systemic issues. When three different engineers independently mention that deployments are painful, that is a signal you would never get from a sprint retrospective where social pressure encourages consensus. The 1:1 aggregates private observations into useful signal, and that is something no other meeting format can replicate.

1:1 Meeting Structure

A good 1:1 meeting structure balances flexibility with consistency. You want enough structure that the conversation is productive, but not so much that it feels like a checklist. The following framework works well for a standard 30-minute weekly 1:1 and can be scaled up for longer sessions. Many engineering management frameworks emphasise the importance of a repeatable structure that still leaves room for the unexpected.

Opening Check-in (3–5 minutes)

Start with a genuine, open-ended question: "How are you doing?" or "What is on your mind this week?" Resist the urge to jump straight into an agenda. The first few minutes set the tone. If someone walks in stressed about a production incident or distracted by a personal issue, you need to know that before diving into career goals. The check-in also signals that you see the person, not just the employee.

Some managers use a simple energy or mood rating - "On a scale of one to five, where are you this week?" - as a lightweight way to track trends over time. This is especially useful for spotting gradual declines that neither of you might notice in the moment.

Their Topics (10–15 minutes)

The 1:1 belongs to your direct report. Their topics come first. Encourage them to add items to a shared document before the meeting - a running Google Doc or Notion page works well - so you both arrive prepared. Common topics include blockers they need help removing, feedback they want to share or request, ideas they want to test, frustrations they need to vent, and career questions they are mulling over.

Your role during this section is primarily to listen. Ask clarifying questions. Reflect back what you hear. Resist the impulse to immediately solve every problem - sometimes people need to think out loud, and your job is to create space for that. When action is needed, help them identify the next step rather than taking it yourself.

Your Topics (5–10 minutes)

After their items, bring your own. This might include context from leadership that affects their work, feedback on something you have observed, a heads-up about an upcoming organisational change, or a stretch opportunity you think they would be well suited for. Keep this section purposeful - if you have nothing pressing, give the time back to them or use it for a deeper conversation on one of their topics.

This is also a natural place to share broader team or company context. Engineers often feel disconnected from decisions made above their level. Translating leadership priorities into language that is relevant to their daily work - and being transparent about what you know and what you do not - builds trust and reduces the anxiety that comes from information vacuums.

Action Items and Wrap-up (2–3 minutes)

End every 1:1 by reviewing what was discussed and explicitly stating any action items - for both of you. Write them down in your shared document. This takes sixty seconds and dramatically increases follow-through. Start the next 1:1 by reviewing those actions. Nothing erodes trust faster than a manager who agrees to do something and then forgets.

If the conversation was particularly heavy - a performance concern, a personal challenge, a difficult piece of feedback - take a moment to check in on how they are feeling before you close. A simple "How are you feeling about what we discussed?" can make the difference between someone leaving the meeting empowered versus anxious.

Questions to Ask

The right question at the right time can unlock a conversation that changes someone's trajectory. Below are 1:1 questions for engineering managers organised by category. You should not ask all of these in a single meeting - pick two or three that feel relevant to what is happening for that person right now.

Career Growth and Development

• What skills do you most want to develop over the next six months?
• Is there a project or responsibility on the team that you wish you were more involved in?
• Where do you see yourself in two years, and what would need to happen for you to get there?
• Do you feel like you are learning and growing in your current role? What would make it better?
• Is there someone in the company or industry whose career path you admire? What about it appeals to you?

Wellbeing and Workload

• How sustainable does your current workload feel?
• Are there any tasks you are doing that you feel are a poor use of your time or energy?
• When was the last time you felt genuinely energised by your work? What were you doing?
• Is there anything outside of work that is affecting your focus or energy right now? Only share what you are comfortable with.
• Do you feel like you can disconnect and recharge at weekends and on holiday?

Feedback

• What is one thing I could do differently as your manager that would make your work life better?
• Do you feel like you get enough feedback on your work? Is it the right kind of feedback?
• Is there a recent piece of feedback - from me or anyone else - that you are still thinking about?
• How comfortable do you feel giving feedback to your peers? Is there anything I can do to make that easier?

Project Work and Technical Challenges

• What is the biggest blocker or frustration in your current work right now?
• Is there a technical decision the team has made recently that you disagree with? I would like to hear your perspective.
• Are there any areas of the codebase or system that worry you from a reliability or maintainability standpoint?
• Do you feel like you have enough context on why we are building what we are building?

Team Dynamics and Collaboration

• How would you describe the team's morale right now? What is driving that?
• Is there anyone on the team you would like to collaborate with more, or differently?
• Do you feel like your contributions are visible and recognised by the broader team?
• If you could change one thing about how the team works together, what would it be?
• Are there any interpersonal dynamics that are making your work harder than it needs to be?

Keep a note of which questions resonate and which fall flat for each person. Over time you will build a personalised repertoire that reliably opens up meaningful conversation. If you want a ready-made set to work from, the Notion templates for engineering managers include a question bank organised by theme and seniority level.

Cadence and Logistics

Weekly vs Biweekly

The default cadence for engineering manager 1:1 meetings should be weekly. Weekly meetings create a rhythm that builds trust quickly, keeps problems small, and ensures feedback is timely. When you meet every week, no single meeting carries too much weight - if one session is light, that is fine, because there is always next week.

Biweekly meetings can work for senior engineers with whom you have an established, high-trust relationship. The risk with biweekly cadence is that one cancellation means a full month without a 1:1, and that is long enough for issues to fester. If you move to biweekly, pair it with a lightweight async check-in mid-week - a brief Slack message asking "Anything you need from me?" can bridge the gap.

For new team members - whether they are new to the company or new to your team - weekly is non-negotiable for at least the first three months. The onboarding period is when trust is most fragile and when the engineer is most likely to have questions, frustrations, and uncertainties they will not raise in a group setting.

Skip-level 1:1s

If you manage managers, schedule skip-level 1:1s with their direct reports on a monthly or quarterly basis. These serve a different purpose from the regular 1:1 - they give you visibility into team health, provide engineers with a secondary channel for concerns, and help you calibrate your managers. Be transparent with your managers about these meetings and their purpose. A skip-level should never feel like a secret audit.

In skip-level meetings, focus on the engineer's experience rather than project specifics. Good questions include: "Do you feel like you are getting the support you need from your manager?", "Is there anything about how the team operates that you would change?", and "Do you feel like your career development is being actively supported?"

Remote and Async Considerations

For distributed teams, 1:1 meetings over video call are the norm, and they can be just as effective as in-person meetings if you are intentional about it. Keep your camera on. Minimise distractions - close Slack, put your phone away. If you are visibly multitasking, you are telling your direct report that they are not important enough for your full attention.

Async 1:1s - where both parties write updates in a shared document and discuss asynchronously - can supplement but should not replace synchronous meetings. The spoken conversation catches nuance, emotion, and spontaneity that text cannot. However, an async written component is valuable as preparation: having both parties add topics to a shared document before the meeting ensures the synchronous time is spent on discussion, not on remembering what you wanted to talk about.

If you are managing across time zones, protect the 1:1 slot even if it means meeting outside your ideal hours occasionally. Rotating the inconvenience - rather than always making the remote engineer accommodate your schedule - demonstrates respect and equity.

Logistics That Matter

Schedule 1:1s at consistent times each week. Avoid Monday mornings (people are still context-switching into the week) and Friday afternoons (energy is low and follow-up is delayed by the weekend). Tuesday through Thursday, mid-morning or early afternoon, tends to work best.

Use a shared running document - not separate notes per meeting. Over months, this document becomes an invaluable record of growth, recurring themes, and commitments made. It is also an excellent input for performance reviews, promotion cases, and career conversations.

Common Mistakes

Even well-intentioned engineering managers fall into patterns that undermine their 1:1s. Recognising these pitfalls is the first step to avoiding them.

Cancelling Frequently

This is the most damaging mistake and the most common. Every cancelled 1:1 sends a message: "Something else is more important than you." Once is understandable. Twice is a pattern. Three times and the engineer stops bringing real topics because they have learned the meeting is unreliable. If you have a genuine conflict, reschedule within the same week - do not simply cancel and assume you will catch up next time. If you find yourself regularly unable to protect 1:1 time, that is a signal that your own calendar management needs attention, or that you are managing too many people. Consider working with a personalised coaching session to address the root cause.

Turning the 1:1 into a Status Update

"So, what are you working on?" is the default question of a manager who has not prepared. It turns the 1:1 into a verbal standup, which wastes the most valuable synchronous time you have with your direct report. Status updates belong in standups, Jira, or async written updates. The 1:1 is for the things that cannot be said in a group setting: career anxieties, interpersonal tensions, honest feedback, and personal challenges.

If your direct report defaults to status updates, gently redirect: "I can see the project updates in our tracker - what I really want to know is how you are feeling about the work, and whether there is anything you need from me." Over time, they will learn that the 1:1 is a different kind of space.

Talking Too Much

A useful rule of thumb: your direct report should be speaking for at least 70% of the meeting. If you find yourself monologuing - explaining strategy, providing context, giving advice - pause and ask a question instead. The 1:1 is their meeting. Your job is to listen, ask thoughtful questions, and contribute when your input adds genuine value. Many managers talk too much because silence feels uncomfortable. Learn to sit with a pause - it often precedes the most important thing your report will say.

No Follow-through on Action Items

Nothing destroys credibility faster than agreeing to do something in a 1:1 and then forgetting. If you commit to investigating a promotion timeline, raising a concern with leadership, or finding a stretch project for someone, write it down and do it. If circumstances change and you cannot deliver, explain why in the next 1:1. People can handle disappointment; they cannot handle being ignored.

A shared running document with an action items section is the simplest accountability mechanism. Start every meeting by reviewing the previous week's actions. This habit alone will transform the quality of your 1:1s because it creates a visible track record of follow-through - or exposes where it is lacking.

Avoiding Difficult Conversations

Some managers use the 1:1 only for pleasant check-ins and defer hard conversations - performance concerns, behavioural feedback, or career-limiting patterns - to formal review cycles. This is a disservice to the engineer. Difficult feedback delivered early, privately, and compassionately in a 1:1 is far less painful than the same feedback delivered months later in a performance review, when the behaviour has calcified and the engineer feels ambushed.

The 1:1 should be the safest place for hard truths. If you have built trust through consistency, follow-through, and genuine care, your direct report will be able to hear difficult feedback without feeling attacked. Frame it around observed behaviour and impact, not character: "In the last two code reviews, the tone of your comments seemed dismissive, and I noticed the junior engineers stopped asking questions afterwards. I want to help you be aware of that pattern because I know it does not reflect your intentions."

1:1 Templates

Having a 1:1 meeting template removes the friction of starting from a blank page every week. Below are four template types that cover the most common scenarios engineering managers face. Each can be adapted to your style and your team's culture. For ready-to-use versions of all of these, explore the full set of Notion templates for engineering managers.

Regular Weekly 1:1 Template

This is your default template for ongoing weekly meetings with established direct reports. It should be a running document - not a fresh page each week - so that context accumulates over time.

• Mood / energy check: A simple scale (1–5) or open-ended prompt. Track this over time to spot trends.
• Their topics: Space for the engineer to add items before the meeting. Encourage them to write at least one item 24 hours in advance.
• Your topics: Space for your items - context from leadership, feedback, opportunities, or follow-ups from previous conversations.
• Action items: Clearly stated with owners and due dates. Reviewed at the start of the following meeting.
• Notes and reflections: A freeform area for capturing key themes, quotes, or observations that will be useful for performance reviews later.

First 1:1 with a New Direct Report

The first 1:1 sets the tone for the entire relationship. Use this template to establish expectations, learn about the person, and build initial rapport. Plan for a longer session - 45 to 60 minutes - and let them know in advance that this meeting will be different from a regular 1:1.

• Get to know them: Background, what they enjoy about engineering, what drew them to the team, how they prefer to receive feedback, what they need from a manager to do their best work.
• Share about yourself: Your management style, your values, what you expect, what you are still working on as a leader. Vulnerability here sets the tone for openness.
• Working preferences: Communication style (Slack vs email vs in-person), preferred feedback cadence, response time expectations, working hours boundaries.
• Establish the 1:1 format: Walk through how you run 1:1s, the shared document, who owns the agenda, and how action items are tracked.
• Early goals: What does success look like in their first 30, 60, and 90 days? What support do they need to get there?

Career Conversation Template

Run a dedicated career conversation at least once per quarter - separate from the regular 1:1. This should be a 50-minute session focused entirely on growth, aspirations, and development planning. These conversations are central to many engineering management frameworks and should be treated with the same rigour as a technical design review.

• Reflection: What has gone well since the last career conversation? What has been challenging? What have they learned about themselves?
• Aspirations: Where do they want to be in one to two years? Has that changed since last time? What is driving the change?
• Strengths and growth areas: What are they naturally good at? Where do they need to stretch? How do their self-perceptions compare with the feedback they have received?
• Development plan: Two to three specific actions they will take before the next career conversation. These should be concrete and time-bound: "Lead the next architecture review by end of Q2" rather than "Get better at system design."
• Support needed: What do they need from you, from the team, or from the organisation to make progress?

Performance Check-in Template

Use this template when you need to address performance concerns or prepare for a formal review cycle. It is more structured than a regular 1:1 and focuses on observable behaviours, measurable outcomes, and agreed-upon next steps.

• Context and purpose: Be clear about why this conversation is happening. "I want to talk about some patterns I have noticed and make sure we are aligned on expectations."
• Observed behaviours: Specific examples with dates and context. Avoid generalisations. "In the last sprint, two of your pull requests were submitted without tests, and both caused regressions" is far more useful than "Your code quality has dropped."
• Impact: Explain the impact of the behaviours on the team, the project, or the individual's own growth.
• Their perspective: Ask for their view. There may be context you are missing - personal challenges, unclear expectations, tooling issues, or competing priorities.
• Agreed actions: Clear, measurable actions with a timeline. "For the next two sprints, all pull requests will include tests, and we will review progress together in two weeks."
• Support plan: What will you provide to help them succeed? Pairing sessions, reduced scope, additional context, or mentoring from a senior colleague.

If you are navigating a particularly complex performance situation or preparing for a difficult conversation, the leadership accelerator programme provides structured frameworks and hands-on practice for these scenarios.