Product Manager
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. We need to map content to these headings. We have: - About Nava (company description) could be "About the role"? Actually "About the role" is about the job, not company. But we have "Position Summary" which describes role. Could map to "About the role". We'll include that. - Responsibilities: "What you'll do" list. - Requirements: maybe "Other Requirements" (legal auth, etc.) plus maybe "Required Skills"? Actually "Required Skills" is skills. "Qualifications" could be education/experience. The posting includes "Required Skills" list (experience, degree, etc.) and also "Other Requirements". We'll need to decide. We have sections: Skills, Qualifications, Requirements. We need to avoid duplication. Let's map: - Skills: list of abilities (e.g., "Ability to generate very strong product plans...") etc. - Qualifications: education/experience: "At least three (3) years of experience as a Product Manager of a cross-functional team", "Bachelor's degree or equivalent experience", "Experience running and/or shipping consumer web applications". Could be under Qualifications. - Requirements: legal auth etc. from "Other Requirements". Also maybe location? But location is separate. - Benefits: list of perks (health coverage, insurance, time off, etc.) from "Perks working with Nava". That's benefits. - Pay: compensation range. - Schedule: not specified; we should not include if not present. The posting does not mention schedule specifics (e.g., full-time, hours). So we omit Schedule. We also need to include maybe "Location" but not in headings list; we can include as a
maybe under a generic heading? The instruction says use headings only from list; we can still include other info as
without heading? Probably we should include location as a
after a heading? But we cannot create a heading not in list. Could embed location in a
under maybe "About the role" or just as a
without heading. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use for section headings (e.g...). Likely they expect only those headings. We can include location as a
after a heading like "About the role" or maybe as its own
without heading. Safer: include location as a
after a heading like "About the role" or maybe under "Requirements". But location is not a requirement; it's eligibility. Could put under "Requirements". But we already have Requirements for legal auth. Could combine. Better: create a section "Requirements" containing legal auth and location eligibility. That seems okay. Thus:
About the role
Position Summary ... (the paragraph about role).
Responsibilities
- ... each bullet from "What you'll do"
Qualifications
- At least three (3) years of experience as a Product Manager of a cross-functional team
- Bachelor's degree or equivalent experience
- Experience running and/or shipping consumer web applications
Skills
- Ability to generate very strong product plans and build buy-in across the team, our government partners, and other contractors
- Excellent written and verbal communication skills for technical, user experience, and project management trade-offs; enthusiastic communicator
- Strong bias towards action; ability to step up into team gaps and ambiguous situations to structure the team’s action plan
- Ability to execute with incomplete information; great product instincts and an ability to create order from divergent needs
- Ability to define a product objective and logically reverse engineer the path and communications to achieve the objective
- Ability to identify market trends and shifts that will affect product direction and update plans based on future expectations
- An adaptive, empathetic, collaborative, and positive mindset
Requirements
- Legal authorization to work in the United States
- Ability to meet any other requirements for government contracts for which candidates are hired
- Work authorization that doesn’t require visa sponsorship, now or in the future
- May be subject to a government background check or security clearance, depending on the contract
- Location: fully remote options if you reside in one of the following states: Alabama, Arizona, California, Colorado, Connecticut, DC, Delaware, Florida, Georgia, Illinois, Louisiana, Maine, Maryland, Massachusetts, Michigan, Minnesota, Missouri, Nevada, North Carolina, New Jersey, New York, Ohio, Oklahoma, Oregon, Pennsylvania, Rhode Island, South Carolina, Texas, Tennessee, Utah, Virginia, Washington, Wisconsin. If you are not living in one of the states listed above, unfortunately, you will not be considered for a position at this time.
Benefits
- 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
Pay
$118,400—$148,000 USD
We should not include Schedule. We must not repeat job title as heading. We didn't. We must not include Job ID etc. Not present. We removed boilerplate like EEO, legal, etc. Check that we preserved all substantive information: About Nava description? We omitted the "About Nava" paragraph at start. That's substantive about company. Should we include it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The About Nava paragraph is substantive. Where to put? Could be part of About the role? Or we could add a separate section maybe "About Nava" but not in allowed headings. Could incorporate into About the role as a preamble. The About the role heading expects role description; we could include both company description and position summary under About the role. That would preserve info. Thus About the role section: include the About Nava paragraph plus Position Summary. Let's craft:About the role
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 our work, from members of the public who rely on benefit programs to government agency staff. Through human-centered design and modern engineering best practices, we help our government partners understand user needs and deliver on their missions more effectively. This focus gives everyone at Nava the opportunity to do work that is meaningful, impactful, and deeply connected to public good. Please note: the level of the role will be determined by Nava leadership based on experience and skillset. Position Summary Nava is at the forefront of reimagining how our government serves its people, and we’re looking for a Product Manager to drive our vision forward. You'll help us execute our mission of reimagining the digital services our government provides. Working directly with government partners and across Nava’s engineering, design, and business teams, you’ll create experiences that improve the lives of millions of Americans. You care deeply about end users and are passionate about crafting simple and usable solutions. You'll work with government partners and cross-functional teams of engineers, designers, and project managers to set direction, scope product features, remove obstacles and barriers, and assess the business impact on a government contract. You will be uniquely positioned and empowered to make a huge impact on Nava's mission to reimagine how our government serves its people. You think holistically and take pride in working through highly ambiguous situations to deliver value to users. You have a strong bias towards action when faced with incomplete information and communicate transparently to build consensus internally and externally.
That covers About Nava and Position Summary. Now Responsibilities: list from "What you'll do". Ensure we capture each bullet. What you'll do list: - 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 We'll put each as