Staff Technical Program Manager, Release Management

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Must not create sections with filler like "commensurate with experience". Must only include sections where posting has real specific content. We need to parse the posting. Content: - Who We Are: description of Aurora mission. That's "About the company" maybe "About the role"? Actually "Who We Are" is about company. Could be "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. We have: - "What We Are Looking For": description of role responsibilities. That's responsibilities. - Then "Required Qualifications": list of qualifications. - Then "Desirable Qualifications": could be Skills? Or maybe "Skills" heading. - Then salary ranges: Pay. - Then "Working at Aurora": hybrid work schedule etc. That could be Schedule? Actually schedule: hybrid work environment where Aurorans are in office at least 3 days per week. That's schedule info. - Also benefits: mention annual bonus, equity compensation, benefits. Also maybe "Benefits" heading. - Also "Our commitment to safety", "Our commitment to inclusion": maybe not needed as they are boilerplate? They are not EEO but still maybe considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Those sections about safety and inclusion might be considered boilerplate? They are not exactly EEO but could be considered corporate values. Might be okay to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The safety and inclusion sections are not explicitly listed, but they could be considered boilerplate? However they are substantive about company values. Might be okay to keep but we need to fit into allowed headings. There's no heading for "Values" etc. Could we put them under "About the role"? Probably not. Safer to omit them as they are not directly about role responsibilities, qualifications, skills, benefits, pay, schedule. The instruction says "Prefer a few substantive sections over many thin ones." So we can omit those. Thus sections we will include: - About the role (maybe "Who We Are" + "What We Are Looking For"? Actually About the role could be a brief description of the role. We have "What We Are Looking For" which includes role description. Could treat that as About the role. But we also have Responsibilities separate. Could combine? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which content goes where. We have: - About the role: maybe a short paragraph summarizing the role: "As a Staff Technical Program Manager (Release Management), you will report to the Manager of Release Management and join our Software Product-Design team. This is a senior individual contributor (IC) role that balances strategic release architecture and automation with hands-on, day-to-day release train execution. We are hiring for this role to help drive scale and automation in our release operations for predictive prevention, establishing robust automated release gating as our commercial driverless fleet scales from a dozen vehicles to thousands. This is a high-impact opportunity for a force multiplier who thrives on combining hands-on tactical execution with long-term operational scale. You are highly motivated to remove manual friction, manage release operations, and automate software release and deployment frameworks in a safety-critical, high-velocity environment." That seems appropriate for About the role. - Responsibilities: the bullet list after "In this role you will". Those are responsibilities. - Requirements: maybe "Required Qualifications". That's requirements. - Qualifications: maybe "Desirable Qualifications"? Actually they are "Desirable Qualifications". Could be Skills? But we have separate Skills heading. Could treat Desirable Qualifications as Skills. Or we could have Qualifications heading for Required Qualifications and Skills heading for Desirable Qualifications. The instruction lists both Qualifications and Skills as possible headings. So we can put Required Qualifications under

Qualifications

and Desirable Qualifications under

Skills

. Or vice versa. Usually Qualifications are required, Skills are desired. We'll follow that. - Benefits: mention annual bonus, equity compensation, benefits. Also maybe "Our Careers page provides insight..." but that's generic. We'll include benefits: annual bonus, equity compensation, benefits (health etc not detailed). We'll just list what's given: annual bonus, equity compensation, benefits. - Pay: salary ranges for locations. - Schedule: hybrid work environment where Aurorans are in office at least 3 days per week. We must not include headings with filler. Ensure each section has real content. Now produce HTML fragment: use

for each heading, then content: either

for prose,

• for lists. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specific tools (Buildkite, GitHub Actions, Bazel), standards (ISO 26262, DO-178C, ISO 13485), locations (Mountain View, CA; Texas; Pittsburgh, PA), etc. We must not repeat job title as heading. Already not. We must not put Job ID/requisition numbers as headings; none present. We must remove duplicated lines: check for any duplicates. The posting had some duplicated lines? Not obvious. We must remove application instructions: none present besides maybe "For the latest news from Aurora, visit aurora.tech or follow us on LinkedIn." That's not application instruction but could be considered boilerplate? It's a link to follow us. Might be considered navigation? It's not cookie/legal/EEO. Might be okay to keep? It's not about role. Could be considered "About the company" but we already have About the role. Might be safe to omit as it's not substantive about role. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is a navigation/link to follow us. Could be considered navigation. Safer to omit. Also "For the latest news from Aurora, visit aurora.tech or follow us on LinkedIn." We'll omit. Also "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." That's also navigation/boilerplate. Omit. Also "At Aurora, we bring together extraordinarily talented and experienced people united by the strength of our values..." That's values; could be considered boilerplate? Not EEO but still generic. Might be omitted. Also "Our commitment to safety..." and "Our commitment to inclusion..." Might be considered boilerplate but they are substantive about company values. However they are not directly about role. The instruction says prefer few substantive sections over many thin ones. Could omit them to keep sections focused. Thus we will include only sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. Now craft content. About the role paragraph: combine the description from "What We Are Looking For" up to before "In this role you will". Let's extract: "What We Are Looking For As a Staff Technical Program Manager (Release Management), you will report to the Manager of Release Management and join our Software Product-Design team. This is a senior individual contributor (IC) role that balances strategic release architecture and automation with hands-on, day-to-day release train execution. We are hiring for this role to help drive scale and automation in our release operations for predictive prevention, establishing robust automated release gating as our commercial driverless fleet scales from a dozen vehicles to thousands. This is a high-impact opportunity for a force multiplier who thrives on combining hands-on tactical execution with long-term operational scale. You are highly motivated to remove manual friction, manage release operations, and automate software release and deployment frameworks in a safety-critical, high-velocity environment." That's good. Now Responsibilities: list after "In this role you will". The bullet points: - Lead Day-to-Day Release Operations & Cadence: Own and execute the end-to-end release cycle, including orchestrating regular release train schedules, managing branch cut-offs, running daily release/build triage, and coordinating hotfix deployments across software and vehicle platforms. - Cross-Functional Coordination & Release Communication: Serve as the primary operational hub for release readiness, driving daily alignment across engineering, safety, hardware, and test operations teams while maintaining transparent release communications and dashboards. - Drive Predictive Prevention and Release Automation: Shift release operations toward predictive prevention by identifying and eliminating manual friction points, automating release workflows, and utilizing AI/ML tools for triage classification and anomaly detection. - Establish Data-Driven Release Gating: Help architect and maintain automated "Release Gates" that auto-assemble compliance evidence using structured data (Single Source of Truth), ensuring rigorous quality and safety standards before release promotion. - Manage High-Scale Branching & Change Control: Govern and orchestrate concurrent release branches across diverse customers, hardware configurations, and Operational Design Domains (ODDs), maintaining absolute branching hygiene and change control. - Ensure Safety-First Rigor and Auditable Compliance: Treat release documentation and launch reports with software-grade discipline—ensuring version control, complete auditability, and safety compliance without introducing operational bottlenecks. We need to preserve the bold headings? In HTML we can keep them as part of list item text. Now Qualifications (Required Qualifications): list: - 7+ Years of Hands-On Release Experience: Technical program management, release engineering, or systems engineering background with direct, day-to-day release train execution and managing software-hardware integrations in complex environments. - Safety-Critical Domain Expertise: Experience working under strict safety-regulated standards (such as ISO 26262, DO-178C, or ISO 13485) within automotive, aerospace, medical or robotics, with strong configuration management, baseline, and change control practices. - Tactical Build & CI/CD Execution: Practical, hands-on technical experience with CI/CD build automation tools (e.g., Buildkite, GitHub Actions) and monorepo build systems (e.g., Bazel) to troubleshoot and execute daily release operations at scale. - Complex Branching & Daily Triage: Proven track record of orchestrating concurrent release branches, running hands-on daily build/release triage, and executing hotfix deployments across diverse teams and hardware platforms. - Cross-Functional Collaboration & Governance: Collaborative track record of partnering across engineering, safety, hardware, and test operations teams to establish transparent governance, shared release visibility, and cross-team trust. - Customer & Team Support Mindset: Strong team player willing to support internal operations, external partners, and high-priority releases with occasional evening or weekend coverage as needed. - Travel Requirement: Ability to travel to engineering centers in Mountain View, CA, Terminal Operations in Texas or Pittsburgh, PA as business needs arise. Now Skills (Desirable Qualifications): list: - AV & Robotics Background: Direct, hands-on experience in autonomous vehicles, robotics, machine learning systems, or complex cyber-physical environments. - AI-Leveraged Release Operations: Practical experience applying ML/AI tooling to day-to-day release operations, such as automated test-failure classification, triage automation, or pipeline anomaly detection. - Automation-First & Collaborative Mindset: Passion for building self-service release tooling and reducing operational friction while fostering seamless cross-functional alignment and developer enablement. - Cloud & SaaS Infrastructure: Practical familiarity with cloud environments (AWS) and progressive deployment methodologies (feature flagging, progressive delivery, service dependency ordering). - Proactive Execution & Planning: Proven capability