ZR_287 SDET (QA Automation)

 About the Role

Associate SDETs at Priority are early-career engineers building strong fundamentals: writingautomated tests, learning our frameworks, and developing the engineering habits that makeautomation trustworthy. You'll ship real code on real automation tasks from your first weeks —with the safety net of close support, code review, and pairing with SDETs, QEs, and SEs aheadof you on the curve. What we care about most at this level isn't what you know on day one; it'syour trajectory.

SDETs at Priority are engineers whose product is proof. The test infrastructure andautomation you build is what lets teams ship financial software fast — because the platformcatches what's wrong automatically. From your first task you'll learn how your automation fitsthat mission: which customer flow the tests you're writing protect, why the platform depends onthe automation being reliable, and what happens when it isn't.

Two things shape how we work, from day one. First, your test code is held to the sameengineering bar as product code — no separate standard for tests. Second, AI-assisteddevelopment is standard — you'll use AI tools daily to generate tests, diagnose failures, andaccelerate learning, validating every output before you commit.

You work alongside SDETs, QEs, and SEs on the team — the SEs build the product, the QEs ownquality strategy (what must be validated and why), and you build the automation that executesthat strategy at scale. Even at this level, you're starting to see how the three roles interlock; thequality-engineering trio you'll be part of later starts making sense here.

What You'll Do

Write automated tests for well-scoped features within the team's existing frameworks

Write reliable (not flaky) test code that follows framework patterns, and keep your pullrequests small and reviewable

Debug failing tests to root cause, and tell a product bug from a test bug — your reports showit

Understand how your tests gate deployments, and move changes through the pipelinecorrectly

Test against documented contracts and use APIs idiomatically

Handle test data securely — never put secrets or real customer data in test code

Learn what customer flow the tests you're writing protect, and why the automation beingreliable matters to that customer

Use AI-assisted tools daily (test generation, failure diagnosis), validating outputs beforecommitting

Keep your work 

visible and current, raise blockers the day they appear, and ask questions inthe open

Fix framework docs when you find them wrong; documentation your team can trust is a first-class contribution

​