Senior Program Manager, Development Testing Operations (Release Testing)

We need to output HTML fragment with sections for headings present: About the role? The posting includes "Who We Are", "What We Are Looking For", "In This Role, You Will", "Required Qualifications", "Desirable Qualifications", "The base salary range...", "Working at Aurora", "Our commitment to safety", "Our commitment to inclusion". According to rules: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map headings to these standard ones if possible, but we must only include sections when posting has real specific content. We should not repeat job title as heading. We should not include Job ID etc. Remove boilerplate like EEO etc? The inclusion statement is EEO-like; but it's about inclusion; we might keep as it's substantive? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The inclusion statement is EEO-like; likely considered boilerplate and should be removed. Similarly "Our commitment to safety" maybe not boilerplate but could be considered values; but it's somewhat generic. However it's specific to Aurora's commitment; might be considered substantive? The instruction says remove EEO/equal-opportunity boilerplate. The inclusion statement is definitely EEO. So remove that. The safety commitment might be considered values; not explicitly prohibited. Could keep as a section maybe "Our commitment to safety". But heading list does not include that; we can still use

for any section heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive; we can use other headings as needed but better to map to those. We could map "Who We Are" to "About the role"? Not exactly. "What We Are Looking For" could be "Responsibilities"? Actually responsibilities are listed under "In This Role, You Will". So we can make a Responsibilities section from that. Required Qualifications -> Requirements or Qualifications. Desirable Qualifications -> Skills? Could be Skills. Pay -> we have base salary range, so we can make Pay section. Benefits -> mention annual bonus, equity compensation, benefits. So Benefits section. Schedule -> hybrid work environment (in office at least 3 days per week). So Schedule section. About the role -> maybe "Who We Are" and "What We Are Looking For" combined? Could be About the role. We'll create sections: About the role (combining Who We Are and What We Are Looking For). Responsibilities (In This Role, You Will). Requirements (Required Qualifications). Skills (Desirable Qualifications). Pay (base salary range). Benefits (annual bonus, equity compensation, benefits). Schedule (hybrid work environment). Possibly also "Our commitment to safety" could be omitted as not in list; but could be included as a separate section but not in examples; better to omit to follow instruction to prefer few substantive sections. We'll omit safety and inclusion. We must preserve all substantive information; not invent or summarize away detail. So we need to include details from each section. Let's extract content: Who We Are: - Aurora’s mission is to deliver the benefits of self-driving technology safely, quickly, and broadly. - The Aurora Driver will create a new era in mobility and logistics, one that will bring a safer, more efficient, and more accessible future to everyone. - At Aurora, you will tackle massively complex problems alongside other passionate, intelligent individuals, growing as an expert while expanding your knowledge. - For the latest news from Aurora, visit aurora.tech or follow us on LinkedIn. What We Are Looking For: - Aurora's Product Operations team plays a critical role in ensuring new software releases are validated with rigor and speed before they reach our commercial fleet. - We partner closely with Engineering, Safety, and Release Management to make sure every release - onboard and offboard - passes through well-defined, consistently executed test gates. - We’re searching for a Senior Program Manager, Development Testing Operations (Release Testing) to own the test procedures that gate software releases, drive operational excellence in how those tests are executed, and close the feedback loop between test results and engineering. - This is a hands-on role for someone who thinks in terms of process rigor, repeatability, and continuous improvement - not just getting a release out the door, but making sure it's actually ready. - You are the owner of "did we test this the right way, and did we act on what we learned." In This Role, You Will (list): - Own release test procedures - maintain, version, and continuously improve the test plans, checklists, and standard operating procedures used to gate software releases, ensuring they stay current with engineering requirements and release cadence. - Communicate with stakeholders - Work with stakeholders to clearly communicate release timelines across engineering and operations - Ensure operational excellence in test execution - define clear pass/fail and escalation criteria, audit test runs for procedural adherence, and drive consistency so releases are tested the same rigorous way every time, minimizing re-work and re-testing. - Close the feedback loop - triage test failures and coverage gaps into actionable engineering tickets, track them to resolution, and ensure lessons learned from each release cycle are incorporated back into test procedures rather than lost. - Serve as a key input to release gating decisions - partner with Release Management and Engineering to confirm test evidence is complete and current ahead of go/no-go decisions. - Identify and reconcile gaps across test types - compare coverage across different stages of the release testing pipeline (e.g., component-level checks vs. full-release regression) to catch blind spots before they become production issues. - Drive continuous improvement of the testing program - lead initiatives to streamline test scope, reduce cycle time, and improve signal quality, balancing coverage against speed and cost. - Report status and risk - provide regular, clear updates to Engineering, Release Management, and Ops leadership on testing progress, blockers, and release readiness. Required Qualifications: - 5+ years of experience in Program Management, Project Management, Quality Assurance, Release Engineering, or a related role - Demonstrated experience owning or improving test procedures, QA processes, or release/quality gates in a technical environment - Ability to develop a functional understanding of how software releases move through a testing pipeline, including regression testing and staged rollout concepts - Experience driving process improvement and change management within a cross-functional organization - Strong organizational skills with the ability to manage multiple test cycles and competing priorities - Clear written and verbal communication skills, with comfort translating technical test results into risk and status reporting for stakeholders at multiple levels - Comfort operating in environments where safety and quality are core requirements - Ability to support being part of an on-call rotation - Ability to operate effectively in a fast-paced, evolving environment with shifting release schedules Desirable Qualifications: - Experience with release management, CI/CD pipelines, or regression testing frameworks in a technology or engineering-driven organization - Familiarity with defect/issue tracking and test management tooling (e.g., Jira, TestRail, or equivalent) - Proven experience managing relationships and expectations with senior leadership and cross-functional stakeholders - Comfort using dashboards or reporting tools to track test coverage, defect trends, and release readiness - Experience in autonomous vehicle, automotive, robotics, or similarly safety-critical operational environments - Passion for shipping reliable, high-quality releases and adapting to new responsibilities as the testing program scales Pay: - The base salary range for this position is $100,000 - $145,000 per year. - Aurora’s pay ranges are determined by role, level, and location. Within the range, the successful candidate’s starting base pay will be determined based on factors including job-related skills, experience, qualifications, relevant education or training, and market conditions. These ranges may be modified in the future. Benefits: - The successful candidate will also be eligible for an annual bonus, equity compensation, and benefits. Schedule/Working at Aurora: - We believe in-person work increases collaboration, empathy and our ability to lead effectively. As a result, we operate in a hybrid work environment where Aurorans are in office at least 3 days per week. - Our Careers page provides insight into what it is like to work at Aurora, and you can find all the latest updates in our Newsroom. We should not include boilerplate like "Our Careers page provides insight..." maybe okay but it's not essential; but it's part of Working at Aurora. Keep. We must not repeat job title as heading. We'll not. We need to output only HTML fragment, no /. Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to decide which content goes into lists vs paragraphs. For About the role: we have prose; we can put into

  maybe multiple paragraphs. Responsibilities: list of duties ->

  • . Requirements: list ->
    • . Skills: list ->
      • . Pay: maybe prose; could be

        . Benefits: maybe

        (annual bonus, equity compensation, and benefits). Schedule: maybe

        (hybrid work environment...). We must not include empty sections. Let's craft. We'll produce:

        About the role

        Aurora’s mission is to deliver the benefits of self-driving technology safely, quickly, and broadly. The Aurora Driver will create a new era in mobility and logistics, one that will bring a safer, more efficient, and more accessible future to everyone. At Aurora, you will tackle massively complex problems alongside other passionate, intelligent individuals, growing as an expert while expanding your knowledge. For the latest news from Aurora, visit aurora.tech or follow us on LinkedIn.

        Aurora's Product Operations team plays a critical role in ensuring new software releases are validated with rigor and speed before they reach our commercial fleet. We partner closely with Engineering, Safety, and Release Management to make sure every release - onboard and offboard - passes through well-defined, consistently executed test gates. We’re searching for a Senior Program Manager, Development Testing Operations (Release Testing) to own the test procedures that gate software releases, drive operational excellence in how those tests are executed, and close the feedback loop between test results and engineering. This is a hands-on role for someone who thinks in terms of process rigor, repeatability, and continuous improvement - not just getting a release out the door, but making sure it's actually ready. You are the owner of "did we test this the right way, and did we act on what we learned."

        Responsibilities

        • Own release test procedures - maintain, version, and continuously improve the test plans, checklists, and standard operating procedures used to gate software releases, ensuring they stay current with engineering requirements and release cadence.
        • Communicate with stakeholders - Work with stakeholders to clearly communicate release timelines across engineering and operations
        • Ensure operational excellence in test execution - define clear pass/fail and escalation criteria, audit test runs for procedural adherence, and drive consistency so releases are tested the same rigorous way every time, minimizing re-work and re-testing.
        • Close the feedback loop - triage test failures and coverage gaps into actionable engineering tickets, track them to resolution, and ensure lessons learned from each release cycle are incorporated back into test procedures rather than lost.
        • Serve as a key input to release gating decisions - partner with Release Management and Engineering to confirm test evidence is complete and current ahead of go/no-go decisions.
        • Identify and reconcile gaps across test types - compare coverage across different stages of the release testing pipeline (e.g., component-level checks vs. full-release regression) to catch blind spots before they become production issues.
        • Drive continuous improvement of the testing program - lead initiatives to streamline test scope, reduce cycle time, and improve signal quality, balancing coverage against speed and cost.
        • Report status and risk - provide regular, clear updates to Engineering, Release Management, and Ops