Optimized Performance → Cut p99 280ms: Backend Bullets With Proof
Free · No signup · Recruiter-reviewed
Replaced two filler nouns ('performance', 'overall system efficiency') with the actual query path, the actual percentile, and the actual remediation. Senior engineers always speak in p99 / p95, never 'overall efficiency'.
Cut checkout API p99 from 420ms to 140ms by rewriting the inventory join and adding a covering index on order_items.
What changed and why
- p99 > p95 > average. Recruiters and staff engineers know average masks the tail · quoting p99 signals seniority.
- Name the endpoint (checkout API), the table (order_items), and the technique (covering index). Three concrete nouns beat any adverb.
- If you remember the before-and-after numbers, you did the work. If you only have 'improved performance', you watched someone else do it.
- Database fixes that survive are usually index changes or denormalisation. Both are defensible in a system-design round.
Recruiter perspective
“p99 280ms cut, named the join, named the index. This is a real staff-eng artifact.”
Related rewrites
Utilized → Shipped: Frontend Bullets That Survive 6-Second Scans
Replaced 'Utilized' (the most over-used engineering AI verb of 2026) with 'Shipped', named the specific surface owned (search + filter on the candidate dashboard), and added the only number a frontend recruiter cares about: interaction latency.
Managed Incidents → Cut MTTR 47%: SRE Bullets Without the Buzzwords
'Managed incidents' is the SRE equivalent of 'utilized React'. It could describe any job. The rewrite names the rotation size, the specific runbook rewritten, and the routing-rule count, all defensible in a 5-minute behavioural round.
Built Pipelines → Cut Snowflake £62k/Yr: Data Eng Bullets
Replaced 'scalable pipelines' (a phrase that means nothing in 2026) with the warehouse name, the £-saving, the pipeline count, the specific dbt patterns, and the warehouse-sizing detail. Data eng is graded on cost + reliability · quote both.