Product Manager, Mobile

We need to output HTML fragment with sections: About the role? The posting includes "About The Job" and then description. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only sections that have real content. We need to parse content: - About The Job: description about BuildOps, mission, etc. That's about the role? Could be "About the role". We'll put that in

About the role

then

with that prose. - Responsibilities: The bullet list under "What You'll Do:" includes multiple items. We'll put

Responsibilities

then

• each. - Requirements: The bullet list under "What We Look For:" includes items. We'll put

  Requirements

  then
  . - Qualifications: Might be same as requirements? But we can treat "Bonus:" as Qualifications? Actually "Bonus:" includes extra desirable experience. Could be "Qualifications" maybe includes required and bonus? But we need to avoid filler. We have required items (2+ years PM experience, organizational skills, written communication, comfortable talking to customers, curiosity about mobile apps, bias toward action). Bonus items: experience with native/hybrid mobile apps, familiarity with field service/construction, experience with Jira, Confluence, mobile release/CI tooling. We could put required under Requirements, bonus under Qualifications or Skills. The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide where each piece goes. We have compensation details: Pay: Raleigh, LA/SF, Toronto ranges. So we will have

  Pay

  with

  containing those ranges. Benefits: The list under "What we offer:" includes many items. We'll put

  Benefits

  then
  . Schedule: Not explicitly mentioned besides hybrid work schedules. There's "Flexible PTO and hybrid work schedules" and "Hubs in Los Angeles, San Francisco, Toronto, and Raleigh with hybrid work schedules". That's schedule info. So we can put

  Schedule

  with

  mentioning hybrid work schedules, flexible PTO. We should not repeat job title. No Job ID. We must remove boilerplate: EEO, legal, etc. Also remove "We welcome applicants from across the U.S...." maybe that's not boilerplate? It's about eligibility; could be considered part of job posting but not a section. Might be okay to keep as prose under About the role? But it's about where they can hire. Could be included in About the role paragraph. However it's not about the role itself. Might be considered boilerplate? It's location eligibility. Might keep as part of About the role? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The eligibility list is not exactly EEO but could be considered operational. Might keep? Safer to keep as part of About the role? It's not about the role but about where they can hire. Could be placed under About the role as extra info. I'd keep it. Also remove "About BuildOps" section after compensation? That's more company description. Could be part of About the role? Might be redundant. But we need to preserve ALL substantive information; we cannot invent or summarize away detail. So we need to include that company description somewhere. Could be under About the role as additional paragraph. Thus About the role will contain the initial "About The Job" paragraph plus the later "About BuildOps" paragraph (the longer description). We'll combine them into one

  maybe two paragraphs. Now ensure we don't include filler like "commensurate with experience" etc. Not present. Now produce HTML. Structure:

  About the role

  ...combined...

  Responsibilities

  • 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

  Requirements

  • 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

  Qualifications

  • 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

  Benefits

  • 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

  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

  Schedule

  Hybrid work schedules with flexible PTO; hubs in Los Angeles, San Francisco, Toronto, and Raleigh offer hybrid schedules and lunch provided for in-office days.

  Now we need to ensure we didn't include any boilerplate like "We welcome applicants from across the U.S...." We omitted that. Also omitted the list of excluded states. That's okay? It's substantive info about eligibility. Might be considered important. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The excluded states list is substantive. Should we include it? It's not a section heading but could be placed under About the role as a note. However it's about where they can hire. Might be considered part of job posting. I'd include it as a short paragraph under About the role. Similarly the "About BuildOps" paragraph we included. Also the "See why contractors choose Buildops here." link? That's maybe a call to action; could be considered boilerplate? It's a link; maybe we should keep as prose? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "See why contractors choose Buildops here." is not boilerplate but maybe a promotional line. Could keep. We also have the funding round description etc. That's part of About BuildOps. Thus we need to incorporate those pieces. Let's craft About the role paragraph(s): 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 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." Second paragraph: maybe include the later "About BuildOps" description: "Join BuildOps, the largest commercial trade platform in the country, as we transform the multi-billion dollar commercial contracting industry! We’re not just talking incremental improvements—we’re talking a full-scale revolution, empowering the hardworking heroes who build and maintain the infrastructure that keeps our world running. See why contractors choose Buildops here. This is your chance to be part of a rocketship. We’re fresh off a $1 billion valuation and a $127M Series C funding round (part of over $275M raised to date) led by industry-leading investors like Meritech Capital, BOND, and SE Ventures, backed by Schneider Electric (Reuters, TechCrunch, LA Business Journal). Our latest investors join our team of industry heavyweights like Next47, former Twitter CEO Dick Costolo, former Salesforce President Gavin Patterson, and Boost Mobile CEO Stephen Stokols. Their investment is fueling our aggressive growth and our commitment to equipping contractors with AI-driven tools to conquer chaos, boost efficiency, skyrocket profitability, and ultimately, deliver exceptional service. At BuildOps, we’re changing the game and doing the best work of our careers. You’ll be a key player in a company that’s truly making a difference for the backbone of our economy. If you’re ready to tackle big challenges, work with a passionate team, and build something extraordinary, BuildOps is the place for you. 🚀" Then eligibility note: "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: Alaska, Hawaii, Kentucky, Mississippi, Nebraska, New Mexico, North Dakota, Rhode Island, South Dakota, West Virginia, and Wyoming. This list is based solely on operational and compliance considerations and is reviewed from time to time as our footprint grows." We'll combine these into maybe