Senior to Staff - Growing on the IC Track
Many engineers feel a plateau after reaching the Senior level. The only path forward seems to be management - or there seems to be no path at all. But the IC (Individual Contributor) track, now taking hold in Türkiye's software sector too, offers another route: moving to Staff and Principal while continuing to write code.
This post covers breaking through the Senior+ plateau, growing your internal impact, and building your promotion case.
Is Management the Only Path Past Senior?
Short answer: no.
Most software organizations in Türkiye still don't clearly distinguish between Engineering Manager (EM) and Individual Contributor (IC) paths. This ambiguity blurs what comes after Senior. Many senior engineers get "the next step is management" in response to a promotion ask - because the organization hasn't defined an IC seniority ladder.
But that undefined state doesn't mean the path doesn't exist. In fact, you can draw it.
What Is the IC Track, and Where Does It Exist?
The IC track is the structural name for growing your technical influence without becoming a manager. Practical examples:
- Startups and growth-stage companies: Often have "Lead Engineer" or "Principal Engineer" titles after Senior. Formal leveling is light, no band system.
- Türkiye offices of foreign companies: Usually carry the parent company's leveling structure. Staff and Principal are already defined.
- Fully remote, foreign employers: Big Tech and scale-ups standardize the IC track. SWE → Senior SWE → Staff SWE → Senior Staff / Principal → Distinguished / Fellow.
If the IC track doesn't exist, you can draw it - but complete your own preparation before asking a manager or HR to formalize it.
The Senior Plateau: What's Happening?
Once you reach Senior, expectations shift. Just taking on work isn't enough - impact is expected. But that impact is usually left undefined.
Three signs you've hit the plateau:
1. You're doing the same class of work. You solve hard tickets, write clean code - but these are well-scoped tasks. The undefined, ambiguous problems that no one wants to own aren't landing on your desk.
2. You can't generate systemic impact. You're stuck between writing a feature and changing how the team works. No one's knocking on your door for the second kind.
3. Promotion conversations stay vague. "You're already Senior, what should change?" gets no concrete answer. "Show more" - more of what, where?
How Is Internal Impact Measured?
At Staff and Principal, the core expectation is this: grow your technical influence from individual code contribution to team-wide or company-wide scope.
Concrete forms:
Setting technical direction
Who resolves architecture decisions, technology choices, technical debt prioritization? If those decisions are hanging in meetings and you're the one driving them, that's Staff-level behavior.
Being a multiplier
Not individual contribution, but increasing others' productivity. Beyond code review: technical onboarding, architecture docs, internal tooling, building an RFC (design document) culture.
Managing ambiguity
Taking the lead in areas where "who will do this, how" has no answer. Defining scope, proposing prioritization, surfacing technical risk.
Cross-organizational visibility
Technical contributions that span team boundaries: cross-product infrastructure, company-wide engineering standards, cross-team coordination.
How Do You Build Your Promotion Case?
A promotion conversation isn't "time served" - it's evidence submission. Staff or Principal requests need concrete examples.
Actions vs. impact
A list of things you did doesn't get you promoted. List impact instead:
- "I rewrote the API" ❌
- "The API rewrite reduced team onboarding time from 3 days to 4 hours; 4 teams migrated to the new infrastructure" ✅
Writing RFCs or technical documents
Document technical decisions. Not just the outcome, but the why. Months later, these documents are your footprint.
Finding sponsorship
Is your manager in a position to advocate for you in the promotion process? Staff and Principal decisions usually require sign-off from more than one manager. Make sure your manager can convince their manager - you can find this out by asking directly.
What Does Leadership Without Direct Reports Look Like?
IC leadership is possible without anyone reporting to you - but staying visible takes active effort.
Technical mentorship
Mentoring junior and mid-level engineers is a direct investment in careers. But mentorship alone isn't the only evidence for Staff - it needs to sit alongside systemic impact.
Internal reading groups or tech talks
Small initiatives like a "monthly architecture review" or "technical reading notes" build visibility. Starting and sustaining them is a concrete example of internal impact accumulation.
Building a code review culture
Framing code review as knowledge transfer rather than error-finding raises quality standards across the team. That framing effect is measurable.
What If the Organization Doesn't Define an IC Path?
Even without a formal IC band, you can enter this path - but be prepared.
1. Add a concrete scope to your current Senior title. Not "the most senior person on the team," but "the person setting technical direction for platform engineering."
2. Define the IC track with your manager. Instead of "make Staff the next promotion," try "if I demonstrate impact in these 3 areas, let's open a Staff evaluation."
3. Do a market comparison. Look at Staff SWE and Principal SWE job postings for fully remote positions at foreign employers. See the requirements - then compare your situation.
4. Know the pay difference. In Türkiye, the Senior → Staff transition can mean 20-40% more net compensation - especially at foreign companies. That gap is real motivation; go into conversations with that clarity.
What Does a Long Senior Plateau Mean?
Staying at the same level for 2+ years isn't always bad - if learning is dense, impact is growing, and pay is being updated, there's no problem.
But watch out if all of this is true at once:
- You don't see growth opportunities
- Promotion conversations keep getting "eventually" as an answer
- Your pay hasn't been updated
In that case, IC track evaluation doesn't require staying at the same company: is that path open at another company? Use the getsalary.dev dashboard to compare salary ranges and career progression data.
Summary
Management is not the only path past Senior. The IC track is how you grow your individual technical influence - making a broader organizational impact while continuing to write code.
If you're doing these 3 things together, you're on the right path toward Staff/Principal:
- Document and lead technical decisions
- Move your impact from individual contribution to multiplier contribution
- Frame promotion conversations as evidence submission
The road is long - but not unclear.