This September, I’ll have been doing this for three years. And I still don’t know exactly when I stopped being a junior developer. Three years of code reviews, stand-ups, pull requests, production bugs that keep you awake at night, and conversations that start with, “So… I was looking at your code.”

Three years of learning things I never knew I’d need. In teams I’d never worked with before, using tools I’d never even touched.

The question nobody warned me about

When you start your first job, the junior label feels temporary. It’s something you wear until you know enough. Then you take it off and replace it with a new one: mid-level. Senior. Whatever comes next.

What nobody tells you is that you never actually feel that transition happen. You don’t wake up one morning thinking, “Right. Today I’m no longer a junior developer.” No achievement pops up.

You just keep going. Then one day someone asks you a question, and you answer it without opening Stack Overflow first. Only later do you realize that the moment had already passed.

Four projects, the same fear

I’m a consultant, which means I don’t stay on the same team forever. I move around. New client, new team, new codebase, new tools, a new overly complicated Confluence setup… you get the idea.

I’m currently on my fourth project. And there’s something I want to admit. Every single time, I was nervous before I started.

Where you think: “This team uses tools I’ve never seen before. Their stack looks completely different from the last one. Everyone here has years of context that I don’t have. What if I can’t keep up?”

Four projects. Four times, exactly the same fear. And four times, exactly the same outcome.

It was fine. Not “fine” as in I understood everything during the first week. Fine because I asked the right questions. Because I read the documentation. Because I broke things safely before breaking anything important. And somewhere around week three or four, I stopped wondering whether I could keep up. I was just… working.

That’s probably the pattern I never expected. Not that the fear disappears. But that you start trusting how quickly you can learn.

What I’ve actually learned in three years

Not a list of technologies. Not a collection of certifications. Mostly this.

How to start from zero and become useful faster than you expect. How to find your way through an unfamiliar codebase until it finally starts making sense. How to ask questions that lead to real answers instead of just hearing, “Check the docs.”

And how to know when to spend another twenty minutes figuring something out yourself, and when asking for help is simply the smarter choice. I’ve also learned how big the difference is between: “I don’t know this yet.” and “I’ll never figure this out on my own.”

That second category turns out to be much smaller than I used to think.

The label problem

What bothers me about the whole junior/mid-level/senior conversation is that it feels like a ladder you’re supposed to climb once. As if there’s a version of yourself somewhere that never feels uncertain anymore. A version that never has to start from scratch again.

I don’t think that version exists. What changes, I think, is your relationship with uncertainty.

Three years ago, I’d look at a new tool and think: “I really hope they don’t notice I’ve never used this before.” Today, the thought is more like: “Alright. How long is it going to take me to get comfortable with this?”

The tool is the same. The question is different. You stop trusting what you already know. You start trusting your ability to learn what you don’t.

I’ve done that four times now. The evidence keeps piling up. Not because I know everything now, but because I have enough past experiences to believe myself when something new feels overwhelming.

Three years later

This September marks three years. I still don’t know which label fits me. And honestly, I don’t think I care as much as I used to.

What I do know is that I’ve learned far more than I expected. And probably more than I give myself credit for. Every time I walked into a new team with that familiar knot in my stomach, there was already a small part of me that knew things would work out. Even if I didn’t fully believe it yet. Maybe that’s what experience really is. Not that uncertainty disappears. But that it stops being the loudest voice in the room.

Ask me again in three years.