Build the infrastructure that payroll forgot
tPay365 is building the orchestration layer between payroll and the bank account. We're looking for engineers and designers who want to solve hard problems in financial infrastructure — not optimise ad click-through rates.
Payroll is a 1968 batch file. We're rewriting it.
BACS — the system that moves salaries in the UK — was designed in 1968. It processes payments in overnight batches. It treats every pound identically. It has no concept of obligations, timing, or intent.
The result: 12 million UK employees live payday to payday. Not because they earn too little — because the infrastructure delivers their salary as a dumb lump sum with no structure. Rent, bills, debt, and spending money arrive in the same pool. The ‘Liquidity Illusion’ makes people feel wealthy on the 27th and broke by the 10th.
tPay365 fixes this at the infrastructure level. We intercept salary at the payroll layer, decompose it into obligation vaults, and release only the genuinely safe-to-spend remainder. We don't ask people to budget better. We make the system handle money better.
This is not a budgeting app. This is not a neobank. This is deep-tier financial plumbing — the layer that should have existed between employer and employee for the last 50 years.
Problems worth solving
The Clean Paycheck Engine
Decompose a gross salary into statutory deductions, obligation vaults, buffers, and safe-to-spend — with Decimal precision, deterministic output, and sub-200ms execution. Every penny must be accounted for. Every calculation must be reproducible.
BACS Standard 18 Parsing
Parse a fixed-width file format from 1968 that’s still used by every UK payroll system. Handle VOL1 headers, variable record lengths, modulus check validation, and the edge cases that 50 years of legacy systems have accumulated.
Split-Key Security Architecture
Build and maintain the two-server PII isolation model. Server A handles business logic with HMAC hashes. Server B stores AES-256 encrypted PII. They communicate over mTLS. Neither server alone can reconstruct a user identity.
Vault Orchestration & Yield
Design the ledger system that ring-fences funds for rent, bills, and debt — then accrues synthetic yield on vaulted balances at Decimal(6) internal precision. Every vault operation must be atomic, auditable, and reversible.
HRIS Integration Layer
Build adapters for Workday, ADP, Xero, and Sage that normalise payroll events into a canonical internal model. Handle three integration modes: file ingestion, pre-payroll API, and continuous webhook sync.
The Employee Experience
Design an interface that makes financial infrastructure feel simple. The Clean Paycheck dashboard, vault visualisations, yield accrual displays, and the payslip redesign. Every screen must explain the math — not hide it.
What we build with
BACKEND
FRONTEND
INFRASTRUCTURE
PRINCIPLES
Operating principles
Specification before code
Every engine, every integration, every feature begins with a written specification. The spec defines inputs, outputs, invariants, and edge cases. Code implements the spec. This is how we build systems that are auditable, testable, and explainable.
Small team, full ownership
You own your domain end-to-end — from spec to deployment to monitoring. No tickets thrown over a wall. No PRDs from people who don’t understand the system. You write the spec, you write the code, you watch it run.
Substance over performance
We don’t do standups for the sake of standups. We don’t measure productivity by commits. We care about: does the engine work? Is it tested? Is it documented? Is the output correct to the penny? Everything else is noise.
0 OPEN ROLES
No open roles right now. Check back soon or email careers@tpay365.com.
Logistics
Location
London, United Kingdom. Remote-friendly for engineering roles within UK time zones (GMT/BST ±1 hour).
Stage
Pre-launch. Pre-funding. This is a founding-stage opportunity with early equity and direct influence on architecture.
Compensation
Competitive for stage. We’ll be transparent about salary bands when roles are posted. Early team members receive meaningful equity.