Production E-Commerce and Savings Platform
Client work · Sole backend engineer — the whole server side of a live platform, with no engineering team behind it: design, implementation, integrations, migrations, and the production consequences of all four.
Sole backend engineer for a production e-commerce and savings platform at a national performance-marketing company.
Years of production ownership of the entire server side of a consumer e-commerce and savings platform: high-volume transaction processing, integrations with partner and aggregator feeds, the accounting that turns qualifying activity into member savings, and the data pipelines behind the reporting on all of it.
Problem
A savings platform pays its users back, so every qualifying transaction has to be captured, attributed, and reconciled correctly across a long tail of external partners whose feeds, formats, and terms change without notice. A mistake there is not cosmetic — it is money a member expected and did not receive, usually discovered long after the fact.
Approach
Treated correctness and continuity as the product. Transaction processing was made idempotent, so a replayed or duplicated upstream event could not double-credit an account. Partner and aggregator integrations sat behind adapters, so an upstream format or contract change was a contained edit rather than an outage. Savings accounting kept an auditable trail from raw activity to the balance a member sees, so a disputed number could be reconstructed instead of argued about. Schema and behaviour changes shipped against a live system in backward-compatible steps, so migrations never needed a maintenance window.
Role
Sole backend engineer — the whole server side of a live platform, with no engineering team behind it: design, implementation, integrations, migrations, and the production consequences of all four.
Stack
- High-volume transaction processing
- Partner and aggregator integrations
- Savings and reward accounting
- Data pipelines
- Zero-downtime migrations
- Audit trails
Outcome
- Carried the entire backend of a live consumer platform for years as its only backend engineer
- Transaction processing stayed correct through duplicated and replayed upstream events
- Partner and aggregator integrations absorbed upstream format and contract changes without member-visible breakage
- Balances were reconcilable end to end, from raw partner activity to the number a member sees
- Schema and behaviour changes shipped against a live system without maintenance windows
Want work like this shipped for you?
Every project starts with a short discovery conversation — no obligation, no boilerplate pitch. Tell me what you're building.