About The Role

You’ll be our lead front-end engineer and operate like a founding product engineer: owning our partner-facing web products end to end, shaping what we build as much as how, and working directly with product, design, and backend engineers. This role is for a self-starter who wants real ownership and is happy to step outside a narrow job description when the team needs it.

What You’d Work On

• Partner-facing web products, owning them end to end from design handoff through to release.
• The embeddable onboarding module. This is the white-label, co-branded UI that fintech partners embed so their customers can open brokerage accounts, both individual and business. It covers multi-step application flows for business accounts, adding and verifying owners and signers, and identity and compliance checks. One codebase produces several apps and partner-specific builds.
• The partner dashboard. Partners use it to view and manage their customers’ accounts: positions, statements, account reporting, joint and advisory account details, and settings such as notification contacts.
• Self-service features that cut down on manual operations work, for example, letting partners edit business details or add participants to existing accounts without filing a support ticket.
• Moving to a new version of our business-account API. That means rebuilding flows on a new data model in step with backend engineers.
• Keeping two codebases healthy, including bringing the onboarding module’s dependencies up to date with the dashboard’s.
• 
  

Our frontend stack

• Core: TypeScript, React, Vite, Tailwind CSS
• Components: Radix UI and React Aria, with Storybook for component development
• Forms and data: React Hook Form with Zod, SWR
• Server-side: Node.js (Koa) talking to our services over gRPC
• Integrations: Plaid, Persona, Auth0, LaunchDarkly
• 
  

What You Will Excel At

• 4+ years building production web applications with React and TypeScript.
• Building complex, multi-step forms and data-heavy screens, with careful validation, edge cases, and error states.
• Working in the Node.js server layer behind our web apps (Koa, gRPC, Postgres), not just the browser.
• Agreeing on API contracts with backend engineers, and pushing back when an API makes the UI hard to build.
• Working directly with design and product, turning Figma designs and product tickets into shipped features.
• Owning the release process: our workflow runs from preview environments through UAT to production.