Frontend Engineer

This role is suitable for a Senior Frontend Engineer with strong product design judgment and experience independently taking fintech or data-intensive features from concept to production.

Required skills include React, TypeScript, shadcn/ui, Radix primitives, Tailwind CSS, design-system architecture, component composition, theming, documentation, and a portfolio demonstrating products built end-to-end.

The candidate should be comfortable defining interaction models, designing and modernizing dashboards and checkout flows, building reusable production components, integrating complex backend data, and making architectural decisions in an ambiguous, fast-moving environment.

How would you structure a reusable design system using shadcn/ui, Radix primitives, Tailwind CSS, and React with TypeScript?

I would use Radix for accessible behavior, shadcn/ui as composable source code, and Tailwind design tokens for consistent styling. Components would expose typed variants and slots, while shared patterns, usage guidance, and visual examples would be documented for adoption across the product.

Why is shadcn/ui’s composition model useful for a growing fintech product?

Unlike a closed component package, shadcn/ui places the component code in the application, giving the team control over behavior, styling, and accessibility adaptations. This makes it easier to evolve components for specialized payment states without fighting library abstractions.

How would you design tokens and theming for a trustworthy, data-dense payments interface?

I would define semantic tokens for surfaces, text, borders, status states, focus rings, spacing, typography, and elevation rather than using raw colors throughout the codebase. Themes should support consistent light and dark modes while preserving accessible contrast and clear distinctions between success, warning, risk, and failure states.

How would you model complex payment, fraud, and settlement states in a React UI?

I would define explicit domain states and map them to predictable visual representations, including labels, descriptions, actions, and recovery paths. The UI should distinguish transient processing from confirmed, failed, reversed, or review-required states and avoid implying finality before the backend confirms it.

How would you build accessible components with Radix primitives?

I would use Radix primitives for keyboard interaction, focus management, ARIA behavior, and common patterns such as dialogs, menus, popovers, and tabs. I would still validate the composed component with keyboard testing, screen readers, automated checks, and real usage scenarios.

How would you architect component composition and variants in TypeScript?

I would keep primitives focused and composable, then build domain components from them rather than creating large components with many conditional branches. TypeScript discriminated unions and typed variant utilities can enforce valid combinations such as loading, error, disabled, and risk-related states.

How would you prevent a design system from becoming difficult to maintain?

I would establish contribution conventions, semantic naming, ownership, visual regression coverage, and documentation from the beginning. Changes should be reviewed for API stability, accessibility, responsive behavior, and whether a new component or variant is genuinely necessary.

How would you optimize a Next.js and React dashboard that displays high-volume financial data?

I would minimize unnecessary client-side state, use server rendering or data fetching where appropriate, and keep component boundaries aligned with data dependencies. For large tables, I would use pagination or virtualization, memoize expensive transformations, and measure performance with profiling and production telemetry.

How would you design a merchant onboarding flow for clarity and conversion?

I would break the process into clearly communicated steps, show progress and prerequisites, preserve entered data, and provide specific validation messages near the affected fields. For compliance or risk checks, the interface should explain why information is required without exposing sensitive internal decision logic.

How would you approach a feature when requirements are ambiguous and no detailed design specification exists?

I would clarify the user goal, constraints, important edge cases, and success criteria with the CTO and backend engineers, then produce a lightweight interaction model or prototype. I would validate the approach quickly with realistic data, ship a coherent first version, and iterate based on usage and feedback.

Coinflow is a rapidly growing fintech building global payment infrastructure with stablecoins, AI-driven fraud prevention, instant settlement, and unified payouts. As a Frontend Engineer, you’ll design and ship polished, end-to-end product experiences while building the company’s design system and modernizing onboarding, dashboards, and checkout flows. The stack includes React, TypeScript, shadcn/ui, Radix, Tailwind CSS, with bonus exposure to Next.js, React Native, or animation libraries; this is a full-time, on-site role in Chicago. Compensation is $150,000–$180,000 plus equity and benefits, making it an exciting opportunity to become Coinflow’s first dedicated frontend hire and shape how money moves worldwide.