Senior Product Manager

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate like EEO, etc. Must preserve all substantive info. We need to parse the posting. Content: - About Lead Bank: description of company. Could be "About the role"? Actually "About Lead Bank" is about company. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" maybe includes description of role? But we have "About Lead Bank" and "Product Team at Lead". Might fit under "About the role"? However we need to preserve all substantive info. Could create sections: About the role (maybe combine company description and product team). Responsibilities: list from "In This Role You Will ..." bullet points. Requirements/Qualifications: list from Qualifications. Skills: maybe from qualifications? Could combine. Benefits: from "What We Offer". Pay: from compensation ranges. Schedule: not mentioned, so omit. We must not create sections with filler. So include only sections with content. We need to use

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

  for prose. We must not repeat job title as heading. No job title given explicitly; it's "seasoned product leader". Not needed. We must not include cookie/navigation/legal/EEO etc. So remove the equal opportunity statements etc. Also remove "Reasonable accommodations..." etc. Also remove "Pursuant to the San Francisco Fair Chance Ordinance..." etc. Also remove "Our compensation reflects the cost of labor..." maybe that's part of Pay section? It mentions pay based on factors; but we have specific pay ranges. The statement about compensation reflecting cost of labor is generic; we could keep as part of Pay section prose? It's not boilerplate? It's somewhat generic but still about pay. Might keep. We must not invent or summarize away detail. Must preserve all substantive information. Let's extract substantive info: Company description: "About Lead Bank Lead is a banking infrastructure platform trusted by the most innovative companies to power complex financial products. We enable fintechs to offer compliant, programmable services like payments, lending, and digital assets at scale. Banking has moved beyond traditional institutions and is now embedded directly into everyday experiences, meaning companies need modern infrastructure that is safe, secure, and operationally sound. Today, Lead is one of the only API-first, developer-focused partner banks with the financial, regulatory, and legal expertise required to help fintechs succeed. We operate offices in San Francisco, Sunnyvale, and New York City, and an FDIC-insured bank in Kansas City." Product Team at Lead: "Lead’s Product team identifies partner needs, defines strategy, and works closely with Engineering and Design to bring products to life, guiding execution from concept through launch. But building financial infrastructure isn't just about shipping features. This team is tasked with transforming the most complex banking systems and regulatory requirements into intuitive products that developers love to build with. To help fintechs launch, grow, and innovate with confidence, the Product team must be driven by a singular goal: creating elegant solutions to difficult problems. To that end, success on this team requires genuine curiosity, exceptional communication, and thoughtful collaboration." Role Description: "We are looking for a seasoned product leader to support the development of our Banking as a Service platform. The services that you build will create the pathway for our clients to deliver innovative financial products relating to deposits, credit and lending, issuing and accepting credit card and/or debit card transactions, and more. An ideal leader will be highly analytical and use “first principles thinking” when understanding a new domain. We are looking for someone with a user-first mindset to build a next-generation platform from the ground up. This is a senior individual contributor role, with success defined by product leadership, end-to-end ownership, and strong cross-functional influence." In This Role You Will Be ... list: - passionate about changing the banking system to meet the needs of a modern digital economy - Break down ambiguous problems, ask the right questions when gathering data across cross-functional groups, and use a structured (first principles approach) to unblock a decision to help create a path forward - Develop and maintain a prioritized product roadmap with well defined product requirements and business justifications - Maintain knowledge of the technical and operational elements of your product which should inform decision making - Develop clear product requirements and communicate them with engineering teams and designers - Be the glue in a diverse cross-functional environment and help drive decisions and consensus - Perform all other duties as assigned Qualifications: "7+ years demonstrated experience in product management and/or engineering with a track record building world class fintech products Prior experience in enterprise software domain, scalable SaaS platform design experience, and highly compliance-centric product Have strong technical competence, with experience and track record of success in building high-velocity, low-latency, high-availability services with beautiful API design The ability to be practical and are eager to collaborate/compromise to get to the best, most efficient outcome Strong judgment and analytical skills Strong communication skills and the ability to work cross-functionally to align stakeholders on the goals and behaviors required for success Operate as a craftsman who will explore and execute on details to create great product experiences Have humility and are open to coaching" What We Offer: "At Lead, we design our benefits to support company culture and principles, to foster an efficient and inspiring work environment, and to create the conditions for our team to give their best in both work and life: Competitive compensation, including opportunities for equity grants based on experience, geographic location, and role Medical, Dental, Vision, Life, 401k Matching, and other wellness benefits, including FSA, HSA and HRAPaid parental leave Flexible vacation policy, including PTO and paid holidays A fun and challenging team environment in a dynamic industry with ample opportunities for career growth" Then EEO etc removed. Pay: "Our compensation reflects the cost of labor across several US geographic markets. Pay is based on a number of factors and may vary depending on geographical market location, job-related knowledge, skills, and experience. These ranges may be modified in the future. Zone 1: $220,000 - $248,200 (SF/Bay Area, NYC, Seattle) Zone 2: $190,000 - $220,000 (Los Angeles, Chicago, Austin, Denver, Boston, Washington DC, San Diego, Philadelphia, Portland, Sacramento, Miami) Zone 3: $180,000 - $206,400 (Other US Metros)" Schedule: none. We need sections: About the role (maybe combine company description and product team?), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. But we have both Qualifications and Requirements; they may overlap. The posting has "Qualifications" section. Could treat that as Requirements. Could also have Skills separate? The qualifications list includes skills like strong technical competence, communication, etc. Could put those under Skills. But we must not invent sections; we can have both Requirements and Qualifications if content distinct. However the posting only has Qualifications; we could treat that as Requirements. Or we could split: Requirements = the 7+ years experience etc; Skills = strong judgment, communication, etc. But better to follow the posting: have a Qualifications section with the list. Could also have a Skills section if we extract skills from qualifications. But risk of duplication. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Qualifications into one section called "Requirements" (or "Qualifications") and not have both. Since the posting uses "Qualifications", we can use that heading. Then we might not need a separate Skills section. But the instruction list includes Skills as possible heading; we can omit if not needed. Thus sections: About the role (company + product team + role description), Responsibilities (the In This Role You Will list), Qualifications (the bullet list), Benefits (What We Offer), Pay (compensation ranges). Possibly also include a short paragraph about role description under About the role. We must not include fluff like "Perform all other duties as assigned" - that's substantive? It's a generic line but it's part of responsibilities; we can keep. We must not include boilerplate like EEO etc. Now produce HTML fragment:

  About the role

  ... combine company description, product team, role description ...

  Then responsibilities as
  • ... each bullet. Then qualifications as
    • ... each bullet. Then benefits as
      • ... each bullet. Then pay as

        ... maybe include the ranges as list? Could be

        • but it's not a list of duties; but we can use

          with the ranges. We must not include schedule. Let's craft the About the role paragraph: We need to preserve all substantive info: company description, product team, role description. We can write:

          Lead is a banking infrastructure platform trusted by the most innovative companies to power complex financial products. We enable fintechs to offer compliant, programmable services like payments, lending, and digital assets at scale. Banking has moved beyond traditional institutions and is now embedded directly into everyday experiences, meaning companies need modern infrastructure that is safe, secure, and operationally sound. Today, Lead is one of the only API-first, developer-focused partner banks with the financial, regulatory, and legal expertise required to help fintechs succeed. We operate offices in San Francisco, Sunnyvale, and New York City, and an FDIC-insured bank in Kansas City. The Product team identifies partner needs, defines strategy, and works closely with Engineering and Design to bring products to life, guiding execution from concept through launch. The team transforms complex banking systems and regulatory requirements into intuitive products that developers love to build with, driven by a singular goal of creating elegant solutions to difficult problems, requiring genuine curiosity, exceptional communication, and thoughtful collaboration. We are looking for a seasoned product leader to support the development of our Banking as a Service platform. The services you build will create the pathway for clients to deliver innovative financial products relating to deposits, credit and lending, issuing and accepting credit card and/or debit card transactions, and more. An ideal leader will be highly analytical and use “first principles thinking” when understanding a new domain, with a user‑first mindset to build a next‑generation platform from the ground up. This is a senior individual contributor role, with success defined by product leadership, end‑to‑ownership, and strong cross‑functional influence.

          Check we didn't miss any details: "end-to-end ownership" we wrote "end‑to‑ownership" typo; correct to "end-to-end ownership". Also "strong cross-functional influence". Good. Now responsibilities list: - passionate about changing the banking system to meet the needs of a modern digital economy - Break down ambiguous problems, ask the right questions when gathering data across cross-functional groups, and use a structured (first principles approach) to unblock a decision to help create a path forward - Develop and maintain a prioritized product roadmap with well defined product requirements and business justifications - Maintain knowledge of the technical and operational elements of your product which should inform decision making - Develop clear product requirements and communicate them with engineering teams and designers - Be the glue in a diverse cross-functional environment and help drive decisions and consensus - Perform all other duties as assigned Make each
        • . Qualifications list: - 7+ years demonstrated experience in product management and/or engineering with a track record building world class fintech products - Prior experience in enterprise software domain, scalable SaaS platform design experience, and highly compliance-centric product - Have strong technical competence, with experience and track record of success in building high-velocity, low-latency, high-availability services with beautiful API design - The ability to be practical and are eager to collaborate/compromise to get to the best, most efficient outcome