The Engineer's Guide to Getting Value from 1-on-1 Meetings

What and Why

A 1-on-1 is a recurring private meeting between you and your manager. It is the single most underused tool in most engineers’ careers. Used well, it is where your career trajectory, scope, and visibility are quietly shaped. Used badly, it is thirty minutes of status that could have been a Slack message.

The point of a 1-on-1 is not to update your manager on what you are doing. They can read tickets. The point is to surface what they cannot easily see: where you are stuck, where you want to grow, and what is silently broken on the team.

Mental Model

Think of the 1-on-1 as your meeting, not your manager’s. You own the agenda. Your manager is there to unblock you, give you context you do not have, and help shape your growth. If you do not bring topics, the meeting drifts to status by default, and you waste your most direct line to someone with more information and influence than you.

A useful mental split: half the meeting is operational (what is stuck, what do you need), and half is strategic (growth, scope, feedback, future). If you only do operational, you are renting attention. If you only do strategic, real problems fester.

Hands-on Example

A simple, reusable 1-on-1 agenda template:

 1-on-1 (30 min)
     |
     +-- 5 min: Wins & blockers
     |       What shipped, what is stuck
     |
     +-- 10 min: One real topic
     |       (rotate weekly)
     |        - team dynamic question
     |        - design decision I'm
     |          unsure about
     |        - cross-team friction
     |
     +-- 5 min: Growth / feedback
     |       "What is one thing I should
     |        do differently?"
     |       "Where do you see me in 6 mo?"
     |
     +-- 5 min: Their topics
     |       Things they want to raise
     |
     +-- 5 min: Action items
            Captured in shared doc

Keep a shared running document with your manager. Each meeting becomes a new section at the top: agenda, notes, actions. After three months you have a written record of your growth, your conversations, and your commitments. That document is gold at promotion time.

A strong opener: “Two wins from last week: shipped X, helped Y unblock Z. One blocker: I am uncertain about the data model in project A, can we talk through it?” That sets the tone for a working meeting, not a status meeting.

Common Pitfalls

• Treating it as status: tickets exist. Use the meeting for things that need real conversation.
• Saving feedback for review season: feedback delivered six months late is almost useless.
• Venting without asking: complaints without a question or proposal feel like noise.
• Skipping it when busy: cancelling 1-on-1s during crunch is exactly when you need them most.
• Never asking your manager about their pressures: knowing their context makes you more effective.

Practical Tips

Send the agenda 24 hours in advance. Even three bullets is enough; it signals seriousness and lets your manager prepare. End every meeting with one explicit ask, even small: “Can you connect me with the platform team lead?” or “Can you nudge the PM about the spec?” Asks turn meetings into actions. Once a quarter, dedicate a full 1-on-1 to growth: career goals, level progression, blockers. Do not skip it. When asking for feedback, ask specifically: “In the last design review, what could I have done better?” beats “Any feedback?” by a mile. And keep notes; memory fades, written commitments do not.

Wrap-up

A great 1-on-1 culture is not your manager’s job to create. It is yours. The engineers who get the most out of 1-on-1s treat them like the most important thirty minutes of the week, because over a long enough horizon they are. Bring real topics, capture decisions, ask for specific feedback, and follow through on what you promise. Do that for a year and you will look back at the running doc and see your own growth in writing — and so will the people deciding your next level.