I was hired before I could speak German, and that CV would be filtered out today

My German was good enough to order bread. It was not good enough to defend an idea.

There is a room in Germany I still think about, an interview I had no business sitting in. No local network, and an accent that made every sentence take longer than it needed to. Everything on paper said no. Somebody in that room said yes anyway.

Sixteen years of building software have happened since. Four ambassador titles, earned honestly. None of it exists if one person had not looked past a file that told them not to bother.

Before you read another line, do one thing for me. Think of the person who said yes to you before you had earned it. You have one. Almost everybody does.

• A manager who ignored the years-of-experience line.
• A lead who took your strange side project seriously.
• Someone who let you into a room you were not qualified for.

Now look at the last five people your team passed on.

What I read this week

A thread is going around from experienced developers, and the title does all the work: Juniors are valuable, and not hiring them is a mistake.

Underneath it, hundreds of people describing the same market:

• Five years of experience and nobody calls back.
• One big company on the CV and that is somehow held against you.
• Early-career developers sending applications into a silence so complete it feels personal.

On the other side, teams that would swear they are hiring, quietly filtering out everyone who does not arrive fully formed. Both rooms are familiar to me. I have been in each.

Nobody hires you for what you already know

Here is the plain opinion. Argue with it.

A team refusing to hire juniors is borrowing speed from next year and calling it discipline. The reasoning always sounds responsible:

• "We are lean."
• "We have no time to teach."
• "We need someone who ships on day one."

Every one of those sentences is true in the moment it is said. That is what makes them so easy to keep saying, quarter after quarter, until the team is five senior people who all already agree with each other.

Watch what happens to that team. Nobody asks why anymore. Everybody knows why. The reason a thing works the way it works stopped being a question years ago, and now it is furniture. A config nobody touches. A service nobody opens. A rule everybody follows without being able to say where it came from.

The person who breaks that open is the person who does not know yet.

When I arrived, my German was too poor to be polite. So the questions came out directly, in the clumsiest possible shape, because the softer version of the sentence was beyond my vocabulary:

• Why does this run twice?
• Who owns this?
• What happens when it fails at night?

Half the time the answer was obvious and I looked like a fool. Half the time nobody in the room knew. That second half is what a junior gives you, and there is no way to buy it from someone senior.

Seniority is partly the ability to stop noticing. A real skill. Also how a codebase quietly rots while everyone competent nods at it.

What it cost the person who hired me

Nothing on their scorecard went up that quarter. They took on someone who needed correcting. Someone whose written German had to be read twice. Someone who would take longer to do a thing they could have finished themselves in an afternoon.

They did it anyway. Kindness was probably not the reason. My guess is they were doing arithmetic over years while everyone around them did arithmetic over months.

That is the whole disagreement, and it never sounds like one. It sounds like a person saying "we need someone who can ship immediately," and another person saying "yes, and also we need to be a team that still knows how to teach in three years." Only one of those two shows up in this quarter's numbers.

Ready was never real

Here is the part nobody puts in the conference talk. Sixteen years in, with the titles and the enterprise work and the clients, things still sit unpublished on my desk. The waiting-to-feel-ready reflex never left. Ready has not once arrived, not at year one, not at year sixteen. The only thing that changed is that moving without it got easier.

Which means the version of me who got hired - the one with the unfinished degree and the borrowed vocabulary - was never less ready than the version writing this. He was less experienced. A different word, and hiring keeps confusing the two.

If applications are going into silence for you right now, nobody should pretend that is fair, because it is not. But the file is not you. It was not me either. Someone eventually read past mine, and sixteen years have gone into being worth that.

And if you are the person deciding, you are allowed to be the one who says yes early. It will cost you a quarter. It might make you a team that still knows how to think in five years.

Your turn

Who said yes to you before you had earned it, and what did it cost them?

If this was useful

I work through this in public, the wins and the freezes both, mostly on LinkedIn and YouTube. If the real version of building in the open is useful to you, that is where it lives. Find me on X, GitHub, and the work at next8n.com.