Lead, Resilience Governance
Waymo · San Francisco, CA · 1 mo ago
OTHR$168k–$207k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes description of company and role. We need to use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real, specific content. We need to preserve all substantive info, no boilerplate.
We need to parse the posting: It starts with description of Waymo, then "In this hybrid role you will report into our Program Manager, Resilience Policy & Process." Then bullet-like sentences describing responsibilities: "You Will Build, own, and continuously improve resilience policies, standards, and plans (including incident and crisis response), ensuring direct alignment with Waymo's Safety Management System (SMS). Cultivate and manage robust cross-functional partnerships ... Lead value stream and process mapping initiatives ... Drive continuous improvement and SMS assurance ... Ensure vendor and partner continuity plans ...". Those are responsibilities.
Then "You Have 5+ years of experience building and writing policy, standards, and processes, especially in resilience, incident management, operations, and/or business continuity. Track record of strong cross-functional partnership ... Extreme curiosity ... Exceptional attention to detail ... Experience reviewing and participating in after action reviews ... Ability to productively solicit feedback ...". Those are requirements/qualifications/skills.
Then "We Prefer Experience with technical writing, especially in a Safety, Product, or Operations focused environment. Background in the autonomous, transportation, and/or weather forecast and response fields. Experience contributing to the implementation or revision of Safety Management Systems (SMS) or equivalent compliance programs. Experience in highly regulated industries such as Automotive, Maritime, Aviation, or similar sectors, providing familiarity with safety-critical systems, compliance frameworks, and complex operational procedures. Certifications or other relevant experience with incident management and business continuity best practices and frameworks (e.g., NIMS/ICS, ITIL Incident Management, or similar), indicating a structured approach to incident handling and continuous improvement." Those are preferred qualifications.
Then "Travel As required, The expected base salary range for this full-time position across US locations is listed below. Actual starting pay will be based on job-related factors, including exact work location, experience, relevant training and education, and skill level. Your recruiter can share more about the specific salary range for the role location or, if the role can be performed remote, the specific salary range for your preferred location, during the hiring process. Waymo employees are also eligible to participate in Waymo’s discretionary annual bonus program, equity incentive plan, and generous Company benefits program, subject to eligibility requirements. Salary Range $168,000—$207,000 USD"
Thus we have Pay info: Salary Range $168,000—$207,000 USD. Also mention bonus, equity, benefits. So we can have a Benefits section (bonus, equity, benefits). Also Travel As required could be Schedule? Not exactly schedule; but Travel As required is maybe a note about travel. Could be under Schedule? The instruction says include Schedule section only if posting actually states them. It mentions "Travel As required". That's not a schedule like full-time/part-time, but it's a requirement. Might be better to put under a "Travel" note but we don't have a heading for Travel. Could incorporate into Responsibilities or a note. Since we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put Travel under Schedule? Not ideal but maybe we can treat "Travel As required" as schedule note. However the instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Travel As required, which could be considered schedule/travel requirement. So we can include a Schedule section with that line.
We also have Benefits: discretionary annual bonus program, equity incentive plan, generous Company benefits program.
We have Pay: Salary Range $168,000—$207,000 USD.
We need About the role: maybe a brief paragraph summarizing role and company description. The posting includes company description at start; we can put that under About the role.
We must not repeat job title as heading. No Job ID.
We must use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real, specific content. We need to preserve all substantive info, no boilerplate.
We need to parse the posting: It starts with description of Waymo, then "In this hybrid role you will report into our Program Manager, Resilience Policy & Process." Then bullet-like sentences describing responsibilities: "You Will Build, own, and continuously improve resilience policies, standards, and plans (including incident and crisis response), ensuring direct alignment with Waymo's Safety Management System (SMS). Cultivate and manage robust cross-functional partnerships ... Lead value stream and process mapping initiatives ... Drive continuous improvement and SMS assurance ... Ensure vendor and partner continuity plans ...". Those are responsibilities.
Then "You Have 5+ years of experience building and writing policy, standards, and processes, especially in resilience, incident management, operations, and/or business continuity. Track record of strong cross-functional partnership ... Extreme curiosity ... Exceptional attention to detail ... Experience reviewing and participating in after action reviews ... Ability to productively solicit feedback ...". Those are requirements/qualifications/skills.
Then "We Prefer Experience with technical writing, especially in a Safety, Product, or Operations focused environment. Background in the autonomous, transportation, and/or weather forecast and response fields. Experience contributing to the implementation or revision of Safety Management Systems (SMS) or equivalent compliance programs. Experience in highly regulated industries such as Automotive, Maritime, Aviation, or similar sectors, providing familiarity with safety-critical systems, compliance frameworks, and complex operational procedures. Certifications or other relevant experience with incident management and business continuity best practices and frameworks (e.g., NIMS/ICS, ITIL Incident Management, or similar), indicating a structured approach to incident handling and continuous improvement." Those are preferred qualifications.
Then "Travel As required, The expected base salary range for this full-time position across US locations is listed below. Actual starting pay will be based on job-related factors, including exact work location, experience, relevant training and education, and skill level. Your recruiter can share more about the specific salary range for the role location or, if the role can be performed remote, the specific salary range for your preferred location, during the hiring process. Waymo employees are also eligible to participate in Waymo’s discretionary annual bonus program, equity incentive plan, and generous Company benefits program, subject to eligibility requirements. Salary Range $168,000—$207,000 USD"
Thus we have Pay info: Salary Range $168,000—$207,000 USD. Also mention bonus, equity, benefits. So we can have a Benefits section (bonus, equity, benefits). Also Travel As required could be Schedule? Not exactly schedule; but Travel As required is maybe a note about travel. Could be under Schedule? The instruction says include Schedule section only if posting actually states them. It mentions "Travel As required". That's not a schedule like full-time/part-time, but it's a requirement. Might be better to put under a "Travel" note but we don't have a heading for Travel. Could incorporate into Responsibilities or a note. Since we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put Travel under Schedule? Not ideal but maybe we can treat "Travel As required" as schedule note. However the instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Travel As required, which could be considered schedule/travel requirement. So we can include a Schedule section with that line.
We also have Benefits: discretionary annual bonus program, equity incentive plan, generous Company benefits program.
We have Pay: Salary Range $168,000—$207,000 USD.
We need About the role: maybe a brief paragraph summarizing role and company description. The posting includes company description at start; we can put that under About the role.
We must not repeat job title as heading. No Job ID.
We must use for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive info; do not invent or summarize away detail. So we need to keep each bullet point as separate
- maybe.
We need to decide which items go where.
Let's extract:
About the role: Could include company mission and description: "Waymo is an autonomous driving technology company with the mission to be the world's most trusted driver. Since its start as the Google Self-Driving Car Project in 2009, Waymo has focused on building the Waymo Driver—The World's Most Experienced Driver™—to improve access to mobility while saving thousands of lives now lost to traffic crashes. The Waymo Driver powers Waymo’s fully autonomous ride-hail service and can also be applied to a range of vehicle platforms and product use cases. The Waymo Driver has provided over ten million rider-only trips, enabled by its experience autonomously driving over 100 million miles on public roads and tens of billions in simulation across 15+ U.S. states. The Waymo Safety team works to promote and help to continuously improve the safety of Waymo’s fully autonomous driving technology. Our experts develop safety goals and strategies, and conduct safety engineering analyses to ensure safety is being considered throughout the design and development of our vehicles. The team develops and promotes safety strategies and policies for autonomous vehicles for its work with regulatory authorities, lawmakers, law enforcement and public and non-profit organizations. Our Safety Team also helps advise on compliance with applicable environmental, health, and safety regulations. In this hybrid role you will report into our Program Manager, Resilience Policy & Process."
That seems like About the role.
Responsibilities: The bullet points after "You Will": Build, own, and continuously improve resilience policies, standards, and plans (including incident and crisis response), ensuring direct alignment with Waymo's Safety Management System (SMS). Cultivate and manage robust cross-functional partnerships (e.g., with Product, Engineering, Operations, Facilities, Legal, and Policy) to design complex process flows, escalation pathways, and robust operational tooling for event-response protocols globally. Lead value stream and process mapping initiatives (from monitoring/triggers to severity categorization) and project manage sub-working groups to standardize resilient workflows across new and existing markets. Drive continuous improvement and SMS assurance by incorporating post-incident reviews and retrospectives to determine root causes, identify corrective actions, and prevent future occurrences. Ensure vendor and partner continuity plans are robustly aligned to support scalability; support the organization's preparation for external audits, inspections, or regulatory assessments across new global geos.
We can list each as
- .
Requirements: The "You Have" bullet points: 5+ years of experience building and writing policy, standards, and processes, especially in resilience, incident management, operations, and/or business continuity. Track record of strong cross-functional partnership with diverse stakeholders, especially to design complex process and escalation flows with a Product and Engineering focus. Extreme curiosity to understand the status quo, always asks “why?”, and considers alternatives. Exceptional attention to detail with the ability to synthesize complex information into clear and concise documentation. Experience reviewing and participating in after action reviews and retrospectives to identify action items for continuous improvement initiatives. Ability to productively solicit feedback and input from stakeholders to build a comprehensive narrative.
We could treat these as Requirements.
Qualifications: maybe the "We Prefer" section? But we also have Skills maybe. The instruction includes Qualifications and Skills separate headings. We need to decide distribution.
We have "We Prefer Experience with technical writing, especially in a Safety, Product, or Operations focused environment. Background in the autonomous, transportation, and/or weather forecast and response fields. Experience contributing to the implementation or revision of Safety Management Systems (SMS) or equivalent compliance programs. Experience in highly regulated industries such as Automotive, Maritime, Aviation, or similar sectors, providing familiarity with safety-critical systems, compliance frameworks, and complex operational procedures. Certifications or other relevant experience with incident management and business continuity best practices and frameworks (e.g., NIMS/ICS, ITIL Incident Management, or similar), indicating a structured approach to incident handling and continuous improvement."
These are preferred qualifications. Could go under Qualifications.
Skills: maybe we could extract technical writing, etc. But we might not need Skills if we already have Qualifications covering them. However we need to include a section only when posting has real, specific content. We have content for Qualifications (preferred). We could also have Skills maybe from "Exceptional attention to detail", "Ability to productively solicit feedback", etc. Those are more like skills. But we already used them under Requirements. Could shift some to Skills.
Better: Requirements = mandatory experience (5+ years, track record, etc). Skills = abilities like extreme curiosity, attention to detail, ability to synthesize, ability to solicit feedback, experience reviewing after action reviews, etc. Qualifications = preferred qualifications (technical writing background, autonomous/transportation/weather, SMS experience, regulated industry experience, certifications). That seems logical.
Thus:
About the role: paragraph(s) as above.
Responsibilities: list of 5 items.
Requirements: list of 6 items (the You Have bullets). Actually there are 6 bullet points: 5+ years experience, track record, extreme curiosity, exceptional attention to detail, experience reviewing after action reviews, ability to solicit feedback.
Skills: maybe we could include "Extreme curiosity", "Exceptional attention to detail", "Ability to productively solicit feedback", "Experience reviewing and participating in after action reviews". But those are already in Requirements. Hmm.
We need to avoid duplication. Let's decide: Requirements = the mandatory experience and track record (5+ years, track record). Skills = the personal attributes and abilities (extreme curiosity, attention to detail, ability to synthesize, ability to solicit feedback, experience reviewing after action reviews). Qualifications = preferred qualifications (technical writing, background, SMS, regulated industry, certifications). That seems okay.
Thus:
Requirements (mandatory):
- 5+ years of experience building and writing policy, standards, and processes, especially in resilience, incident management, operations, and/or business continuity.
- Track record of strong cross-functional partnership with diverse stakeholders, especially to design complex process and escalation flows with a Product and Engineering focus.
Skills:
- Extreme curiosity to understand the status quo, always asks “why?”, and considers alternatives.
- Exceptional attention to detail with the ability to synthesize complex information into clear and concise documentation.
- Experience reviewing and participating in after action reviews and retrospectives to identify action items for continuous improvement initiatives.
- Ability to productively solicit feedback and input from stakeholders to build a comprehensive narrative.
Qualifications (preferred):
- Experience with technical writing, especially in a Safety, Product, or Operations focused environment.
- Background in the autonomous, transportation, and/or weather forecast and response fields.
- Experience contributing to the implementation or revision of Safety Management Systems (SMS) or equivalent compliance programs.
- Experience in highly regulated industries such as Automotive, Maritime, Aviation, or similar sectors, providing familiarity with safety-critical systems, compliance frameworks, and complex operational procedures.
- Certifications or other relevant experience with incident management and business continuity best practices and frameworks (e.g., NIMS/ICS, ITIL Incident Management, or similar), indicating a structured approach to incident handling and continuous improvement.
Benefits:
- Discretionary annual bonus program.
- Equity incentive plan.
- Generous Company benefits program (subject to eligibility).
Pay:
- Salary Range $168,000—$207,000 USD.
Schedule:
- Travel as required.
We must not include filler like "commensurate with experience". Not present.
We need to output only HTML fragment, no markdown fences.
Thus:
About the role
Waymo is an autonomous driving technology company with the mission to be the world's most trusted driver. Since its start as the Google Self-Driving Car Project in 2009, Waymo
- for any list of duties/requirements/benefits. Use
for prose. We need to preserve all substantive info; do not invent or summarize away detail. So we need to keep each bullet point as separate
- maybe. We need to decide which items go where. Let's extract: About the role: Could include company mission and description: "Waymo is an autonomous driving technology company with the mission to be the world's most trusted driver. Since its start as the Google Self-Driving Car Project in 2009, Waymo has focused on building the Waymo Driver—The World's Most Experienced Driver™—to improve access to mobility while saving thousands of lives now lost to traffic crashes. The Waymo Driver powers Waymo’s fully autonomous ride-hail service and can also be applied to a range of vehicle platforms and product use cases. The Waymo Driver has provided over ten million rider-only trips, enabled by its experience autonomously driving over 100 million miles on public roads and tens of billions in simulation across 15+ U.S. states. The Waymo Safety team works to promote and help to continuously improve the safety of Waymo’s fully autonomous driving technology. Our experts develop safety goals and strategies, and conduct safety engineering analyses to ensure safety is being considered throughout the design and development of our vehicles. The team develops and promotes safety strategies and policies for autonomous vehicles for its work with regulatory authorities, lawmakers, law enforcement and public and non-profit organizations. Our Safety Team also helps advise on compliance with applicable environmental, health, and safety regulations. In this hybrid role you will report into our Program Manager, Resilience Policy & Process." That seems like About the role. Responsibilities: The bullet points after "You Will": Build, own, and continuously improve resilience policies, standards, and plans (including incident and crisis response), ensuring direct alignment with Waymo's Safety Management System (SMS). Cultivate and manage robust cross-functional partnerships (e.g., with Product, Engineering, Operations, Facilities, Legal, and Policy) to design complex process flows, escalation pathways, and robust operational tooling for event-response protocols globally. Lead value stream and process mapping initiatives (from monitoring/triggers to severity categorization) and project manage sub-working groups to standardize resilient workflows across new and existing markets. Drive continuous improvement and SMS assurance by incorporating post-incident reviews and retrospectives to determine root causes, identify corrective actions, and prevent future occurrences. Ensure vendor and partner continuity plans are robustly aligned to support scalability; support the organization's preparation for external audits, inspections, or regulatory assessments across new global geos. We can list each as
- .
Requirements: The "You Have" bullet points: 5+ years of experience building and writing policy, standards, and processes, especially in resilience, incident management, operations, and/or business continuity. Track record of strong cross-functional partnership with diverse stakeholders, especially to design complex process and escalation flows with a Product and Engineering focus. Extreme curiosity to understand the status quo, always asks “why?”, and considers alternatives. Exceptional attention to detail with the ability to synthesize complex information into clear and concise documentation. Experience reviewing and participating in after action reviews and retrospectives to identify action items for continuous improvement initiatives. Ability to productively solicit feedback and input from stakeholders to build a comprehensive narrative.
We could treat these as Requirements.
Qualifications: maybe the "We Prefer" section? But we also have Skills maybe. The instruction includes Qualifications and Skills separate headings. We need to decide distribution.
We have "We Prefer Experience with technical writing, especially in a Safety, Product, or Operations focused environment. Background in the autonomous, transportation, and/or weather forecast and response fields. Experience contributing to the implementation or revision of Safety Management Systems (SMS) or equivalent compliance programs. Experience in highly regulated industries such as Automotive, Maritime, Aviation, or similar sectors, providing familiarity with safety-critical systems, compliance frameworks, and complex operational procedures. Certifications or other relevant experience with incident management and business continuity best practices and frameworks (e.g., NIMS/ICS, ITIL Incident Management, or similar), indicating a structured approach to incident handling and continuous improvement."
These are preferred qualifications. Could go under Qualifications.
Skills: maybe we could extract technical writing, etc. But we might not need Skills if we already have Qualifications covering them. However we need to include a section only when posting has real, specific content. We have content for Qualifications (preferred). We could also have Skills maybe from "Exceptional attention to detail", "Ability to productively solicit feedback", etc. Those are more like skills. But we already used them under Requirements. Could shift some to Skills.
Better: Requirements = mandatory experience (5+ years, track record, etc). Skills = abilities like extreme curiosity, attention to detail, ability to synthesize, ability to solicit feedback, experience reviewing after action reviews, etc. Qualifications = preferred qualifications (technical writing background, autonomous/transportation/weather, SMS experience, regulated industry experience, certifications). That seems logical.
Thus:
About the role: paragraph(s) as above.
Responsibilities: list of 5 items.
Requirements: list of 6 items (the You Have bullets). Actually there are 6 bullet points: 5+ years experience, track record, extreme curiosity, exceptional attention to detail, experience reviewing after action reviews, ability to solicit feedback.
Skills: maybe we could include "Extreme curiosity", "Exceptional attention to detail", "Ability to productively solicit feedback", "Experience reviewing and participating in after action reviews". But those are already in Requirements. Hmm.
We need to avoid duplication. Let's decide: Requirements = the mandatory experience and track record (5+ years, track record). Skills = the personal attributes and abilities (extreme curiosity, attention to detail, ability to synthesize, ability to solicit feedback, experience reviewing after action reviews). Qualifications = preferred qualifications (technical writing, background, SMS, regulated industry, certifications). That seems okay.
Thus:
Requirements (mandatory):
- 5+ years of experience building and writing policy, standards, and processes, especially in resilience, incident management, operations, and/or business continuity.
- Track record of strong cross-functional partnership with diverse stakeholders, especially to design complex process and escalation flows with a Product and Engineering focus.
Skills:
- Extreme curiosity to understand the status quo, always asks “why?”, and considers alternatives.
- Exceptional attention to detail with the ability to synthesize complex information into clear and concise documentation.
- Experience reviewing and participating in after action reviews and retrospectives to identify action items for continuous improvement initiatives.
- Ability to productively solicit feedback and input from stakeholders to build a comprehensive narrative.
Qualifications (preferred):
- Experience with technical writing, especially in a Safety, Product, or Operations focused environment.
- Background in the autonomous, transportation, and/or weather forecast and response fields.
- Experience contributing to the implementation or revision of Safety Management Systems (SMS) or equivalent compliance programs.
- Experience in highly regulated industries such as Automotive, Maritime, Aviation, or similar sectors, providing familiarity with safety-critical systems, compliance frameworks, and complex operational procedures.
- Certifications or other relevant experience with incident management and business continuity best practices and frameworks (e.g., NIMS/ICS, ITIL Incident Management, or similar), indicating a structured approach to incident handling and continuous improvement.
Benefits:
- Discretionary annual bonus program.
- Equity incentive plan.
- Generous Company benefits program (subject to eligibility).
Pay:
- Salary Range $168,000—$207,000 USD.
Schedule:
- Travel as required.
We must not include filler like "commensurate with experience". Not present.
We need to output only HTML fragment, no markdown fences.
Thus:
About the role
Waymo is an autonomous driving technology company with the mission to be the world's most trusted driver. Since its start as the Google Self-Driving Car Project in 2009, Waymo