Use the job description without stuffing your CV
Connect requirements to real evidence instead of chasing keywords.
Understand the request first
A recruiter may search keywords, while another workflow uses semantic matching or human review. Not every system matches literal words alone. Precise names still make your experience easier to understand.
Three fields for each requirement
Write the requirement, your evidence and the sentence that needs changing. Fictional example: the posting asks for SQL; your evidence is a project using queries; your CV explains what you queried and why. A tool you have never used belongs in a learning-gap list, not your current skills.
Separate required from preferred criteria. Do not turn “preferred” into an absolute barrier or ignore an explicitly required licence. If the posting is unclear, keep a question to ask the employer.
Make a focused edit
Start with the summary and the two most relevant projects or roles. Name the tool accurately and describe its use. A dashboard is not necessarily a Power BI dashboard: claiming that software without having used it would be misleading.
Read the result aloud. If it sounds like a vocabulary list, connect each skill to an action and an outcome. Choose a posting from open opportunities and keep a clear version in the CV builder. A fit analysis is a review aid, not the employer’s internal score.