Skip to content

Proof Pack · One-pager

How I work

Ownership & scope

  • Interlining, an airfare limit-order engine and price alerts — each from schema to live feature, each still running.
  • De-facto owner of the money path since January 2020 — informal, no title, no reports.
  • All five design specs behind the accepted ADRs for a two-airline interlining engine are mine.
  • I integrated four bank payment providers into a provider-agnostic abstraction I did not design.
  • Where a system is not mine I say so — a colleague's response cache, a supplier hub I handed over.

Engineering quality

  • Routine pull-request review on the money path.
  • A written design spec before the code whenever a decision is expensive to reverse.
  • Idempotency and race-condition hardening on money paths.
  • Findings from an external penetration test remediated — the response, not the report.
  • I have no public evidence of automated testing practice, and no claim to make about it.

Delivery

  • I ship against live production traffic; the money path is never idle.
  • Behaviour goes behind runtime parameters, so a change can be enabled without a deploy.
  • Most of what I have built I still run.
  • I re-platform rather than rewrite where the read side can carry it.
  • Pipelines and containers are my record's gap: no CI/CD or Docker evidence to show.

Reliability & incidents

  • I fix incidents on the systems I own. No formal on-call rotation — ownership, not a rota.
  • Bounded retry under a fixed cap; re-inquiry with the bank rather than assuming an errored call failed.
  • Gateway state persisted before the side effect, so a duplicate cannot slip through.
  • Concurrency held by Redis locks keyed on what they protect — the credit, or the account.
  • Serilog structured logging across the money paths, and a daily stuck-refund report to supervisors.

Collaboration & communication

  • English in writing every day: specs, tickets, code review. No certificate.
  • I onboarded one to two junior engineers.
  • I exposed an admin API so the marketing team could run campaigns without a deploy and without me in the loop.
  • Operations tune eligibility on the limit-order engine themselves. I built the surface, not the tickets.
  • When retries exhaust, the customer is told. The system does not go quiet.

Read the case study →   ← Back to the Proof Pack