How to apply for Sr. Manager, US Government Programs

About Tomorrow.io

Tomorrow.io provides weather intelligence that helps organizations optimize operations and build climate resilience. The company works with U.S. government agencies on defense, aviation, emergency management, and homeland security programs. This role sits at the center of the company, connecting government and enterprise business units to the technical organization.

About the role

You will own U.S. government programs end to end, from pre-sale technical engagement through post-sale delivery and operational support. You will track contract terms, technical requirements, acceptance criteria, stakeholder maps, risks, and critical paths. The team is small and the operating model is still maturing, so you will build frameworks and processes while keeping multiple engagements moving.

A typical day

A typical day may involve checking contract milestones and invoicing, resolving a blocker on one government program, and aligning technical teams with customer expectations on another. You will likely spend time tracking risks and critical paths across multiple engagements while building or refining the processes the team uses to execute. Ask the hiring team how they divide time between customer-facing work and internal process building.

Who Tomorrow.io is looking for

• Has direct experience delivering technical programs to U.S. government agencies in defense, civil aviation, emergency management, or homeland security.
• Is a hands-on operator who personally owns delivery, not a governance or advisory layer.
• Can earn trust inside government agencies and drive complex technical commitments to completion.
• Has built program frameworks and processes in a fast-moving company without a large program office.

Tips for this application

• Name specific U.S. government agencies or program types you have supported, such as defense, civil aviation, emergency management, or homeland security.
• Describe programs you personally owned end to end, including contract terms, acceptance criteria, and critical path management.
• Give examples of frameworks or processes you built from scratch when no program office existed.
• Show how you tracked contract milestones and invoicing without surprises to leadership or the customer.
• Explain how you resolved blockers early and closed gaps between customer expectations and delivery across multiple engagements.

What to cover in your cover letter

['Your hands-on ownership of complex technical government programs from pre-sale through post-sale delivery.', 'Specific experience earning trust inside U.S. government agencies and driving technical commitments to completion.', 'Examples of building program frameworks and processes in a small, fast-moving team without a large program office.', 'How you manage contract terms, acceptance criteria, risks, and critical paths across multiple simultaneous engagements.']

Research before applying

• Tomorrow.io's weather intelligence products and how they apply to defense, civil aviation, emergency management, and homeland security.
• Tomorrow.io's existing U.S. government contracts or public-sector customers, if available.
• The structure of Tomorrow.io's Customer Delivery and Operations team and how it connects government, enterprise, and technical organizations.
• The company's stage of growth and what maturing operating model means for program delivery.

Likely interview topics

Based on the job description, expect questions about:

• How you have earned trust inside a U.S. government agency and maintained it through a complex technical delivery.
• A program you owned end to end where you tracked contract terms, acceptance criteria, and critical path without surprises.
• How you built program frameworks or processes from scratch when the operating model was still maturing.
• How you identify and resolve blockers early across multiple government engagements at the same time.
• How you close gaps between customer expectations and technical delivery when there is no large program office behind you.

Common mistakes to avoid

• Presenting yourself as a governance or advisory layer rather than someone who personally owns delivery.
• Focusing on generic program management without naming specific U.S. government agencies or technical commitments.
• Claiming process-building experience without concrete examples of frameworks you created and used.