Product Checkout Real-time dashboard AI Workforce VCI verified identity Six payment states
Pricing
Developers Documentation API reference Webhooks SDKs Full docsComing soon Updates Changelog SandboxComing soon Migration toolComing soon
Compare Security
Company Our story Press Brand kit Updates Changelog
Live Try the demoComing soon Sign inComing soon Talk to us Get started

Careers

Careers at Fluxa.

Not hiring yet. Fluxa is a lean UK team building a payment processor, ahead of launch and focused on shipping the founding cohort. When paid roles open, this page will show the team, the work, the expectations and the process in full. Speculative applications are welcome and read by the founders directly.

Lean by design.

Fluxa runs as a deliberately lean team. Engineering, product, design and brand sit on one side of the company. Compliance, operations, KYB and merchant correspondence sit on the other. Both sides are run end to end by their owners, and both sides ship.

Five production AI agents handle the supporting work that would otherwise queue for a human: merchant support 24/7, onboarding assistance, platform health monitoring, revenue integrity checks, and regulatory coverage. The agents are part of the product, not staff. They reduce the support headcount Fluxa needs at each stage of growth, but they do not replace a hire when the role calls for judgement, ownership, or a difficult conversation with a merchant.

The team will grow when the constraint stops being build capacity and starts being merchant-facing capacity. That moment will be visible in the queue: support replies slowing down, onboarding cohorts backing up, founding-cohort merchants asking for something the current team cannot ship fast enough. When it arrives, the next role will be listed in full on this page.

How working at Fluxa will feel.

Remote-friendly, UK-based.

The team is in the UK and the time zone is London. You can work from anywhere with reliable internet, provided you have UK right-to-work and reasonable overlap with UK working hours. No mandatory in-person days, no return-to-office mandate, no surprise relocations.

Direct with Fluxa.

Every hire works directly with a founder on the actual problem. No project managers, no skip levels, no deck-driven planning cadence. The org chart stays flat for as long as it can; decisions are made on the quality of the idea, not the seniority of the person proposing it.

Written-first, async by default.

Most decisions happen in writing on Linear, GitHub, or a short doc. Meetings are reserved for things genuinely better as a conversation. Outcomes are measured by what shipped and by merchant feedback, not by hours logged or seat time.

No theatre.

No status meetings for the sake of it, no slide decks for what could be a paragraph, no leadership offsites. No monitoring software, no time-tracking, no performance review process designed to fill a calendar. Time in meetings has to earn its rent against time building or supporting merchants.

When the first hire happens.

The first paid hire is planned once there is reliable monthly revenue from live merchants. Realistic timing: Q3 to Q4 2026, contingent on cohort onboarding speed and payments partner sign-off. The date will be posted here when it firms up.

The first role will be one of two shapes. The order depends on which constraint becomes tighter first: build capacity or merchant-facing capacity. As of May 2026, both are still manageable with the current two-person team and the AI agents.

Compensation will be benchmarked competitively against UK payments roles, weighted to equity in Fluxa Ltd for the early team. Standard UK statutory benefits (pension, holiday, sick leave) plus the things that matter: decent equipment, no monitoring software, no time-tracking, no surprise on-call. We do not work with recruitment agencies; direct applications only.

What Fluxa hires for.

Fluxa hires people the team is excited to work with. The bar is set high because the company is small, the work is regulated, and every hire shapes what Fluxa becomes. Every applicant is assessed against the same six baseline competencies; senior or specialist roles will list additional requirements in the job description when posted. The evidence that satisfies each competency differs by discipline.

  1. Production delivery

    Evidence of having built and shipped software, processes, or operational tooling that real users or merchants have relied on. Assessment is on the systems built and the decisions made building them, not on the languages or frameworks listed on a CV. Prior payments experience is welcome; the willingness and capacity to learn the domain is essential.

  2. Security and regulatory awareness

    A baseline understanding of how regulated systems work and why. For engineering: PCI-DSS scope, the OWASP Top 10, tokenisation patterns, and the principle that handling card data is a privilege with rules attached. For operations: the UK regulatory landscape, including the Payment Services Regulations 2017, FCA expectations of the payments partner, and the KYB and sanctions obligations that follow.

  3. Domain readiness

    A genuine interest in the payments domain and the discipline to learn it. Technical roles will be expected to develop fluency in 3DS2, scheme rules, chargeback workflows, settlement timing, and reconciliation. Operations roles will be expected to develop fluency in KYB, sanctions screening, dispute evidence, and FCA reporting frameworks. Neither requires prior certification; both require curiosity and structured study.

  4. Clear written communication

    Most decisions at Fluxa happen in writing: on tickets, in pull requests, on internal documents, and in correspondence with merchants and regulated partners. The ability to write clear, structured prose that survives forwarding to a non-technical reader is a core working tool, not an optional polish. Candidates are assessed on the quality of their written reasoning alongside their verbal explanation.

  5. Independent judgement

    A lean team relies on every member taking work end to end, escalating risk early, and making sensible decisions when the path forward is ambiguous. Senior pedigree at a large company is not, on its own, evidence of this. Comfort with ambiguity, ownership of outcomes, and the judgement to know when to pause and ask are the qualities that distinguish an effective hire at the founding-team stage.

  6. Reliability, punctuality and team fit

    Technical skill is necessary; on its own it is not sufficient. Fluxa hires people the rest of the team wants to work alongside, measured against practical and observable standards: meeting commitments on the timeline agreed, arriving on time to calls and reviews, communicating early when something will slip, and treating colleagues, partners and merchants with the same care regardless of who is in the room. The team is small enough that one unreliable hire changes the working day of every other person on it.

Want to work at Fluxa one day?

Speculative applications are welcome and read by the founders directly. One paragraph on what you would want to build, one link to something you have shipped, a CV or LinkedIn. No cover letter, no questionnaire, no application form. If you sound like a good fit, you will hear back within one working week.