What technical skills to put on a resume when your real value is more than a keyword list

The answer is not “all of them”

If you are wondering what technical skills to put on a resume, the tempting answer is every tool you have ever opened.

Python. React. SQL. Docker. Kubernetes. AWS. Azure. Terraform. Kafka. Git. Linux. Agile. Excel, because why not.

That feels safe for about five minutes. Then your CV starts looking like a keyword drawer with a career attached to it.

For experienced technical candidates, the skills section has one job. It should help the reader quickly understand what kind of work you can credibly do. It should not be a memory dump.

Start with the job, not your toolbox

The right skills depend on the role in front of you.

A senior backend role might care about distributed systems, databases, cloud infrastructure, observability, and performance. A data engineering role might care about pipelines, orchestration, modelling, warehouses, and Python. An AI product role might care about LLM workflows, evaluation, retrieval, prompt design, and product judgement.

Same person. Different emphasis.

Before editing the skills section, read the job description and mark:

• skills they repeat
• tools that look essential
• concepts that define the work
• nice-to-haves you actually have
• skills you have but cannot honestly defend

The last group is the one to be careful with. If you cannot talk about it in an interview without squirming, it probably does not belong near the top of your CV.

Group skills so a human can scan them

A random list is hard to read. Grouping makes it easier.

For example:

• Languages: Python, TypeScript, SQL
• Backend: FastAPI, Node.js, REST APIs, event-driven systems
• Data: PostgreSQL, dbt, BigQuery, Airflow
• Cloud and infrastructure: AWS, Docker, Terraform, CI/CD
• Practices: observability, incident response, technical mentoring

This is not about making the CV pretty. It is about reducing the reader’s effort. A recruiter can scan it. A hiring manager can see the shape of your experience. An applicant tracking system can still find the words it is looking for.

Prove the important skills somewhere else

The skills section is a signpost, not evidence.

If Kubernetes appears in your skills list, I want to see where you used it. If you list machine learning, I want to know whether you trained models, shipped model-backed features, maintained pipelines, or just completed a course three years ago.

The strongest CVs repeat the key skills in context.

Not like this:

“Skilled in cloud architecture, microservices, and DevOps.”

More like this:

“Reworked the deployment pipeline for a microservices platform on AWS, reducing failed releases by tightening environment checks and rollback steps.”

That tells me more. It gives the skill a real job.

Cut stale and decorative skills

This bit is oddly painful.

You might have a tool on your CV because it used to matter. You might keep it because you are proud you learned it. You might keep it because removing things feels like losing part of your career.

But a CV is not an archive.

If the skill is old, shallow, irrelevant, or likely to distract from the role you want now, cut it or move it down. Your CV should make the strongest case for this job, not preserve every version of you that ever existed.

For senior people, this matters even more. A huge undifferentiated list can make you look less senior, not more. Seniority usually shows through judgement, scope, and tradeoffs, not through having 43 technologies in a row.

What I would put on a technical CV

For most technical roles, I would include:

• core languages you can actually use
• frameworks and platforms relevant to the job
• cloud, data, or infrastructure tools you have used in real work
• practices that show how you operate, such as testing, observability, incident response, mentoring, or architecture review
• domain knowledge if it matters, such as fintech, healthtech, logistics, public sector, or developer tools

I would avoid:

• basic office tools unless they are genuinely relevant
• every methodology you have ever heard of
• tools you used once in a tutorial
• vague soft skills with no proof
• stuffing the exact job advert back into the CV

The goal is not to impress everyone. It is to make the right reader think, this person fits the work we need done.

Where OutRung helps

This is exactly the sort of job-search admin that gets tedious fast.

With OutRung, the useful thing is having one master profile that holds the full version of your experience. Then, when a job comes along, you can score the role, see which skills matter, and generate a tailored CV that pulls forward the relevant evidence.

That is a better workflow than manually rewriting the same skills section for every application while half-watching the clock.

The important bit is still honesty. A tool can help organise and tailor. It should not turn a passing familiarity into a core capability.

A final rule

Put a technical skill on your CV if three things are true.

You have used it enough to discuss it.

It matters for the role.

You can point to evidence.

If it fails one of those tests, think carefully before adding it. A shorter, sharper skills section usually beats a long one that makes the reader wonder what is real.