Design Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes "About OnePay", "About The Experience Design Team", "The Role", "What we’re looking for", "Tools We Use", "You Bring", "What We Offer", "Standard Interview Process", "Equal Employment Opportunity". We need to use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. The posting does not have explicit "Responsibilities", "Requirements", "Qualifications", "Skills", "Pay", "Schedule". It has "What we’re looking for" (which could be Requirements/Qualifications/Skills). It has "You Bring" (similar). It has "What We Offer" (benefits). It has "Tools We Use" (maybe not a standard heading but could be part of Requirements? Not required). We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include sections only if content exists. We have "About OnePay" and "About The Experience Design Team" - could be considered "About the role"? Actually "About the role" is a section heading we can use for description of role. The posting includes "The Role" and "About The Experience Design Team". We could combine into About the role section. Responsibilities: Not explicit. Could infer from "What we’re looking for" but that's more qualifications. Safer to omit Responsibilities if no explicit. Requirements: Could be "What we’re looking for" and "You Bring". We'll put Requirements. Qualifications: Could be similar; maybe we can combine but we should not duplicate. Could put Qualifications as same as Requirements? Better to have one section. Since we can have multiple sections but we should avoid thin ones. Perhaps we put Requirements and Qualifications combined? But we need to follow headings exactly. We could have Requirements and Qualifications both with content. But we need to ensure we don't repeat same content. Could split: Requirements = "What we’re looking for" (the bullet points). Qualifications = "You Bring" (the bullet points). That seems reasonable. Skills: Could be "Tools We Use" maybe? But that's more tools. Could treat as Skills. Or we could omit Skills if not explicit. The posting mentions fluency in Figma and code, AI tools, design tokens, component architecture, communication, operating in fluid environments. Those are skills. Could put Skills section with those bullet points. Benefits: "What We Offer" includes competitive base salary, stock options, health benefits, 401(k) plan with company match, remote-friendly, FTO, growth opportunities, high-growth mission-driven culture. That's benefits. Pay: Not explicit salary numbers, just "competitive base salary". That's vague but still mentions salary. The rule says do NOT include Pay section unless posting actually states them. It does state "competitive base salary" but not a number. Is that considered stating? It's a statement but not specific. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Competitive base salary" is somewhat vague but not exactly placeholder like those. Might be okay to include Pay section with that sentence. However they said "Prefer a few substantive sections over many thin ones." Might be better to incorporate pay into Benefits section. Since Benefits already includes compensation aspects. We could omit Pay. Schedule: Not mentioned. Thus we will output sections: About the role, Requirements, Qualifications, Skills, Benefits. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include boilerplate like EEO, equal opportunity, scam warning, navigation, cookie, legal, application instructions, interview process details? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also "Standard Interview Process" and "Equal Employment Opportunity" should be removed. So we omit those sections. We also need to remove "About OnePay" and "About The Experience Design Team" as separate headings? We'll combine into About the role. We need to keep all substantive info: description of OnePay, mission, backing, etc. Also description of Experience Design Team. Also The Role description. Also What we’re looking for bullet points. Also Tools We Use. Also You Bring bullet points. Also What We Offer bullet points. We need to ensure we don't lose any info. Let's extract. About OnePay paragraph: "OnePay is the consumer fintech trusted by millions of Americans to make money better. Our financial system is broken. High fees, low rates, and too few ways to actually grow your money. We’re fixing it. And we’re moving fast. We’re an all-in-one financial services platform that brings together banking, high-yield savings, credit cards, point-of-sale lending, investing, and crypto in one place. We also partner with employers, HCM providers, gig platforms, and others to deliver embedded financial services to millions of employees and frontline workers. We’re backed by Walmart, the world’s largest retailer, and Ribbit Capital, one of fintech’s most respected investors, giving us rare scale, distribution, and the opportunity to build something truly category-defining." About The Experience Design Team: "Experience Design at OnePay shapes how millions of people interact with their money. The product touches saving, spending, borrowing, and growing wealth – often for people the traditional financial system has underserved. That weight raises the bar on what we ship and how we ship it. We’re a small, senior team with roots at Apple, Meta, Ford, Airbnb, and leading fintechs – low ego, high craft, and genuinely collaborative. AI is a baseline part of how we work, not a future we’re talking about." The Role: "We’re looking for a Design Engineer to help define what modern design-to-code looks like at OnePay. This is a first-class engineering role with design fluency. You’ll generate production-ready components directly, use AI coding tools aggressively, and help push the team past traditional spec-based handoff. You’re not executing the current model – you’re shaping what comes next." What we’re looking for bullet points (list): - You ship in code. Figma is part of how you communicate, but you’re most fluent in the codebase. You generate production-ready work, not just specs. - You’re AI-native at production velocity. Cursor, Claude Code, v0, similar tools – they’re already how you move. You ship more in a day than most teams do in a week. - You’re rethinking handoff. The traditional model is breaking down, and you’re excited to define what replaces it. - You translate fluently. You speak both languages. Designers trust you, engineers trust you, and you make the gap between them disappear. - You sweat the implementation. A two-pixel drift in production matters to you. So does a token that doesn’t quite map. You catch what others miss. - You operate in motion. Process is fluid here, and you help shape it as you ship. Tools We Use: "We use Node and TypeScript on the server, leveraging the NestJS framework within a microservice-oriented architecture running on Kubernetes and AWS. On the client side, we build and ship product features for iOS, Android, and web platforms using React Native. We also embrace AI-assisted development, so engineers have their choice of Claude Code or Cursor to fit their workflow. While you don't need experience with our exact stack, familiarity with modern software engineering practices will help you ramp up quickly." You Bring bullet points: - Fluency in both Figma and code (React Native or React). - Active use of AI coding tools (Cursor, Claude Code, v0, or similar) at production velocity. - Fluency in design tokens, component architecture, and how design systems map to code. - Experience shipping on cross-functional teams where design and engineering overlap. - Strong communication across both disciplines. - A track record of operating in fluid environments and helping define how teams work. What We Offer: "Competitive base salary, stock options, and health benefits from Day 1 401(k) plan with company match Remote-friendly (US), flexible time off (FTO), and opportunities for growth A high-growth, mission-driven, inclusive culture where your work has real impact" Note there is a missing punctuation but we keep as is. We need to format as HTML. We'll have:

  About the role

  ... combined paragraphs ...

  Then maybe

  Requirements

  with
  • for "What we’re looking for" bullet points.

    Qualifications

    with
    • for "You Bring" bullet points.

      Skills

      with
      • for "Tools We Use" maybe? But Tools We Use is more about stack; could be considered Skills. We'll put that. Alternatively we could put Skills as the bullet points from "You Bring" but we already used that for Qualifications. Let's decide: Requirements = What we’re looking for (expectations). Qualifications = You Bring (candidate qualifications). Skills = Tools We Use (technical skills). Benefits = What We Offer. We need to ensure we don't lose any info: The "Tools We Use" paragraph includes Node, TypeScript, NestJS, Kubernetes, AWS, React Native, AI-assisted development. We'll put that as a

        maybe not a list. But rule: Use

        • for any list of duties/requirements/benefits. For prose, use

          . Tools We Use is a paragraph, not a list. So we can put

          . Similarly About the role is prose. Thus final HTML:

          About the role

          OnePay is the consumer fintech trusted by millions of Americans to make money better. Our financial system is broken. High fees, low rates, and too few ways to actually grow your money. We’re fixing it. And we’re moving fast. We’re an all-in-one financial services platform that brings together banking, high-yield savings, credit cards, point-of-sale lending, investing, and crypto in one place. We also partner with employers, HCM providers, gig platforms, and others to deliver embedded financial services to millions of employees and frontline workers. We’re backed by Walmart, the world’s largest retailer, and Ribbit Capital, one of fintech’s most respected investors, giving us rare scale, distribution, and the opportunity to build something truly category-defining.

          Experience Design at OnePay shapes how millions of people interact with their money. The product touches saving, spending, borrowing, and growing wealth – often for people the traditional financial system has underserved. That weight raises the bar on what we ship and how we ship it. We’re a small, senior team with roots at Apple, Meta, Ford, Airbnb, and leading fintechs – low ego, high craft, and genuinely collaborative. AI is a baseline part of how we work, not a future we’re talking about.

          We’re looking for a Design Engineer to help define what modern design-to-code looks like at OnePay. This is a first-class engineering role with design fluency. You’ll generate production-ready components directly, use AI coding tools aggressively, and help push the team past traditional spec-based handoff. You’re not executing the current model – you’re shaping what comes next.

          Requirements

          • You ship in code. Figma is part of how you communicate, but you’re most fluent in the codebase. You generate production-ready work, not just specs.
          • You’re AI-native at production velocity. Cursor, Claude Code