[ resume tips ]

WRITE IT
LIKE A
MATCHER
WILL READ IT.

Because one will. Here's exactly what we look at, what we skip, and what gets you the call.

[ 01 / do this ]

Six things that get you the call.

Lead with what you shipped.

"Built the checkout flow used by 2M users" beats "responsible for frontend development." Shippable things. Measurable things.

State your stack per role.

Not a skills blob at the top. Inside each job entry. Context makes it real. A stray "Kubernetes" in a box above your jobs means nothing.

Include the hard number once.

Traffic, revenue, users, uptime, latency. One metric that proves scale. That's all it takes.

Name the company in one sentence.

"B2B data infra, Series B, ~80 engineers" is more useful than the company name alone. Most matchers don't know most companies.

Show the why on gaps.

Left to do a startup. Burned out. Family. These are fine. One sentence. Silence looks like you're hiding something.

One page per decade.

Ten years → one page. Fifteen years → you can push to two. Three pages for eight years of experience is noise.

[ 02 / don't do this ]

Six things that get you skipped.

"Passionate about technology."

Everyone says this. It means nothing. What specifically excited you about the last hard problem you solved?

A skills section with 40 items.

"Proficient in Git" is table stakes. "Comfortable with Kubernetes" when you ran one cluster for two weeks is a lie. List what you'd put on code review.

An objective statement.

"Seeking a challenging role where I can leverage my skills." This is from 2004. Delete it.

Responsibilities instead of outcomes.

"Worked on the team that built X" is what everyone writes. "Owned the cache layer, cut p99 from 480ms to 60ms" is what gets the call.

PDF that bricks an ATS.

Columns, tables, icons, multi-column layouts. ATS systems parse these as garbage. Clean single-column for submission, fancy version for humans who ask.

Mismatched levels.

Applying as "Senior" with three years and no staff experience signals you don't know what senior actually means there. Read the JD first.

[ 03 / format ]

Three formats. One right answer for most people.

Reverse chronological.

most common

Default. Works for 95% of people. Most recent job first.

Functional.

red flag risk

Skills-first, hides dates. Used for career changes. Matchers find it suspicious. Use sparingly.

Hybrid.

underused

Skills summary at top, chronological below. Works well for senior ICs making a pivot.

resume-check.sh
$ run resume_check --strict
[]each role has a shipped outcome
[]stack listed per role, not globally
[]one measurable metric present
[]no "responsible for" language
[]gaps explained in one line
[]fits on one page (or two max)
[]single-column PDF for ATS
[]"passionate about technology" removed
// ready to send

One last check before you send.

Read your resume out loud. If you cringe anywhere, that's the bit to fix. If a sentence sounds like it was written by someone trying to sound impressive rather than someone who built things, rewrite it.

A matcher will spend 90 seconds on your resume before deciding to call. Make those 90 seconds land on the three things you most want them to remember.

Get a matcher review →Browse open roles