The Question That Changes Everything (But Doesn’t Have To)
“So… are you going to stay technical or go into leadership?”
At some point, every developer hears this. And if you’re anything like me, it feels…weird.
Because you've spent years getting better at your craft. Writing code. Solving problems. Mentoring a junior or two. And suddenly, people expect you to choose?
Like it’s a one-way ticket.
But here's the truth: it’s not.
The Fork in the Road Isn’t a Trap
You’re not choosing forever. You’re choosing where to grow right now.
That question, tech or leadership, isn’t about locking yourself in. It’s about finding where you thrive. What gives you energy. What challenges excite you instead of drain you.
And you can only figure that out by trying things.
What the Technical Path Looks Like
Some devs just know: they light up when the problem is hard and the solution is elegant.
They want to go deep. Architecture, performance, scalable systems. Becoming the person people turn to when no one else has the answer.
They grow into roles like Staff Engineer, Principal Developer, or Tech Architect.
Leadership, here, is about technical influence and not managing people.
If this path fits you, you might:
- Lead architecture discussions and code reviews
- Push for performance and maintainability
- Mentor others through code, not 1-on-1s
- Care more about design systems than team rituals
What the People Path Looks Like
Others, like me, discover joy in helping others grow. In creating clarity in chaos. In connecting devs, product, and design.
It’s less about writing the code yourself, and more about creating the environment where great code gets written.
Roles here look like Team Lead, Engineering Manager, or Technical Program Lead.
If this path fits you, you might:
- Facilitate retros, standups, and planning
- Mentor juniors and medior devs
- Act as bridge between stakeholders and engineers
- Take ownership of delivery and communication
You still code, but often less. And more strategically.
Some Myths That Need Busting
🚫 “If I want to grow, I have to go into management.”
✅ Nope. The technical ladder is real and valuable.
🚫 “Managers don’t code.”
✅ Depends on the org. Many still do or stay technical in other ways.
🚫 “Once I choose, I’m stuck.”
✅ Careers are long. You can switch, blend, or return.
How I Figured It Out (Kind Of)
After I hit senior, I didn’t know what was next. I liked code. But I also liked mentoring. Running demos. Talking to stakeholders.
So I started experimenting:
- Took ownership of features
- Mentored juniors
- Stepped up when someone needed to lead
That’s when I realized: I loved helping others grow.
And slowly, without waiting for a title, I grew into a lead.
Because leadership isn’t assigned. It’s earned.
Through behavior. Initiative. Repetition.
If Growth Isn’t Handed to You
Not every company supports this kind of growth. If you feel stuck, here’s what helped me:
Pick a theme: Dive deep into accessibility, testing, performance: anything that sparks curiosity.
Suggest value-adding: Propose something small that helps both you and the business.
Be visible: Share what you learn. Demo it. Talk about it.
Use side projects: Stretch yourself outside your day job.
Start the conversation: Ask your manager how you can grow. Even if they don’t have answers yet, you’ve planted a seed.
And if nothing changes: Leave. Growth isn’t a luxury. It’s your job to seek it out.
Final Thoughts
There’s no “right” next step after senior.
But there is a right question:
“What gives me energy and how can I grow in that direction?”
Try both paths. Blend them. Change your mind.
Just don’t stop moving.
💬 What’s your path right now? Are you going deep into tech or leaning into people and process? What gave you clarity?
I’d love to hear your story in the comments.
