Senior Payments Engineer
Payments & Reconciliation·Senior
Make payment, refund and reconciliation workflows understandable and dependable for restaurants and their customers.
The job
You will own engineering work where customer experience and financial correctness meet. A payment event may arrive late, a webhook may be repeated and a refund may start in a different system, so clear state modelling and traceability are essential. You will partner with product, operations and other engineers to design robust money-related workflows and support effective investigation. This is a software role.
What you would be doing
- Build and maintain payment-provider integrations for checkout, refunds and connected merchant accounts.
- Design idempotent webhook processing and explicit payment-state transitions.
- Develop reconciliation workflows that identify mismatches without silently changing financial records.
- Model monetary values, fees and rounding consistently across interfaces and storage.
- Create tests for repeated events, partial failures, refunds and delayed confirmations.
- Improve audit trails and internal tools used to investigate payment issues.
- Coordinate payment releases and provider changes with relevant engineering and operational teams.
What we are looking for
- Strong backend engineering experience on payment or other financially sensitive workflows.
- Understanding of idempotency, retries, reconciliation and reliable event processing.
- Confident SQL and data-modelling skills, including transactions and traceability.
- Ability to handle monetary calculations consistently without unsafe floating-point assumptions.
- Experience explaining complex failure modes to technical and non-technical colleagues.
Useful, but not essential
- Hands-on Stripe or Stripe Connect experience.
- Experience with multi-merchant commerce platforms.
- Familiarity with payment-security practices and minimising sensitive data exposure.
Tools you might use
- TypeScript
- Stripe
- Stripe Connect
- PostgreSQL
- Webhooks
- Integration testing
Your first 90 days
- Days 1–30Map payment and refund lifecycles and agree the most valuable correctness or visibility improvement.
- Days 31–60Deliver a scoped improvement with replayable test scenarios and useful diagnostics.
- Days 61–90Release the change, review exception handling and share a practical reconciliation-improvement plan.
The practical bits
- 2 days per week in the London office and 3 days working remotely within the UK.
- 37.5 hours per week, Monday–Friday. Core collaboration hours are agreed with the team.
- Occasional planned team or customer visits; approved expenses are reimbursed.
What we offer
- 30 days of annual leave plus public holidays
- A company pension contribution
- A £1,000 annual learning budget for courses, conferences or professional development
- A company laptop and role-appropriate equipment; engineering roles include a development setup
- Flexible start and finish times, agreed with your team around customer and collaboration needs
- Wellbeing support and regular development conversations with your manager
- Reimbursement of approved business travel and customer-visit expenses
Apply
Four fields. That is the whole application.
No account, no portal, and no covering letter unless you want to write one. A person reads every application and replies either way.
- Introduction, 25 minutesDiscuss your interests, the role, location, working arrangements and compensation expectations.
- Experience and problem-solving, 45 minutesWalk through relevant work and explain the decisions, trade-offs and lessons behind it.
- Practical conversation, 60 minutesModel a payment workflow where a webhook is duplicated and a refund begins before a delayed confirmation is processed.
- Meet the team, 30 minutesMeet someone from another team, see how we work together and ask anything still open.