Sr. Manager, US Government Programs

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting and extract content for each section. Let's identify sections: - About the role: The initial paragraph(s) describing role: "This role is for someone who can earn trust inside U.S. government agencies and drive complex technical commitments to completion..." up to maybe before "What Winning Looks Like". That seems like role description. - Responsibilities: Likely the "What You Will Own" section with bullet points (Program Delivery, Stakeholder Management, Pre-Sale Support, Governance and Reporting). Also maybe "What Winning Looks Like" could be responsibilities? But we can treat "What You Will Own" as responsibilities. - Requirements: The "What You Must Bring" list (experience, etc). Also maybe "Strong Plus" etc? Those are qualifications/skills. - Qualifications: Could be the "Strong Plus" items (experience with weather, SaaS, FAR, etc). Also maybe eligibility for security clearance. - Skills: Could be communication skills, cross-functional influence, etc. But we might combine. - Benefits: The posting mentions "Comprehensive health benefits, unlimited paid time off and other benefits included. Relocation assistance may be offered/available for certain roles." Also maybe "Eligibility for security clearance" is not benefit. Also "Willingness to travel" is not benefit. - Pay: "Anticipated salary range for this role is $130-165k subject to local market and candidates skills and experience." - Schedule: Not explicitly mentioned. There's no schedule info (like full-time, hours). So we should not include Schedule section. We must not include sections with filler like "commensurate with experience". We have concrete pay range. We must not include boilerplate like EEO, E-Verify, etc. Remove those. We must preserve all substantive info; do not invent or summarize away detail. So we need to keep the details as they appear, but we can format into HTML lists and paragraphs. We need to use

