One-on-ones are a career lever, not a status update
Most engineers treat their one-on-one with a manager as a slightly more formal standup: what shipped, what’s blocked, any feedback. That is a waste of one of the few recurring blocks of time you have with someone whose job partly depends on your trajectory. A one-on-one is better framed as a system design review for your role—a chance to debug friction, validate direction, and align on where you are headed, not just what you did this week.
Your manager can already see your pull requests and velocity. What they cannot see is the reasoning behind your choices, the trade-offs you are weighing, and the parts of the job that feel misaligned with where you want to go. That is the material worth bringing.
Treat growth conversations like versioning, not release milestones
Many engineers wait until promotion season to start talking about career progression. By then the conversation is reactive and limited. Growth discussions work better when they start early and run continuously—even when the next level is a year or more away.
If you are far from a promotion, use the time to find out where you already meet expectations and where you should be strengthening skills. If you are approaching the next level, shift the conversation toward what kind of work would demonstrate readiness and what opportunities would expand your scope or visibility. Treating growth as an iterative process gives you room to course-correct before formal review cycles.
A practical structure for these conversations is the Three Circles of Impact:
- Individual Contributions – the direct value delivered by your own work.
- Collaboration – how you work with and support the people around you.
- Enabling Others – mentorship, knowledge sharing, and improving systems or tooling for the team.
If you are unsure how to demonstrate impact across all three, your manager likely has ideas. But they can only guide you if they know your goals. Bring them up early and let the manager help you find the work that stretches you in those areas. The clearer your contributions map to this model, the easier it is for your manager to advocate for you when it counts.
Bring friction into the open
Managers have limited visibility into your day-to-day. Persistent blockers, unclear expectations, and time sinks are easy to absorb silently—and impossible for anyone else to fix. The one-on-one is the venue to surface them.
A useful habit is to frame these issues in terms of trade-offs rather than as a request for approval. If you are deciding whether to refactor a service now or later, present the pros and cons and ask how each path aligns with broader business goals. That converts the conversation from a status check into a decision-making session.
Consider a case where an endpoint's latency sat slightly above the SLO target. The engineer had spent a substantial amount of time optimizing, until a manager asked whether the metric itself was the problem: the latency was a consequence of system design, users were not affected, and the SLO was something the team controlled. The fix was not more performance engineering—it was revisiting the threshold. A conversation like that can save hours and reframe the problem entirely. Sometimes the issue is not in the code, but in how success is being measured.
Make the meeting work for you
Bring what is going well, what is stuck, and where you want to grow. Think about your career earlier than feels comfortable. Treat each one-on-one as a chance to shape your environment, not just report on it. Your manager is not a mind reader, and they cannot support goals you never share. You cannot expect useful guidance if you arrive without a direction of your own. Growth is a shared effort—but it begins with how you use the hour.
