Product Manager, Design Systems

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Must not create sections with filler like "commensurate with experience". Must not invent or summarize away detail. We need to parse the posting. Let's extract sections: - About The Role: paragraph describing role. - Responsibilities: list of bullet points after "In this role, you can expect to" (list of responsibilities). Those are bullet points. - Requirements/Qualifications/Skills: The posting includes "To thrive in this role, you have 8+ years of experience as a Product Manager." then bullet list of experience requirements. Could be considered Requirements or Qualifications. We need to decide which sections to include. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We can include multiple but only if content exists. We have content for Responsibilities (list). We have content for Requirements/Qualifications/Skills (list of experience). Could combine into one section "Requirements" or separate "Qualifications" and "Skills". The list includes experience, experience working on design systems, track record, partnering, driving adoption, evidence of using data, experience operating in environments... These are more qualifications/skills. Could put under "Qualifications". We'll decide to have a single section "Qualifications" containing the list. We also have "A Little About Us" which is company description. That's not a required heading; could be omitted as not in list? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The headings list is just examples; we can include other headings if appropriate? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when applicable. "A Little About Us" is not in that list; maybe we should not create a heading for it; we could incorporate into About the role? But it's separate. However we could omit it because it's not required headings; but we must preserve ALL substantive information. If we omit it, we lose info. We could include it as a

without a 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 we use those headings for the sections we have. For company description, maybe we can include as a

under About the role? But it's separate. Could we treat "About The Role" as heading and include both role description and company description under it? That would mix. Better to have a separate heading like "About Chime" but not in list. However instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but the examples are those. Safer to stick to those headings only. Then we need to decide where to put company description. Could we put it under "About the role"? That heading is about the role, not company. Might be considered filler if we put unrelated content. But we could include a brief paragraph about company under "About the role" as context? Might be okay but not ideal. Alternatively, we could create a section "About Chime" using

even though not in examples; risk of being marked wrong. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies those are the allowed headings. So we should only use those. Then we need to fit all substantive content into those sections. We have: - About the role: role description (first paragraph). Could also include "A Little About Us" as part of About the role? Might be okay but it's about company not role. However the instruction says preserve ALL substantive information; we can't drop it. So we need to include it somewhere. Perhaps we can include it as a

under About the role heading, even if not strictly about role. It's still substantive. - Responsibilities: list after "In this role, you can expect to". We'll capture each bullet. - Requirements/Qualifications/Skills: list after "To thrive in this role, you have 8+ years of experience as a Product Manager." We'll capture each bullet. - Benefits: The posting includes "Full-time employees are also eligible for a bonus, competitive equity package, and benefits." Then later "What We Offer For Our Full-time, Regular Employees" with a list of benefits (in-office policy, backup child care, etc). That's benefits content. So we should include a Benefits section with that list. - Pay: The posting includes salary range: "The base salary offered for this role and level of experience will begin at $196,000 and up to $255,000. The actual base salary offered may be higher, depending on your location, skills, qualifications, and experience." Also mentions bonus, equity. So we have Pay info. - Schedule: The posting includes in-office work policy: "Our in-office work policy is designed to keep you connected - with four days a week in the office and Fridays from home for those near one of our offices, plus team and company-wide events depending on location. Whether you’re coming in regularly or are part of our fully remote program, you’ll stay engaged with your work and teammates." That's schedule info. So we can include Schedule section. Thus we will have sections: About the role, Responsibilities, Qualifications (or Requirements), Benefits, Pay, Schedule. Possibly also Skills but we can incorporate into Qualifications. We must not create sections with filler like "commensurate with experience". We have real content. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip out the EEO paragraph, the accommodation contact, privacy notice, the list of country codes (that seems like garbage), the "We know that great work can’t be done without a diverse team..." paragraph (that's EEO/diversity statement) - remove. Also remove the "Chime is proud to be an Equal Opportunity Employer..." etc. Also remove the "If you have a disability..." etc. Also remove the "To learn more about how Chime collects..." etc. Also remove the "244 results found No results found ..." and the long list of country codes (looks like some garbage). Also remove the "What We Offer For Our Full-time, Regular Employees" heading? Actually that's part of benefits; we keep the content but not the heading as we will use our own

