Senior Product Manager

We need to output HTML fragment with sections: About the role? The posting includes "About Nava" description, then "Position Summary", then "What you'll do", then "Required Skills", then "Compensation", then "Other Requirements", then "Perks", then "Location". Also maybe "About Nava" is not a section heading per rules: we can use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to map content accordingly. The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create headings that match these generic names, but we must include only sections where posting has real specific content. We need to decide which sections to include: About the role (maybe corresponds to Position Summary?), Responsibilities (What you'll do), Requirements (Required Skills?), Qualifications (maybe education?), Skills (maybe required skills?), Benefits (Perks), Pay (Compensation), Schedule (maybe not present). We must not repeat job title as heading. Also we should not include metadata like Job ID. We need to preserve all substantive information. So we need to include content under each heading. We need to avoid filler like "commensurate with experience". Not present. We need to remove boilerplate: EEO, legal, application instructions, etc. So we must cut out the Equal Employment Opportunity paragraph, the "Stay in touch", "Please contact recruiting team", "We participate in E-Verify", etc. Also remove "About Nava" maybe? It's descriptive about company; could be considered part of About the role? Might be okay to keep as part of About the role section. But the instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have an About the role section that includes the Nava description and Position Summary. We need to not repeat the job title as heading. The job title is Product Manager. Not to be used as heading. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

... (Nava description and Position Summary)

Responsibilities

• ... each bullet from "What you'll do"

Requirements

• ... each bullet from "Required Skills"

Maybe also Qualifications: education (Bachelor's degree required, Advanced degree preferred). Could be separate. Skills: maybe we already covered in Requirements; but we could split: Requirements (experience, leadership, etc.) and Skills (technical, certifications). But we can combine. Better to follow the example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role, Responsibilities, Requirements (maybe split into Requirements and Qualifications), Skills (certifications), Benefits (Perks), Pay (Compensation). Schedule not present, so omit. We must not create empty sections. Let's extract content. About Nava description: paragraphs about Nava consultancy, mission, etc. Position Summary: paragraph starting "Nava is at the forefront...". Combine. Responsibilities: bullet list under "What you'll do": each line starting with a verb. Let's list them: - Define the vision, goals, and measures of success for the products and services you manage - Work with designers, business analysts, and technical leads to discover and synthesize market research, user needs, business requirements, and technical approaches - Define the direction, scope, and priority of projects, from high-level initiatives to specific features, user stories, and business metrics - Work closely with cross-functional teams to develop and ship projects - Proactively socialize, iterate on, and build buy-in for product initiatives with the team, government partners, and other contractors - Collaborate with the project management team to prioritize roadmaps and inbound units of work - Represent Nava’s outcome-centric and user-centric approach in discovery meetings with agencies and contractors - Understand and communicate the needs of end users and population segments we serve and government partners we work with - Measure product progress toward business goals or user needs and translate data insights into action - Make tactical decisions to improve the design, define requirements, and generate stakeholder buy-in for our desired path forward That's 10 bullets. Required Skills: list of bullet-like sentences. Let's extract each requirement: - Demonstrated experience (10+ years) managing cloud-based products or platforms within federal agencies or similarly regulated environments - Proven ability to lead cross functional teams and facilitate collaboration across government and contractor organizations - Strong communication skills for briefing senior leadership, documenting decisions, and engaging diverse stakeholder groups - Strong understanding of cloud architectures, shared responsibility models, and cloud security frameworks - Familiarity with AWS, Azure, or other FedRAMP 20x authorized cloud environments - Ability to interpret security controls, compliance requirements, and technical documentation to inform product decisions. - Experience working within federal IT governance structures, including ATO processes, continuous monitoring, and enterprise architecture reviews - Understanding of ED/FSA mission, systems, and regulatory environment preferred - Relevant certifications strongly desired include Certified Scrum Product Owner (CSPO) or equivalent Agile certification, Project Management Professional (PMP) or PMI ACP, ITIL Foundation, Cloud certifications (AWS, Azure, or equivalent), Security or compliance certifications (e.g., Security+, CCSP), etc - Bachelor’s degree required in Information Technology, Computer Science, Business Administration, Public Administration, Engineering, or a related field. Advanced degree preferred We could split Qualifications: education bullet. Skills: maybe the technical and certification bullets. But we can also keep Requirements as all those, and Qualifications as education. Let's decide: - Requirements: experience, leadership, communication, cloud understanding, familiarity with AWS/Azure, ability to interpret security controls, experience with federal IT governance, understanding of ED/FSA mission (preferred). (These are experience/requirements) - Qualifications: Bachelor’s degree required ... Advanced degree preferred. - Skills: Relevant certifications strongly desired include ... (list). Could also include maybe "Strong understanding of cloud architectures" but that's already in Requirements. But to avoid duplication, we need to allocate content uniquely. Let's parse: From Required Skills section: 1. Demonstrated experience (10+ years) managing cloud-based products or platforms within federal agencies or similarly regulated environments 2. Proven ability to lead cross functional teams and facilitate collaboration across government and contractor organizations 3. Strong communication skills for briefing senior leadership, documenting decisions, and engaging diverse stakeholder groups 4. Strong understanding of cloud architectures, shared responsibility models, and cloud security frameworks 5. Familiarity with AWS, Azure, or other FedRAMP 20x authorized cloud environments 6. Ability to interpret security controls, compliance requirements, and technical documentation to inform product decisions. 7. Experience working within federal IT governance structures, including ATO processes, continuous monitoring, and enterprise architecture reviews 8. Understanding of ED/FSA mission, systems, and regulatory environment preferred 9. Relevant certifications strongly desired include Certified Scrum Product Owner (CSPO) or equivalent Agile certification, Project Management Professional (PMP) or PMI ACP, ITIL Foundation, Cloud certifications (AWS, Azure, or equivalent), Security or compliance certifications (e.g., Security+, CCSP), etc 10. Bachelor’s degree required in Information Technology, Computer Science, Business Administration, Public Administration, Engineering, or a related field. Advanced degree preferred We could treat 1-8 as Requirements, 9 as Skills (certifications), 10 as Qualifications (education). Now Benefits: list under "Perks working with Nava". Let's extract each perk: - Health coverage — comprehensive medical, dental, and vision plans to support your overall health needs - Insurance coverage — Nava provides disability, life, and accidental death insurance at no cost - Time off — vacation, holidays (including Juneteenth), and floating holidays to rest and recharge - Company holidays — enjoy 12 paid federal holidays each year on top of your regular PTO - Annual bonus — when Nava meets its goals, eligible employees receive a performance-based annual bonus - Parental leave — paid time off for new parents, plus weekly meals delivered to your home - Wellness program — full platform offering physical, mental, & emotional health resources & support tools - Virtual care — see doctors online with no copay through a virtual visit program (depending on available providers) - Sabbatical leave — earn extended unpaid leave after continuous service for personal growth or rest - 401(k) match — Nava matches 4% of your salary to support your retirement savings plan - Flexible work — remote-first environment with flexibility built around your schedule and responsibilities - Home office setup — company laptop & setup assistance provided via Staples for remote work needs - Utility support — monthly reimbursement to help offset eligible home office utility expenses - Learning opportunities — internal training programs and resources to help grow your professional skills - Development opportunities — LinkedIn Learning access & an annual allowance for courses, tuition, & certs - Referral bonus — get rewarded when you refer great people who join the Nava team - Commuter benefits — pre-tax commuter programs to support in-office travel when applicable - Supportive culture — A collaborative and remote-friendly team environment where people genuinely care That's many. Pay: Compensation $98,000—$153,000 USD. Schedule: Not present, so omit. Location: list of states where fully remote options if you reside in one of the following states: long list. Also statement: If you are not living in one of the states listed above, unfortunately, you will not be considered for a position at this time. This is location requirement. Should we include a Location section? The instruction says we can include Schedule, Benefits, Pay, etc. Location not in the example headings but we could still include if we think it's substantive. However the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive list. It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. Location may not be needed; but it's substantive. However they said "include a section ONLY when the posting has real, specific content for it". Location does have specific content (list of states). But they didn't list Location as example heading; but we could still use

Location

. The instruction didn't forbid other headings, just gave examples. Safer to include Location as a section. But we need to avoid boilerplate like "Stay in touch", EEO, etc. We'll remove those. Now construct HTML. We'll need to wrap each section in

and then content. For lists, use

• ...

. For prose, use

. We need to preserve all substantive information; do not invent or summarize away detail. Thus we need to include all bullets exactly as in posting. Let's craft About the role section: combine Nava description and Position Summary. Nava description paragraphs: "About Nava Nava is a consultancy and public benefit corporation working to make government services simple and effective. Since 2015, federal, state, and local agencies have trusted Nava to help solve highly scrutinized technology modernization challenges. As a client services company, we guide agencies constrained by legacy systems to a future with sharp user experiences built on secure, reliable, fault-tolerant cloud infrastructure. We bill for our time, offering our expertise and problem-solving approach to help our government partners enhance their digital products and services. People are at the heart of