How to tailor a CV without rewriting your life

There are two bad ways to apply. The first is sending the same CV to every posting and hoping the reader does the matching for you. The second is letting a tool invent a version of you that interviews cannot support. Both waste a week you will not get back.

Tailoring sits between those mistakes. You do not become someone else. You decide which true lines earn the first page.

Read the role before you write

A job description is a list of evidence the hiring team wants to see. Read it once for the work, once for the words. Circle the problems they name. Circle the tools they repeat. Ignore the fluff that every posting copies from the last one.

Then look at your own page with that list in hand. Which roles, projects, or degrees actually answer those problems? Those lines move up. The rest can wait for a different job.

Keep the metric. Cut the noise.

A tailored bullet is usually a shorter bullet. Keep the action and the result. Drop the committee names, the internal tools nobody outside your team uses, and the duties that do not touch this role.

• If the role asks for user research, lead with the study you ran — not the slide deck software.
• If it asks for shipping, keep the launch date and the number that moved.
• If a line only proves you were busy, it is not proving you fit.

Close keyword gaps with real work

Parsers and tired humans both scan for the language of the posting. That does not mean stuffing a skills row with words you cannot discuss. It means naming the work you already did in the terms the role uses — when those terms are honest.

Did you run interviews? Say user research if that is what they called it. Did you write SQL every week? Put it next to the project, not in a lonely cloud of logos. A gap you cannot close with truth is a gap. Leave it. Inventing it is how you fail the screen that comes after the parser.

Then make the page readable

None of this helps if the file cannot be parsed. One column. Real text, not a screenshot of text. Your name and email as text. Dates as years. Headings a system can recognize: summary, experience, skills, education. Save the decorative layout for a portfolio.

If you work in Arabic and English, keep both pages to that same discipline. A bilingual CV that a parser cannot read is still an unread CV.

Let the software do the aiming

You should not rebuild the skeleton for every application. Build the source of truth once. When a role appears, point that source at the description: highlight the fit, close honest keyword gaps, export a page the ATS can extract.

That is what Waem is for. Your story stays yours. The page changes aim. The interview still has to be about work you actually did.