Work-life balance for software engineers usually breaks in a few predictable places: on-call shifts that spill into your nights, deadlines that turn into weeks of overtime, remote work with no clear end to the day, and a workload that keeps growing because nobody pushes back. The fixes are mostly specific agreements with your team and your manager, not generic self-care tips.
This guide takes each of those pressure points in turn, covers how to spot burnout early, and gives you scripts for negotiating your workload.
On-call without wrecking your sleep
On-call is part of many engineering jobs, and when it’s run well it’s a manageable part. When it’s run badly, it’s often the biggest single source of exhaustion on a team.
Google’s SRE book gives a useful reference point. Its chapter on being on-call caps on-call at no more than 25% of an SRE’s time, and it estimates that two incidents per 12-hour shift is the most an engineer can handle properly, because each incident includes investigation, the fix, and the postmortem afterward. Your company doesn’t have to follow Google’s rules, but these figures are a solid anchor when you need to argue that a rotation is overloaded.
Before your shift:
- Get a handoff from the previous on-call engineer: open issues, flaky alerts, anything still in progress.
- Check that you can reach runbooks, dashboards, and production tools from wherever you’ll be.
- Arrange swaps early around travel, appointments, and family events. PagerDuty’s guide to being on-call recommends sorting these out ahead of time and making sure pages can get through your phone’s do-not-disturb settings.
During your shift:
- Escalate early. The same PagerDuty guide’s motto is “Never hesitate to escalate.” Struggling alone at 3 a.m. helps nobody.
- Write short notes as you go, so the handoff is easy and the postmortem doesn’t depend on your memory.
After a bad night:
- Agree on a team norm that whoever was paged overnight starts late or takes the time back. Google, for example, offers time off in lieu or cash compensation for on-call work.
- Don’t let overnight pages become normal. If an alert fires and nobody needs to act on it, it shouldn’t page anyone. Track pages per shift and bring the numbers to your retro so noisy alerts get fixed or deleted.
When you interview for a new job, ask about on-call directly: how many people are in the rotation, how many pages a typical week brings, and whether on-call is compensated. The answers tell you a lot about the team. These interview tips for your first remote job cover more questions worth asking.
Deadlines without permanent crunch
First, separate real deadlines from targets. A contract date, a launch event, a legal requirement, or a marketing campaign that’s already paid for is a real deadline. A date someone picked in a planning meeting is a target, and targets can move.
When a deadline is at risk, scope is usually the only lever that moves quickly. Adding people late rarely helps, and longer hours wear the team down. So turn “can you just push a bit harder?” into a choice:
“To hit the 15th, we can ship the checkout flow and the receipts and move saved cards to the next release. If saved cards have to be in, we need until the 29th. Which matters more?”
That isn’t refusing. It hands the decision to the person who owns the priority, with the trade-off in plain view.
If a short crunch really is necessary, agree on two things before it starts: when it ends, and how much recovery time follows. Crunch without an end date isn’t crunch anymore. It’s the new normal.
Prevention is cheaper than recovery. Break work down before you estimate it, add explicit time for testing and integration, and flag risk on the day you see it, not the week before the deadline.
Burnout: know the signs early
The World Health Organization describes burn-out as a syndrome resulting from chronic workplace stress that hasn’t been successfully managed. It has three dimensions: exhaustion, growing mental distance from or cynicism about your job, and reduced professional efficacy. WHO classifies it as an occupational phenomenon, not a medical condition, which is a useful reminder that the causes usually sit in the work itself.
In engineering, those three dimensions often look like this:
- Exhaustion: dread on Sunday evenings, needing the whole weekend just to recover, a jolt of stress at every chat notification.
- Cynicism: sarcastic code review comments, a sense that nothing the team does matters, no interest in technology you used to enjoy.
- Reduced efficacy: small tasks taking all day, rereading the same code without taking it in, no longer caring whether the work is good.
If you recognize several of these for weeks rather than days, act early:
- Tell your manager plainly what’s happening and, if you know, what’s causing it.
- Take real time off, with the laptop closed and notifications off, not a “vacation” where you check messages twice a day.
- Ask to step out of the on-call rotation or a high-pressure project for a while.
- Talk to a doctor or a mental health professional if symptoms persist or affect your sleep, mood, or health. This article isn’t medical advice.
Boundaries in remote work
Remote work removes the commute and the office door, which used to mark the end of the day. You have to rebuild those boundaries on purpose.
- Publish your hours. Put your working hours in your calendar and chat profile so colleagues know when to expect replies.
- Agree on response times. Most messages don’t need an answer within minutes. Ask your team to agree on what counts as urgent and how to reach someone for it, so everything else can wait.
- Take work apps off your phone when you’re not on-call, or at least silence them outside your hours.
- Use a shutdown routine. Write down tomorrow’s first task, close every work tab, and shut the laptop. If you can, work in a different spot from where you relax.
Being clear about when you’re available is also basic remote work etiquette, and most teams appreciate it.
Time zones need their own agreement. If you work from Southeast Asia for a company in Europe or the US, it’s easy to end up available for both your morning and their afternoon, which turns into a workday with no real end. Negotiate a fixed overlap window of a few hours, keep the rest of your day for focused work, and ask for recurring meetings to rotate so the awkward time slot isn’t always yours. More habits like this are in 10 habits for thriving in remote work.
Negotiating your workload
“I’m too busy” rarely changes anything. A visible list and a clear question usually do.
- Make the work visible. List everything you’re committed to, with rough sizes. Include the invisible work: reviews, interviews, support questions, on-call.
- Ask for a priority call, not sympathy. Bring the list to your 1:1 and ask your manager to rank it.
- Bring evidence. Hours in meetings, pages per on-call shift, interruptions per day. Numbers from your own calendar are hard to argue with.
- Offer options. Suggest what could be dropped, delayed, or handed to someone else.
A script for when new work lands on a full plate:
“Happy to take on the reporting migration. Right now I’m on the API rewrite and the auth bug backlog, and both are already tight for this sprint. If the migration is the new top priority, which of those should slip?”
If nothing changes after a few honest conversations, the problem is structural, not personal. At that point your options include raising it with your manager’s manager, moving to another team, or finding a company whose pace suits you better. None of those is a failure.
Habits that protect your time
- Block two or three focus sessions a week on your calendar and treat them like meetings.
- Check chat in batches instead of keeping it open in front of you all day.
- Decline meetings that have no agenda, or ask for one first.
- Plan vacations with a written handoff so you can actually disconnect.
- Protect the basics: sleep, movement, and time with people who have nothing to do with your job.
FAQ
Is regular overtime normal for software engineers?
Occasional extra hours around a launch or an incident happen on most teams. Regular overtime, week after week, usually points to a planning or staffing problem rather than a personal one. Treat it as something to raise with your manager, not something to quietly absorb.
Should on-call be paid?
Practices vary widely between companies and countries. Some pay a stipend per shift, some give time off in lieu, and some include it in salary. Check your contract and local labor rules, and ask about it before you accept an offer, while you’re in the strongest position to negotiate.
Will taking time off hurt my career?
Taking the leave you’re entitled to, with a clean handoff, rarely hurts anyone’s career. Burning out and doing poor work for months does. If your team treats normal time off as a lack of commitment, that tells you something important about the team.
Your next step
This week, write down your working hours and put them in your calendar and chat profile. Then pick the one thing from this article that drains you most, whether it’s noisy alerts, a fuzzy deadline, or an overloaded sprint, and bring it to your next 1:1 with a specific proposal. Fixing one real problem does more for your balance than a list of good intentions.