Three Years In: My Honest Career Audit—and the Checklist That Saved Me from Drifting
職場心得
2026.07.12
匿名
I hit the three-year mark as a front-end engineer last month. And let me tell you—it felt nothing like the milestone I'd imagined.
When I first traded my chef's knife for a keyboard, I thought three years would be some golden moment. I'd be crushing pull requests, mentoring juniors, maybe even leading a project. Instead, I found myself staring at a Jira board, feeling like a fraud. Same salary bumps as my second year. Same tech stack. Same vague uncertainty about whether I was actually moving forward or just spinning wheels.
Sound familiar? The three-year mark is weird. You're no longer a newbie, but you're not a senior. You've got enough experience to know what you don't know—and that can be paralyzing. That's why I decided to run a personal career audit. Not a performance review from my manager, but an honest, no-BS inventory of where I stood. What I found surprised me—and it might help you too.
Why Three Years? The "Drift Zone"
I call year three the "drift zone." You've lost the survival adrenaline of year one, and you haven't hit the impact pressure of year five. It's easy to coast—to keep doing what you're doing because it's comfortable, even if it's not growing you.
I know because I drifted. Between year two and three, I stopped pushing. I picked up tickets, closed them, went home. No side projects. No learning new frameworks. No networking. My code worked, but my career stalled.
The wake-up call came when a recruiter reached out for a role I should have been perfect for—and I bombed the technical screen. Not because I lacked skills, but because I'd been using the same patterns for 18 months straight. I'd stopped reading, stopped building, stopped being curious. That rejection stung, but it lit a fire.
So I sat down with a notebook and asked myself seven hard questions. Here's the checklist I now use (and teach) at every three-year checkpoint.
The Three-Year Career Audit Checklist
1. Am I still learning, or just repeating?
Look at your last 12 months of work. Be honest: have you learned a new concept, a new pattern, a new tool that genuinely expanded how you think? Or have you been solving the same problems with the same solutions?
I failed this one hard. I'd been writing React components the same way since 2020. I hadn't touched TypeScript deeply. I hadn't bothered with testing beyond what my team required. When I finally cracked open a modern testing library, I felt like I'd been working with one hand tied behind my back.
Action: If you can't name three things you learned this year that changed how you work, you're repeating. Pick one skill (testing, state management, accessibility) and go deep for 30 days.
2. Does my salary reflect my market value?
I know, talking money feels awkward. But three years is the perfect time to check. You've proven you can stick with a company and deliver. According to levels.fyi and Glassdoor, front-end engineers with 3 years of experience see a median salary jump of 15-25% when they switch jobs. But if you never check, you'll never know.
I didn't check. I assumed my annual 3-5% raises were "normal." When I finally asked a friend in a similar role at another company, I discovered I was underpaid by nearly 20%. That conversation hurt my pride—but it saved my bank account.
Action: Research 5 comparable roles on salary sites. If you're below the 50th percentile, start a conversation with your manager. If they can't adjust, update your resume.
3. What's my relationship with failure?
Here's the thing about cooking: you fail in public. A sauce breaks, a steak overcooks, and the table sees it. When I moved to code, I initially hid my mistakes. I'd spend hours debugging alone before asking for help. That approach worked until I hit a bug that cost my team two sprint days.
By year three, I'd learned to wear my failures differently. I started writing post-mortems for myself—not to assign blame, but to capture what I'd learned. One of my biggest career breakthroughs came from a failed interview. I recorded the questions I couldn't answer, studied them, and six months later crushed a similar interview.
Action: Write down your biggest professional mistake this year. Next to it, write one concrete thing you now do differently because of it. If you can't find a lesson, you haven't processed the failure—you've just buried it.
4. Am I building relationships, not just tickets?
When I was a line cook, the kitchen was a hierarchy—you respected the head chef, kept your head down, and worked. In tech, I carried that same introverted mindset. I thought coding well was enough. It wasn't.
At the three-year mark, the people who advance aren't always the best coders—they're the ones who are known. The ones who review PRs thoughtfully, who answer questions in Slack, who show up for lunch-and-learns. I realized I'd been invisible. My code was fine, but no one knew who I was.
Action: Set a goal to have one coffee chat per month with someone outside your immediate team. Contribute to a cross-team project. Write a short internal blog post. Visibility isn't vanity—it's career oxygen.
5. Is my work meaningful to me?
This is the most dangerous question because you might not like the answer. After three years, the novelty of "I'm a developer!" wears off. If the only thing keeping you going is the paycheck, that's okay—but you need to know it now, not five years in when burnout hits.
For me, the meaning came from building tools that helped real people. I'd left cooking because I wanted to create, not just execute. But in year three, I was stuck maintaining a dashboard that three people used. That realization led me to volunteer for a project that supported small businesses. The code wasn't sexy, but the impact was.
Action: Write down what made you proud this year. If that list is empty, ask yourself: do you need a new role, a new team, or a new career? Be honest—it's cheaper than therapy.
6. What's my technical debt—personally?
Yes, personal technical debt. Outdated skills, bad habits, shortcuts that became crutches. I had personal tech debt all over: I didn't understand the build tools we used, I'd never written a proper integration test, I avoided performance profiling because it felt hard.
Just like code debt, personal tech debt compounds with interest. The longer you ignore it, the harder it is to fix.
Action: Pick one area where you're relying on luck (e.g., "I've never dealt with Webpack config" or "I can't explain React reconciliation"). Schedule two hours this week to close that gap. A focused deep dive beats a year of shallow scrolling.
7. Where do I want to be at year five?
I asked this and drew a blank. I had a vague idea—"senior engineer"—but no specifics. Year five is coming faster than you think. Do you want to be a tech lead? A staff engineer? A manager? A freelancer? The answer doesn't have to be set in stone, but you need a direction.
I decided I wanted to be the engineer who could explain complex ideas simply—the person junior devs went to for clarity. That goal shaped my next two years: I started writing, mentoring, and speaking at internal meetups. It wasn't a straight line, but it was a compass.
Action: Write a one-sentence description of your ideal work in two years. Then list three things you can start now to move toward it. Don't overthink—just pick one action and do it this week.
What I Found After My Audit
After going through this checklist, I realized I wasn't as stuck as I thought. Yes, I was underpaid and had ignored some technical gaps. But I also had a solid foundation: I could deliver, I collaborated well, and I genuinely cared about the craft. The audit gave me a roadmap, not a verdict.
I negotiated a raise (and got it). I spent three months improving my testing skills. I started a blog to practice explaining concepts. I'm not at year five yet, but I'm no longer drifting. The checklist didn't fix everything overnight—but it stopped me from waking up at year five wondering where the time went.
If you're at the three-year mark, don't wait for your manager or a recruiter to give you a wake-up call. Do the audit. It's uncomfortable, but so is being stuck.
And hey—if you're reading this and you've been cooking with JavaScript for three years, you're not alone. We all drift sometimes. The trick is to notice before the current takes you too far.
This article originally appeared on my blog. I'm an ex-chef turned front-end engineer, and I write about the practical side of career transitions—including the failures.
