Resume Review

Every bullet opens with a verb and ends with a measurable outcome ('Reduced p95 latency from 280ms to 95ms across 12M daily requests').

Bullets describe responsibilities ('Responsible for improving API performance') with no number, no baseline, no outcome.

Each role shows two to five bullets, ordered by magnitude of impact, each under twenty-five words.

One massive paragraph per role, or ten near-identical bullets that restate the job description.

Named technologies are specific ('Postgres 15 with logical replication', 'Kafka with idempotent producer, EOS semantics') and tied to the impact.

Generic stack dump at the top with no roles showing which tech actually drove which outcome.

Concrete magnitudes: MB/s, requests per second, users, revenue, teams coordinated, incidents resolved.

Vague scale words: 'massive', 'large', 'significant', 'high-performance'.

At least one bullet per role mentions a specific partner function (product, design, DS, ops) and the concrete artifact you co-produced.

Pure engineering bullets. No indication you coordinated with humans outside your own team.

One page per five years of experience, max two pages. Reverse chronological. Consistent date format. No graphics that break ATS parsing.

Columns, sidebars, icons, skill bars, or photos that confuse machine parsing or waste vertical space.

Resume matches the target company's role archetype: system-design signal for infra roles, modeling and experimentation signal for DS roles, leadership and scope signal for senior+ roles.

Same resume sent to every role regardless of function or seniority.