Remote Product Manager - Mobile

We need to output HTML fragment with sections: Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. We need to parse the posting. Content: Position Summary: "Do you want to put powerful, easy-to-use tools directly in the hands of the people who keep trucks on the road? At Karmak, we're looking for a Product Manager - Mobile to help drive the day-to-day direction and delivery of our mobile applications for heavy-duty truck dealerships. In this role you'll turn customer and business needs into clear requirements, partner closely with engineering to ship well-built features, and keep our mobile messaging and connectivity products moving forward. It's a hands-on product role for someone who loves translating real-world problems into practical software and seeing it land in customers' hands." Why Join Karmak? bullet points: Employee-Owned, Impactful Work, Collaborative Culture, Growth Opportunities. Essential Job Functions: list of functions: Requirements & User Stories, Backlog Ownership, Cross-Functional Collaboration, Customer & Support Insight, Delivery Support, Roadmap Contribution, Enablement & Documentation. Knowledge, Skills, And Abilities: list: 3 years experience, Strong requirements-gathering skills, Excellent written and verbal communication, Working knowledge of Agile methodologies and tools such as Azure DevOps, Figma and Aha, Well-organized and detail-oriented, Comfort working with mobile applications and a genuine interest in mobile product experiences. Preferred Qualifications: list: Experience with mobile applications (iOS/Android) or mobile-first software products, Familiarity with the commercial transportation, dealership, or heavy-duty trucking industry, Basic SQL or comfort working with data to inform product decisions, Formal product management or business analysis training or certification. What Success Looks Like: list: Shipping well-defined mobile features..., A healthy, well-groomed backlog..., Strong working relationships..., Customer and support feedback consistently reflected... Why Join Us At Karmak... (similar to Why Join Karmak? maybe duplicate). Then "Apply now!" and other boilerplate. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Apply now!" and "The above statements..." etc. We need to preserve all substantive information. We need to decide sections: Likely we have: - About the role (maybe from Position Summary and Why Join Karmak? Actually "Why Join Karmak?" could be Benefits? But it's more about company culture. Could be placed under "Benefits"? But guidelines: Use headings for Benefits, Pay, Schedule only if posting actually states them. The posting does not mention Pay or Schedule. Benefits? It mentions Employee-Owned (ESOP), Impactful Work, Collaborative Culture, Growth Opportunities. Those could be considered benefits. So we could create a Benefits section with those bullet points. - Responsibilities: Could be the Essential Job Functions list. - Requirements: Could be Knowledge, Skills, And Abilities (required). Also maybe Preferred Qualifications separate? Could be Qualifications section (maybe combine required and preferred?). But guidelines: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have multiple sections. We need to avoid filler headings. So we need to decide which sections have real content. We have: - About the role: Could be Position Summary paragraph. That's substantive. - Responsibilities: Essential Job Functions list. - Requirements: Knowledge, Skills, And Abilities (required). - Qualifications: Preferred Qualifications list. - Skills: Could be overlapping with Requirements; maybe we can combine? But we can have Skills section maybe from the same list? However we need to avoid duplication. Perhaps we put Skills as part of Requirements? But we need to follow instruction: Use headings for those categories if content exists. We have content for Requirements (required experience/skills). We also have content for Qualifications (preferred). We also have content for Skills? The required list includes skills like requirements-gathering, communication, Agile knowledge, organized, comfort with mobile. Those are skills. Could treat them as Skills section. But we already have Requirements. Might be okay to have both Requirements and Skills, but ensure not duplicate. Better: Use Requirements for the required experience and qualifications (3 years experience, etc). Use Skills for the specific abilities (requirements-gathering, communication, Agile, organized, mobile comfort). Use Qualifications for preferred qualifications. But we need to ensure not to repeat same content. Let's extract: Required (Knowledge, Skills, And Abilities): - 3 years of experience in product management, business analysis, or a closely related role. - Strong requirements-gathering skills, with the ability to write clear user stories and acceptance criteria. - Excellent written and verbal communication with both technical and non-technical audiences. - Working knowledge of Agile methodologies and tools such as Azure DevOps, Figma and Aha. - Well-organized and detail-oriented, able to manage multiple work items and priorities at once. - Comfort working with mobile applications and a genuine interest in mobile product experiences. Preferred Qualifications: - Experience with mobile applications (iOS/Android) or mobile-first software products. - Familiarity with the commercial transportation, dealership, or heavy-duty trucking industry. - Basic SQL or comfort working with data to inform product decisions. - Formal product management or business analysis training or certification. Now Responsibilities (Essential Job Functions): - Write clear, detailed user stories and acceptance criteria that give engineering everything they need to build the right thing. - Own and groom the product backlog for assigned mobile applications, keeping work prioritized, well-defined, and ready for each sprint. - Partner day-to-day with engineering, QA, Support, and design to deliver mobile features on time and at quality. - Gather feedback from customers, Client Success, and Support to identify pain points and validate what to build next. - Work within Agile ceremonies and Azure DevOps to track progress, resolve ambiguity, and keep releases on schedule. - Contribute to the mobile product roadmap and help translate business goals into a practical, sequenced plan of work. - Support release readiness with clear documentation, and help enable Support and training teams on new mobile functionality. Now Benefits (Why Join Karmak?): - Employee-Owned: As an ESOP, every Karmak employee is an owner with a real stake in our success. - Impactful Work: Your work reaches dealerships, service teams, and drivers across the commercial transportation industry every day. - Collaborative Culture: Join a talented, driven team in an environment that values your insights and ideas. - Growth Opportunities: Build your product career at a company that invests in its people. Also there is a "Why Join Us At Karmak" later similar but we can ignore duplicate. Now About the role (Position Summary): - Paragraph: "Do you want to put powerful, easy-to-use tools directly in the hands of the people who keep trucks on the road? At Karmak, we're looking for a Product Manager - Mobile to help drive the day-to-day direction and delivery of our mobile applications for heavy-duty truck dealerships. In this role you'll turn customer and business needs into clear requirements, partner closely with engineering to ship well-built features, and keep our mobile messaging and connectivity products moving forward. It's a hands-on product role for someone who loves translating real-world problems into practical software and seeing it land in customers' hands." We should not repeat job title as heading. Already we have Position Summary content. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We need to decide which sections to include: About the role, Responsibilities, Requirements, Skills, Qualifications, Benefits. Possibly also "What Success Looks Like" could be a section? Could be considered "Performance Expectations" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could map "What Success Looks Like" to maybe "Requirements" or "Skills"? But it's more about success metrics. Could be placed under "Responsibilities"? Not exactly. Might be better to omit if not fitting allowed headings. However we must preserve ALL substantive information; we cannot omit success looks like content. We need to include it somewhere. Perhaps we can include it under a heading "Requirements" as part of expectations? But that may be inaccurate. However guidelines: "Use

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

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It might imply we should use those headings when appropriate, but we could also use other headings? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they want us to use those specific headings for sections. It doesn't forbid other headings, but likely they expect only those. However we need to preserve all substantive information; we could incorporate "What Success Looks Like" content into existing sections like Responsibilities or Requirements. For example, we could add bullet points under Responsibilities about shipping well-defined features, healthy backlog, strong relationships, feedback reflected. Those are indeed responsibilities/outcomes. So we can merge them into Responsibilities. Thus we can add those bullet points to Responsibilities list. Now we need to ensure we don't create Pay or Schedule sections because not present. Now we need to output HTML. Structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • 3 years of experience in product management, business analysis, or a closely related role.
  • Strong requirements-gathering skills, with the ability to write clear user stories and acceptance criteria.
  • Excellent written and verbal communication with both technical and non-technical audiences.
  • Working knowledge of Agile methodologies and tools such as Azure DevOps, Figma and Aha.
  • Well-organized and detail-oriented, able to manage multiple work items and priorities at once.
  • Comfort working with mobile applications and a genuine interest in mobile product experiences.

  Skills

  But we already listed skills in Requirements; maybe we can rename Requirements to "Requirements & Skills"? But we need separate Skills section if we want. However we could combine: Use Requirements for experience and qualifications, Skills for abilities. But we already put experience and abilities together. Might be okay to have only Requirements and Qualifications and Benefits and About the role and Responsibilities. The instruction says we can use those headings; we don't have to use all. So we can omit Skills if we feel it's redundant. However we need to ensure we don't lose any substantive info; we already captured abilities in Requirements list. That's fine. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. Now we need to ensure we don't include duplicated lines. The "Why Join Karmak?" and later "Why Join Us At Karmak" are similar; we will include only one Benefits section. Now we need to strip any boilerplate like "Apply now!" and "The above statements..." etc. Now produce HTML. Check for any missing substantive info: The "Essential Job Functions" list we captured. The "Knowledge, Skills, And Abilities" captured. The "Preferred Qualifications" captured. The "What Success Looks Like" we merged into Responsibilities (maybe add bullet points). Let's incorporate those bullet points: - Shipping well-defined mobile features that solve real customer problems and require minimal rework. - A healthy, well-groomed backlog that keeps engineering moving without ambiguity. - Strong working