Member-only story
Why Senior Java Engineers Never Become Staff Engineers (Even When They’re Better)
He knew Spring Boot, Kafka, PostgreSQL, and Kubernetes better than anyone on the team. The engineer who got promoted asked him one question he couldn’t answer.
Daniel had been a Senior Java Engineer for eight years when his manager told him he wasn’t ready for Staff.
The conversation lasted twenty-three minutes. Daniel had spent the previous eleven months fixing production incidents, reviewing difficult pull requests, mentoring junior developers, and keeping a collection of Spring Boot services alive through several releases that probably should have been postponed.
His performance review was excellent. His promotion request was rejected. The part that bothered him wasn’t the rejection itself. It was that Sarah, another Senior Engineer with considerably less experience, had been promoted to Staff Engineer that same morning.
Daniel knew more Java than Sarah. He understood Hibernate internals, could diagnose PostgreSQL lock contention without opening Stack Overflow, and had once fixed a Kafka consumer rebalance problem while the rest of the team was still arguing about whether restarting Kubernetes would help.
