Senior Product Designer - Embed

Kota is making insurance and retirement benefits more accessible through innovative software solutions. They are seeking a Senior Product Designer to work on their embedded insurance product, focusing on creating exceptional user experiences and collaborating with stakeholders to ensure design quality in a dynamic environment.

Responsibilities:

• Think as part of the job (not just ship)
• Design a surface where a sort-order decision moves real money for tens of thousands of people
• Co-design the data model with the UI
• Manage 6–10 stakeholders in major decisions
• Turn constraints into design surfaces rather than obstacles
• Create prototypes that serve as specifications
• Own the design quality in a rapidly changing environment
• Work inside a complex product, ideally B2B and API-driven
• Ship products with invisible complexity
• Conduct research methods at sprint cadence
• Perform 5-user tests, rapid prototyping, and log analysis
• Facilitate internal design reviews
• Promote outcomes-over-outputs discipline
• Lock down problem/assumptions/success criteria before agreeing to a solution
• Apply systems thinking to promote patterns to primitives
• Influence UX work and get stakeholders to attend usability sessions
• Build and facilitate design ceremonies
• Apply craft fundamentals such as type, spacing, rhythm, and hierarchy
• Close the gap between design and engineering by treating prototypes as specs

Requirements:

• A designer who has worked inside a complex product (ideally B2B, double ideally it was API-driven), understands why the data model constrains the interface, and finds that constraint interesting rather than annoying
• You've shipped something with invisible complexity. Not a marketing site, not a dashboard with toggles. You succeeded, and you can explain how you thought through it
• Research methods at sprint cadence. 5-user tests, rapid Figma Make/Cursor/Paper prototyping, Datadog/Mixpanel log analysis, facilitating internal design reviews. You also know when to skip research and ship. The mantra: 'rough data is better than no data; you can't remove uncertainty - triage it'
• Outcomes-over-outputs discipline. Lock down problem / assumptions / success criteria before agreeing to a solution
• Systems thinking - promoting patterns to primitives. Recurring interaction surfaces become design-system components
• UX influence work. Getting devs/stakeholders to attend usability sessions. Building and facilitating ceremonies (standups, retros, backlog grooming) so design becomes shared team context, not an isolated artifact
• Craft fundamentals. Type, spacing, rhythm, hierarchy. The basics, worked at 400% zoom - quality and speed aren't opposites
• Builder craft. Cursor / Claude Code comfort. Treating prototypes as spec means producing working prototypes is the design output. Closing the gap between design and engineering rather than widening it
• Embedded financial products
• Fintech, financial services, insurance, or benefits platforms
• Developer product experiences, understanding of how to design for technical users and embedded/integration-heavy products