How to put side projects and self-taught skills on your résumé

I've built four products on nights and weekends — a résumé tool, a robotics ops platform, a handicapping engine, and the social manager that posts for me. None of it started as a job. It started as side projects, built to learn things I couldn't learn any other way. So when people ask whether self-taught skills and personal projects "count" on a résumé, my answer is yes. But only if you present them the way you'd present a job: as evidence, not as filler.

Most people get this wrong in one of two directions. They hide the self-taught work because it doesn't feel "real." Or they inflate it, and a weekend tutorial becomes "two years of experience." Both cost you. Hiding it throws away real proof of what you can do. Inflating it hands the interviewer a claim you can't back, which is worse than a short résumé — you fail in the room instead of on paper, and you spend your credibility doing it.

Here's how I'd actually do it.

The test: could you defend it out loud?

Same test I use for a skills line, applied to a project: if an interviewer stopped and said "walk me through that," could you? Could you explain what you built, why, the parts that broke, and what you'd do differently? If yes, it belongs on the résumé. If you followed a tutorial start to finish and couldn't change one thing about it, it's study — real, worth doing, but not experience yet.

That line is the whole thing. A project earns a spot when it produced something you can show and talk about, not when you spent a weekend near it. (The same prove-it rule runs your skills section — everything on a résumé is a promise you can be asked to keep.)

Where projects go

You have two honest options, and which one you pick depends on how much directly-relevant paid experience you already have.

If your work history already covers the job, put projects in a short, clearly labeled Projects section near the bottom — two or three entries, no more. It's supporting evidence, not the headline.

If you're changing fields or early in your career and your paid history doesn't say much about the job you want, projects can move up, right under the summary, and do the work your job titles can't. When the most convincing proof you can do the work is a thing you built on your own, lead with it. Don't bury your best evidence out of a sense that it's less legitimate than a job. The person hiring cares whether you can do the thing, not whose payroll you were on when you learned it.

Either way, give each project a real name, a one-line role ("solo build," "contributor," "team of three"), and a link if there's something live to look at. A link that works is worth more than a paragraph that describes.

Write a project bullet like any other bullet

A project bullet follows the exact shape that makes a job bullet good: what you did, plus the result, with a number on it wherever one honestly exists.

Skip this:

Built a personal finance app using React and a Postgres database.

That tells me the tools and nothing else. Every bootcamp grad has a version of it. Write this instead:

Built and shipped a budgeting app that 400 people use monthly; cut my own category-tagging time from 20 minutes a week to under 2.

The tools moved into a supporting line or the skills section, and the bullet now carries evidence — a real user count, a real before-and-after. If nobody uses it yet, that's fine; measure something true anyway. What you learned, what it handles, how long it's run without breaking. There's almost always a number if you look for one — the full method is in quantifying your bullet points.

Self-taught skills are a claim, not a certificate

A finished course is study, not a job, and it doesn't get a spot in your work history. This one has bitten people I've talked to: a certificate becomes a "role," and a résumé quietly invents a whole stage of a career that never happened. Don't. List certifications and courses under Education or a short Certifications line, plainly, with the date. That's honest and it's enough.

The self-taught skill itself earns its place the same way any skill does — you list it because you can demonstrate it, not because you watched someone else demonstrate it. If the only proof you've touched a tool is the course completion screen, the tool goes in "learning," not in the skills line you're telling a recruiter to trust. The gap between "I took a course in it" and "I built something with it" is the entire gap that matters, and the project is what closes it. That's why the two belong together on a résumé: the skill is the claim, the project is the proof.

The career-change version

I've changed industries three times — heavy-civil construction, then project management, then facilities and robotics. Every one of those moves, the thing that made the jump believable wasn't a class I'd taken. It was work I'd done on my own that showed I could operate in the new field before anyone paid me to. The class got me the vocabulary. The project got me the credibility.

If you're making that kind of move, this is your strongest card. A hiring manager reading a career-change résumé is asking one quiet question: can this person actually do the work, or do they just want to? A real project you built, described in the new field's terms with a result attached, answers it better than any summary paragraph can. Use it.

Where a tool helps — honestly

Once you've decided what's genuinely provable, the keyword step is the part a tool makes faster. ResumAI's ATS check reads a job description against your résumé and tells you which of the posting's exact terms you're missing, so a project you built with a skill the job wants doesn't get overlooked just because you named it something else. It won't invent a project for you, and it shouldn't — the honest part is on you. It scrubs your personal details before any of it reaches an AI model, too, which matters when the résumé you're working on names things you're still building on the side.

The one thing to do today

Open your résumé and find the most impressive thing you've built on your own that isn't on it. Give it a name, one line on what it does, and one true number. Then look at any course or certificate you've listed as though it were a job, and move it to where study actually goes. A short list of things you built and can defend beats a long list of things you sat through — on paper, and in the room.