Benefits. We must preserve all substantive information: role description, responsibilities list, qualifications list, benefits list, pay info, schedule info. We need to format as HTML fragment: use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not output markdown code fences. Let's extract precise content. First, "About The Role" paragraph: "About The Role We are hiring a Product Manager to join our AI & App Experience (AAX) team, with a focus on design systems. In this role, you’ll help shape the shared foundations that make it easier for teams across Chime to build consistent, intuitive, and high-quality member experiences. You’ll own product strategy and execution for design-system capabilities that sit at the intersection of product, design, and engineering. You’ll work across teams to understand where fragmented patterns, tooling, and workflows create friction, then turn those insights into scalable systems that improve both the quality of our app experience and the speed at which teams can build it." We need to ensure we keep that exactly (maybe minor punctuation). We'll output as

  . Then responsibilities: after "In this role, you can expect to" there is a list of sentences each starting with a verb. Let's extract them: - Own the product vision, strategy, and roadmap for design-system capabilities within AAX, connecting platform investments to meaningful improvements in Chime’s member experience. - Partner closely with Design and Engineering to evolve shared components, patterns, tooling, and infrastructure that enable teams to build cohesive app experiences more efficiently. - Identify high-leverage opportunities to improve how product teams discover, adopt, and contribute to Chime’s design system, balancing consistency with the flexibility teams need to innovate. - Develop a deep understanding of the needs of internal product builders and translate those needs into clear product priorities, requirements, and measurable outcomes. - Drive alignment across multiple product areas, helping teams make thoughtful tradeoffs when shared platform needs, individual product needs, and longer-term experience quality intersect. - Establish success measures for the design system, using quantitative and qualitative signals to understand adoption, developer and designer effectiveness, experience consistency, and business impact. - Help define how emerging AI capabilities can improve the way Chime teams design, build, and maintain app experiences, where relevant to the design-system strategy. We'll put each as

• . Now qualifications: after "To thrive in this role, you have 8+ years of experience as a Product Manager." then list: - Product management experience owning complex products, platforms, or internal systems from strategy through execution in a technology environment. - Experience working on design systems, developer platforms, UI frameworks, shared product infrastructure, or similarly horizontal capabilities used by multiple teams. - A track record of translating ambiguous, cross-functional problems into a clear product strategy, prioritized roadmap, and measurable outcomes. - Experience partnering deeply with Product Design and Engineering, with enough technical and design fluency to navigate component architecture, platform constraints, user experience tradeoffs, and implementation decisions. - Experience driving adoption of a shared product or platform across multiple teams, including identifying user pain points and influencing stakeholders without relying on direct authority. - Evidence of using data, research, and customer or internal-user feedback to prioritize investments and assess whether a product or platform is delivering meaningful value. - Experience operating in environments where quality, consistency, scale, and speed all matter, and where product decisions require balancing near-term delivery with durable foundations. We'll put as
• under Qualifications. Now Benefits: after "What We Offer For Our Full-time, Regular Employees" there is a list with emojis. We need to extract the substantive content, ignoring emojis maybe but keep text. List: - Our in-office work policy is designed to keep you connected - with four days a week in the office and Fridays from home for those near one of our offices, plus team and company-wide events depending on location. Whether you’re coming in regularly or are part of our fully remote program, you’ll stay engaged with your work and teammates. - Benefits that support your work and life, including backup child, elder, and pet care and subsidized commuter benefits for eligible employees. - Comprehensive health, financial, and wellbeing benefits designed to support you at every stage of life. - Generous vacation policy and company-wide paid days off - 1% of your time off to support local community organizations of your choice - Annual wellness stipend to use towards eligible wellness related expenses - Up to 22 weeks of paid parental leave for birthing parents and 12 weeks of paid parental leave for non-birthing parents - Access to family planning reimbursement - A challenging and fulfilling opportunity to join one of the most experienced teams in FinTech and help millions unlock financial progress We need to ensure we