The Art of 1:1 Meetings with Engineers

Research consistently shows that frequent, high-quality 1:1s correlate with higher engagement, lower turnover, and stronger team performance. For engineers, they're a rare opportunity to share what's working, raise concerns, and get coaching in a private, focused setting.

But here's the challenge: managers often don't see the full picture. Without data, they rely on gut feel, Slack messages, or the few interactions they have in sprint ceremonies. AI-powered insights help close that gap by giving managers and engineers a shared, objective view of what's happening across code contributions, reviews, incidents, and collaboration patterns.

Not all 1:1s should follow the same script. The best engineering managers adapt their approach based on what each engineer needs at that moment. Here are five proven formats:

Career Growth 1:1s

Focus: Long-term development, skill building, and promotion preparation.

Structure:

• Review progress toward career goals set in previous conversations
• Discuss new skills or technologies they want to explore
• Identify stretch assignments or mentoring opportunities
• Map out concrete steps for the next level promotion

Ideal frequency: Monthly or quarterly for goal-oriented conversations.

Example questions: "What skills do you want to develop in the next six months?" "What would need to be true for you to feel ready for senior engineer?"

Tactical 1:1s

Focus: Current sprint, active projects, and immediate blockers.

Structure:

• Review work in progress and upcoming priorities
• Address any blockers or dependencies
• Discuss technical decisions and trade-offs
• Align on expectations and deadlines

Ideal frequency: Weekly during intense project phases.

Example questions: "What's your biggest concern about the current sprint?" "Is there anything you need from me to unblock the payment integration?"

Skip-Level 1:1s

Focus: Broader team health, process feedback, and organizational perspective.

Structure:

• Understand how the team is functioning from their perspective
• Gather feedback on leadership effectiveness
• Discuss company direction and strategy
• Address concerns they might not raise with their direct manager

Ideal frequency: Quarterly for senior managers; monthly for VPs.

Example questions: "How effectively is the team communicating?" "What would you change about our current development process?"

Feedback 1:1s

Focus: Performance discussions, both positive recognition and improvement areas.

Structure:

• Share specific, recent examples of strong performance
• Address areas for improvement with concrete suggestions
• Discuss impact of their work on team and business goals
• Set clear expectations going forward

Ideal frequency: As needed, typically after major milestones or when issues arise.

Example questions: "Your code review on the authentication service prevented a security issue — that attention to detail is exactly what we need." "I've noticed PRs taking longer to get reviewed lately — let's talk about how to improve that."

Check-in 1:1s

Focus: General well-being, work-life balance, and team satisfaction.

Structure:

• How they're feeling about work and team dynamics
• Any personal or professional challenges affecting their work
• General feedback on processes, tools, or team culture
• Opportunity to raise topics they want to discuss

Ideal frequency: Bi-weekly as a regular rhythm.

Example questions: "How are you feeling about your workload lately?" "What's going well on the team? What could be better?"

The key is intentionally choosing the right format for the right moment. A tactical 1:1 during a critical launch isn't the time for career development. A feedback 1:1 shouldn't turn into a status update session.

Even well-intentioned managers fall into predictable 1:1 traps. Here are the most common mistakes and how to avoid them:

Mistake #1: Turning 1:1s into Status Updates

The trap: "What did you work on this week? What are you working on next week?"

Why it's problematic: This information already exists in standups, Jira, and GitHub. You're wasting precious face time on data you could get elsewhere.

The fix: Use async standup data to prepare, then focus on interpretation, coaching, and strategy during the meeting.

Mistake #2: Dominating the Conversation

The trap: Using 1:1 time to download information, share updates, or give lengthy explanations.

Why it's problematic: The 1:1 is their time, not yours. When managers talk too much, engineers stop engaging.

The fix: Aim for a 70/30 split — they should talk 70% of the time. Ask questions, then listen.

Mistake #3: Avoiding Difficult Conversations

The trap: Sticking to safe topics and avoiding performance issues, interpersonal conflicts, or challenging feedback.

