Staff SDETs
at Priority are domain-level test-infrastructure architects. You own how
the test infrastructure is structured for your domain, decide how it evolves,
and are accountable for itslong-term reliability. This is the first level where
infrastructure ownership is explicit and consequential — you don't just build
well within the domain's frameworks; you own them, evolve them, and hold the
standards that keep them trustworthy.
You're
hands-on. Still. At
Priority, the Staff title doesn't graduate you out of the framework code— it
puts you in the hardest infrastructure work in the domain, and keeps you close
to the pipelines and the flaky gates that eat the team's time, so your
direction stays grounded in reality. You lead by example — your framework code,
your review bar, your AI-native practice, and your engineering judgment set
what the domain's automation looks like at its best.
You're the
infrastructure authority for your domain: you write the architecture decision
records(ADRs) for the significant infrastructure choices, you set the
automation standards teams build within, you own the CI/CD quality-gate design
for the domain, and you drive AI-native test practices where agents generate,
execute, and triage on infrastructure you built for exactly that.
Your
primary partnerships live on the team as a quality-engineering trio. The Staff Quality Engineer for
your domain owns what the platform must prove and why — the strategy. You own
the engineering that executes that strategy at scale. Staff Software
Engineers own the code being tested — you partner with them on designing
for test ability, contract testing, and the practices that keep automation
trustworthy. Together, the three of you — Staff SDET, Staff QE,Staff SE — are
the domain's quality-engineering trio. You solve hard problems together, not by
throwing artifacts over the wall.
You know
the customer and business outcomes your domain's automation protects — not
slide-deep, but real. R