Product Manager, Mobile

We need to output HTML fragment with sections: About the role? The posting includes "About The Job" paragraph, then "What You'll Do", "What We Look For", "Compensation", "What we offer", "About BuildOps". Also location-based compensation details. We must not repeat job title as heading. Use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when there is real specific content. The posting has sections: About the job (intro), What You'll Do (responsibilities), What We Look For (requirements/qualifications/skills), Compensation (Pay), What we offer (Benefits), About BuildOps (maybe about the company). We need to map to allowed headings: About the role (intro), Responsibilities (What You'll Do), Requirements (What We Look For), Pay (Compensation), Benefits (What we offer). Possibly also Qualifications? But we can combine Requirements with Qualifications. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate ones. We must not include sections with filler like "commensurate with experience". We have actual content. We need to preserve all substantive info, not invent or summarize away detail. So we need to include all details from each section. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. At the end there is EEO statement, fraud warnings, etc. Remove those. Also remove duplicated lines: maybe "BuildOps is an equal opportunity employer." etc. Remove. We need to keep location-based compensation details: Raleigh, LA/SF, Toronto ranges. We need to keep benefits list: generous equity grant, comprehensive benefits package, flexible PTO and hybrid work schedules, one-time work-from-home allowance, hubs with hybrid work schedules and lunch provided, company events, fast-paced collaborative environment, opportunities for growth, chance to work with cutting-edge tech, chance to get in on ground floor. We need to keep About BuildOps paragraph (the long description). Keep that as maybe "About the company" but we only have allowed headings; maybe we can put it under "About the role"? Actually About the role is intro about job. The About BuildOps is company description; we could put under "About the role"? Not ideal. Could create a section "About the company" but not in allowed list. However instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we should map content to those headings. About BuildOps could go under "About the role"? Not exactly. Maybe we can treat it as "About the role" includes both job and company? But the intro already has "About The Job". Could combine. Better: Use headings: About the role (intro + company description?), Responsibilities, Requirements, Pay, Benefits. Possibly also Skills? But we can incorporate skills into Requirements. We must not create Schedule section unless posting states schedule; there is mention of hybrid work schedules, flexible PTO, but not explicit schedule like "full-time". Might be considered schedule info? The posting mentions hybrid work schedules, flexible PTO, but not a specific schedule. Probably we should not create Schedule heading because it's not explicit schedule like "Mon-Fri 9-5". Safer to omit. Thus sections: About the role, Responsibilities, Requirements, Pay, Benefits. Now we need to format content. About the role: combine the introductory paragraph(s) before "What You'll Do": "About The Job At BuildOps, we’re building a groundbreaking software solution, purpose-built to support today’s commercial contractors. From helping our customers manage their service department all the way to project management, we’re breaking the mold and building a team that invests in our mission statement. We love driven, self-motivated folks experienced in tech start-ups and thrive in fast-paced environments. Could you be our next hire? This candidate will join a well-funded, fast-growing technology startup with the unique opportunity to help build out a critical function for the company. As a Product Manager on our Mobile team, you'll be the connective tissue between engineering, design, and the technicians who rely on our app every day out in the field. You'll run point on sprint planning, grooming, and retros, turn customer feedback into well-scoped tickets, and make the fast, in-the-weeds prioritization calls that keep the team shipping. Over time, you'll build deep expertise in the core mechanics that make a great mobile experience — navigation, data loading, and offline sync — and become the person other product domains turn to when they need their features to work well on mobile." That is the About The Job section. We could also include the later "About BuildOps" paragraph as part of About the role? Might be redundant but we need to preserve all substantive info. So we should include that too, maybe after the intro. So About the role will contain both paragraphs. Now Responsibilities: the bullet list under "What You'll Do:" each line starts with a verb. We need to put each as

inside

