Remote Team One on One Meeting Template for Engineering Managers with Direct Reports

Engineering managers overseeing remote teams face a unique challenge: building genuine connection and providing meaningful guidance without the benefit of in-person interactions. A well-structured one-on-one meeting template becomes your primary tool for maintaining engagement, catching issues early, and helping your direct reports grow professionally.

This guide provides a template you can implement immediately, along with the reasoning behind each section and practical code snippets for automating meeting prep.

The Core One-on-One Template Structure

Effective remote one-on-ones follow a consistent structure that balances multiple objectives: career development, project updates, blockers removal, and relationship building. Here’s a template that works for engineering managers:

Pre-Meeting Async Check-In (Sent 24 Hours Before)

## Pre-1:1 Async Check-in

**Quick status (bullet points):**
- What did you accomplish this week?
- What are you working on next?
- Any blockers or concerns?

**Discussion topics I want to cover:**
1.
2.
3.

**Anything you want me to prepare or look at before our call?**

This async pre-check transforms your one-on-one from a status meeting into a strategic conversation. Your direct report comes prepared with specific topics, and you arrive knowing exactly what matters most.

The Meeting Agenda (30-45 Minute Call)

1. Quick Wins & Progress (5 min)
   - Celebrate completed work
   - Connect sprint work to bigger picture

2. Current Challenges & Blockers (10 min)
   - Technical obstacles
   - Resource constraints
   - Dependencies blocking progress

3. Career Development Discussion (10 min)
   - Growth goals for this quarter
   - Skills to develop
   - Feedback for me as your manager

4. Team & Project Context (5 min)
   - Cross-team coordination
   - Upcoming milestones
   - Any concerns about team dynamics

5. Open Discussion (5-10 min)
   - Anything on your mind
   - Unexpected topics

Question Framework for Engineering Managers

Generic questions produce generic answers. Use specific, open-ended questions tailored to engineering contexts:

For Technical Blockers

Instead of “Any blockers?” try:

“What’s the most frustrating technical problem you solved this week?”
“Is there any infrastructure or tooling issue slowing you down?”
“Which dependency or external service is causing the most pain?”

For Career Development

Instead of “How’s your career going?” try:

“What technical skill do you want to develop most in the next 6 months?”
“Are there any projects outside your current scope you’d like to explore?”
“What’s one thing I could do differently to better support your growth?”

For Team Dynamics (Remote-Specific)

“Do you feel you have enough context about what other team members are working on?”
“Are there any communication gaps with other teams or stakeholders?”
“How can I help make async communication work better for you?”

Automating Meeting Prep with Scripts

Reduce administrative overhead with a simple automation script that pulls relevant data before each meeting:

#!/usr/bin/env python3
"""Pre-1:1 meeting preparation script for engineering managers."""

import os
import json
from datetime import datetime, timedelta
from github import Github

def prepare_one_on_one(direct_report_github_handle):
    """
    Gather relevant data before a one-on-one meeting.
    """
    g = Github(os.getenv("GITHUB_TOKEN"))
    user = g.get_user(direct_report_github_handle)

    # Get recent pull requests
    prs = list(user.getPullRequests(state='all',
                                     sort='updated',
                                     direction='desc')[:10])

    # Get recent commits
    commits = list(user.getCommits()[:5])

    # Build the async check-in template
    template = f"""## Pre-1:1 Async Check-in for {datetime.now().date()}

### Recent Activity
- **{len(prs)} PRs** reviewed/created recently
- **{len(commits)} commits** pushed this period

### Your Reflection
**What did you accomplish this week?**

_Your answer here_

**What are you working on next?**

_Your answer here_

**Any blockers or concerns?**

_Your answer here_

### Discussion Topics
1. _Add your topics here_
2.
3.

### Anything you want me to prepare?
"""
    return template

if __name__ == "__main__":
    # Usage: python prepare_1on1.py github_username
    import sys
    if len(sys.argv) > 1:
        print(prepare_one_on_one(sys.argv[1]))
    else:
        print("Usage: python prepare_1on1.py <github_username>")

This script generates a personalized check-in template by pulling your direct report’s recent GitHub activity. Run it the day before your one-on-one and send the output to your direct report.

Handling Different Experience Levels

Your template should adapt based on who’s sitting () across from you:

For Junior Engineers (0-2 years)

Add explicit “learning goals” section
Include questions about onboarding experience
Ask about mentorship needs
Discuss technical fundamentals regularly

For Mid-Level Engineers (2-5 years)

Focus on technical depth and breadth
Discuss mentorship opportunities (giving back)
Explore specialization vs. generalist paths
Career progression clarity

For Senior Engineers & Staff (5+ years)

Leadership and influence topics
Architecture and technical strategy
Cross-team impact
Career options (IC vs. management track)

Async One-on-One Alternative

When time zones make synchronous meetings difficult, implement an async one-on-one using a shared document:

# Async 1:1 - [Name] - [Month/Year]

## This Period's Review

**Accomplishments:**
-

**Challenges:**
-

**Growth Focus:**
- What's working?
- What needs adjustment?

## Manager Feedback

**What I'm noticing:**
-

**What's going well:**
-

**Areas for development:**
-

## Discussion Items

| Topic | Status | Notes |
|-------|--------|-------|
| Topic 1 | 🔲 Open | |
| Topic 2 | 🔲 Done | |

Set a weekly cadence where both parties write their sections asynchronously. Schedule a 15-minute synchronous call only when specific topics require real-time discussion.

Common Pitfalls to Avoid

The status meeting trap: If your one-on-ones feel like status updates, you’re doing it wrong. Save status for standups or Slack updates. One-on-ones should be strategic, not operational.

The always-scheduled trap: Following the same agenda every week leads to autopilot. Rotate questions, focus on different themes each month, and leave room for unexpected topics.

The manager-dominated conversation: If you’re talking more than 30% of the time, your direct report isn’t getting value. Your role is to ask questions and listen.

Skipping async prep: Without the pre-check, you waste meeting time on basic updates. The 10 minutes spent on async prep saves 20 minutes of meeting time.

Measuring One-on-One Effectiveness

Track these signals to assess if your one-on-ones are working:

Retention: Are your direct reports staying on your team?
Engagement: Do they seem prepared and interested in meetings?
Growth: Are they progressing in skills and responsibilities?
Feedback: Do they give you honest feedback about your management?

If these metrics decline, your one-on-ones need adjustment.

Implementation Checklist

Schedule consistently: Same day/time each week, protected from other meetings
Send async prep 24 hours before: Use the template above
Start with wins: Brief celebration builds positive momentum
End with open space: Leave 5-10 minutes for unexpected topics
Follow up in writing: Send a brief summary of action items after each call
Iterate quarterly: Review and adjust your approach based on feedback

A well-executed one-on-one template transforms a simple meeting into your most powerful management tool. The consistency builds trust over time, and the structure ensures nothing important falls through the cracks.

Built by theluckystrike — More at zovo.one