Staff Product Designer

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Novo" description, then "The Role", "What You'll Do", "Own the design system", "Design for a regulated product", "Use AI as part of the craft", "Multiply the team", "Must Have", "Nice to Have", "How We Work". We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content. We need to decide which sections correspond. We have description about Novo (company overview) maybe "About the role"? Actually "About the role" is typical heading for role description. Could use "About the role" for the role overview (The Role). Responsibilities: "What You'll Do". Requirements/Qualifications/Skills: Must Have, Nice to Have could be Requirements/Qualifications/Skills. Benefits: "How We Work" includes values, maybe benefits? Also there is mention of Competitive salary and stock options, medical/dental/vision, learning budget, offices, Wednesday lunches. That's benefits. Pay: mention competitive salary and stock options - could be Pay. Schedule: not mentioned. So we should not include Schedule. We must not repeat job title as heading. No Job ID. We need to preserve all substantive info, not invent. Remove boilerplate (cookie/navigation/legal/EEO etc). There's none. We need to output only HTML fragment, using

for section headings,

• for lists,

  for prose. We need to decide sections: About the role (role overview), Responsibilities (What You'll Do), Requirements (Must Have), Qualifications (Nice to Have maybe), Skills (maybe combine?), Benefits (Competitive salary etc), Pay (maybe separate). But we should prefer few substantive sections over many thin ones. Could combine Must Have and Nice to Have into Requirements? But they are distinct. Could have Requirements (Must Have) and Qualifications (Nice to Have). Skills maybe not needed. Benefits separate. Pay separate. We must not create sections with filler like "commensurate with experience". We have actual content. Let's extract content: About Novo description: paragraphs about mission, product, etc. That's company overview, not role. Could be placed under About the role? Actually About the role could include company overview and role summary. We'll put that as About the role. The Role paragraph: "We're looking for a Staff Product Designer..." That's role overview. Could be part of About the role as well. But we can separate: About the role includes company description and role summary. Then Responsibilities: "What You'll Do" bullet list. Let's parse "What You'll Do" list items: - Lead design on Novo's most complex problems - Own end-to-end design for cross-surface initiatives — onboarding and account opening, money movement, lending and credit, invoicing and getting paid — from problem framing through shipped, measured outcomes - Turn ambiguous business goals and regulatory constraints into clear product strategy, information architecture, and interaction models - Work upstream with product and engineering leads to shape the roadmap, not just execute it - Set and raise the bar for craft - Define what "done well" means for interaction, visual, and content design at Novo, and hold the team (and yourself) to it - Run design critique that makes people better and work sharper - Ship polished, accessible (WCAG-conformant), production-ready design across web and native mobile - Own the design system - Lead the evolution of Novo's design system: tokens, components, patterns, documentation, and the process by which it grows - Partner with engineering to keep Figma and production in lockstep, and to retire the inconsistencies that accumulate in a fast-moving product - Make the system the default path — faster for designers and engineers to use it than to go around it - Design for a regulated product - Work hand-in-hand with Compliance, Risk, and Legal so that disclosures, consent, KYC/KYB, and error states are designed with care rather than bolted on - Treat trust as a design surface: security, clarity around fees and terms, and honest handling of edge cases - Use AI as part of the craft - Fluency across the AI design stack — Figma AI, Claude/ChatGPT, Cursor or Claude Code for prototyping, generative tools for exploration — with a clear point of view on where they accelerate the work and where they don't - Help the team build repeatable AI-assisted workflows for research synthesis, exploration, prototyping, and documentation - Contribute design thinking to Novo's own AI-powered product experiences - Multiply the team - Mentor senior and mid-level designers through pairing, critique, and feedback - Write and codify the principles, patterns, and playbooks that make good design repeatable at Novo - Be the design voice in cross-functional and leadership conversations We need to turn these into

  • . Could flatten or keep nested? Probably just flat list items; nested could be
    • with inner
      . Acceptable. Next Must Have list: - 10+ years of product design experience, with at least 3 operating at a staff or lead scope — owning cross-team, cross-platform problems as an ICA - portfolio of shipped, complex products that shows the full arc: research and problem framing, systems thinking, interaction design, visual polish, and business results - Deep experience building and scaling design systems across web and native mobile (iOS and Android) - Expert-level Figma, strong prototyping skills, and enough technical fluency to pair effectively with engineers and understand what's cheap versus expensive to build - Data fluency: you read funnels, frame experiments, and use quantitative and qualitative signals to make design decisions defensible - Experience designing in a regulated environment — fintech, financial services, healthcare, or similar — including disclosures, consent flows, and identity verification - Hands-on AI fluency in your daily design work, with sound judgment about when it adds value and when it introduces risk - Exceptional communication: you present clearly, give and take hard feedback well, and influence without authority - Comfortable with ambiguity and speed, without letting quality slide Nice to Have list: - Direct experience designing lending, credit, payments, or business onboarding products - Comfort prototyping in code (React, SwiftUI, or similar) - Experience designing agentic or AI-assisted product experiences - Motion and brand sensibility that can bridge product and marketing design - Experience working with distributed teams across time zones How We Work (values) list: - Run for the bus. When you see something that needs fixing, you fix it. You don't wait for a ticket. - Hierarchy is not authority. The best idea wins regardless of who had it — including when it isn't yours. - Assume best intention. Hard weeks and mistakes happen. We give grace to each other and to ourselves. - Intellectual honesty. We own our mistakes, say so before doubling down, and lead by example. Benefits/Pay: The posting includes: "Competitive salary and stock options for every full-time employeeMedical, dental, and vision coverageLearning and development budgetOffices in NYC and India, with Wednesday team lunches that rotate cuisines". That's benefits. Pay: competitive salary and stock options. Could combine into Benefits section, but we could also have Pay separate. Since they said prefer few substantive sections, maybe combine Pay and Benefits into one Benefits section that includes salary, stock options, medical, etc. But they said never create Pay/Schedule/Benefits sections unless posting actually states them. It does state competitive salary and stock options (Pay) and medical etc (Benefits). Could make two sections: Pay and Benefits. But that's many thin sections. However they are substantive. Could combine into Benefits and mention salary/stock options there. That would be one Benefits section. That seems okay. Thus sections: About the role, Responsibilities, Requirements (Must Have), Qualifications (Nice to Have), Benefits (including Pay). No Schedule. We need to ensure we don't repeat job title as heading. We'll not. Now produce HTML:

      About the role

      About Novo ... (the company description) ... plus maybe the role summary paragraph "We're looking for a Staff Product Designer...". We'll combine. Let's craft About the role paragraph: combine the initial Novo description and the role overview. Novo description: "About Novo Small businesses are the backbone of the US economy — nearly half of GDP and the private workforce — yet big banks don't give owners the access, assistance, or modern tools they need to grow. We started Novo to change that. Our mission is to increase the GDP of the modern entrepreneur by building the go-to banking platform for small businesses. Novo is a fintech, not a bank. We give entrepreneurs, freelancers, and SMBs an operating system for their money: no-fee business checking, debit and credit cards, loans and funding, payments across every rail (ACH, wires, FedNow), invoicing, bill pay, expense management, and integrations with the tools they already run their business on. We've helped hundreds of thousands of businesses get powerfully simple banking, and we're just getting started. Why Novo? A mission-driven team building for the people big banks pretend don't existReal ownership: we make decisions that affect real businesses every day, and we trust people to act on thatA flat culture where ideas win on merit — hierarchy is not authorityModern stack, modern tooling, and a team that takes AI seriously as part of how we work" Then The Role paragraph: "We're looking for a Staff Product Designer to be the highest-leverage individual contributor on our product design team. You'll own the hardest, most ambiguous design problems at Novo — the ones that cut across checking, payments, credit, and invoicing, and across web, iOS, and Android — and you'll set the bar for what great looks like for everyone else. This is not a management role. It is a role with real authority over the quality and coherence of the product. You'll partner directly with product leads, engineering leads, data, and compliance to shape what we build, not just how it looks. You'll multiply the team's output by making the design system, the patterns, and the standards stronger than any one designer could on their own. You'll know you're succeeding when Novo feels like one product instead of a collection of features, when a small business owner can move money, get paid, and access capital without ever having to think about how banking works underneath, and when other designers ship better work because of the foundations you built." We'll combine into one

      maybe long but okay. Then Responsibilities:

      Responsibilities

      with items. We need to preserve the bullet points exactly as given, but we can rephrase slightly? Must preserve all substantive information; we can keep same meaning. We'll create list items for each top-level bullet; sub-bullets can be nested
      . Let's list: - Lead design on Novo's most complex problems - Own end-to-end design for cross-surface initiatives — onboarding and account opening, money movement, lending and credit, invoicing and getting paid — from problem framing through shipped, measured outcomes - Turn ambiguous business goals and regulatory constraints into clear product strategy, information architecture, and interaction models - Work upstream with product and engineering leads to shape the roadmap, not just execute it - Set and raise the bar for craft - Define what "done well" means for interaction, visual, and content design at Novo, and hold the team (and yourself) to it - Run design critique that makes people better and work sharper - Ship polished, accessible (WCAG-conformant), production-ready design across web and native mobile - Own the design system - Lead the evolution of Novo's design system: tokens, components, patterns, documentation, and the process by which it grows - Partner with engineering to keep Figma and production in lockstep, and to retire the inconsistencies that accumulate in a fast-moving