. Preserve exact wording. Responsibilities content: - Drive sprint cadence for the mobile team — leading grooming, planning, and retros, and keeping the team focused on the right work at the right time - Write clear, well-scoped tickets and make the day-to-day prioritization calls (bug vs. task, now vs. next) that keep the backlog healthy and the team unblocked - Own release notes and feature announcements for mobile, keeping customers and the company informed on what's shipping - Meet directly with customers and field technicians to gather feedback and turn it into concrete product improvements - Spot when engineers are blocked and escalate quickly to keep execution moving - Ensure fix versions and release scope stay aligned with the broader roadmap, partnering with engineering leads to ship predictably - Develop deep fluency in the technical fundamentals of the mobile experience — navigation, data loading, and offline sync — and use that expertise to help other product domains design features that work well on mobile We need to keep em dashes and punctuation. Now Requirements: "What We Look For:" includes bullet points. List: - 2+ years of product management experience, or equivalent experience (engineering, QA, technical program management) with direct exposure to shipping software - Strong organizational skills — comfortable owning the mechanics of agile execution (grooming, planning, standups, retros) and keeping a backlog clean and current - Clear written communication — you can write a good ticket, a crisp release note, and an announcement people actually read - Comfortable talking directly to customers and translating open-ended feedback into a scoped, actionable ticket - Genuine curiosity about how mobile apps work under the hood — navigation patterns, data loading, offline/sync behavior — and the persistence to dig in - A bias toward action: you'd rather ship something this sprint and iterate than wait for the perfect plan - Bonus: Experience with native or hybrid mobile apps (iOS, Android, or React Native) from a PM, QA, or engineering seat - Familiarity with field service, construction, or other frontline/offline-first mobile use cases - Experience with Jira, Confluence, and mobile release/CI tooling We should keep as list. Now Pay: Compensation section includes location-based ranges. Compensation Raleigh: $115,000 - $140,000 base + annual bonus opportunity LA/SF: $118,000 - $147,000 base + annual bonus opportunity Toronto: 100,000 - 125,000 CAD base + annual bonus opportunity We need to preserve exactly. Now Benefits: "What we offer:" list. List: - Generous equity grant, become an owner in our company! - A comprehensive benefits package - Flexible PTO and hybrid work schedules - One-time work-from-home allowance - Hubs in Los Angeles, San Francisco, Toronto, and Raleigh with hybrid work schedules and lunch provided for in-office days - Company events and team-building activities, both in-person and virtual - Fast-paced, collaborative, and dynamic work environment - Opportunities for growth and career advancement - Chance to work with cutting-edge technology and innovative solutions - The chance to get in on the ground floor and build something truly groundbreaking for ourselves and our amazing customers We need to keep each as
• . Now we must not include any other sections like Schedule. Now we need to output only HTML fragment, no or , no markdown fences. Thus:

  About the role

  ... (intro + About BuildOps paragraph)

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Pay

  ... compensation lines maybe as

  or

  ? The instruction: use
  • for any list of duties/requirements/benefits, and

    for prose. Compensation is not a list of duties/requirements/benefits; it's prose. So we can put as

    with line breaks? Could use

    with
    but better to keep as

    with sentences separated by
    or just separate

    for each line? The instruction says use

    for prose. So each line could be its own

    . But we could also combine into one

    with
    . Safer to make each line its own

    . However that might be considered list? Not exactly. I'll use separate

    for each location. Thus:

    Pay

    Raleigh: $115,000 - $140,000 base + annual bonus opportunity

    LA/SF: $118,000 - $147,000 base + annual bonus opportunity

    Toronto: 100,000 - 125,000 CAD base + annual bonus opportunity

    Now Benefits:

    Benefits

    • ...
    ...
    Now ensure we didn't repeat job title as heading. We didn't. Now check for any boilerplate: we removed EEO, fraud warnings, etc. Also removed "We welcome applicants from across the U.S. where we are registered to do business and able to support employment. Currently, this excludes the following states: ..." That's also boilerplate/legal; should remove. Also removed "About BuildOps Join BuildOps, the largest commercial trade platform..." Actually we kept that as part of About the role. That's substantive company description, not boilerplate. Good. Now check for any duplicated lines: none. Now ensure we didn't include any "Schedule" section. Now output HTML. Let's craft the About the role paragraph: combine the two paragraphs. First paragraph: "About The Job At BuildOps, we’re building a groundbreaking software solution, purpose-built to support today’s commercial contractors. From helping our customers manage their service department all the way to project management, we’re breaking the mold and building a team that invests in our mission statement. We love driven, self-motivated folks experienced in tech start-ups and thrive in fast-paced environments. Could you be our next hire? This candidate will join a well-funded, fast-growing technology startup with the unique opportunity to help build out a critical function