Thunes operates a global cross-border payments infrastructure and API platform connecting banks, digital wallets and mobile‑money providers to enable interoperable, real‑time transfers across 130+ countries and 80+ currencies.
<p><strong>About the Role</strong></p> <p>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 admin tool, embeddable payment widgets, and publisher-hosted transaction pages — all securely handling real money, real compliance requirements, and real users.</p> <p>This isn't a "build marketing pages" gig. You'll be working with GraphQL APIs backed by Go microservices, writing code that touches invoicing, payouts, KYC verification, and fraud detection. The work matters and the stakes are real.</p> <p><strong>What You'll Work On</strong></p> <ul> <li><strong>Admin Tools</strong> (React, Vite, Chakra UI, Apollo Client): Internal tooling used by operations teams to manage accounts, transactions, and payment methods. Turborepo monorepo with a GraphQL BFF layer.</li> <li><strong>Payment Widgets</strong> (Next.js, React, Tailwind CSS, Server Components): Embeddable checkout, payout, and KYC flows where every millisecond of load time impacts conversion. Active rewrite with a performance-first architecture.</li> <li><strong>Publisher-Hosted Pages</strong> (Next.js, Chakra UI, SSR): Multi-tenant, themeable transaction pages served under publisher-branded domains with CNAME routing and per-publisher customization.</li> </ul> <p><strong>Day-to-Day</strong></p> <ul> <li>Ship features and fixes across multiple TypeScript/React codebases.</li> <li>Write and maintain unit tests (Vitest + React Testing Library) and help with Playwright e2e tests (Python/pytest).</li> <li>Work with a GraphQL API layer that translates between the frontend and Go microservices (accounts, payments, invoicing, wallets).</li> <li>Run the full local stack via Docker Compose (makeworld) with hot-reload - no waiting for builds.</li> <li>Maintain or improve test coverage.</li> <li>Collaborate on a small team where you'll have real ownership and influence over frontend architecture.</li> </ul> <p><strong>You Should Have</strong></p> <ul> <li><strong>React</strong> applications - you've shipped features that real users depend on.</li> <li><strong>TypeScript proficiency</strong>.</li> <li><strong>Testing discipline</strong> - experience with Vitest or Jest and React Testing Library or similar.</li> <li><strong>Component library experience</strong> - you've worked with Chakra UI, MUI, or similar design systems and can extend them without fighting them.</li> <li><strong>Linux shell proficiency</strong> - comfort navigating the file system, using common utilities, and basic scripting.</li> </ul> <p><strong>Bonus Points</strong></p> <ul> <li>Experience with payment/fintech UIs - checkout flows, KYC, compliance screens.</li> <li>Familiarity with Playwright or similar e2e frameworks.</li> <li>Docker comfort - you don't panic when the local stack is containerized.</li> <li>Python literacy. Enough to read and write Playwright test scripts.</li> <li>Go literacy. Enough to read the backend services and understand the APIs you will be calling.</li> <li>GraphQL experience - you've worked with Apollo Client or a similar GraphQL client and understand queries, mutations, caching, and schema design.</li> <li>Experience building UIs for role-based access control (RBAC) or complex permission systems.</li> <li>You've worked on multi-tenant/white-label products with theming systems.</li> <li>Experience working in monorepos (Turborepo, Nx, or similar).</li> </ul> <p><strong>What We're NOT Looking For</strong></p> <ul> <li>Someone who needs a design system handed to them pixel-perfect - you'll make pragmatic UI decisions in lieu of hi fidelity mockups.</li> <li>A "framework tourist" chasing the latest meta-framework - we need someone who ships, not someone who rewrites.</li> <li>Someone uncomfortable with legacy code - parts of the codebase are being actively migrated and you'll need to work in both old and new patterns gracefully.</li> </ul> <p><strong>Why This Role</strong></p> <ul> <li><strong>Small team, big impact</strong> - you won't be pixel-pushing in a feature factory. You'll shape frontend architecture across multiple products.</li> <li><strong>Real domain complexity</strong> - payments, compliance, multi-currency, fraud detection. The problems are genuinely interesting.</li> <li><strong>Modern stack, active migration</strong> - you get to help move things forward rather than maintain a frozen codebase.</li> <li><strong>Strong engineering culture</strong> - enforced coverage thresholds, pre-commit hooks, CI gates, deployment on merge. The team cares about quality and process aerodynamics.</li> </ul>