A self-check framework to find out where you actually stand, not where your title says you are.
Why This Matters
I once interviewed a software engineer with over ten years of experience. Solid resume. Good communication. Then I asked him about a time he troubleshot a production incident. He paused. "I've never really done that," he said. "I've always been on the development side. Someone else handles production issues."
So I gave him a scenario. A payment service starts throwing 500s in production during peak hours. Logs show database connection pool exhaustion. Customers are stuck on the checkout page. What do you do?
He froze. Ten years of experience, and he had no instinct for it. No mental model for triage. No muscle memory for checking thread dumps, connection pool configs, or slow query logs. He'd been writing features for a decade, but the moment code left his machine and hit real users, it had always been someone else's problem.
That's not ten years of engineering experience. That's ten years of half the job. And the half he was missing is exactly the half that separates developers who write code from engineers who own systems.
He's not alone. Most engineers have a blind spot between where they think they are and where they actually are. And that gap doesn't just hurt your interview performance. It hurts your career trajectory, because you end up studying the wrong things, applying for the wrong roles, and wondering why you keep getting stuck.
This post gives you a framework to close that gap. No ego. No judgement. Just a clear-eyed look at where you really stand.
The Misconception
Most people think experience equals skill. "I have 7 years of experience, so I must be a senior engineer."
Here's the thing: there's a difference between seven years of experience and one year of experience repeated seven times. If you've been doing the same type of work, in the same comfort zone, without being stretched by harder problems, your growth flatlined years ago.
Your title is given to you by a company. Your level is earned by what you can do. These two things diverge more often than you'd think.
The Title vs. Skill Gap
Let me break this down with a table. Here's what each level is supposed to look like, and the common gap I see at each one:
| Level | What the Title Implies | Where Most Engineers Actually Are | The Gap |
|---|---|---|---|
| Junior (0-2 yrs) | Can write basic code | Can copy-paste from Stack Overflow but struggles to debug independently | Understanding "why" vs just "how" |
| Mid (2-5 yrs) | Can design features well | Can build features but can't explain design trade-offs | Design thinking, not just coding |
| Senior (5-8 yrs) | Can own systems end-to-end | Can own tasks but avoids architectural decisions | System-level thinking, ownership |
| Lead (8-12 yrs) | Can make the team better | Still mostly an individual contributor with a fancy title | Influence, mentorship, multiplying output |
| Staff+ (12+ yrs) | Can shape technical direction | Can execute well but doesn't drive strategy | Vision, business alignment |
If you looked at this table and felt a little uncomfortable, that's the whole point.
The Self-Assessment Framework
Here are five questions. Be brutally honest with yourself. Nobody else needs to see your answers.
1. Can you explain your daily work to a non-technical person?
This sounds easy. It's not. If you can't explain what you do in simple terms, you might not understand it as deeply as you think. Engineers who truly understand a concept can explain it simply. Engineers who only know the surface reach for jargon.
Try this: Explain your last major project to an imaginary 12-year-old. If you get stuck, that's a signal.
2. When was the last time you were genuinely stuck?
If the answer is "I can't remember," you're either a genius or you're not pushing yourself. Growth happens at the edge of your ability. If every task feels comfortable, you've stopped growing.
| Frequency of Being Stuck | What It Means |
|---|---|
| Never | You're in your comfort zone. Seek harder problems. |
| Rarely (once a quarter) | You're coasting. Look for stretch assignments. |
| Sometimes (monthly) | Healthy growth zone. Keep going. |
| Often (weekly) | Either you're learning fast, or you might be in over your head. Check which one. |
3. Could you mass-reproduce your skills?
Imagine your company hires five new developers tomorrow. Could you write down what you know well enough that they could do your job in three months? If yes, you have structured knowledge. If not, you're running on instinct and pattern matching, which works until it doesn't.
This is the difference between a chef who can write a recipe and a cook who just "knows" when the food is done. Both make good food. Only one can scale.
4. What would break if you left tomorrow?
If the answer is "nothing," you're either very good at making yourself replaceable (which is a senior trait), or you haven't built enough ownership. If the answer is "everything," you've created a single point of failure, and that's a different problem.
The healthy answer is: "A few things would slow down for a week or two, but the team would figure it out because I've documented and shared knowledge."
5. Do you know what you don't know?
This is the most important question. At every level, there's a set of things you're expected to know and a set you're not. The problem is when you don't know what's in each set.
I've seen engineers with three years of experience stressing about Kubernetes. I've seen engineers with ten years who've never written a proper unit test. Both are misallocating their energy.
Go back to the Career Level Breakdown. Find your level. Read the "What to focus on" table. How many of those topics can you confidently explain? How many could you teach to someone else? That's your real level.
The Honest Calibration Exercise
Here's a practical exercise. Take the focus areas from your current level in the Career Level Breakdown and rate yourself:
| Rating | What It Means | Action |
|---|---|---|
| 1: Never heard of it | Completely new concept | Start from scratch. This is a critical gap. |
| 2: Heard of it | You know the name but can't explain it | Read, watch, get the basics down. |
| 3: Used it once | You followed a tutorial or copied from a project | Build something small from scratch without a guide. |
| 4: Can use it | You can work with it day-to-day | Push deeper. Learn the "why," not just the "how." |
| 5: Can teach it | You can explain it to a junior and answer their follow-ups | This is mastery. Move on to the next gap. |
Anything below a 4 on your current level's topics is a gap that needs closing before you look at the next level.
Most people overrate themselves by one full point. If you think you're a 4, test it: try explaining the concept out loud as if you're teaching someone. If you stumble, you're a 3.
The Trap of Upward Comparison
There's another pattern I see constantly. Engineers compare themselves to the most senior person on their team and feel inadequate. Or they compare themselves to people posting on social media and feel behind.
Stop doing that. Your only useful comparison is: "Am I better than I was six months ago?"
If you are, you're on the right track. If you're not, something needs to change: your projects, your learning approach, or your comfort zone.
What to Do After This Assessment
Here's the straightforward playbook:
If your skills match your title: Great. Start looking one level ahead. Pick one or two topics from the next level and start exploring.
If your skills are below your title: No shame in that. Most people are here. Go back to the level that matches your actual skills and fill in the gaps. It's faster to build a strong foundation than to keep patching holes at a higher level.
If your skills are above your title: You might be ready for a bigger role, or you might be in an environment that's not stretching you. Either way, start documenting your impact. Titles follow demonstrated capability, not the other way around.
Key Takeaways
- Your title is what a company gave you. Your level is what you can actually do. These two things are often different.
- Growth isn't about years of experience. It's about years of being challenged, stretched, and forced to learn new things.
- Rate yourself honestly on the focus areas for your level. Anything below a 4 is a gap worth closing.
- The most dangerous place to be is comfortable. If you haven't been stuck in months, you've stopped growing.
- The only comparison that matters: are you better than you were six months ago?
If you haven't already, use the Career Level Breakdown as your map. Find your real level, focus on the gaps, and build from there.
This post is part of my Engineering Career Roadmap series. Follow me for the next post on what got you promoted and why it won't work again.
Connect with me on LinkedIn
Top comments (0)