The engineering behind the product
Payments that change state across systems. Monitoring that needs to become reviewable work. Driver locations that stop updating. Explore the engineering questions behind the products we build and run.
Featured · Payments engineering
A request can time out while a payment continues elsewhere. A provider can send the same update twice. The engineering problem is keeping a clear account of the transaction while different systems report what they know.
Read the engineering guidePayments engineering
A payments product continues to change after the first app reaches the store. The mobile experience is connected to transfers, external services and the tools people use to run the operation.
5 min readEngineering notes
Comparing two names can help a system find a possible connection. It does not establish, by itself, that two records refer to the same person.
4 min readPayments engineering
A request can time out while a payment continues elsewhere. A provider can send the same update twice. The engineering problem is keeping a clear account of the transaction while different systems report what they know.
5 min readPayments engineering
A monitoring rule can flag a transaction. A useful system also needs to explain what triggered, give a reviewer the relevant context and record what happens next.
4 min readEngineering operations
A service can accept a message without proving that a person saw it. Notifications are an important part of the experience, but the product still needs an authoritative place to show what happened.
5 min readMobility
A moving pin makes a ride-hailing app easy to recognise. The harder product question is whether passengers, drivers and the operation understand the same journey as it changes.
4 min readMobility engineering
A map can keep showing a driver’s last position after updates stop. The important question is whether the product knows how recent that position is and what the passenger should understand from it.
5 min readSoftware takeover
When software is difficult to launch or change, a fresh start can sound reassuring. The useful first step is to understand which parts are worth keeping and what the next version actually needs.
5 min readRetail operations
A phone retailer works with individual devices as well as stock quantities. Software needs to make that distinction useful to the people recording repairs and understanding what each shop holds.
5 min readDocument workflows
Getting text out of a PDF is one step. A useful team workflow also needs to help people find the right document and understand whether the extracted information is suitable for their task.
5 min readExplore payments, mobility, document tools and business software in our portfolio.
Explore our work