Many senior security engineers reach a point where the only visible promotion is into management, and either take a people role they did not want or stall without knowing what the next technical level actually expects. Staff and principal security engineer roles are the senior individual contributor (IC) track: technical leadership with organisation-wide scope and no direct reports. This guide sets out what changes at staff and principal level, the common archetypes, how the track compares with security management, what evidence promotion panels look for and how organisations can build the track well. It is for senior engineers deciding their next move and for security leaders designing career ladders. The entry and mid-career path is covered in the Security Engineer Career Guide; this page starts where that one ends.
Key takeaways
- Scope, not skill, is the step change. Public ladders describe senior engineers owning team goals, staff engineers owning multi-year, multi-team risk reduction and principal engineers shaping security strategy with department or company leadership.
- Code becomes one lever among several. Staff engineers usually write less code than before and spend more time on direction, design review, sponsorship and the glue work that keeps programmes moving.
- There is more than one shape of staff engineer. Tech lead, architect, solver and right hand are distinct archetypes; knowing which one your organisation needs is half of getting there.
- Senior is often a career level. Some ladders state that most engineers are expected to reach senior and may stay there; staff is not an automatic next step, and the roles are created by organisational need.
- Promotion is an evidence case. Keep a running record of staff-scope projects, quantified risk outcomes, mentorship, advocates and gaps long before a panel asks for it.
What changes above senior
Titles vary between employers, so compare scope and influence rather than names. Two public career frameworks are useful anchors because they publish security-specific expectations: Dropbox's Engineering Career Framework (security engineer levels IC2 to IC6) and GitLab's security engineer job family (Associate to Distinguished). They are listed alphabetically and used here only as published examples.
| Dimension | Senior security engineer | Staff security engineer | Principal security engineer |
|---|---|---|---|
| Time horizon | Semi-annual and annual team goals | Multi-year, multi-team security goals | Organisation or company-wide multi-year goals, with an industry-leading view of where threats are heading |
| Problem definition | Large problems where the design may or may not be defined | Areas where the security strategy is not defined; the problem may not be known at the start | The most ambiguous, cross-cutting security challenges, spanning other organisations |
| Influence | Leads own team; impact starting to extend beyond it | Aligns teams and organisations towards coherent security goals; favours wider security priorities over local optimums | Influences the technical strategy of a whole group; partners with directors and senior leadership |
| Strategy | Leads or helps define security strategy for an area | Sets a multi-year risk reduction strategy and delivers it through implementation, technical leadership or guidance | Develops long-term security and technical strategy with leadership; maps business goals to security investments |
| Typical reporting line (GitLab) | Manager | Manager or senior manager | Senior manager or director |
| Representation | Within the team and partner teams | Builds security awareness across the company and at industry events | Represents security inside and outside the company, with industry peers and customers |
Both frameworks expect the staff engineer to fill gaps that are not clearly in anyone's job description. Dropbox's staff security engineer description says the engineer sometimes assumes roles not clearly scoped as security engineering or IC, and partners with leads to move the organisation towards higher maturity. GitLab expects staff engineers to act as directly responsible individual (DRI) for cross-team technical decisions when needed and to set standards within their speciality.
The four staff archetypes in a security organisation
Will Larson's StaffEng project describes four staff-plus archetypes, and Dropbox's framework adopts three of them explicitly, noting that senior IC levels do not require becoming a tech lead. Each maps naturally onto security work.
| Archetype | Definition (StaffEng) | What it looks like in security | Signals you fit |
|---|---|---|---|
| Tech lead | Guides the approach and execution of one team or a small cluster of teams; the most common first staff role | Technical lead for detection engineering, product security or cloud security, owning the roadmap with an engineering manager | You enjoy unblocking others and delegating hard projects rather than doing them yourself |
| Architect | Owns the direction and quality of a critical, complex technical domain | Owner of identity and access architecture, cryptography and key management, or the secure platform baseline | Teams already ask you to review designs in your domain and adopt your patterns |
| Solver | Works deeply on hard, high-risk problems that leadership has prioritised, until resolved | Leading the response to a systemic weakness: a secrets sprawl clean-up, a cross-estate vulnerability class, a major incident's root cause programme | You are pulled into the hardest problem of the quarter and prefer depth to coordination |
| Right hand | Extends a senior executive's attention and authority across business, technology, people and process; the least common | Working directly for the CISO on the problems that cross security, engineering and the business | Usually only exists in organisations with hundreds of engineers |
Decide which archetype you are working towards and say so to your manager. A strong solver case presented against a tech lead expectation tends to fail, not because the work was weak but because the panel was looking for a different shape.
What staff and principal engineers actually do
StaffEng's description of staff work lists setting technical direction, mentorship and sponsorship, injecting engineering context into organisational decisions, exploration of ambiguous problems and being glue. In a security organisation that becomes:
- Setting direction: writing the security strategy for a domain, for example the target state for workload identity or the organisation's approach to secrets, with the reasoning behind each choice so it stays useful as context changes.
- Design review at scale: reviewing the designs that many future projects will depend on, and turning repeated review findings into standards. StaffEng's method for strategy is to write five design documents and pull out the similarities; in security, five threat models of similar systems usually reveal the paved road worth building.
- Sponsorship as well as mentorship: StaffEng notes that the most effective staff engineers pair moderate mentorship with considerably more sponsorship, actively putting others forward for visible work.
- Representing security in decisions: bringing security context into time-sensitive leadership decisions (an acquisition, a platform migration, a new AI product) and representing the interests of engineering as a whole, not one team.
- Exploration: investigating problems existing systems are not built for, such as how to govern non-human identities created by AI agents, before there is a team for them.
- Glue work: the coordination that makes cross-team security programmes finish, recorded so it is visible at review time.
Most staff engineers still write some code, but impact is measured over months and years rather than sprints. Principal engineers extend this to the whole security function: GitLab expects them to drive complex, multi-department initiatives, turn strategic guidance into direction the organisation adopts and teach other domain experts.
Staff and principal compared with security management
The IC and management tracks reach similar levels of influence by different means. GitLab notes that a senior security engineer may choose the management track instead of continuing on the IC path, and StaffEng observes that some companies have no technical leadership track at all and push experienced engineers into management.
| Aspect | Staff or principal security engineer | Security engineering manager or head of function |
|---|---|---|
| Primary accountability | Quality and direction of technical decisions and systems | Team health, hiring, delivery and budget |
| Source of authority | Expertise, track record and trust; borrowed authority in the right hand archetype | Positional: reporting lines and resource allocation |
| Main outputs | Strategies, architectures, standards, reviewed designs, solved hard problems | Staffed teams, delivered roadmaps, performance management, stakeholder agreements |
| Time on people | Mentoring and sponsorship across teams, no direct reports | One-to-ones, career development, hiring and performance for direct reports |
| Failure mode | Becoming a reviewer of last resort or an ivory-tower architect | Losing technical judgement and deferring every decision upward or downward |
| Typical next step | Principal, distinguished or fellow; security architect leadership | Director, head of security, CISO |
A useful test: if the work you most want to do next involves deciding who is on the team, choose management. If it involves deciding what the team builds and how, and you are content to influence without directing, choose the IC track. Moves in both directions are common. See the First Time Security Manager Guide for the management route, and the Security Architect vs Security Engineer guide, where architect roles overlap with the staff architect archetype.
Getting there: a staged plan
- Confirm the role exists: ask your manager whether the organisation has staff and principal security levels and how many. If there are none, getting the title where you are may not be possible, and the decision becomes whether to build the case for creating one or move.
- Pick the archetype and the problem: agree with your manager which archetype the organisation needs and one staff-scope problem you will own end to end. GitLab's model of staff-plus engineers owning one agreed initiative for roughly 20 to 40 per cent of their time is a workable pattern.
- Work at the next scope before the title: deliver one multi-team outcome with a defined goal and baseline, for example reducing long-lived cloud credentials across all product teams, not just your own.
- Write things down: publish a strategy or standard for your domain and design documents for the projects that will outlive you. Written direction scales; meetings do not.
- Build advocates: engineering and product leaders outside security who can say what your work changed for them.
- Keep a promotion packet: start it long before you expect promotion and review it with your manager regularly so a change of manager does not erase progress.
- Test and adjust: ask a current staff or principal engineer to review the packet; if feedback names a gap, plan the next half around closing it rather than resubmitting the same case.
What goes in the packet
| Section (StaffEng) | Security-specific evidence |
|---|---|
| Staff projects | Goal, impact against the goal, what made it complex, links to design docs and threat models |
| Organisational improvements | A security review process you redesigned, a paved road adopted by other teams, an incident process change |
| Quantified impact | Risk reduced: critical findings closed, exposure removed, mean time to remediate, incidents prevented by a control you designed |
| Mentorship | Who you mentored and sponsored, and what they went on to achieve |
| Glue work | Cross-team programmes you kept on track and their outcome |
| Advocates | One sentence each from leaders who value your work |
| Gaps | Real or perceived gaps, with one sentence on how you are addressing each |
Skills that matter at staff level
- Deep expertise in one domain: Dropbox's staff level expects a high level of depth in a platform or product category that brings unique business value. Breadth alone rarely carries a case.
- Risk translation: mapping business goals to security investments and explaining trade-offs to people who do not share your vocabulary. GitLab lists clear communication of security to peers in other teams as a staff requirement.
- Threat modelling as a design habit: leading threat modelling for systems you will never build yourself, and teaching others to do it.
- Conflict and change management: GitLab lists conflict management within high-impact initiatives for principal engineers; Dropbox expects staff engineers to introduce change and help others understand the business case for it.
- Writing: strategies of one to two pages, design documents and decision records. StaffEng suggests a two to three year horizon for a technical vision.
- Certifications: useful as evidence of breadth (for example the CISSP Certification Guide or architecture credentials such as the GIAC Defensible Security Architect Guide), but no ladder examined treats them as a staff requirement; impact does the work.
Where identity fits
Identity is one of the most common staff and principal domains because it cuts across every team: workforce access, privileged access, customer identity and the growing population of service accounts, API keys and agent credentials. An architect-archetype engineer who owns machine identity strategy across cloud, CI/CD and AI agents has exactly the multi-year, multi-team, undefined-strategy problem staff ladders describe. See the NHI and Machine Identity Engineer Career Guide and the Identity Architect Career Guide.
Market context
Demand data for senior IC roles is thin, so treat it as indicative. The UK government's Cyber security skills in the UK labour market 2026 report defines senior as typically six or more years' experience. It found that core cyber job postings asking for six to nine years' experience fell 23 per cent between 2022 and 2025, and those asking for more than ten years fell 30 per cent, while noting that over 70 per cent of postings lack enough experience detail for firm conclusions. Security engineer was 21 per cent of core cyber postings in 2025. The same report quotes recruiters saying specialist technical skills such as penetration testing and secure software development remain hard to fill, and notes limited progression routes for mid-level staff. A clear senior IC track is one answer to that last point.
Building the track: guidance for security leaders
- Publish level expectations: write scope, influence and impact expectations per level, as the public frameworks do, and include security-specific examples.
- Create roles from need: staff roles should exist because the organisation has staff-scope problems, not as a retention title. Name the domains (identity, detection, product security, cloud) that need an owner.
- Protect the IC path from management by default: make the staff level equivalent in standing to a manager level, so the best engineers do not become reluctant managers.
- Accept senior as a career level: Dropbox's promotion guidelines state that L4 will be a career level for many engineers; saying so openly removes pressure for inflated promotions.
- Small organisations: with one or two security engineers, a staff title is rarely meaningful; give the senior engineer architect-style ownership and a clear external benchmark instead.
- Large organisations: calibrate staff and principal promotions across security and wider engineering, so security ICs are judged against the same bar as their software peers.
Detection and measurement
For an individual, measure whether your direction is adopted without you; for a leader, measure whether the track works.
- Number of teams using a standard, pattern or paved road you authored, and whether they adopted it without your direct involvement.
- Change in a domain risk measure you own, such as long-lived credentials, critical findings older than SLA or mean time to remediate, against the baseline in your project goal.
- Design documents in your domain written by others that follow your strategy; StaffEng suggests comparing design docs written years apart to judge a vision.
- People you mentored or sponsored who were promoted or took on larger scope.
- For leaders: ratio of staff-plus security ICs to security managers, time in level at senior, and regretted attrition of senior engineers.
Common failure patterns
- Doing senior work faster: delivering more of the same team-scope work and expecting a staff title. Scope must change, not volume.
- The reviewer of last resort: becoming the bottleneck every design must pass through instead of writing standards that let teams decide alone.
- Invisible glue: keeping cross-team programmes alive without recording it, so the panel sees no staff-scope outcome.
- Wrong archetype: building a solver case in an organisation that only promotes tech leads, or the reverse.
- Strategy without rationale: publishing rules without the reasoning, so they are ignored the moment context changes.
- Title without role: organisations granting staff titles as retention, with no staff-scope problem attached, which dilutes the level for everyone.
Framework mapping
| Framework | Reference | Relevance to the senior IC track |
|---|---|---|
| NIST CSF 2.0 | GV.RR-02, GV.RR-04, PR.AT-02 | Defined roles and authorities, cybersecurity in HR practices, skills for specialised roles |
| NIST SP 800-53 Rev 5 | PM-13 Security and Privacy Workforce, PL-8 Security and Privacy Architectures, SA-8 Security and Privacy Engineering Principles, SA-17 Developer Security and Privacy Architecture and Design | Workforce development, plus the architecture and engineering work staff and principal engineers typically own |
| NICE Framework (NIST SP 800-181 Rev 1) | Work roles, competencies and tasks; components version 2.2.0 listed by NIST | Common language for describing senior security engineering work in level expectations |
Practitioner checklist
- Find out whether your organisation has staff and principal security levels and read the published expectations.
- Agree with your manager which archetype you are working towards.
- Own one multi-team security outcome with a defined goal and baseline.
- Write a strategy or standard for your domain, with rationale, and publish it.
- Turn repeated design review findings into a reusable pattern or paved road.
- Sponsor at least one engineer into visible work each half.
- Start a promotion packet now and review it with your manager regularly.
- Ask a staff or principal engineer to critique your packet and close the gaps they name.
- Leaders: publish level expectations with security examples and calibrate them against wider engineering.
Standards and references
- GitLab: Security Engineer job family
- Dropbox: Engineering Career Framework (security engineer levels)
- StaffEng: Staff archetypes
- StaffEng: What do Staff engineers actually do?
- StaffEng: Writing engineering strategy
- StaffEng: Promotion packets
- NIST: NICE Framework current versions
- UK Government: Cyber security skills in the UK labour market 2026
Related NHI Mgmt Group resources: Security Engineer Career Guide · Security Architect vs Security Engineer · Application Security Engineer Career Guide · Security Architect Career Guide · Path to CISO Career Guide