I hired a “junior” developer last year who outperformed three “seniors” within her first month.
She had no computer science degree. No five years of experience at a FAANG company. No impressive LinkedIn title. What she had was an obsessive curiosity, a GitHub profile full of creative side projects, and the ability to look at a complex problem and see the elegant solution hiding inside it.
Meanwhile, I watched a “Senior Lead Architect” at a client company spend six weeks building something that should have taken six days because nobody had ever questioned whether his title matched his ability. His resume was flawless. His output was not.
This is the problem with job titles in tech. And it is killing your hiring.
The Label Factory
Somewhere along the way, the tech industry decided that career progression looks like a ladder with three rungs: junior, medior, senior. Sprinkle in some “lead” and “principal” for seasoning, and you have got a system that tells you absolutely nothing about what someone can actually do.
Here is what these labels actually measure:
- Time served. Two years? Junior. Five years? Medior. Eight years? Senior. As if sitting in a chair for a decade automatically makes you good at your job.
- Interview performance. Can you whiteboard a binary tree inversion? Congratulations, you are now a senior engineer. Never mind that you have never shipped a product.
- Negotiation skills. The developer who asks for the senior title gets it. The one who quietly builds brilliant things stays “medior” forever.
None of this measures what matters: can this person solve the problem you actually have?
The Real Cost of Title-Based Hiring
When you filter candidates by title, you are not finding the best people. You are finding the people who are best at accumulating titles. These are not the same thing.
Every time you write “5+ years experience required” in a job posting, you are telling a brilliant career-switcher with two years of obsessive coding that they are not welcome. You are telling the self-taught developer who can run circles around your team that their knowledge does not count.
I have seen this play out hundreds of times:
- A “junior” React developer who had built and shipped three production apps on her own, rejected because the client wanted “senior only.”
- A “senior” Java developer with twelve years of experience who could not explain dependency injection in plain language.
- A “medior” DevOps engineer who had single-handedly migrated an entire company to Kubernetes, but his title did not reflect it because his employer had a strict promotion policy.
- A “lead” who got the title because he was the loudest person in the room, not because anyone actually wanted to follow him.
The labels are not just inaccurate. They are actively harmful. They create a false sense of certainty that makes hiring managers lazy and candidates anxious.
Skills Over Stamps
What if instead of asking “what is your level?” we asked “what have you built?”
This is not a radical idea. It is common sense that the industry has somehow forgotten. A developer’s ability is demonstrated by:
- Their portfolio. Show me the code. Show me the deployed product. Show me the pull request that fixed a gnarly bug at 2 AM.
- Their problem-solving approach. Give them a real problem, not a LeetCode puzzle, and watch how they think.
- Their communication. Can they explain what they built and why? Can they argue for a technical decision without getting defensive?
- Their learning velocity. How fast do they pick up something new? This matters more than what they already know, because what they already know will be outdated in three years.
This is harder than scanning a resume for keywords. It requires you to actually evaluate people as individuals instead of sorting them into boxes. But the payoff is enormous: you find people others miss, and they tend to be fiercely loyal because you were the first company that saw them for what they actually are.
How We Do It at InitLabs
When we started InitLabs, we made a deliberate decision: no labels. We do not categorize our professionals as junior, medior, or senior. We refuse to.
Instead, we evaluate every person on what they can actually do. We look at their work, we challenge them with real scenarios, and we build a profile based on demonstrated skills, not years on a clock. When we present someone to a client, we say: “This person can do X, Y, and Z. Here is the proof.” Not: “This person is a senior.”
We call our professionals Pioneers, because that is what they are. People who forge their own path, who do not fit neatly into a spreadsheet, and who deliver results that no label could have predicted.
Is it harder to sell? Sometimes. Some hiring managers want the comfort of a title. But the ones who trust the process? They end up with better teams, lower turnover, and the quiet satisfaction of knowing they hired the right person, not the right resume.
Job titles in tech are dead. The companies that figure this out first will win the talent war. The rest will keep hiring expensive labels and wondering why their teams underperform.
Your move.