What this archetype means
You believe good work should speak for itself. It does not, because the people making decisions about your career are not reading your pull requests - they are reading a document your manager wrote from memory. This is the most common and most fixable pattern in engineering.
Your strength
You have substance. Everything you need for the promotion case already exists - it just has not left your machine.
The risk
You will watch people with weaker work get the visible projects, and it will feel like the system is rigged. It is not; it is that the record is missing.
Three moves that change this
-
Report outcomes, not tasks
"Notification failures dropped from 4% to 0.2%" is a fact, not a boast. Send it when work lands.
Talking about achievements without bragging → -
Speak in the first ten minutes
One specific point early, tied to a number. The longer you wait, the higher your own bar gets.
Speaking up in meetings → -
Keep a weekly impact log
One line per meaningful piece of work. Reconstructing a year in December is impossible and you will undersell yourself.
Building the promotion case →