Back to Q&A board

I've worked as a Senior Platform Engineer with a much bigger scope for over 6 years, how do I get a staff, principal or architect role elsewhere?

Anonymous October 20, 2026 DevOps engineer, Netherlands

I have worked as an independent contractor for about a decade and then started working full-time for a company as a "DevOps" cloud engineer (IC role), fairly quickly growing my scope to include department-wide (±80 engineers) DevEx, security and resilience design. While there were no official titles or roles beyond "Senior Engineer", I then architected, validated, and implemented a complete internal platform everyone uses to self-service their engineering efforts from code to production, steering the engineering direction for a platform team of 7.

At this point, I'm looking for a role elsewhere, to grow but to also to have a more official role and compensation for the scope, impact and work I'm already doing.

I have applied to various roles and gotten some interviews, but it is a bit of a wide net with positions ranging from senior infrastructure engineer to director of platform engineering and every staff and principal role in between.

I'd appreciate some insight in going from a role that would be described as a senior IC, to a Staff, Principal or Architect scope without having previously had that as official mandate with official direct reports.

4 answers
Top answer by
Profile picture for Geoff M.
SuperCoachcertified
DevOps engineer, Software engineer, Engineering manager +5 others
Google, Microsoft, Pandora, Talarian Corp
5.0 avg rating, 465 clients
Answered October 21, 2026

Be careful what you wish for. At many companies, especially FAANGs, the jump from Senior to Staff is huge. As other coaches have stated here, much more is expected than just technical mastery.

Promotions up the career ladder work like a pyramid. Not everyone who deserves it gets promoted. And because the competition is fierce for such coveted roles, external hires applying for Staff-level roles need to be even more deserving. Be ready to walk on water twice, backward, if you are desiring a Staff role as an external candidate.

Then there's the current tech job market. You don't need a coach to tell you how challenging this current lull is. Ample talent is sitting on the sidelines, willing to compromise on role and level to get employed again. Managers and Staff ICs are interviewing for tech lead roles, willing to step back to rejoin a team. Sr. Staff ICs are willing to accept a level-down to Staff. Even if you are a stellar Staff IC, your competition for those roles will be far fiercer. So ask yourself: is it better to step up to the plate and attempt to hit a grand slam (obtain a Staff-level offer), or would it be strategically better to put the ball in play, hit a single or double, get in the game as a Senior (Tech Lead), and then prove yourself to be Staff over time?

How risk-averse are you? How confident are you that you will meet all expectations as a Staff Eng out of the gate? In this job market, does it make sense to lower expectations, take a Sr. role, and be promoted to Staff later?

Even if you hit that grand slam, getting hired as Staff is just the first inning. Now you have to deliver daily. That's a tall order for someone external to the organization trying to assimilate into the culture, learn how to navigate the politics, draw the faction map to determine who has power and authority across the org, and then brilliantly listen, communicate, mentor, and influence across a wide swath of stakeholders. Welcome to the life of a Staff engineer.

Profile picture for Manny R.
SuperCoach
Product manager, Software engineer, Engineering manager +7 others
Amazon, Boston Scientific, Google, IEEE Computer Society +5 others
4.97 avg rating, 760 clients
Answered October 23, 2026

Based on your experience, I would not assume you need another Senior Engineer role before pursuing Staff. You may already be operating at Staff level without the title.

Building a developer platform used by 80 engineers, leading technical direction for seven engineers, and owning security, resilience, and developer experience are strong indicators. However, Staff-level hiring evaluates measurable organizational impact, not just responsibilities.

Here's my recommendation:

1. Quantify your impact. Show how your platform improved deployment frequency, lead time, reliability, developer productivity, or infrastructure costs. Use before-and-after metrics whenever possible.

2. Demonstrate cross-team influence. Staff engineers drive technical decisions beyond their immediate teams. Prepare examples of resolving architectural disagreements, establishing standards, and influencing stakeholders without formal authority.

3. Prepare three leadership stories. Focus on a major architectural decision, a complex cross-team initiative, and a measurable business outcome. Explain trade-offs, alternatives, decisions, and results.

4. Target the appropriate level. Staff Platform Engineer, Staff Infrastructure Engineer, and Platform Architect are strong matches.

5. Address your title confidently. Explain that Senior was your company's highest IC title, while your actual responsibilities expanded to department-wide architecture and technical leadership.

6. Prepare for Staff interviews. Expect deep system design discussions covering distributed systems, scalability, security, reliability, and architectural trade-offs, plus behavioral interviews assessing influence and strategic thinking.

My recommendation: Apply directly to Staff roles and use interview feedback to calibrate your level. Your challenge isn't necessarily gaining more experience; it's demonstrating that your existing work meets Staff-level expectations. It would be an honor to support you on this journey.

Profile picture for Tom P.
SuperCoach
DevOps engineer, Software engineer, Engineering manager +7 others
Elsevier, G Research, Hargreaves Lansdown, Meta
4.95 avg rating, 243 clients
Answered October 21, 2026

Within this progression of roles there are a few different things to consider and what I have seen.

Within infrastructure and devops teams there is a clear focus on solving technology problems to support other organisation teams. Where really gives a differentiator is starting from the real business goal and outcome to how to support this from an underlying technology perspective and to articulate this.

With the business first and dealing with the largest ambiguous problems this helps you show where you are driving the direction

Profile picture for Alex H.
SuperCoach
Software engineer, Engineering manager, Founder / Entrepreneur +4 others
Accenture, DXC Luxoft, Google, Growith.AI
5.0 avg rating, 189 clients
Answered October 21, 2026

With 6+ years of experience you can apply for Staff (L6) level. The lack of direct reports should not be a problem for IC.

Be prepared to describe and explain your independent contractor roles with regard to the scope of your projects as the expectation for L6 is having more impactful longer term (9 months or longer) projects with technical leadership of teams of 6-10 engineers.

Google as well as many BigTech companies have special SRE teams in Europe so you can check these specifically

Find a coach
Get support to achieve
your career goals:
practice interviews, improve your resume, negotiate your offers, etc.