title: "What 5 years of bootcamp-to-senior taught me, in 7 sentences I wish someone had said to me at year 2" slug: 'bootcamp-to-senior-7-sentences' date: '2026-04-25' excerpt: "The career arc nobody talks about clearly: what changes between mid and senior." tags: ['career', 'bootcamp', 'mentorship'] category: 'Career' published: true
Year 2 of my engineering career, somebody at Arizona State gave me feedback that took me three years to actually understand. They said: the work you do at year 5 isn't going to be the work you do now, only better. It's going to be a different job.
I nodded politely and went back to writing React components.
They were right, of course. The job at year 5 IS different. Not because the keystrokes change, but because the unit of value you produce changes — and nobody tells you the keystrokes are no longer the bottleneck.
Things I wish someone had told me at year 2, in the order I had to learn them:
-
Your code stops being the constraint around year 3. You've internalized React. You can ship a feature. The constraint moves to: did you ask the right questions before you started, did you write the docs the next person needs, did you push back on a bad spec.
-
"Senior" is a verb, not a title. It's a thing you do for people around you. The first time you watch a junior write something they wouldn't have written without your standard influencing them, you understand what the title means. Until then it's just compensation.
-
Most of the bug reports you'll get aren't bugs. They're communication failures upstream of your code. Investing time in understanding the request before writing the patch is the highest-leverage thing you can do.
-
Performance budgets are a leadership skill. Anyone can ship fast code. Setting a number, defending it across a team, and making it stick when stakeholders push back — that's something else.
-
You'll meet engineers smarter than you who can't ship. I used to find this depressing. Now I find it useful — it tells me that "smarter" was never the variable that mattered. Shipping discipline is a skill. It's learnable.
-
The thing you learn from coaching juniors is your own reasoning. I had to explain bounded queries to seven mid-levels before I understood why it mattered as deeply as I did. Teaching makes the implicit explicit.
-
The people who hire seniors aren't looking for a list of frameworks. They're looking for someone who has stopped breaking things in particular ways. Your interview answer to "tell me about a time you debugged something hard" is more important than your TypeScript score.
I'm not saying any of this is novel. I am saying that nobody at year 2 tells you these things in a way that lands. They tell you "communicate clearly" and "write good tests," and you nod, and you go write the code, because the code is the part you know how to control.
The shift to senior happens when you stop trying to control the part you already know.