Senior Frontend Engineer

This role is suitable for a Senior Frontend Engineer with 5+ years of production web development experience, including at least 3 years with React and deep TypeScript expertise. Required skills include scalable component libraries or design systems, REST and WebSocket API integration, frontend architecture, testing, performance optimization, and clear async communication. The candidate should be experienced in building dashboards, onboarding flows, customer-facing interfaces, and mentoring engineers through code reviews, pair programming, and documentation.

How would you structure a React and TypeScript application for Axra’s dashboard, onboarding flows, and customer-facing pages?

I would organize the application around domain-oriented feature modules, shared UI components, and clearly defined API boundaries. TypeScript types would be generated or centralized from API contracts where possible, with strict compiler settings and predictable data-fetching patterns.

How would you design a scalable state management strategy for a financial web application?

I would separate server state from client state: use a query library or equivalent for REST data, caching, retries, and invalidation, while keeping local UI state close to components. Shared client state should be limited to genuinely cross-cutting concerns such as authentication, user preferences, and multi-step onboarding context.

How would you integrate REST and WebSocket APIs in React?

REST would handle initial data loading and mutations, while WebSockets would provide live updates such as transfer status or balance changes. I would manage connection lifecycle, authentication, reconnection, message validation, and cache updates centrally, ensuring stale or duplicated events cannot corrupt displayed financial data.

What principles would you use to build and maintain Axra’s design system?

I would establish accessible, composable primitives with consistent tokens for spacing, typography, color, and interaction states. Components should have documented APIs, visual and interaction tests, clear ownership, and versioning practices that allow the product to evolve without introducing inconsistent patterns.

How would you ensure the design system remains accessible?

I would follow semantic HTML and WCAG practices, including keyboard navigation, focus management, sufficient contrast, screen-reader labels, and appropriate ARIA usage only when necessary. Automated checks would be combined with manual testing using keyboard navigation and assistive technologies.

Which performance metrics would you prioritize, and how would you improve them?

I would monitor Core Web Vitals, especially LCP, INP, and CLS, alongside bundle size and real-user performance data. Improvements could include route-level code splitting, lazy loading, image optimization, reducing unnecessary renders, prefetching likely navigation paths, and minimizing JavaScript sent to the initial page.

How would you make TypeScript provide real safety rather than just satisfy the compiler?

I would use strict mode, discriminated unions, branded types for values such as currency or transaction identifiers, and runtime validation at API boundaries. Types should model valid domain states and make invalid operations difficult, while avoiding excessive type complexity that harms maintainability.

How would you test a critical money-transfer onboarding flow?

I would combine unit tests for validation and domain logic, component tests for interactive states, contract tests for API assumptions, and end-to-end tests covering successful, failed, interrupted, and retry scenarios. Tests should also verify accessibility, loading states, error recovery, and protection against duplicate submissions.

How would you handle real-time financial data when WebSocket events arrive out of order?

Each event should include a sequence number, timestamp, or version that can be compared against the client’s current state. The client should ignore stale events, reconcile inconsistencies through a REST refresh, and display a clear status rather than presenting potentially misleading balances or transfer states.

How do you approach mentoring and maintaining quality in a remote-first frontend team?

I would use focused code reviews, pairing sessions, lightweight architectural documents, and examples within the codebase to make standards explicit. Written decisions, reusable checklists, and constructive feedback help the team move consistently across time zones while encouraging junior engineers to develop ownership.

Axra is a fast-growing cross-border money platform helping the African diaspora send, spend, and save across GBP, EUR, and USD. As a Senior Frontend Engineer, you’ll build the Axra dashboard, onboarding flows, customer-facing interfaces, and scalable design system using React and TypeScript, while integrating REST and WebSocket APIs and mentoring engineers. This is a full-time, fully remote worldwide role offering £75,000–£95,000, equity, flexible hours, unlimited PTO, health cover, and a learning budget. Apply to shape a trusted financial product serving millions in an underserved market while having meaningful ownership over its frontend architecture and craft.