Most advice on this topic tells you to "be honest with your manager" and "frame it as a performance concern." That advice is not wrong. But it skips the part that actually makes this hard: in tech, saying you are struggling can feel like career risk. Here is a more honest guide.
There is a reason most engineers do not talk to their managers about burnout. It is not that they do not know they should. It is that the cost of saying "I am not okay" feels disproportionately high — especially when layoffs are in the news, performance reviews are coming up, or they are on a team that rewards resilience and punishes vulnerability.
The standard advice — "be proactive," "frame it as a business problem," "come with solutions" — assumes a level of psychological safety that many engineers simply do not have. So before we get to the how, let us be honest about the why this is hard.
Why engineers do not speak up
Tech culture rewards pushing through. Saying you are struggling can feel like admitting weakness.
Performance reviews are tied to perception. You do not know how this will land.
Layoff anxiety makes vulnerability feel dangerous. Now is not the time to seem less capable.
Your manager may not be safe. Not every manager responds with empathy.
You are not sure it rises to the level of "a conversation." You keep thinking it will pass.
If any of those resonate, you are not being irrational. These are real dynamics. Acknowledging them does not mean you should stay silent — it means the conversation requires more care than "just be honest."
Step 1 — Know what you are actually asking for
Before the conversation, get clear on what you need. Not the feeling — the ask. "I am burned out" is a feeling. "I need to reduce my on-call rotation for the next sprint" is an ask. "I am overwhelmed" is a feeling. "I need to remove two projects from my plate this quarter" is an ask. The more specific your ask, the easier the conversation is for both of you — and the less it sounds like a complaint and more like a solvable problem. If you do not know what you need yet, that is okay. But try to identify at least one concrete change that would help.
Step 2 — Assess your manager before you open up
Not every manager is safe to be vulnerable with. Before you have this conversation, honestly assess: Has your manager responded with empathy when others have raised concerns? Do they separate performance from wellbeing? Do they have a track record of actually changing things when someone raises an issue, or do they acknowledge it and move on? If the answer to these is mostly no, you may need a different approach — raising it more neutrally, going to HR, or addressing the structural issues without framing it as burnout specifically.
*Step 3 *— Pick the right moment and the right framing
Do not have this conversation in a rushed 1:1 or right before a deadline crunch. Ask for dedicated time: "I want to talk about my workload and capacity — can we carve out 30 minutes this week?" This signals it is important without creating alarm. When you open the conversation, lead with impact on work, not personal distress. Not: "I am really struggling and feeling overwhelmed." But: "I have noticed my ability to do deep work has been declining, and I want to address it before it affects delivery." Both are true. The second framing is easier for a manager to respond to constructively.
Step 4 — Be specific about what has changed
Vague burnout is hard for a manager to act on. Specific burnout is actionable. Instead of "I am just exhausted," try: "Since taking on the platform migration on top of my regular sprint work, I have been working until 9pm most nights and I am noticing my decision quality is dropping." The more you can point to concrete changes — in workload, in output quality, in how you are showing up — the easier it is for your manager to understand what has shifted and what might help.
Step 5 — Come with one or two possible solutions
You do not need to solve it yourself — that is partly what the conversation is for. But coming with one or two ideas shows you are thinking constructively and not just offloading. "One thing that might help is removing me from the on-call rotation for the next two weeks" or "I think if we could move the platform migration timeline by three weeks, I could do both things well instead of both things badly." Managers respond better to options than to open-ended distress.
Step 6 — If you cannot say it, write it first
Some people find it easier to write out what they want to say before saying it. A short email before the meeting — "I wanted to give you some context before we talk" — can reduce the pressure of having to articulate everything in real time. It also creates a record. If vulnerability in person feels too exposed, starting in writing is not avoidance. It is preparation.
What if your manager does not respond well?
It happens. Some managers are not equipped to handle this conversation. Some will minimize it. Some will respond with action items that miss the point entirely. If that happens, it is not a reflection of the validity of what you raised. Your options include: going to HR, going to your manager's manager, seeking support outside work while you figure out a longer-term plan, or — if the environment is fundamentally unsafe — starting to look elsewhere.
But do not let the fear of a bad response be the reason you say nothing at all. Silence has its own cost. And the cost compounds over time.
The conversation is hard. But burnout that goes unaddressed does not resolve itself. It builds quietly — until it shows up in your code quality, your relationships, your health, or your resignation letter. Speaking up earlier, even imperfectly, is almost always better than waiting until you have nothing left.
Recharge (https://rechargedaily.co) is a private AI burnout coach for tech workers. It helps you track how you are doing over time — so when you do have this conversation, you have patterns and data, not just feelings. Try it free for 14 days →
Top comments (0)