From Crash Carts to Keyboard

What Night Shifts Taught Me About On-Call Rotations

3 min read

Working the overnight in a hospital prepared me for on-call engineering in ways I didn't expect. Both require calm under pressure and good handoff skills.

The first time I got paged at 2 a.m. for a production incident, my partner looked at me with genuine concern. "Are you okay?" she asked, watching me calmly open my laptop and start triaging.

I was more than okay. I'd been training for this moment for years — just in a different building.

The Night Shift Mindset

Hospital night shifts teach you something that's hard to learn any other way: how to function at your best when conditions are at their worst. The staffing is thinner. The patients are sicker. The decisions are yours because the day team is asleep.

You learn to prioritize ruthlessly. You learn that "good enough right now" is sometimes better than "perfect in an hour." And you learn that the handoff — the notes you leave for the person who takes over — is as important as the work itself.

All of this translates directly to on-call engineering.

Triage Is Triage

In the ER, triage means rapidly assessing severity and allocating resources accordingly. A sprained ankle waits. Chest pain doesn't. You don't treat them in the order they arrived — you treat them in order of urgency.

Incident response works the same way. Not every alert is a five-alarm fire. Learning to quickly assess severity — is this a minor UI glitch or is data being corrupted? — is a skill, and it's one that clinical experience sharpens.

When I'm on call now, I run through a mental version of the same rapid assessment I used in the ER: What's the scope? Who's affected? Is it getting worse? What do I need to stabilize before I can investigate?

The Art of the Handoff

The best thing night shifts taught me was how to write a good handoff. In healthcare, a bad handoff can literally endanger someone's life. You learn to be specific, structured, and honest about what you don't know.

In tech, I write incident reports and handoff notes the same way I wrote nursing shift reports: what happened, what was done, what's still pending, and what the next person should watch for.

The format is almost identical:

  • Situation: What's going on right now
  • Background: What led up to this
  • Assessment: What I think the problem is
  • Recommendation: What should happen next

Healthcare folks will recognize this as SBAR — a communication framework used in hospitals worldwide. It works just as well in a Slack thread about a database outage.

Staying Calm Isn't Natural — It's Practiced

People sometimes compliment me for staying calm during incidents. They assume it's personality. It's not. It's practice. Hundreds of night shifts where panic wasn't an option because someone needed you to think clearly.

That composure is transferable. And it's one of the most underrated skills a career changer brings to a tech team.

When the alerts are firing and the dashboards are red, having someone on the team who's been in high-pressure situations before — who knows how to breathe, prioritize, and communicate — that's not a nice-to-have. It's an asset.