Why it's problematic: Problems don't resolve themselves. Avoiding hard conversations erodes trust and lets issues fester.

The fix: Address problems early when they're still manageable. Use specific examples and focus on behavior and impact.

Mistake #4: Inconsistent Scheduling

The trap: Canceling 1:1s when things get busy or treating them as optional.

Why it's problematic: Inconsistency signals that the engineer isn't a priority. It breaks trust and reduces engagement.

The fix: Protect 1:1 time. If you must reschedule, do it proactively and suggest alternative times.

Mistake #5: Flying Blind Without Context

The trap: Walking into 1:1s without reviewing recent work, team dynamics, or performance patterns.

Why it's problematic: Generic questions lead to generic answers. Without context, you miss opportunities to coach effectively.

The fix: Spend 10-15 minutes before each 1:1 reviewing their recent contributions, standup patterns, and any notable events. Come prepared with specific questions.

Great 1:1s start with great preparation. Here's a systematic approach:

Review Recent Activity (10 minutes)

• Pull requests: What have they shipped recently? Any complex technical decisions?
• Code reviews: Are they participating actively? Quality of feedback?
• Standup patterns: Any blockers, mood shifts, or engagement changes?
• Meeting participation: How engaged are they in planning, retros, and team discussions?

Check Goal Progress (5 minutes)

• Current quarter goals: Are they on track? Any obstacles?
• Career development: Progress on skills, certifications, or promotion criteria?
• Previous 1:1 commitments: Did they follow through on what they committed to?

Identify Conversation Topics (5 minutes)

Based on your review, choose 2-3 specific topics:

• Recent wins worth celebrating
• Challenges or blockers you want to discuss
• Growth opportunities or stretch assignments
• Feedback (positive or constructive) based on recent work
• Process improvements or team dynamics issues

Prepare Specific Questions

Generic: "How's it going?"
Specific: "I noticed you spent extra time on the authentication PR review — what made that one particularly complex?"

Generic: "Any blockers?"
Specific: "You mentioned the API dependency in standup three times this week. Have you been able to connect with the platform team yet?"

The difference between good and great 1:1s often comes down to how specific and contextual your questions are.

Some engineers naturally share openly in 1:1s. Others need more coaxing. Here are strategies for getting meaningful engagement from quieter team members:

Start with Recent Work

"I was looking at your work on the caching layer — can you walk me through the approach you took?" Technical discussions often feel safer than personal topics and can build momentum for deeper conversation.

Use Data as Conversation Starters

"I noticed your code review responses have been getting more detailed lately — what's driving that?" Data removes the guesswork and gives you specific, objective talking points.

Ask About Process, Not Feelings

"What's working well with our current sprint structure?" is easier to answer than "How are you feeling?" Process questions feel safer but often reveal underlying satisfaction or frustration.

Give Them Think Time

Some engineers need time to process questions. Ask a thoughtful question, then wait. Count to 10 if you need to. Don't fill the silence immediately.

Share Your Own Observations First

"I've noticed you've been taking on more of the complex database optimization work lately, and the performance improvements have been significant. How are you feeling about diving deeper into that area?"

Leading with positive observations creates psychological safety for them to share their perspective.

Focus on Their Interests

"What's the most interesting technical problem you've worked on lately?" Engineers who are quiet about personal topics often open up about technical challenges they find engaging.

Give Them Homework

If they're consistently quiet, try: "Think about one thing we could improve as a team and come prepared to discuss it next time." This gives introverted engineers time to prepare thoughts in advance.

Remember: some engineers genuinely prefer concise, focused conversations. Not everyone needs to share extensively to be engaged and productive.

Daily standups generate a wealth of data that most managers underutilize. Here's how to mine standup responses for 1:1 conversation starters:

Blocker Patterns

If someone mentions similar blockers across multiple days, that's a 1:1 topic: "I noticed you've been blocked on API access for three days. Let's figure out how to escalate this more effectively."

Language and Sentiment Shifts

Pay attention to how people describe their work:

