Resume keywords for tech jobs should be the languages, frameworks and practices you have used, written the way the job posting writes them. A recruiter search for a skill will find that word. A paragraph of every technology you have ever seen will not help, and it fails the moment someone asks you to go deeper.
Take keywords from the posting
Copy the names of skills you have, using the employer's spelling. If they say "PostgreSQL" and you have used it, write PostgreSQL, not "relational databases" alone. Keep the plain-language description as well, so a human reader understands the work.
- Mark repeated skills in the posting. Those are the search terms.
- Include the seniority clue they use, such as "production" or "mentoring", only if it is true.
- Add the domain if it is specific, such as payments or logistics.
Put each important keyword in a bullet
A skills list gets you found. A bullet gets you believed. For the three or four skills that define the role, add one line on what you built, fixed or ran, and the result.
- Prefer "Cut checkout errors by rewriting the payment retry job" over a bare tool name.
- Group minor tools on one line so they do not drown the core stack.
- Remove skills you could not use without a manual in front of you.
Skip the keyword dump
A block of fifty tools signals that none of them are strong. Rank your stack. The top lines should match this job. Older tools can sit lower or disappear.
- Lead with the stack from the last two years.
- Spell names correctly. Search is literal.
- Keep the same keywords in the profile, the skills list and the top role.
Use the posting's words for skills you have, and prove the important ones in a bullet.
Questions people ask
Should I add keywords for tools I studied but did not ship?
- Put them under learning or projects, with the scope. Do not place them next to production experience.
Do abbreviations matter?
- Use the form the posting uses, and the long form once if it is obscure. "CI" alone is ambiguous. "CI pipelines" is clearer.
How many skills should I list?
- Enough to cover the posting and your real stack, usually a short list. If everything is highlighted, nothing is.
Related reading
Kabir Menon
Kabir covers applicant tracking systems and leadership hiring. He explains how shortlists are actually built, for candidates and for hiring managers.
