"How to run effective 1-on-1 meetings with engineers"

"Effective engineering 1-on-1s follow three rules: they belong to the engineer (not you), they focus on people issues (not project status), and they happen weekly without exception. Ask open-ended questions like 'What's frustrating you right now?' and 'What would make your work easier?' instead of 'How's the sprint going?' Listen for energy changes, repeated frustrations, and things they're not saying. Cancel a 1-on-1 three times and you've told your engineer their growth doesn't matter to you."

How to Run Effective 1-on-1s With Your Engineers: What to Ask and What to Actually Listen For

Here’s what most engineering managers’ 1-on-1s look like: “How’s the sprint going? Any blockers? Cool, see you next week.” That’s not a 1-on-1. That’s a standup with one person.

The 1-on-1 is the single highest-leverage meeting on your calendar. It’s where you learn that your best engineer is thinking about leaving before they start interviewing. It’s where you catch a team dynamic problem before it becomes a team-destroying problem. It’s where you build the trust that makes everything else — feedback, delegation, hard conversations — possible.

But only if you do it right.

Rule 1: It’s Their Meeting, Not Yours

The 1-on-1 belongs to the engineer. They set the agenda. If they don’t have an agenda, that’s information too — either they don’t trust you enough to bring real issues, or things are genuinely fine (rare, but possible).

Stop bringing your list of questions and project updates. If you need a status update, read the standup notes or check the board. The 1-on-1 is for the stuff that doesn’t fit in any other meeting: career goals, frustrations, team dynamics, ideas they’re not confident enough to share publicly, and feedback they have for you.

I tell every engineering leader I work with: if you’re talking more than 30% of the time in a 1-on-1, you’re doing it wrong.

Rule 2: People Topics, Not Project Topics

I keep two lists in my head for every 1-on-1. The first is the list of things I want to ask about: how the engineer is feeling about their work, their growth, their teammates, and the direction of the team. The second is the list of project questions I’m tempted to ask — and I actively resist asking them.

Project questions kill 1-on-1s. The moment you ask “where are we on the API migration,” the engineer shifts into reporting mode. They tell you what they think you want to hear. The vulnerability disappears.

Instead, try these:

“What’s the most frustrating thing about your work right now?”
“Is there anything you’ve wanted to tell me but haven’t?”
“What would make your day-to-day easier?”
“Do you feel like you’re learning and growing here?”
“If you could change one thing about how the team works, what would it be?”

These questions feel uncomfortable at first. Good. Comfortable 1-on-1s are useless 1-on-1s.

Rule 3: Weekly, Non-Negotiable

I’ve heard every excuse. “We’re in a crunch, let’s skip this week.” “I see them in standup every day, we don’t need a separate meeting.” “I have eight direct reports, I can’t do weekly with everyone.”

If you have eight direct reports and can’t do weekly 1-on-1s, you have too many direct reports. That’s a span-of-control problem, not a scheduling problem. Fix it.

Canceling 1-on-1s sends a clear message: your growth and concerns are less important than whatever else I have going on. Cancel three times in a row and your engineer has already started updating their resume. They won’t tell you that in the 1-on-1 you eventually get around to having. They’ll tell you in their resignation letter.

Thirty minutes, every week, same time. Move it if you must, but never skip it.

What to Listen For

The most important information in a 1-on-1 isn’t in the words. It’s in the patterns.

Energy shifts. An engineer who was excited three weeks ago and is now flat is telling you something. Don’t wait for them to say “I’m unhappy.” Ask: “You seem less energized than a few weeks ago. What’s going on?”

Repeated frustrations. If someone mentions the same problem three 1-on-1s in a row, it’s not a passing annoyance — it’s a retention risk. Either fix it or have an honest conversation about why you can’t.

What they’re not saying. If an engineer never brings up career growth, it doesn’t mean they’re content. It might mean they’ve given up on growing at your company. If they never give you feedback, it doesn’t mean you’re a perfect manager. It means they don’t trust you enough to be honest.

“Everything’s fine.” This is the most dangerous response in a 1-on-1. Sometimes it’s true. More often, it’s a wall. Probe gently: “If everything’s fine, what’s the thing that’s closest to not being fine?”

The Hard Conversations

1-on-1s are also where you deliver difficult feedback. Not in Slack. Not in a group meeting. Not in an annual review six months after the behavior you’re addressing.

When an engineer’s performance is slipping, the 1-on-1 is where you say so — directly, specifically, and with enough time for a real conversation. “I’ve noticed the last three PRs had significant issues caught in review. What’s going on?” is a very different conversation than “your Q3 review rating is below expectations.”

The former gives them a chance to tell you they’re burned out, dealing with a personal issue, or struggling with a new technology. The latter gives them a rating.

Keep Notes

After every 1-on-1, spend two minutes writing down the key points. Not a transcript — just the signals. “Mentioned frustration with code review turnaround for the second time.” “Asked about promotion timeline.” “Seemed disengaged when discussing the platform project.”

These notes are invaluable during performance reviews, when making promotion decisions, and when you need to have a difficult conversation backed by specific observations rather than vague impressions.

The best engineering managers I’ve worked with treat their 1-on-1 notes as their most important management artifact. Not the sprint board, not the velocity chart — the notes from their conversations with their people.