The engineer who undersold a migration
Backend engineer, 8 yearsSenior roles
The challenge
A CV that listed duties (“responsible for”, “worked on”) and buried the one project that mattered: a payments migration with no downtime.
The approach
Discovering her value surfaced a clear identity: the engineer who makes risky systems boring. She then rebuilt every line of her CV around outcomes, in US conventions.
Left with
- A two-page CV led by outcomes
- A LinkedIn headline she could say out loud
- Stories for the six likeliest questions
Before: Responsible for maintaining the payment service and fixing bugs.
Cut failed payments by a third by rebuilding retry logic in a nine-year-old service, with zero downtime.1
Before: Worked on the migration of the payments platform to the cloud.
Planned and led the cut-over of two million daily payments to AWS, with no downtime and no rollback.2
Before: Passionate backend developer and team player.
The engineer who makes risky systems boring: eight years of payments, migrations and the incidents that never happened.3