Five Mental Shifts That Turn Juniors Into Seniors
One engineer. Five near-misses. One quiet transformation.
Eight months ago, I got a message.
“I’m a junior engineer with over three years of experience. I think I’m ready for promotion, but I don’t know how. Can you help me?
-Ramesh”
That was the first version.
Then we got on a call, and the second version came out.
“I’ve been quietly killing myself doing the right things, and I’m starting to suspect the wrong people keep winning.”
He wasn’t wrong.
But he wasn’t exactly right either.
My initial read?
Methodical. Quiet. Sharp.
The kind of engineer who’d fix the ugliest part of your system and never mention it out loud.
He had a career ladder bookmarked—the kind with seven tiers, three dimensions, and a paragraph per bullet. Perhaps built by a committee of principal engineers who sincerely believe in adjectives. I don’t know. But I remember it like that.
He said things like “cross-functional influence” and “end-to-end ownership.”And meant them.
He’d fixed bugs no one saw coming.
Onboarded new hires.
Gave away credit in Slack and didn’t secretly want it back.
He could tell you exactly what “senior” meant according to the chart.
And still, nothing was moving.
Because nowhere in that chart did it say what to do when someone who shipped less—and with worse quality—got promoted faster.
Here’s what happened last week:
Ramesh got promoted.
But this isn’t the story of how he nailed it.
It’s the story of how he almost didn’t.
Because Ramesh already knew what senior engineers were supposed to do. He just wasn’t doing it. Not really.
Knowing what to do doesn’t mean jack if you’re looking through the wrong lens.
Here’s how to think about it:
Two mechanics are staring at the same engine.
One sees hoses and clamps and bolt torque.
The other sees pressure.
Where it’s building.
Where it’s leaking.
Where it’s about to blow.
Same engine. Different eyes.
Ramesh could recite the parts.
But pressure?
That wasn’t on his radar.
Not yet.
This is the story of five moments.
Not where he failed.
Not where he succeeded.
But where he almost stayed still.
Five mindset shifts.
Junior to senior.
Here’s how it started.
One
“It wasn’t my fire.”
Wednesday, 6 or 7 p.m.
“Hey, you got time?”
He was pacing. I could hear it in his voice.
“How’s your week?” I asked.
“Long.”
A pause.
“Our tech lead’s out. Something he ate. There was a thing in prod yesterday—billing, of course.”
“You involved?”
“Nah. Not really. It was someone else’s thing. A bunch of people were on it.”
A little laugh. Dry.
“You ever watch ten smart people talk themselves in circles?”
“You knew the system?”
“I cleaned up part of the retry logic a few months ago. That thing never got documented. I knew where the logs were.”
But that was it.
No follow-up.
No “so I helped.”
“You didn’t step in?” I asked.
“Wasn’t mine.”
Then, quicker:
“Didn’t want to step on anyone.”
I let him sit with it.
Then:
“Ever seen someone watching a house on fire from across the street?”
“No. But… sure.”
“They’re not screaming. They’re not calling anyone. They’re just watching. You know why?”
“Because it’s not their house.”
“Exactly.”
“You think I should’ve jumped in.”
“I think you knew where the hose was. And you stood on the curb.”
The silence after that was different.
He wasn’t pacing anymore.
“I didn’t want to step on anyone. That’s all.”
“Maybe.
Or maybe you didn’t want to be wrong.”
Then:
“Are you the kind of guy who waits to be asked? Or the kind who notices and takes action?”
He didn’t answer.
But on Friday, he messaged:
“Pushed a patch. It worked.”
Two
“They don’t need me to say it.”
Next month. Zoom call. Same tension hiding under the surface.
“They dropped observability from the sprint,” he said.
“PM said it’s not a priority.”“You agree?”
“Doesn’t matter. I’m not going to win that argument.”
“I didn’t ask if you’d win.”
He didn’t respond.
I waited.
Then:
“We lost three days last time because we couldn’t trace a single thing.
This time? It’s ‘not a priority.’”
I said,
“You ever see those dogs in movies. Mutts that smell the fire first?”
“What?”
“They hear something no one else does.
They pace. Bark once. Look back at the humans.
And the humans just say, ‘What is it, boy?’
Then go back to their toast.”“Okay…”
“They don’t save anyone. Not because they were wrong.
Because no one listened and they waited for a signal.
And eventually, the dog just... stops barking.”“You’re saying I’m the dog.”
“I’m saying you’ve smelled the smoke.
You just haven’t decided if you care enough to fight.”
His lips moved like he might argue.
But nothing came out.
“I could test tracing on one part of the flow,” he mumbled.
“Not for them.
Just for signal.”
The next week, he sent a screenshot:
A Slack thread.
His name buried in the middle.
The PM’s comment:
“Getting surprisingly good signal here. Might be worth rolling out.”
Ramesh didn’t add commentary. Just ✅ it.
I liked that.
Three
“I didn’t know I was the bottleneck.”
He joined the call already heated. You could feel it through the mic.
“I was actually enjoying my work this week.”
There was emphasis on was.
