Say you spent two years learning spreadsheet automation from videos and trial and error. You can build things that save a coworker hours. Then you type “Excel” into a skills list, and it looks exactly like the “Excel” on every other resume in the pile.
That gap, between what you can do and what a stranger can verify in thirty seconds, is the whole problem. This guide shows how to close it with proof, on a resume and on a professional networking profile.
What employers say about self-taught skills
A February 2026 release from Express Employment Professionals, based on Harris Poll surveys of 1,002 U.S. hiring decision-makers and 1,003 U.S. adults conducted in November 2025, gives a useful picture. Treat it as a staffing company’s survey, not a government count, but the numbers line up with what career offices tell students.
| Finding | Figure |
|---|---|
| Job seekers who now list self-taught skills on a resume | 47% |
| Hiring managers who see skills learned on informal online platforms as credible | 71% |
| Hiring managers who still prefer formal education | 53% |
| Hiring managers who value formal and self-taught learning equally | 29% |
| Hiring managers who favor self-taught learning | 18% |
| Hiring managers who say showing how a skill was used beats reading a resume | 92% |
Two things stand out. Most managers consider informal learning credible, yet more than half still lean toward formal education. And almost all of them say a demonstration is more persuasive than a line on a page. Your job is to supply the demonstration.
NACE, the association of college career centers and employers, points the same way. In a spring 2025 survey, about two-thirds of responding employers said they use skills-based hiring to identify promising candidates, and fewer than 40% screen by GPA. A separate NACE piece on resumes notes that listing a skill lets you explain your proficiency further in an interview. The skill on paper opens the conversation. The example closes it.
Key takeaways
- Most hiring managers surveyed see informal learning as credible, but many still prefer formal credentials, so you carry the burden of proof.
- A project, a result or a person who can vouch for you beats any adjective.
- Put proof where a skimming reader will see it: near the top, with a link that works.
- State your level plainly. You will be asked to show it.
Start with the job, not with your list
Before you write anything, pick one target role and open three postings. Copy the skills they repeat. That short list is what you are proving; everything else is background.
O*NET OnLine, the Department of Labor’s occupational database, helps here. You can look up an occupation and see the tasks, tools and skills it typically involves, and its “Hot Technologies” markers flag software employers often name in postings. If you are changing fields, it can also show you which of your existing skills carry over.
Then sort your skills into three piles:
- Provable now. You have a project, a client, a published piece or a person who can vouch for it.
- Provable soon. You know the skill but have nothing to show. A weekend project fixes this.
- Claimed only. You have read about it or tried it once. Leave it off, or label it “learning.”
Only the first pile belongs near the top of your resume.
Turn each skill into evidence
A claim is a noun. Evidence is a sentence with a verb, a context and an outcome. Here is how common claims can be backed up.
| Claim | Evidence a reader can check |
|---|---|
| “I can build websites” | Links to two live sites, with a note on who they were for |
| “I know data analysis” | A project stating the question, the data source, the method and the finding |
| “I can write” | Three published or shareable samples with links |
| “I can design” | A short portfolio with before-and-after examples |
| “I can code” | A public repository with a README that explains what it does and how to run it |
| “I can manage projects” | A volunteer or side project with dates, team size and what shipped |
If you have nothing in the right-hand column, that is useful information. It tells you what to build next. Our guide to building a project portfolio with no job experience walks through picking a first project.
Write bullets that show what changed
A good bullet answers three questions: what did you do, with what, and what happened? Numbers help, but only numbers you can support from your own records.
| Weak | Stronger |
|---|---|
| Learned Excel | Built a monthly budget workbook with formulas and charts that tracks 40 recurring expenses |
| Self-taught web design | Designed and published a five-page site for a local bakery using HTML, CSS and free hosting |
| Good at writing | Wrote 12 articles for a community newsletter and edited submissions from three volunteers |
| Knows social media | Scheduled a month of posts for a small shop and tracked which ones drew the most replies |
| Familiar with Python | Wrote a script that renames and sorts 500 files by date, saving about an hour a week |
Notice what the stronger versions have in common. Each one names a tool, a scale and a result. None of them uses the word “self-taught.” You do not have to apologize for how you learned. The bullet shows the skill is real.
If you cannot measure the outcome, describe it plainly: “Replaced a paper sign-in sheet with a shared form the front desk still uses.” A true, modest sentence beats a vague big one.
A quick formula
Try: Action verb + what you made + tool + result or scale. For instance, “Built a scheduling sheet in Google Sheets that cut double-bookings for a four-person volunteer team.” Then read it aloud. If you could not explain every word to an interviewer, cut it.
Where each skill belongs on a resume
Different sections do different jobs. Use them together instead of repeating the same line.
- Summary. One or two lines naming your field and strongest skills. “Self-taught front-end developer with three shipped projects” is clear and honest.
- Projects. If you lack formal job experience, put this section above education. List two or three projects, each with a link, one line on what it is and one on the result.
- Experience. Freelance, volunteer and informal work count as work. List them with dates, a role title that describes what you did and bullets like the ones above.
- Skills. Group by type, such as tools, languages and methods. Keep it to what you can use confidently. Every item should be supported somewhere else on the page.
- Education and training. Courses and certificates go here, lower than projects and experience unless the employer asks for a specific credential.
For more on structure, see our resume guide and the walkthrough on tailoring your resume for every application.
Use the posting’s words
If the posting says “data visualization” and you wrote “charts and graphs,” a keyword scan may miss you and a skimming human may hesitate. Match the posting’s terms wherever they are true. Never add a term you cannot back up.
Make your LinkedIn profile carry the proof
A profile has more room than a resume, and it can hold live links. Use that.
Headline. Say what you do or are moving toward, not just “open to opportunities.” For example, “Self-taught data analyst | Excel, SQL, dashboards for small nonprofits.”
About section. Three to five short sentences: your focus, what you have built, what you are looking for. Write in first person and keep it concrete. Skip adjectives you cannot prove.
Featured section. This is the profile’s version of a projects section. LinkedIn’s own nonprofit team suggests featuring work you are proud of, adding a short description to each item that explains your role, and reordering so the most important comes first. Good candidates: a live project, a write-up, a short demo video or a document.
Skills. List skills that match the roles you want. Rely on the first few lines, since few readers scroll the whole list. Ask people who have seen your work to endorse the two or three that matter most.
Recommendations. One specific recommendation from a client or mentor outweighs a long list of endorsements. More on that below.
Your profile and resume should tell the same story with the same dates. Our comparison of a LinkedIn profile and a resume covers what should match and what can differ.
Add outside voices
The Express survey asked hiring managers what builds their confidence in a self-taught candidate. Demonstrated industry knowledge and clear explanations of how skills were used each came in around 46 to 47%, completed work samples or assessments at 45%, references at 37%, and employee referrals at 29%. Notice that outside voices still matter, just after your own demonstrations.
Ask for a reference or recommendation the right way. Make it easy, specific and optional.
Asking for a recommendation
Hi Dana, I’m applying for junior analyst roles and I’m pulling together proof of the work I did on the pantry inventory sheet last spring. Would you be willing to write two or three sentences on what I built and how it was used? I can send a short draft of the facts to make it quick, and totally understand if you’re too busy.
Never write fake testimonials or ask someone to say something untrue. If a person cannot speak to your work, they are not the right voice.
Be honest about your level
Inflated skills tend to get found out, usually in an interview or a first-week task. Describe your level in terms a reader can test.
- Better: “Working knowledge of SQL; wrote joins and aggregations weekly for a volunteer project.”
- Better: “Comfortable with Photoshop for web graphics; not experienced with print production.”
- Avoid: Star ratings, progress bars and “expert” unless you could teach it.
A clear limit makes the rest of your claims easier to believe. “I have used it for a year, mostly for X” sounds more credible than a blanket “advanced.”
Keep learning visible
Add recent courses, practice or certifications with dates. It shows that your knowledge is current. A certificate from a recognized provider is a supporting signal, but it is thinner than a project because anyone can finish a course. Pair it: “Completed a data visualization course, then built a public dashboard of local bus delays.”
Talk about it in interviews
Interviewers will likely ask how you learned. Prepare a short story with four parts: what pushed you to start, how you structured your learning, what you built and what you would do next.
Answering “You don’t have a formal background in this, do you?”
That’s right. I learned it by building. I started with a small scheduling problem for a volunteer group, taught myself the formulas I needed, and the sheet is still in use. I can walk you through it if that’s helpful. The next thing I want to learn is how to automate the weekly report.
That answer is calm, specific and invites a demonstration. Be ready to open your project and explain a decision you made and a mistake you fixed. Many hiring managers use behavior-based questions, so having your examples organized helps. Our guide to the STAR method shows how to structure them.
A worked example, start to finish
Imagine Sam, who spent a year learning to build dashboards while working in a warehouse office. Nobody gave Sam the title “analyst.” Here is how the pieces could come together. This is an illustration, not a real case.
The raw material. Sam built a shared workbook that tracked late deliveries by supplier. The office manager used it in a weekly meeting. Sam also finished two online courses and wrote a short summary of what the workbook showed.
The resume entry. Under Projects: “Delivery Tracker, shared workbook for a six-person office. Combined weekly carrier reports into one view and flagged repeat late suppliers. Used in weekly planning meetings.” Under Skills: “Excel (pivot tables, lookup formulas, charts); SQL (basic queries, learning joins).”
The profile. The headline names the target role. The Featured section holds a cleaned-up, anonymized version of the workbook and a one-page write-up. A recommendation from the office manager describes the meeting use in two sentences.
The interview story. Sam explains why the first version failed (the reports used different date formats), how the fix worked and what the next improvement would be.
Nothing here required a degree or a fancy title. It required a real task, a record of what happened and the willingness to explain it. Remove or blur anything confidential before you share work from a past employer, and ask permission if you are unsure.
Common situations, quick answers
I learned on the job but my title does not show it. Keep the real title, then add a clarifying line in the bullets: “Took over reporting for the team and built the weekly dashboard in Excel.”
My best work is private or under an agreement. Describe it without names or figures, or recreate a small version with sample data. Say plainly that the original is confidential.
I am changing fields. Use the skill list you built from the postings and O*NET’s soft skills list, which groups social skills such as persuasion and coordination with thinking skills such as active learning and problem solving. Those transfer more easily than tools, so give each one a short example from your past work.
I have only course projects. Label them honestly as coursework, then add one project you chose yourself. A reader can tell the difference, and the self-chosen one shows initiative.
An employer uses software to screen resumes. Keep formatting plain, use the posting’s terms where they are true and avoid putting key proof only in images or graphics. For more, see our piece on automated resume screening.
Mistakes to avoid
- Listing a skill with no proof anywhere. A skills list full of unsupported terms reads like filler.
- Dead or private links. Test every link in a private browser window before you send anything.
- Projects with no explanation. A repository without a README, or a design without context, forces the reader to guess.
- Exaggerating scope. Calling a class exercise “client work” can backfire if someone asks the client’s name.
- Using self-taught as the headline. It is a fact about how you learned, not a skill. Lead with what you can do.
- Hiding relevant work in a list of hobbies. If it relates to the job, give it a real section.
- Mismatched resume and profile. Different dates or titles raise questions you do not need.
Do not claim what you cannot show
If you list a tool, expect to be asked to use it. A short skills test or a live task is common for technical roles. If you are still learning something, say “learning” and name what you have done with it so far.
A checklist before you apply
- List the five skills the target jobs repeat most.
- Next to each, write your best proof: a link, a number, a person or a sample.
- For any skill with no proof, plan one small project this month, or drop it from the top of the page.
- Rewrite your bullets with the action, tool and result formula.
- Move a projects section above education if you lack formal credentials.
- Add your best project to your profile’s Featured section with a two-sentence description.
- Test every link in a private window.
- Ask one person for a specific recommendation.
- Practice your two-minute “how I learned it” story out loud.
The bottom line
Self-taught skills are common and, by most surveys of hiring managers, widely seen as credible. What readers lack is a way to check them. Give them one: a project with a link, a plain description of your level and a short story about what you built.
This week, pick one target role, choose your single strongest piece of proof and rewrite one bullet and one Featured item around it. Then repeat for the next skill. This is general career information, not a guarantee of any result, and what employers value will vary by field and company.
