Staff Technical Program Manager
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide which sections to include: About The Team, About The Role, Execution Strategy & Risk Management, Cross-Functional and Strategic Leadership, Process Improvement & Team Growth, Goal Tracking & Reporting, About You, Nice to haves (maybe as "Preferred Qualifications" or "Nice-to-haves"), Benefits, Pay.
We must not create sections with filler. Ensure each heading has substantive content.
Let's extract content.
About The Team paragraph: "The Vehicle Engineering organization at Relativity Space owns the Terran R launch vehicle across its full life cycle - from design through build, qualification, and flight - along with the analysis, software, CONOPs development, risk management, and customer-facing and regulatory activities needed to operate Terran R successfully."
That's prose.
About The Role: multiple paragraphs. We'll combine into prose maybe with lists for duties? The role description includes responsibilities: manage cross-functional program execution across product lifecycle, comfortable operating between 10,000 ft view and zooming in, collaborate with technical leaders, manufacturing and ops counterparts, other program managers to ensure successful execution of top line business objectives, translating ambiguous long-term ideas into clear trade-offs and priorities, analyze problems and drive recommendations balancing technical teams and business, anchoring back to data, actively own and manage schedules, identify & mitigate programmatic risk, drive communication across functional teams, strong desire to build agile, fit for purpose processes from scratch, get your hands dirty, influence wide range of technical and operational teams.
We could turn some of these into
- list for responsibilities. But the instruction: Use
- for any list of duties/requirements/benefits. So we should create a list for duties under About The Role. However we also have a separate section Execution Strategy & Risk Management etc which are more detailed responsibilities. Those could be lists as well.
We need to avoid duplication. The posting already has sections: Execution Strategy & Risk Management, Cross-Functional and Strategic Leadership, Process Improvement & Team Growth, Goal Tracking & Reporting. Those are subheadings under the role description. We should keep them as headings with content.
Thus About The Role could be a brief summary paragraph, then the subsections.
Let's parse:
After "About The Role" heading, we have:
"We are seeking a Staff Technical Program Manager to manage cross-functional program execution across a product lifecycle from early design through to flight. We are looking for someone who is comfortable operating between the 10,000 ft. view of the program and zooming in to solve a critical bottleneck. In this role, they will collaborate with technical leaders, manufacturing and ops counterparts, and other program managers to ensure successful execution of top line business objectives, often translating ambiguous long-term ideas into a set of clear trade-offs and priorities. They will analyze problems and drive recommendations that balance the needs of technical teams and the business, anchoring back to data. They will actively own and manage schedules, identify & mitigate programmatic risk, and drive communication across functional teams. A strong desire to build agile, fit for purpose processes from scratch, get your hands dirty, and influence a wide range of technical and operational teams are foundational to success in this role."
That's prose; we can keep as
.
Then we have subheadings:
Execution Strategy & Risk Management
- bullet points (each line starts with a verb). We'll make
- .
Cross-Functional and Strategic Leadership
- bullet points.
Process Improvement & Team Growth
- bullet points.
Goal Tracking & Reporting
- bullet points.
About You
- bullet points (requirements). We'll make list.
On Other Teams And At The Company Level (nice to haves) - bullet points.
Benefits: we have list: competitive salary and equity, generous PTO and sick leave policy, parental leave, annual learning and development stipend. We'll make list.
Pay: hiring range $152,000—$228,000 USD. We'll make
maybe.
We must not include sections like Schedule.
Now ensure we don't include boilerplate: EEO line, accommodation line, unsolicited resumes line, "We are an equal opportunity employer..." etc. Also remove "If you need a reasonable accommodation, please contact us at accommodations@relativityspace.com." Remove "Please note: Relativity Space does not accept unsolicited resumes..." etc.
Also remove "At Relativity Space, we are committed to transparency and fairness in our compensation practices." maybe.
Now produce HTML.
Structure:
About The Team
...
About The Role
...
Execution Strategy & Risk Management
- Translate long-term business objectives and priorities into a clear execution plan for your area of ownership
- Build and own the schedule, deriving it from real requirements, resources, and dependencies & ensuring alignment with key company milestones
- Identify, assess, and mitigate risks associated with program execution, ensuring proactive resolution of issues coming down the pipeline
- Identify resource gaps and coordinate cross-functional planning for resource allocation, including headcount, budget, and workspace needs
- Develop ways of working and cadences between teams to ensure efficient execution, collaboration, and alignment
- Communicate program updates, risks, and trade-offs to senior management and cross-functional stakeholders, grounded in data, deciphering signal from noise, and driving decision making when required
- Identify and drive to resolve future programmatic risks, keeping line of sight to 12mo+ strategic initiatives that are critical for business milestones
Cross-Functional and Strategic Leadership
- Collaborate with PMOs and department leaders to integrate workstream schedules into the program-level Integrated Master Schedule (IMS), and use the IMS to understand true program critical path, dependencies, and decision points
- Work with functional partners to align priorities when there are competing needs
- Drive improvements to department-level program management tooling to continually improve program efficiency and operational excellence
- Coordinate efforts across key bodies of work over development lifecycle, including design release, engineering trades, handoffs between teams, and operational burndown ahead of key milestones
- Incorporate new capabilities leveraging automation and AI, when available
- Lead by influence and collaborate with technical owners (engineering, supply chain, manufacturing, test, and launch) to establish a plan & empower strong functional ownership
Process Improvement & Team Growth
- Spearhead the creation and continual refinement of effective, lightweight program management processes, tools, and templates that improve efficiency and cross-team collaboration
- Establish ways of working and ownership model to ensure programmatic lessons learned are being incorporated each design, build, test, launch cycle
- Build trust, credibility, and buy-in with functional team & program stakeholders to implement processes effectively
Goal Tracking & Reporting
- Establish goals and metrics to monitor program performance and increase the predictability and efficiency of engineering work
- Monitor and report on progress toward organizational goals, objectives, and milestones, presenting an objective and clear path forward
- Facilitate strong communication within departments and across the program to ensure transparency in program status & maintain culture of high ownership
About You
- Bachelor's degree in engineering, science, mathematics, or a related field; aerospace, electrical, or mechanical engineering degree preferred
- 7+ years leading a complex program. This can include work in a program management role or a technical role where you were leading a large complex technical hardware program. Experience spanning software and operations preferred
- Demonstrated success supporting cross-functional hardware teams from concept through delivery in fast-paced, high-ambiguity environments
- Able to move fluidly between tactical execution and big-picture perspective
- Track record of solving ambiguous problems, developing processes and tools from scratch. Able to work scrappy whilst building sustainable longterm processes
- Proven ability to communicate with highly technical teams and bridge communication between technical and non-technical audiences
- A systems mindset: able to identify program dependencies, interfaces, and risks, and understand the impact of technical and program decisions
Nice-to-haves
- Hands-on experience with launch vehicles, propulsion systems, or aerospace hardware
- PMP, MBA, Master's in engineering, science, mathematics, or related field, or equivalent experience
- Strong executive presence, with the ability to drive clarity and action across all levels of the company
- Technical leadership experience, proven track record of success and strategic thinking while balancing conflicting priorities and goals
Benefits
- Competitive salary and equity
- Generous PTO and sick leave policy
- Parental leave
- Annual learning and development stipend
Pay
Hiring range: $152,000—$228,000 USD
Check for any leftover boilerplate: we removed EEO etc. Also removed "To see some of the benefits & perks we offer, please visit here." Good.
Now ensure no duplicate content: The About The Role paragraph we included earlier. Let's craft that paragraph:
We are seeking a Staff Technical Program Manager to manage cross-functional program execution across a product lifecycle from early design through to flight. We are looking for someone who is comfortable operating between the 10,000 ft. view of the program and zooming in to solve a critical
for prose. We need to decide which sections to include: About The Team, About The Role, Execution Strategy & Risk Management, Cross-Functional and Strategic Leadership, Process Improvement & Team Growth, Goal Tracking & Reporting, About You, Nice to haves (maybe as "Preferred Qualifications" or "Nice-to-haves"), Benefits, Pay. We must not create sections with filler. Ensure each heading has substantive content. Let's extract content. About The Team paragraph: "The Vehicle Engineering organization at Relativity Space owns the Terran R launch vehicle across its full life cycle - from design through build, qualification, and flight - along with the analysis, software, CONOPs development, risk management, and customer-facing and regulatory activities needed to operate Terran R successfully." That's prose. About The Role: multiple paragraphs. We'll combine into prose maybe with lists for duties? The role description includes responsibilities: manage cross-functional program execution across product lifecycle, comfortable operating between 10,000 ft view and zooming in, collaborate with technical leaders, manufacturing and ops counterparts, other program managers to ensure successful execution of top line business objectives, translating ambiguous long-term ideas into clear trade-offs and priorities, analyze problems and drive recommendations balancing technical teams and business, anchoring back to data, actively own and manage schedules, identify & mitigate programmatic risk, drive communication across functional teams, strong desire to build agile, fit for purpose processes from scratch, get your hands dirty, influence wide range of technical and operational teams. We could turn some of these into
- list for responsibilities. But the instruction: Use
- for any list of duties/requirements/benefits. So we should create a list for duties under About The Role. However we also have a separate section Execution Strategy & Risk Management etc which are more detailed responsibilities. Those could be lists as well.
We need to avoid duplication. The posting already has sections: Execution Strategy & Risk Management, Cross-Functional and Strategic Leadership, Process Improvement & Team Growth, Goal Tracking & Reporting. Those are subheadings under the role description. We should keep them as headings with content.
Thus About The Role could be a brief summary paragraph, then the subsections.
Let's parse:
After "About The Role" heading, we have:
"We are seeking a Staff Technical Program Manager to manage cross-functional program execution across a product lifecycle from early design through to flight. We are looking for someone who is comfortable operating between the 10,000 ft. view of the program and zooming in to solve a critical bottleneck. In this role, they will collaborate with technical leaders, manufacturing and ops counterparts, and other program managers to ensure successful execution of top line business objectives, often translating ambiguous long-term ideas into a set of clear trade-offs and priorities. They will analyze problems and drive recommendations that balance the needs of technical teams and the business, anchoring back to data. They will actively own and manage schedules, identify & mitigate programmatic risk, and drive communication across functional teams. A strong desire to build agile, fit for purpose processes from scratch, get your hands dirty, and influence a wide range of technical and operational teams are foundational to success in this role."
That's prose; we can keep as
. Then we have subheadings: Execution Strategy & Risk Management - bullet points (each line starts with a verb). We'll make
- .
Cross-Functional and Strategic Leadership
- bullet points.
Process Improvement & Team Growth
- bullet points.
Goal Tracking & Reporting
- bullet points.
About You
- bullet points (requirements). We'll make list.
On Other Teams And At The Company Level (nice to haves) - bullet points.
Benefits: we have list: competitive salary and equity, generous PTO and sick leave policy, parental leave, annual learning and development stipend. We'll make list.
Pay: hiring range $152,000—$228,000 USD. We'll make
maybe. We must not include sections like Schedule. Now ensure we don't include boilerplate: EEO line, accommodation line, unsolicited resumes line, "We are an equal opportunity employer..." etc. Also remove "If you need a reasonable accommodation, please contact us at accommodations@relativityspace.com." Remove "Please note: Relativity Space does not accept unsolicited resumes..." etc. Also remove "At Relativity Space, we are committed to transparency and fairness in our compensation practices." maybe. Now produce HTML. Structure:
About The Team
...
About The Role
...
Execution Strategy & Risk Management
- Translate long-term business objectives and priorities into a clear execution plan for your area of ownership
- Build and own the schedule, deriving it from real requirements, resources, and dependencies & ensuring alignment with key company milestones
- Identify, assess, and mitigate risks associated with program execution, ensuring proactive resolution of issues coming down the pipeline
- Identify resource gaps and coordinate cross-functional planning for resource allocation, including headcount, budget, and workspace needs
- Develop ways of working and cadences between teams to ensure efficient execution, collaboration, and alignment
- Communicate program updates, risks, and trade-offs to senior management and cross-functional stakeholders, grounded in data, deciphering signal from noise, and driving decision making when required
- Identify and drive to resolve future programmatic risks, keeping line of sight to 12mo+ strategic initiatives that are critical for business milestones
Cross-Functional and Strategic Leadership
- Collaborate with PMOs and department leaders to integrate workstream schedules into the program-level Integrated Master Schedule (IMS), and use the IMS to understand true program critical path, dependencies, and decision points
- Work with functional partners to align priorities when there are competing needs
- Drive improvements to department-level program management tooling to continually improve program efficiency and operational excellence
- Coordinate efforts across key bodies of work over development lifecycle, including design release, engineering trades, handoffs between teams, and operational burndown ahead of key milestones
- Incorporate new capabilities leveraging automation and AI, when available
- Lead by influence and collaborate with technical owners (engineering, supply chain, manufacturing, test, and launch) to establish a plan & empower strong functional ownership
Process Improvement & Team Growth
- Spearhead the creation and continual refinement of effective, lightweight program management processes, tools, and templates that improve efficiency and cross-team collaboration
- Establish ways of working and ownership model to ensure programmatic lessons learned are being incorporated each design, build, test, launch cycle
- Build trust, credibility, and buy-in with functional team & program stakeholders to implement processes effectively
Goal Tracking & Reporting
- Establish goals and metrics to monitor program performance and increase the predictability and efficiency of engineering work
- Monitor and report on progress toward organizational goals, objectives, and milestones, presenting an objective and clear path forward
- Facilitate strong communication within departments and across the program to ensure transparency in program status & maintain culture of high ownership
About You
- Bachelor's degree in engineering, science, mathematics, or a related field; aerospace, electrical, or mechanical engineering degree preferred
- 7+ years leading a complex program. This can include work in a program management role or a technical role where you were leading a large complex technical hardware program. Experience spanning software and operations preferred
- Demonstrated success supporting cross-functional hardware teams from concept through delivery in fast-paced, high-ambiguity environments
- Able to move fluidly between tactical execution and big-picture perspective
- Track record of solving ambiguous problems, developing processes and tools from scratch. Able to work scrappy whilst building sustainable longterm processes
- Proven ability to communicate with highly technical teams and bridge communication between technical and non-technical audiences
- A systems mindset: able to identify program dependencies, interfaces, and risks, and understand the impact of technical and program decisions
Nice-to-haves
- Hands-on experience with launch vehicles, propulsion systems, or aerospace hardware
- PMP, MBA, Master's in engineering, science, mathematics, or related field, or equivalent experience
- Strong executive presence, with the ability to drive clarity and action across all levels of the company
- Technical leadership experience, proven track record of success and strategic thinking while balancing conflicting priorities and goals
Benefits
- Competitive salary and equity
- Generous PTO and sick leave policy
- Parental leave
- Annual learning and development stipend
Pay
Hiring range: $152,000—$228,000 USD
Check for any leftover boilerplate: we removed EEO etc. Also removed "To see some of the benefits & perks we offer, please visit here." Good. Now ensure no duplicate content: The About The Role paragraph we included earlier. Let's craft that paragraph:We are seeking a Staff Technical Program Manager to manage cross-functional program execution across a product lifecycle from early design through to flight. We are looking for someone who is comfortable operating between the 10,000 ft. view of the program and zooming in to solve a critical
- .
Cross-Functional and Strategic Leadership
- bullet points.
Process Improvement & Team Growth
- bullet points.
Goal Tracking & Reporting
- bullet points.
About You
- bullet points (requirements). We'll make list.
On Other Teams And At The Company Level (nice to haves) - bullet points.
Benefits: we have list: competitive salary and equity, generous PTO and sick leave policy, parental leave, annual learning and development stipend. We'll make list.
Pay: hiring range $152,000—$228,000 USD. We'll make
- for any list of duties/requirements/benefits. So we should create a list for duties under About The Role. However we also have a separate section Execution Strategy & Risk Management etc which are more detailed responsibilities. Those could be lists as well.
We need to avoid duplication. The posting already has sections: Execution Strategy & Risk Management, Cross-Functional and Strategic Leadership, Process Improvement & Team Growth, Goal Tracking & Reporting. Those are subheadings under the role description. We should keep them as headings with content.
Thus About The Role could be a brief summary paragraph, then the subsections.
Let's parse:
After "About The Role" heading, we have:
"We are seeking a Staff Technical Program Manager to manage cross-functional program execution across a product lifecycle from early design through to flight. We are looking for someone who is comfortable operating between the 10,000 ft. view of the program and zooming in to solve a critical bottleneck. In this role, they will collaborate with technical leaders, manufacturing and ops counterparts, and other program managers to ensure successful execution of top line business objectives, often translating ambiguous long-term ideas into a set of clear trade-offs and priorities. They will analyze problems and drive recommendations that balance the needs of technical teams and the business, anchoring back to data. They will actively own and manage schedules, identify & mitigate programmatic risk, and drive communication across functional teams. A strong desire to build agile, fit for purpose processes from scratch, get your hands dirty, and influence a wide range of technical and operational teams are foundational to success in this role."
That's prose; we can keep as