I didn't end up where I planned.
I came into tech wanting to write code. I'd been self-teaching JavaScript, building small things, convinced I was headed for a developer role. Then I landed in integration engineering, configuring enterprise platforms, building workflows sending data to Salesforce Marketing Cloud, Adobe Campaign, WhatsApp Business API and then something unexpected happened.
I loved it.
Not in a "this is fine" way. In a genuinely engaged, staying late because I want to, thinking about it in the shower kind of way. The role wasn't what I'd aimed for. It turned out to be better.
So I worked hard. I learned fast. I took on enterprise clients, Ford, IKEA, H&M, Coca Cola. I got comfortable with multiple applications I never thought I'd be using two years ago. I figured out how to sit between a technical team and a client who doesn't speak tech and make both sides feel understood.
And then, somewhere in year three, something shifted.
The signal I didn't expect
The work that used to scare me stopped scaring me.
Problems that used to take me a week I can now navigate in a day. Integrations that felt impossibly complex when I started are now just... work. Familiar work. Manageable work.
That sounds like a good thing. And it is, it means I built real skill, not just time in a seat. But it also means something else: I've hit a ceiling. Not a crisis. Not burnout. A ceiling. And those are very different things.
Burnout feels like not wanting to work. A ceiling feels like wanting to work harder, on bigger things, and realizing the current container won't stretch that far.
What ready actually feels like
I'm not unhappy. I'm not resentful of the role or the company. I built something real here and I know it.
But I'm ready for:
More depth. I want to go further into the problems, not just resolve them and move on.
More ownership. I want to have a stake in decisions, not just execute them.
More challenge. The kind that requires me to grow again, not just perform what I already know.
And I'll be honest — more pay. Three years of enterprise integration experience is worth more than where I started, and I know that now in a way I didn't before.
The part that's actually hard
I know what I want the next thing to feel like. I don't know what it is yet.
DevRel? Senior integration engineering? Solutions architecture? Something I haven't named yet? I'm genuinely not sure. And the career advice industry doesn't have a lot to say about this phase. There's an enormous amount of content about breaking into tech, and almost nothing about what to do when you've done that, mastered it, and now need something new.
The silence in that space is what made me want to write this.
What I'm doing instead of waiting to feel certain
Paying attention to what pulls my attention. I keep gravitating toward explaining things, writing posts, breaking down how integrations work, helping people understand systems they find confusing. That's a signal worth following.
Having conversations I would have put off. Reaching out to people in roles that seem adjacent. Asking questions I don't have the answers to yet.
Letting the next thing be a direction before it's a destination. I know I want more ownership, more depth, more growth, more pay. That's not nothing. That's a compass even without a map.
If you're here too
Good at what you do. Proud of what you built. Quietly asking what comes next.
You're not being difficult. You're not being ungrateful. You're not doing it wrong.
Outgrowing something you worked hard to build is still growth. Hitting a ceiling after two years of climbing is not a setback, it's the natural next step that nobody prepared you for because everyone was too busy preparing you for step one.
The ceiling isn't the end. It's just where the next climb starts.
Top comments (0)