Technical Program Manager, Solutions
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to parse the posting.
We have:
- About The Role: description of role, responsibilities, etc. So we can have About the role
with
content. - Impact You'll Own: seems like responsibilities. Could be under Responsibilities. - What You Bring: qualifications/requirements. - What Makes You Stand Out: maybe skills or additional qualifications. - Benefits: listed. - Compensation: salary range. - Schedule: "This is a full-time, hybrid role which will require you to work from our Washington, DC or Denver, CO office 3 days per week." So schedule info. - Also there is Application Deadline, EAR/ITAR Requirements, etc. Those are not required sections; we can drop or fold into short p? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we could include a short p for Application Deadline and EAR/ITAR maybe. But we must not repeat job title as heading. The page already shows it, so we don't add heading for Technical Program Manager. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out EEO statement, Privacy Policy, AI in Interviewing Process, Candidate AI Policy, etc. Also remove "Welcome to Planet..." intro? That's company description; maybe we can keep as part of About the role? Probably not needed; but we can include a brief intro? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The intro about Planet is substantive? It's company overview; maybe we can keep as a short p under About the role? But the heading "About the role" is for role specifics; company overview maybe not needed. However we could include a short p before sections? The instruction says output ONLY the HTML fragment; we can include multiple sections. We could include a
for company overview if we want to preserve. But they said "Prefer a few substantive sections over many thin ones." Might be okay to include a brief intro as a
before sections. But we must not include boilerplate like EEO, Privacy Policy, etc. So we strip those. We need to decide sections: - About the role: include role description: "As a Technical Program Manager (TPM) at Planet, you will drive Planet’s largest, complex efforts that cross many teams and organizational boundaries. You will focus on execution of programs through the product life cycle. You will work closely with team leads to develop and manage end to end program plans. This includes establishing and managing internal processes, schedules, metrics, risks, and clearly communicating them to project stakeholders. You will work with both technical and non-technical teams. We are looking for a Technical Program Manager to support solutions development for Defense and Intelligence. You will be the connective tissue between Product, Engineering, and our customers, turning big-picture roadmaps into structured execution plans and accountable timelines. From managing custom customer deployments to supporting the engineering release train, you’ll cut through ambiguity, manage cross-functional dependencies, and proactively mitigate risk to ensure seamless delivery." - Responsibilities: maybe "Impact You'll Own" bullet list. Let's extract bullet-like sentences: Orchestrate end-to-end program execution across Engineering, Product, Design, Space Systems, Enablement, and Customer Support to ensure successful releases. Scope comprehensive program schedules and break down complex requirements into actionable, incremental milestones. Translate requirements across business and technical stakeholders with communication clarity. Identify dependencies and risks and proactively mitigate them. Facilitate decision making through data-driven analysis and healthy debate. Communicate vertically & horizontally across Planet to keep stakeholders informed of progress, priorities, risks, and changes to requirements or plans. Drive for results by continuously improving ways of working and processes, now and for the future. We can put these as
- items.
- Requirements / Qualifications: "What You Bring": 4+ years of software development or program management experience in the areas of SaaS, platform development, or analytics. Bachelor’s degree in a relevant field. Experience working with cross-functional teams across a broad organization. Thrives in ambiguous environments, with a track record of designing and implementing scalable processes and frameworks from scratch. Experience with the product life cycle: concept through development, launch preparation, go-to-market, deprecations, and end-of-life. Analytical, problem-solving, and creative thinking skills paired with the ability to communicate findings and recommendations. Equally comfortable explaining your analyses and recommendations to business leaders as you are discussing technical trade-offs with engineers. Ability to balance the tactical day-to-day with forward-looking improvements to scale operational efficiencies.
We could split into Requirements (experience, education) and Qualifications (skills). But we have headings for Requirements and Qualifications separate. We could put experience/education under Requirements, and skills under Qualifications. Or we could combine. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine into one section "Requirements" covering all. But we have both headings available; we could use Requirements for experience/education, Qualifications for skills. That seems reasonable.
- Skills: "What Makes You Stand Out": desire to improve processes, tools, and ways of working to scale operations cycles. Experience with remote sensing, earth observation data, or geospatial systems. Experience working with remote, worldwide teams. A growth mindset and a desire to learn quickly. Actively exploring AI technologies to automate workflows, improve data, or enhance team productivity.
We could put these under Skills.
- Benefits: list: Comprehensive Medical, Dental, and Vision plans; Health Savings Account (HSA) with a company contribution; Generous Paid Time Off in addition to holidays and company-wide days off; 16 Weeks of Paid Parental Leave; Wellness Program and Employee Assistance Program (EAP); Home Office Reimbursement; Monthly Phone and Internet Reimbursement; Tuition Reimbursement and access to LinkedIn Learning; Equity; Commuter Benefits (if local to an office); Volunteering Paid Time Off.
We need to output as
- .
- Pay: Compensation section: US base salary range $127,000—$158,700 USD; plus note about discretionary short-term and long-term incentives (bonus and equity). Also note that final salary range determined by job related experience, skills and location. The range displays typical hiring range for new hire salaries in US locations only. Recruiter can share more about specific salary range for preferred location. We should include that as substantive content. So we can have
Pay
withcontaining that info. - Schedule: "This is a full-time, hybrid role which will require you to work from our Washington, DC or Denver, CO office 3 days per week." Also maybe mention hybrid role. So we can put that under Schedule. - Also we might include a short p for Application Deadline and EAR/ITAR Requirements as metadata. Could fold into a short p under maybe a generic section? But we could just include a
after sections for those. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can add a
for Application Deadline and EAR/ITAR Requirements. We must not include boilerplate like EEO, Privacy Policy, etc. Now produce HTML fragment: start with maybe a
for company overview? Not required. Could skip. We'll output sections in order: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule, then a
for metadata. Make sure to use
for each section heading. Let's craft. About the role:
About the role
As a Technical Program Manager (TPM) at Planet, you will drive Planet’s largest, complex efforts that cross many teams and organizational boundaries. You will focus on execution of programs through the product life cycle. You will work closely with team leads to develop and manage end to end program plans. This includes establishing and managing internal processes, schedules, metrics, risks, and clearly communicating them to project stakeholders. You will work with both technical and non-technical teams. We are looking for a Technical Program Manager to support solutions development for Defense and Intelligence. You will be the connective tissue between Product, Engineering, and our customers, turning big-picture roadmaps into structured execution plans and accountable timelines. From managing custom customer deployments to supporting the engineering release train, you’ll cut through ambiguity, manage cross-functional dependencies, and proactively mitigate risk to ensure seamless delivery.
Responsibilities:Responsibilities
- Orchestrate end-to-end program execution across Engineering, Product, Design, Space Systems, Enablement, and Customer Support to ensure successful releases.
- Scope comprehensive program schedules and break down complex requirements into actionable, incremental milestones.
- Translate requirements across business and technical stakeholders with communication clarity.
- Identify dependencies and risks and proactively mitigate them.
- Facilitate decision making through data-driven analysis and healthy debate.
- Communicate vertically & horizontally across Planet to keep stakeholders informed of progress, priorities, risks, and changes to requirements or plans.
- Drive for results by continuously improving ways of working and processes, now and for the future.
Requirements
- 4+ years of software development or program management experience in the areas of SaaS, platform development, or analytics.
- Bachelor’s degree in a relevant field.
- Experience working with cross-functional teams across a broad organization.
- Thrives in ambiguous environments, with a track record of designing and implementing scalable processes and frameworks from scratch.
- Experience with the product life cycle: concept through development, launch preparation, go-to-market, deprecations, and end-of-life.
Qualifications
- Analytical, problem-solving, and creative thinking skills paired with the ability to communicate findings and recommendations.
- Equally comfortable explaining your analyses and recommendations to business leaders as you are discussing technical trade-offs with engineers.
- Ability to balance the tactical day-to-day with forward-looking improvements to scale operational efficiencies.
Skills
- A desire to improve processes, tools, and ways of working to scale operations cycles.
- Experience with remote sensing, earth observation data, or geospatial systems.
- Experience working with remote, worldwide teams.
- A growth mindset and a desire to learn quickly.
- Actively exploring AI technologies to automate workflows, improve data, or enhance team productivity.
Benefits
- Comprehensive Medical, Dental, and Vision plans
- Health Savings Account (HSA) with a company contribution
- Generous Paid Time Off in addition to holidays and company-wide days off
- 16 Weeks of Paid Parental Leave
- Wellness Program and Employee Assistance Program (EAP)
- Home Office Reimbursement
- Monthly Phone and Internet Reimbursement
- Tuition Reimbursement and access to LinkedIn Learning
- Equity
- Commuter Benefits (if local to an office)
- Volunteering Paid Time Off
Pay
The US base salary range for this full
- .
- Pay: Compensation section: US base salary range $127,000—$158,700 USD; plus note about discretionary short-term and long-term incentives (bonus and equity). Also note that final salary range determined by job related experience, skills and location. The range displays typical hiring range for new hire salaries in US locations only. Recruiter can share more about specific salary range for preferred location. We should include that as substantive content. So we can have