Back to resources
Resume Tips

Showing emerging skills on your resume without faking them

You are always learning something new, and your resume should say so. Here is how to present a skill you are still building honestly, at the level you actually have, without overclaiming your way into an interview you cannot pass.

6 min read26 July 2026By ResumeCommand Team

You picked up a new tool six months ago. You have shipped one real thing with it, you are far from an expert, and now you are staring at a job posting that asks for it. Do you list it? How? The honest answer is more useful than either extreme, because the goal is not to look impressive, it is to get into a room you can actually hold your own in.

Why emerging skills belong on your resume

The skills that define a job are a moving target, and everyone knows it. LinkedIn's 2025 Work Change Report estimates that by 2030, 70% of the skills used in most jobs will have changed, with AI acting as the main accelerant. The same report notes that the rate at which people add new skills to their profiles has jumped 140% since 2022. In other words, showing skills you are actively building is not padding; it is exactly what a current, credible professional looks like.

So the question is never "should I mention the new skill." It is "how do I represent it at the level I actually have, so the resume opens a door I can walk through." Overstate it and you win an interview you then lose badly. Understate it and you screen yourself out of roles you could grow into. The skill is threading that needle.

Note

An emerging skill is an asset when it is framed as one. The problem is never that you are still learning something. The problem is a resume that implies you have mastered it, followed by a technical screen that proves you have not.

The trap: overstating proficiency

Skills are the easiest part of a resume to inflate and the easiest to expose. A padded years-of-experience line survives until a background check; a padded skill dies in the first technical conversation. Claim "expert in Kubernetes" and a competent interviewer needs about two questions to find the floor. That failure costs you more than never listing it, because now the interviewer is also recalibrating how much to trust the rest of your resume.

This matters more as hiring leans on skills. When a role is screened on skills rather than pedigree, the claimed skill gets tested, in a take-home, a pair session, or a pointed question. Honesty here is not just ethics; it is self-interest. The version of you that gets and keeps the offer is the one whose resume matched what showed up in the room.

How to show a skill you are still building, honestly

You have more honest options than a flat keyword list. The trick is to signal level and show evidence, not to hide the skill or oversell it.

  • Signal proficiency instead of implying mastery. A simple, honest scale reads clearly: "Proficient: Python, SQL. Working knowledge: Rust, Terraform." You are telling the reader exactly where you are, which is far more credible than one undifferentiated pile of technologies.
  • Show evidence, not adjectives. "Built and deployed a side project in React" says more than listing "React" among ten others. A repository, a shipped feature, a completed course, or a certification in progress all convert a claim into a fact.
  • Name the learning in progress. "Currently completing the [course or certification]" is a legitimate, honest line. It signals direction and initiative without pretending the journey is finished.
  • Anchor the new skill to a proven one. If you are strong in one area and building an adjacent one, say so: "Applying 6 years of backend experience while building depth in data engineering." That frames the emerging skill as a credible extension, not a leap.
  • Put level-setting where it counts. The strongest place to contextualize a new skill is next to real work. This is the same instinct behind quantifying your bullet points: specifics beat labels.

Tip

Ask one question of every skill you list: if an interviewer opened with "tell me about a time you used this," could you answer with something real? If yes, list it, at the level your story supports. If no, it is not ready for the resume yet.

What not to do

  • Do not list a tool you touched once as a core skill. A single tutorial is not "experience." If it belongs anywhere, it belongs under "familiar with," not among your strengths.
  • Do not claim years you do not have. "3 years of TypeScript" is checkable against your own timeline and your projects. Vague is safer than false, but specific and true is best of all.
  • Do not keyword-stuff for the ATS. Cramming every term from the posting into a skills block to beat the filter just moves the failure one step later, into an interview where the mismatch is obvious. Match honestly instead, the way you would when tailoring rather than tweaking an application.
  • Do not bury real strengths under aspirational ones. If half your skills section is things you are "learning," the reader cannot find what you are actually good at. Lead with proven, add emerging with context.

Reframe: emerging skills as a skills-first story

If you are deliberately pivoting, a whole resume can be built to carry emerging skills well. Grouping your experience around capabilities, and showing the projects that back each one, lets a growing skill sit next to the evidence for it rather than in a decontextualized list. That is the core idea behind a skills-first resume, and it is the most honest home for a skill you are still developing: value first, level made clear by the work attached to it.

The honest takeaway

Emerging skills are not something to hide or to fake; they are something to frame. Show them at the level you actually have, back them with evidence, and let the proven skills lead. Do that and your resume does the one thing it is supposed to do: get you into a conversation you can win on the merits, not one you have to survive. In a market where most job skills are changing within a few years, the candidate who represents a growing skill set honestly is not the weaker applicant. Often, they are the more current one.

ResumeCommand tailors your resume from your own history against a specific job posting, surfacing the skills that genuinely match the role and phrasing them against the work you have actually done. It helps you show relevant, real skills at the right level, rather than padding a list to beat a filter. Paste a job URL and see it in under 5 minutes.

Try it free → ResumeCommand

Sources