Resume guide
How to compare your resume with a job description
A good comparison asks whether your evidence supports the job’s outcomes. It is not a hunt for identical phrases. Use the posting to identify priorities, then map real achievements, responsibilities and constraints from your CV.
Published by MatchRadar, Romania · Last updated
Separate outcomes from the employer’s wording
Highlight the responsibilities that describe what success looks like: growing a channel, delivering projects, managing risk, improving a process or supporting customers. Tool lists matter, but they often describe how the work happens rather than why the role exists.
Group repeated ideas together. If stakeholder management appears in three bullets, it is probably a central signal even if the exact phrase varies.
Build an evidence map
For every central requirement, find the strongest CV line that proves comparable work. Evidence becomes stronger when it names scope, context and outcome. If there is no supporting line, mark a real gap rather than forcing a weak match.
- Requirement or outcome in the posting
- Comparable responsibility from your experience
- Tool, method or domain used
- Scale: budget, team, geography, volume or complexity
- Result you can state accurately
Check seniority and constraints
A role can share your skills and still be wrong in level. Look for ownership language, team scope, decision authority and expected years of experience. Then check location, work authorisation, schedule and travel before spending time tailoring.
These practical constraints can outweigh a high skills overlap, which is why they belong in the comparison rather than at the end.
Tailor by emphasis, not invention
Move the most relevant evidence higher, make implicit context explicit and use the employer’s natural terminology where it truthfully describes your work. Do not add tools you have never used or inflate ownership.
Keep one accurate base CV. Tailoring should improve relevance and clarity, not create a new professional identity for each posting.
An evidence map, line by line
The posting and CV lines here are a prepared illustration. The posting is for a data analyst: build and maintain dashboards, write SQL against a warehouse, present findings to non-technical stakeholders, three years of experience, Python a plus. For each line, the map records the CV sentence that proves it and a verdict.
- Dashboards: "Built and ran the weekly sales dashboard used by 40 managers" — met, with a scope
- SQL on a warehouse: "Wrote the SQL behind the dashboard, on BigQuery" — met
- Presenting to non-technical people: "Presented the monthly numbers to the regional directors" — met
- Three years: two and a half in the role, plus a year of analysis inside a finance job — a band, not a gap
- Python: one university project, nothing at work — partial; name it honestly, do not upgrade it
What the map changes in the CV
The map usually shows two kinds of gap. A missing line is a real gap, and you decide whether it matters. A line you have but the CV does not say, such as presenting to directors buried under a job title, is a gap on paper only, and the fix is to write the truthful sentence near the top.
It also shows what to cut. Responsibilities the posting never mentions take space from the ones it does; they can move down or out for this application. The order of the CV should follow the order of the posting's core work, not the order of your career.
For the decision before any of this, whether to apply at all, the ten-minute qualification check comes first: gates, then the core of the role. A fit check in MatchRadar builds this map for a posting you paste, 35 a month on the plan.
Common questions
How many keywords should match?
There is no universal count. Coverage of the role’s core responsibilities and gates matters more than repeating a fixed percentage of words.
Should I rewrite my whole CV for every job?
Usually no. Reorder and clarify the most relevant truthful evidence, then make only the changes the role actually justifies.
What if the job description is vague?
Use the company context, title, seniority and repeated themes, then research before applying. A vague posting creates uncertainty no matcher can remove.
Should I rewrite my CV for every job?
Reorder and reword it, do not rewrite it. Put the evidence for the posting's core work first, use the posting's words where they are true of your work, and cut what the posting does not ask for.