for section headings. Use

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

  for prose. We must not repeat job title as heading. Not include Job ID. We must output only HTML fragment. Let's extract content precisely. First, "About the role": The initial paragraph(s) before "What Winning Looks Like". Let's copy: "This role is for someone who can earn trust inside U.S. government agencies and drive complex technical commitments to completion. We are looking for a hands-on operator who personally owns delivery, not someone who operates only as a governance or advisory layer. Tomorrow.io's Customer Delivery and Operations team sits at the center of the company, connecting the Government and Enterprise business units to the technical organization. We own the full lifecycle of customer programs, from pre-sale technical engagement through post-sale delivery and operational support. This role focuses on high-stakes U.S. government programs with defense, civil aviation, emergency management, homeland security, and other public-sector organizations. You will own programs end to end. That means knowing the contract terms, technical requirements, acceptance criteria, stakeholder map, risks, and critical path. You will identify and resolve blockers early, close gaps between customer expectations and delivery, and maintain momentum across multiple engagements at the same time. You will join a small, high-output team in a fast-moving company where the operating model is still maturing. There is no large program office behind you. You will build the frameworks and processes needed to execute and use them to keep programs moving." That seems good. Now "What Winning Looks Like" could be considered responsibilities or maybe part of responsibilities. But we already have responsibilities in "What You Will Own". However "What Winning Looks Like" describes outcomes; could be part of responsibilities or maybe a separate section like "Expectations". But we only have predefined headings; we could put that under Responsibilities as well, but we need to avoid duplication. The instructions: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can choose to include Responsibilities and maybe also include a section for "What Winning Looks Like" if we think it's responsibilities. But we should not create extra headings not in list. So we must map content to those headings. Thus: - About the role: as above. - Responsibilities: combine "What You Will Own" and "What Winning Looks Like" maybe. But we need to keep all substantive info. Let's extract "What You Will Own" bullet points: Program Delivery: - Own and drive the full lifecycle of U.S. government programs, including contract kickoff, solution delivery, POC execution, operational deployment, and ongoing support. - Translate signed contracts and statements of work into executable program plans with defined milestones, deliverables, acceptance criteria, ownership, and accountability. - Drive follow-through across all stakeholders. - Manage scope, schedule, budget, contractual commitments, and technical risk across multiple concurrent programs and agency environments. - Ensure all contract deliverables, including documentation, reporting, invoicing, and compliance artifacts, are completed accurately and on time. Stakeholder Management: - Serve as the primary point of contact for U.S. government customers on active programs. - Build direct relationships with program leaders, contracting stakeholders, and technical counterparts. - Drive alignment across Legal, Finance, Product, Science, Engineering, Customer Success, and Business Development. - Bring the right people together, resolve blockers, and maintain program momentum. - Navigate U.S. government acquisition processes, contracting norms, compliance requirements, and agency-specific decision paths with the confidence that comes from direct experience. - Manage relationships with prime contractors, subcontractors, integrators, and other external partners involved in delivery. Pre-Sale Support: - Support Business Development on active U.S. government opportunities by participating in deal reviews, validating POC scope, and ensuring the technical, financial, and delivery analysis is complete before commitments are made. - Bring an operational perspective into pre-sale conversations: what is realistic to deliver, what risks and dependencies exist, and what the program will require after award. - Contribute to proposal, RFP, RFQ, and RFI responses where credible execution planning is a differentiator. Governance and Reporting: - Report program health, risks, decisions, and progress to senior leadership on a regular cadence with clear, honest assessments. - Build and maintain program tracking, governance frameworks, and reporting standards that work for our scale and pace. - Provide clear guidance and governance support to cross-functional team members involved in program execution. Now "What Winning Looks Like" paragraph: "What Winning Looks Like Your programs deliver on time, within scope, and with zero surprises to leadership or the customer. Contract milestones are tracked, invoicing is clean, and required documentation and compliance artifacts are complete without being chased.Government stakeholders in your programs trust you personally. Program leaders, contracting stakeholders, and technical counterparts come to you when something needs attention because you follow through consistently.Internal teams in Science, Product, Engineering, Legal, and Finance treat your programs as well run and easy to support because you bring clear requirements, realistic timelines, and full context instead of last-minute fire drills.You run multiple concurrent programs across different agencies, contracts, and compliance environments without dropping threads. Each program has a clear status, a clear next step, and a clear owner for every open item.When a new U.S. government opportunity enters the pipeline, you step into the pre-sale engagement to support deal reviews, scope POCs, and ensure the technical, financial, and delivery picture is sound before we commit.Risks surface early in your programs. You identify issues before they escalate and bring proposed mitigations with the diagnosis.You raise the standard for the teams around you. Business Development teams produce stronger scoping because you challenge requirements and delivery assumptions before they reach the technical organization. Your programs become examples of well-run delivery." We can treat this as part of Responsibilities (outcomes). We'll include as prose under Responsibilities after the bullet lists. Now Requirements: "What You Must Bring" list: - 8+ years of hands-on program or project management experience delivering complex technical programs for or with U.S. government customers. This must include direct delivery responsibility, not advisory or consulting roles where execution sat with another team. - Direct experience working with U.S. government agencies, ideally at the federal level, such as defense, civil aviation, emergency management, homeland security, or similar organizations. You understand government procurement and contracting because you have managed work within that environment. - A track record of personally owning and delivering programs end to end in environments without extensive institutional support. You have built the structures and processes needed to execute, not only operated within existing ones. - Proven ability to manage multiple concurrent programs across different agencies, contracts, and compliance environments without losing control of details or timelines. - Strong cross-functional influence skills. You have delivered through teams you do not manage, including Engineering, Science, Legal, Product, and Finance. You know how to align people, resolve conflicts, and create urgency without formal authority. - Excellent communication skills in English, written and spoken. You can write a clear program status, run a structured review, and communicate credibly with senior government officials. - Willingness to travel within the United States as programs require, with occasional international travel when needed. Although the role is remote, meaningful on-site presence is expected when customer relationships or program milestones demand it. - Eligibility for security clearance Note: "Eligibility for security clearance" is a requirement. Now Qualifications: "Strong Plus" items: - Strong Plus Experience with weather, climate, earth observation, or environmental monitoring technologies. - Familiarity with SaaS or Data-as-a-Service delivery models in a government context. - Familiarity with federal acquisition and contracting frameworks, including FAR and DFARS, and experience supporting RFP, RFQ, RFI, or other procurement paths. - Experience delivering through prime contractor, subcontractor, or systems integrator relationships. - Commercial acumen, including an understanding of deal economics, pricing structures, contract negotiation dynamics, and how delivery decisions affect margin. - Experience in a high-growth startup or scale-up environment where you built the operating model while running programs. - If you have reached this point and you are super excited but not sure you check all the boxes - we still want to speak with you! Your passion is priceless. Other things can be learned. Also maybe "Eligibility for security clearance" already in requirements. We could treat the "Strong Plus" as Qualifications. Now Skills: Could be communication skills, cross-functional influence, etc. But we already have those in Requirements. However we could separate: Skills: communication skills, cross-functional influence, etc. But we risk duplication. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Skills into Requirements or Qualifications. But we need to follow the headings list; we can include Skills if we have content. Let's see if we have distinct skills not covered elsewhere: "Excellent communication skills in English, written and spoken." "Strong cross-functional influence skills." Those are skills. Could put them under Skills. Meanwhile Requirements could focus on experience years, direct experience, track record, ability to manage multiple programs, willingness to travel, eligibility for security clearance. Qualifications could be the Strong Plus items. Thus we split: - Requirements: experience (8+ years, direct experience, track record, manage multiple programs, willingness to travel, eligibility for security clearance). Also maybe "direct delivery responsibility" etc. - Skills: communication skills, cross-functional influence skills. - Qualifications: Strong Plus items. Now Benefits: "Comprehensive health benefits, unlimited paid time off and other benefits included. Relocation assistance may be offered/available for certain roles." Also maybe "Willingness to travel" is not benefit. Pay: "Anticipated salary range for this role is $130-165k subject to local market and candidates skills and experience." Schedule: none. Now we need to output HTML. We must not include boilerplate