Frontend Development at Dodo payments

Role Overview

We are looking for a Frontend Engineer to build the interfaces thousands of businesses use to get paid: dashboard, checkout, onboarding, billing, and analytics. This is not a role that converts Figma screens into React. You will look at a flow, question it, improve it, and ship the better version.

About Dodo payments

Dodo Payments is the Monetisation Engine for AI-native products. We're a Merchant of Record + Billing & Monetization platform that helps SaaS, AI, and digital businesses accept payments globally, automate billing (subscriptions, usage-based, one-time), and stay fully compliant with taxes and regulations in 220+ countries.

Key Responsibilities

Product Ownership: Own features from problem to production. Understand the problem, prototype the experience, build it, talk to the API, handle the weird states, ship it, then watch how people use it and make it better.
Core Surfaces: Build and improve the merchant dashboard, checkout, onboarding, subscriptions and usage billing, customer management, revenue analytics, and payment and payout flows.
Interface Craft: Own the last 10% of UI quality. Loading, error, and empty states are part of the product, not cleanup afterwards.
0 to 1 Product: Take new products from a rough idea to something customers use, often before there is a full spec or design.
Systems and Reuse: Build primitives and shared components where they pay off, and know when to just ship the thing instead.

Requirements & Eligibility

Experience: 2+ years building production web applications, with strong React and TypeScript.
Shipping Record: You have shipped real products used by real customers, not projects that ended at localhost.
UI Quality: Demonstrable care for craft. You notice the modal that is 30px too wide and the form that technically works but feels exhausting.
Product Judgment: You can build from a rough idea without waiting for a 20-page spec, and you push back when something is not good enough.
AI Fluency: You use AI heavily and still know what good code looks like.