Product · Role 03 of 03

UX Design Lead — Product

Four to five years of fintech UX. Own the product surface that small business owners open every morning.

Experience: 4–5 years Domain: Fintech UX Location: Hybrid Reports to: Engineering Lead

Lending software is hard. Most of it looks it. We do not want that. At Nexo you will own the product surface — corporate cards, expense management, working capital, the dashboards small-business owners actually open every morning, and the bank-side panels their relationship managers use to underwrite them.

You will work alongside the founder, the engineering team, and the 2026 Fellowship cohort. We expect taste, opinions, and a portfolio that shows you have shipped — not just designed. Four to five years of fintech UX is the bar. This is a senior IC role with leadership scope; you will set the design bar for the company, build the design system, and have a small team report into you within twelve months.

What you will do

  • Drive end-to-end product design workstreams across cards, expense, factoring, and dashboards — from problem framing through high-fidelity execution.
  • Contribute meaningfully to the design system — components, patterns, tokens, accessibility standards, and documentation.
  • Leverage AI-native and AI-assisted tools and workflows to accelerate iteration, prototype faster, and explore solution spaces responsibly.
  • Sit close to the founder on product direction; push back when needed.
  • Lead user research with SMB customers and bank partners.
  • Mentor a small design cohort and the Fellowship engineers on craft.

What you bring

  • 4–5 years designing fintech specifically — not generalist B2B.
  • A portfolio showing shipped, end-to-end work — not Dribbble shots.
  • Design system fluency — built or maintained one in production.
  • Comfort designing inside regulatory constraint (RBI / SEBI / IRDAI).
  • Strong written and visual communication — you write before you draw.

What you do not need

  • · A specific previous title — staff, senior, lead, principal. We care about scope, not labels.
  • · A management background. This is a senior IC role with leadership scope; people come later.
  • · Motion or 3D specialism. Pure product design taste is what we are hiring.
The written application

Apply for this role.

Eleven questions. Most should be answered in 100–300 words each. We will read every word and look closely at your portfolio.

Required. Reviewable. If password-protected, include the password in your answer to Q10.

Q01 · Fintech tenure

Lending? Payments? Wealth? Cards? Underwriting tools? B2B vs B2C? Be specific.

Q02 · B2B / SaaS context

We are building a B2B financial OS for SMBs — the constraints, the user, and the pace are different from consumer. We want to know how you have thought about that before.

Q03 · One screen, end-to-end

Problem → research → design choices → ship → outcome. Numbers help (drop-off reduction, conversion lift, time saved). Link a Figma or case study if you have one.

Q04 · A product design problem you solved

Different from Q03 — we are looking for product thinking and ownership beyond a single screen. The problem can be a flow, a mental model, an architectural decision, or a recovery from a shipped mistake.

Q05 · Design system

If yes — link the system or describe the structure (tokens, components, accessibility standards, governance). If you maintained someone else's — describe what you changed and why.

Q06 · Designing under regulation

Tell us about a clause that shaped a screen. Or a moment when compliance and UX disagreed and how you resolved it.

Q07 · Strongest opinion

An opinion most of your peers would push back on. Defend it briefly.

Q08 · Tools and AI-assisted workflow

Research tools, prototyping (Origami / Protopie / code), motion (Rive / After Effects), AI design tools (v0 / Galileo / Cursor / Claude / Magic Patterns / etc.) — what you actually use, what's part of your iteration loop, and what you have stopped using.

Q09 · Working with engineers

Where the handoff lives, how you handle "we can't ship that," how often you write code (or not), what makes a good engineering partner from a designer's side of the table.

Q10 · Why Nexo

Read our materials before answering. What's right, what's not yet right, and where you would push us. (If your portfolio is password-protected, include the password here.)

Q11 · The basics
Optional · Resume / CV

By submitting, you agree that we may store your responses for the purpose of evaluating this application. We will not share them outside Nexo.

Trouble with the form? Email your responses directly to hello@nexo.money.