Burnout Doesn't Look Like What You Think

I wasn't exhausted or disengaged. I was performing well and shipping on time. But I'd stopped caring about the craft — and that was the warning sign I missed.

For six months, I was the model engineering lead. I hit every deadline, attended every meeting, and kept the team running smoothly. From the outside, everything looked fine.

The Subtle Signs

I stopped reading technical blogs. I stopped experimenting on weekends — not because I was resting, but because nothing excited me. Code reviews became mechanical: approve, approve, approve. I was optimizing for throughput, not quality.

What Triggered the Realization

A junior engineer showed me a creative solution to a problem I'd dismissed as "not worth the complexity." I felt annoyed instead of excited. That reaction scared me.

What Helped

I took two weeks off — genuinely off, no Slack, no "just checking in." Then I made structural changes: blocked two afternoons per week for exploration (no meetings, no PRs), started pair programming again, and said no to one recurring meeting that added no value.

The Bigger Lesson

Burnout in senior roles doesn't always look like burnout. It looks like efficiency. You're so good at going through the motions that nobody notices — including you — until the joy is completely gone.

If you've stopped being curious, that's the signal. Don't wait for exhaustion to validate what you already know.