Product Leader

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Lead Bank", "Product Team at Lead", "Role Description", "Qualifications", "What We Offer". We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We need to include sections only when posting has real specific content. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate like EEO etc. Also remove application instructions (none). Also remove duplicated lines. We need to decide which sections to include: "About the role" maybe corresponds to Role Description? The posting has "Role Description" with bullet points (list). Also "Qualifications" list. "What We Offer" includes benefits and compensation details (Pay). Also there is "About Lead Bank" and "Product Team at Lead" maybe could be "About the role"? But they are more about company. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly. We have: - About Lead Bank (company overview) maybe could be "About the role"? But that heading is for role description. However we could still include an "About the role" section summarizing role description. The role description is under "Role Description". So we can put that under

About the role

and include the paragraphs and list. - Responsibilities: The role description includes many responsibilities bullet points. Could be separate "Responsibilities" section. But we already have role description includes responsibilities. The instruction: prefer a few substantive sections over many thin ones. Could combine role description and responsibilities into one "About the role" section with paragraphs and list. But we also have Qualifications separate. - Benefits: "What We Offer" includes benefits and compensation. Could split into Benefits and Pay sections. The posting includes compensation ranges (Pay). So we can have

Benefits

for benefits list (medical, dental, etc.) and

Pay

for compensation ranges. - Schedule: Not mentioned, so omit. - Skills: Not explicitly separate; qualifications include skills. Could omit Skills section. - Requirements: Could be Qualifications. Thus we will output:

About the role

... (the role description paragraph before list? Actually the role description includes a paragraph: "We are looking for a Product Leader to support the development of our Banking as a Service platform...." plus bullet list starting with "In This Role You Will Be ...". We'll include that paragraph and then the list as

• ... etc. Then

  Qualifications

  with list. Then

  Benefits

  with list of benefits. Then

  Pay

  with paragraph describing compensation ranges and zones. We must not include boilerplate like EEO etc. Remove those lines. Also remove duplicated lines: The posting includes "Lead Bank is proud to have an inclusive culture..." etc. That's EEO boilerplate; remove. Also remove "Reasonable accommodations may be made..." etc. Also remove "Pursuant to the San Francisco Fair Chance Ordinance..." etc. Also remove "Our compensation reflects the cost of labor..." maybe part of Pay section? Actually that is part of Pay description; we can keep it as it's substantive about pay determination. It's not boilerplate? It's generic but still about pay. We'll keep. Now we need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact text? We can keep the substance but we can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can keep them as is. Probably we should copy the text verbatim (except removing boilerplate). So we need to include the exact sentences from the posting for each section. Let's extract: About Lead Bank paragraph: "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 paragraph: "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 paragraph: "We are looking for a 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. Our ideal product manager is highly analytical and uses “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." Then bullet list under "In This Role You Will Be": each line starts with a capitalized phrase. Let's capture them: - passionate about changing the banking system to meet the needs of a modern digital economy - Define product strategy and ensure alignment with broader company goals and vision - Break down ambiguous problems, ask the right questions when gathering data across cross-functional groups, and use a structured (first principles) approach to create clarity and move forward - Develop and maintain a prioritized product roadmap with well-defined product requirements and compelling business justifications - Set clear goals and success metrics to measure product performance and guide decision-making - Maintain knowledge of the technical and operational elements of your product to make informed, data-driven decisions - Develop clear, actionable product requirements and communicate them effectively to engineering and design teams - Collaborate closely across engineering, design, compliance, operations, and other teams to drive execution from concept to launch - Be the glue in a diverse cross-functional environment, facilitating alignment, decisions, and consensus - Manage and mentor a team of product managers, providing guidance, support, and feedback to help them grow - Own resource allocation and hiring decisions to ensure the team is structured to meet product and business goals - Gather customer insights and feedback to inform roadmap prioritization and feature design - Begin making trade-off decisions that balance user value, technical complexity, and business impact - Perform all other duties as assigned Note: The first bullet "passionate about changing the banking system..." is lower-case p; but we keep as is. Qualifications list: - 10+ 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 paragraph: "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:" then bullet list: - 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 HRA - Paid 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 after that there is EEO boilerplate etc which we remove. Then Pay paragraph: "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: $250,000 - $275,000 (SF/Bay Area, NYC, Seattle) Zone 2: $220,000 - $250,640 (Los Angeles, Chicago, Austin, Denver, Boston, Washington DC, San Diego, Philadelphia, Portland, Sacramento, Miami) Zone 3: $200,000 - $240,233 (Other US Metros)" We need to decide sections. Option: About the role could include the company overview and product team? But heading "About the role" maybe just role description. However we have "About Lead Bank" and "Product Team at Lead" which are about company/team. Could we put them under a heading like "About the company"? Not in allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit content into those headings. We could put company overview under About the role? Might be odd but acceptable. Or we could omit it? But we must preserve ALL substantive information; cannot omit. So we need to include it somewhere. Perhaps we can include it under About the role as introductory paragraphs before responsibilities. That seems okay. Thus About the role section will contain: - Lead is a banking infrastructure platform... (company overview) - Lead’s Product team identifies partner needs... (product team) - We are looking for a Product Leader... (role description paragraph) - Then the bullet list of responsibilities. That preserves all. Qualifications section: list. Benefits section: list of benefits (competitive compensation, medical etc, paid parental leave, flexible vacation, fun team environment). Note that "Competitive compensation, including opportunities for equity grants..." is actually compensation; but we have a separate Pay section. However the benefits list includes that line; we could keep it there, but then Pay section would duplicate. Better to split: Benefits section includes medical, dental, vision, life, 401k matching, FSA/HSA/HRA, paid parental leave, flexible vacation policy, fun team environment. The competitive compensation line we could move to Pay section. However the instruction: "Prefer a few substantive sections over many thin ones." Having both Benefits and Pay is fine. We'll keep compensation in Pay section. Thus Benefits section list: - Medical, Dental, Vision, Life, 401k Matching, and other wellness benefits, including FSA, HSA and HRA - Paid 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 Pay section: paragraph about compensation ranges and zones, plus maybe the line about competitive compensation and equity grants? Actually that line is part of What We Offer bullet list; we could include it in Pay section as part of description. Let's include it: "Competitive compensation, including opportunities for equity grants based on experience, geographic location, and role" plus the compensation ranges paragraph. Thus Pay section will have:

  Competitive compensation, including opportunities for equity grants based on