Positive momentum: "Making great progress on..." "Excited to tackle..."
Stagnation: "Still working on..." "Trying to figure out..."
Frustration: "Dealing with..." "Stuck on..."

Engagement Levels

Compare current standup responses to their typical pattern:

• Shorter responses might indicate disengagement or overload
• Detailed technical explanations might suggest they're excited about the work
• Generic responses ("working on tickets") often signal they're not feeling challenged

Project Enthusiasm Indicators

Notice which projects generate detailed updates and which get generic mentions. This tells you what work energizes them versus what feels like a chore.

Cross-Team Dependencies

When someone repeatedly mentions waiting on other teams, that's your cue to help remove organizational blockers.

Using Vereda AI for Deeper Insights

Vereda AI analyzes standup data automatically and surfaces patterns you might miss:

• Sentiment trending: "Alex's engagement has declined 20% over the past two weeks"
• Blocker analysis: "Sarah has mentioned authentication issues in 4 of her last 6 standups"
• Collaboration patterns: "Mike's responses suggest he's working more independently lately"

This gives you specific, data-backed conversation starters rather than vague check-ins.

Learn more about how Vereda AI's 1:1 prep transforms standup data into actionable insights.

Manual 1:1 preparation is time-consuming and inconsistent. You might remember to review recent work for one engineer but forget to check goal progress for another. Vereda AI systematizes this process:

Automated Context Gathering

Before each 1:1, Vereda AI pulls together:

• Recent standup responses with sentiment analysis
• Pull request activity and code review participation
• Progress toward current quarter goals
• Any flagged concerns from burnout detection
• Themes from previous 1:1 notes

Conversation Starter Generation

Based on the data, AI generates specific talking points:

"Alex shipped three significant features this sprint and has been actively mentoring junior developers in code reviews. Consider discussing:

• Recognition for the mentoring work
• Interest in more formal tech lead responsibilities
• Feedback on the complexity of recent features"

Pattern Recognition

AI identifies trends across multiple data points:

"Sarah's standup sentiment has declined while her code output remains strong. This pattern often indicates process frustration rather than capability issues. Consider asking about:

• Current sprint planning effectiveness
• Team communication satisfaction
• Tools or process improvements she'd recommend"

Goal Tracking Integration

For career development conversations, AI connects recent work to stated goals:

"Mike's goal was to improve system design skills. Recent work shows increased involvement in architecture discussions and detailed PR comments on design decisions. Discussion points:

• Feedback on recent design contributions
• Next-level architecture challenges to consider
• Potential conference talks or blog posts to share learnings"

Follow-up Reminders

AI tracks commitments made in previous 1:1s and reminds you to check progress:

"In your last conversation, Lisa committed to shadowing customer support calls to better understand user pain points. It's been three weeks — worth checking on progress and learnings."

Custom Question Suggestions

Based on the engineer's role, seniority, and recent patterns, AI suggests targeted questions:

For senior engineers: "What technical debt should we prioritize next quarter?"
For junior engineers: "What's been most challenging about the new codebase?"
For engineers showing signs of disengagement: "What type of problems do you most want to solve?"

The result: every 1:1 is prepared, personalized, and purposeful. You spend your time having meaningful conversations instead of scrambling to remember what everyone is working on.

As engineering work becomes increasingly distributed and complex, relying solely on anecdotal feedback is no longer enough. AI-powered insights turn 1:1s into data-informed coaching sessions that are both human and precise.

When managers and engineers come to the table with a shared understanding of recent work patterns, successes, and pain points, they can spend less time reconstructing what happened—and more time shaping what happens next.

The next evolution of 1:1s will be:

• More strategic: Less time on status, more time on growth and development
• More personalized: Conversations tailored to each engineer's working style and career goals
• More proactive: Addressing challenges before they become problems
• More data-informed: Objective insights complementing subjective feedback

The best engineering managers will combine the irreplaceable human elements — empathy, coaching, and relationship building — with AI-powered insights that ensure no important pattern goes unnoticed.

For related reading, check out our guide on spotting burnout signals and learn about using data for more effective performance reviews.