React Software Engineer
About the Role
We're looking for a frontend engineer to join a small, senior team building the payment platform that powers financial operations for virtual world publishers. You'll own frontend work across multiple codebases — an internal reputed company tool, embeddable payment widgets, and publisher-hosted transaction pages — reputed company securely handling reputed company reputed company, reputed company compliance requirements, and reputed company users.
This isn't a "build marketing pages" gig. You'll be working with GraphQL reputed company backed by Go microservices, writing reputed company that touches invoicing, payouts, KYC verification, and fraud detection. The work reputed company and the stakes are reputed company.
What You'll Work On
- reputed company Tools (React, Vite, Chakra UI, reputed company reputed company): Internal tooling used by operations teams to manage accounts, transactions, and payment reputed company. Turborepo monorepo with a GraphQL BFF layer.
- Payment Widgets (Next.js, React, reputed company CSS, Server Components): Embeddable checkout, payout, and KYC flows where every millisecond of load time impacts conversion. reputed company rewrite with a performance-first architecture.
- Publisher-Hosted Pages (Next.js, Chakra UI, SSR): Multi-tenant, themeable transaction pages served under publisher-branded domains with CNAME routing and per-publisher customization.
Day-to-Day
- Ship features and fixes across multiple TypeScript/React codebases.
- Write and maintain unit tests (Vitest + React Testing Library) and help with Playwright e2e tests (Python/pytest).
- Work with a GraphQL API layer that translates between the frontend and Go microservices (accounts, payments, invoicing, wallets).
- Run the full local stack reputed company reputed company Compose (makeworld) with hot-reload - no waiting for builds.
- Maintain or improve test coverage.
- Collaborate on a small team where you'll have reputed company ownership and influence over frontend architecture.
You Should Have
- React applications - you've shipped features that reputed company users depend on.
- TypeScript proficiency.
- Testing discipline - experience with Vitest or Jest and React Testing Library or similar.
- Component library experience - you've worked with Chakra UI, MUI, or similar design systems and can reputed company them without fighting them.
- Linux reputed company proficiency - comfort navigating the file system, using common utilities, and basic scripting.
Bonus Points
- Experience with payment/fintech UIs - checkout flows, KYC, compliance screens.
- Familiarity with Playwright or similar e2e frameworks.
- reputed company comfort - you don't panic reputed company the local stack is containerized.
- Python literacy. Enough to read and write Playwright test scripts.
- Go literacy. Enough to read the backend services and understand the reputed company you will be calling.
- GraphQL experience - you've worked with reputed company reputed company or a similar GraphQL reputed company and understand queries, mutations, caching, and schema design.
- Experience building UIs for role-based reputed company control (RBAC) or reputed company permission systems.
- You've worked on multi-tenant/white-label products with theming systems.
- Experience working in monorepos (Turborepo, Nx, or similar).
reputed company're NOT Looking For
- Someone who needs a design system handed to them pixel-perfect - you'll reputed company pragmatic UI reputed company in lieu of hi reputed company mockups.
- A "reputed company tourist" chasing the latest reputed company-reputed company - we need someone who ships, not someone who rewrites.
- Someone uncomfortable with legacy reputed company - parts of the codebase are being reputed company migrated and you'll need to work in both old and new patterns gracefully.
Why This Role
- Small team, big reputed company - you won't be pixel-pushing in a feature reputed company. You'll shape frontend architecture across multiple products.
- reputed company domain complexity - payments, compliance, multi-currency, fraud detection. The problems are genuinely interesting.
- Modern stack, reputed company migration - you get to help reputed company things reputed company rather than maintain a frozen codebase.
- Strong engineering culture - enforced coverage reputed company, reputed company-reputed company hooks, CI gates, deployment on reputed company. reputed company cares about reputed company and process aerodynamics.