Software Engineer, Front End

Level: Senior Front-End Software Engineer / Lead Product Engineer with 4+ years of professional experience building production applications with React and TypeScript.

Required skills: TypeScript, React, Vite, Tailwind CSS, complex forms, validation, data-heavy interfaces, Node.js, Koa, gRPC, Postgres, API design, release workflows, and close collaboration with product, design, and backend teams.

The ideal candidate should be familiar with owning web products end to end, developing multi-step onboarding and compliance flows, building dashboards and self-service features, maintaining multiple codebases, and working independently in ambiguous, fast-moving environments; fintech, white-label, Plaid, Persona, or brokerage experience is advantageous.

How would you architect a multi-step brokerage account onboarding flow using React, TypeScript, React Hook Form, and Zod?

I would model each step with a typed schema, compose them into a flow-level validation strategy, and persist progress safely between steps. React Hook Form would manage field state and performance, while Zod would provide shared validation and strongly typed form data.

How would you build a white-label onboarding module that supports multiple fintech partners from one codebase?

I would separate core business logic and reusable components from partner-specific configuration such as branding, copy, feature flags, and API settings. A typed configuration layer combined with theme tokens and build-time or runtime partner selection would reduce duplication while preserving customization.

How would you handle asynchronous data fetching and cache management with SWR in a partner dashboard?

I would use stable, parameterized cache keys and configure appropriate revalidation, optimistic updates, and error handling. After mutations, I would invalidate or update affected keys so positions, statements, account settings, and reporting data remain consistent.

What are the key considerations when integrating Plaid, Persona, or similar identity and compliance services?

I would isolate provider-specific SDK logic behind application-level interfaces, handle loading, cancellation, retries, and failure states, and avoid exposing sensitive data unnecessarily. I would also design for webhook or server-confirmed status rather than trusting only client-side completion events.

How would you design the Node.js Koa layer that communicates with backend services over gRPC?

The Koa layer should translate HTTP requests into typed gRPC calls, normalize errors, enforce authentication and authorization, and validate inputs before invoking services. It should also provide structured logging, request correlation, timeouts, and safe mapping of backend errors to user-facing responses.

How would you collaborate with backend engineers to define an API for a complex business-account flow?

I would agree on explicit request, response, state-transition, and error contracts before implementation, including partial completion and idempotency requirements. I would raise UI concerns early, especially when the API requires excessive round trips or makes validation and recovery difficult.

How would you manage accessibility for reusable components built with Radix UI, React Aria, and Storybook?

I would use the accessibility primitives provided by Radix UI and React Aria, ensure correct labels, keyboard behavior, focus management, and screen-reader announcements, and test realistic interaction states. Storybook would document and exercise states such as errors, disabled controls, loading, and validation feedback.

How would you approach migrating an onboarding flow to a new business-account API and data model?

I would first map the old and new domain models, identify incompatible states, and define an incremental migration plan with backend engineers. Feature flags, contract tests, adapter functions, and targeted UAT would allow the new flow to be validated without destabilizing existing partner experiences.

How would you use LaunchDarkly when releasing a new partner-facing feature?

I would release behind a narrowly scoped flag, targeting internal users or selected partners first and monitoring errors and business metrics. The implementation should include safe defaults, clear ownership of flag removal, and consideration of both enabled and disabled code paths.

What would you include in a reliable release workflow from preview environments through UAT to production?

I would automate type checking, linting, unit and integration tests, build verification, and environment-specific configuration checks before deployment. Preview environments would support product and design review, UAT would validate partner workflows and integrations, and production rollout would use monitoring and progressive feature activation.

Atomic is a fast-growing, mission-driven fintech building infrastructure that expands access to investing and wealth creation. As a Front-End Software Engineer, you’ll own partner-facing web products end to end, including embeddable onboarding, dashboards, complex account flows, self-service tools, and API migrations. The stack includes TypeScript, React, Vite, Tailwind CSS, Node.js, Koa, gRPC, Postgres, React Hook Form, Zod, SWR, Radix UI, and React Aria. This is a fully remote, full-time role for candidates in Canada or LATAM within the Americas time zones; salary is not disclosed, and it’s worth applying for the opportunity to lead impactful products supporting billions in assets under custody.