Career Ladder

The GRC engineering career ladder

Six levels, from your first control test to enterprise assurance strategy. Each level has one outcome and one proof that another person can check. Levels 1 to 3 are a curriculum you can finish in the Club. Levels 4 to 6 describe the role, and the proof comes from your job.

Start at Level 1
Levels 1 to 3

Build it: the curriculum

You can complete these three levels with Club labs, projects, and the CGE-P capstone. Each one ends with work that someone else has to be able to run.

L1

Foundations

Reproduce and explain a control test.

What you can do

  • Use Git, a terminal, and Python to run a script from a clean environment
  • Trace a cloud action back to the identity and the log event behind it
  • Write a control test that reports pass, fail, and missing evidence as three different results

Proof

Someone else reproduces your control test using only your README.

Club path

The First 30 Days roadmap covers this level: tool setup, the access review lab, the password policy check, and the key rotation check.

L2

Junior GRC Engineer

Deliver an evidence collector another person can test and operate.

What you can do

  • Collect from an API with authentication, pagination, and rate limits handled
  • Store observations and query them for missing or stale evidence
  • Write automated tests and a CI check that blocks a failing change
  • Never report a failed or partial collection run as compliant

Proof

A reviewer reruns your collector and can tell a control failure, incomplete evidence, and a collection error apart.

Club path

The CGE-P coursework and the 6-Week GRC Build-In Challenge carry most of this level. API collection and test automation are where the Club library is thinnest today, and new labs are being built against those gaps.

L3 CGE-P is earned here

GRC Engineer

Own a control pipeline through changes and failures.

What you can do

  • Test controls as code with Terraform plans and a policy engine such as OPA
  • Schedule collection and measure evidence freshness and completeness
  • Run a finding from detection through assignment, retest, and closure
  • Track exceptions with an owner and an expiry date

Proof

Another operator follows your runbook from detection through remediation and retest without your help.

Club path

The CGE-P labs on policy as code and evidence pipelines build these skills, and the CGE-P capstone is the proof: a working pipeline you submit on GitHub.

Levels 4 to 6

Lead it: the role

No course makes you a senior, staff, or principal engineer. These levels are defined by scope and by other people depending on your work, so the evidence has to come from a real organization.

L4 CGE-AZ fits between L3 and L4

Senior GRC Engineer

Make and defend assurance decisions across systems and teams.

What the work looks like

  • Agree scope across teams, with system boundaries and named owners
  • Threat model a system with trust boundaries and tested mitigations
  • Set and measure reliability targets for evidence, including a dependency outage
  • Keep evidence comparable across two clouds
  • Roll out, stop, and roll back a policy change with before and after evidence

Evidence from your job

A two-system assurance design that survived stakeholder disagreement, with the review findings and your revisions on record.

How the Club helps

CGE-AZ adds a second cloud on top of CGE-P. Chapter leadership and open-source contribution give you practice leading work you do not own.

L5

Staff GRC Engineer

Create a shared capability that independent teams adopt.

What the work looks like

  • Version control and evidence contracts, and handle a breaking change
  • Publish a reference design and templates a new team can use from the docs
  • Migrate to a new path with parity checks, a tested rollback, and a retirement date for the old one
  • Measure adoption, setup effort, and support burden

Evidence from your job

A second team integrates your component without forking it, and it holds across a release.

How the Club helps

Teaching is the fastest practice for this level. Lead a live builder session or apply as a guest instructor and find out whether other people can build on your work.

L6

Principal GRC Engineer

Set and revise enterprise assurance direction from measured results.

What the work looks like

  • Reconcile systems, controls, owners, and gaps into one enterprise baseline
  • Write a strategy that states what evidence would change its direction
  • Rank investments under explicit cost, risk, and staffing limits
  • Brief executives on a decision, its tradeoffs, and who owns the follow-up

Evidence from your job

A strategy that engineering and risk leaders challenged, with the decisions, the dissent, and the later outcomes recorded.

How the Club helps

At this level you give more than you take: mentoring, speaking, and shaping what the Club teaches next.

Built with the community

This ladder grew out of a learning tracker built by Club member Claire Torrez, who mapped Club lessons, labs, and certifications to a six-level engineering progression. Her tracker goes deeper, with milestones and progress tracking for every level.

Open the tracker

Frequently asked questions

The GRC Engineering Club ladder has six levels: Foundations, Junior GRC Engineer, GRC Engineer, Senior GRC Engineer, Staff GRC Engineer, and Principal GRC Engineer. Each level is defined by one outcome and by the proof that shows you can deliver it, from reproducing a single control test at Level 1 to setting enterprise assurance strategy at Level 6.

No. Levels 1 through 3 are a curriculum you can complete with labs, projects, and a capstone. Levels 4 through 6 describe a role. Their proof is work that only happens inside an organization, such as a design two teams agreed to or a platform a second team adopted. Courses and community practice prepare you for that work, and the evidence comes from your job.

CGE-P is earned at Level 3. Its coursework builds Level 2 and Level 3 skills, and its capstone, a working compliance pipeline submitted on GitHub, is the Level 3 proof. CGE-AZ requires CGE-P and sits between Levels 3 and 4. CGE-AUD is a specialty for auditors and sits beside the engineering ladder.

No. Every level is proven by work another person can check: a control test someone else reproduces, a collector a reviewer reruns, a runbook another operator follows. Certifications can confirm knowledge along the way, and they never replace the practical proof.

Start at the first level whose proof you cannot show today. Many experienced GRC analysts have the control and audit knowledge of Level 3 or higher and still need the Level 1 and Level 2 engineering skills: Git, Python, APIs, and automated tests. The First 30 Days roadmap is the quickest way to find out.

Find your level, then prove the next one

Join the GRC professionals building their way up the ladder with hands-on labs, a capstone that ships on GitHub, and a community that reviews your work.

Join the Club

See what membership includes →