How to Present Side Projects on Your Resume
How to present side projects on your resume as a career changer: where to place them, the exact entry format, action verbs, ATS tips, and the mistakes that get resumes skipped.
Present your side projects on your resume as a dedicated Projects section, formatted with the same rigor as paid work: each entry names what you built, the tools you used, the problem it solved, and at least one measurable result. When you are changing careers and lack direct experience, projects are the strongest evidence you can do the job — and the hiring climate is moving your way. As of January 2024, 52% of U.S. job postings on Indeed listed no formal education requirement, up from 48% a year earlier (Indeed Hiring Lab), and SHRM's 2024 Talent Trends report found that 73% of employers now use skills-based hiring, up from 56% in 2022. Skills are replacing credentials, and well-presented projects are how you prove them. Traecta — Your Personalized Career Roadmap maps your existing skills to your target role and points you to the project pieces that read as professional evidence on your resume.
This guide covers where projects belong on a career-changer's resume, the exact format for each entry, how to describe a project so it sounds professional rather than academic, and the mistakes that get resumes skipped.
Why projects belong on a career-changer's resumePermalink to “Why projects belong on a career-changer's resume”
A resume without relevant job history is not a weakness if you have the work to show. Two independent data points explain why.
First, employers are steadily removing degree gates. Beyond Indeed's 52% figure, Lightcast found that between 2017 and 2019 roughly 46% of middle-skill and 37% of high-skill occupations saw employers reset degree requirements downward. When the credential disappears, the work itself becomes the proof — which is exactly what a project provides.
Second, hiring has shifted toward evaluating demonstrated skill. SHRM's 73% skills-based-hiring figure is reinforced by LinkedIn's Economic Graph, which shows a 21% year-over-year rise in skills-first hiring in the United States. A hiring manager who can no longer lean on "five years of experience and a relevant degree" will look instead at what you have actually shipped. That makes the way you present projects a direct lever on whether you get an interview.
If you are still building the work to show, start with our complete portfolio guide for career changers, which covers how many projects you need and realistic timelines.
Where to place the Projects sectionPermalink to “Where to place the Projects section”
Placement depends on how much relevant experience you already have. The principle is simple: put your strongest evidence highest on the page.
| Your situation | Where Projects goes | Why |
|---|---|---|
| Little or no relevant experience | Directly below your summary, above Experience | Projects are your main evidence of ability |
| Some related experience | Below Experience, as its own section | Work history leads, projects add depth |
| Strong relevant experience | Fold one flagship project into a "Selected Projects" line near the top | Avoid crowding the page with redundant detail |
Recruiters spend an average of 7.4 seconds on an initial resume screen before deciding whether to read further, according to an eye-tracking study from The Ladders. In that window they scan your most recent title, employer, skills, and dates. A career changer whose current title does not match the target role has seconds to surface relevant work — which is exactly why a prominent Projects section matters.
The anatomy of a project entryPermalink to “The anatomy of a project entry”
Treat each project like a small job. A strong entry has five elements:
- Project name — descriptive, not clever. "Inventory Turnover Dashboard" beats "Project 2."
- Tech stack — the tools, languages, and frameworks, listed as text so an Applicant Tracking System can parse them.
- Problem statement — one line on the real-world scenario the project addresses.
- Action-verb bullets — three or four lines on what you built and decided.
- A measurable result — at least one number: time saved, error rate reduced, users, rows processed.
Here is the format, with a before-and-after that shows the difference it makes.
Before (weak):
Sales Dashboard — Python, Tableau Made a dashboard for sales data.
After (strong):
Sales Performance Dashboard | Python, Pandas, Tableau, SQL Self-directed project analyzing 18 months of retail sales data from a public dataset.
- Built an automated pipeline in Python that cleaned and aggregated 480,000 transaction records.
- Designed a Tableau dashboard tracking revenue, margin, and inventory turnover by region.
- Cut the time needed to reproduce the monthly report from a full day to under 30 minutes.
- Live dashboard · Source code
The second version tells a recruiter what you built, the scale of the data, and the result — in the same format they expect from a paid role.
Side projects vs. work experience: how to format eachPermalink to “Side projects vs. work experience: how to format each”
Career changers often blend paid work that is only loosely related with projects that are squarely on target. Format them differently so the reader can tell which is which.
| Element | Work experience entry | Project entry |
|---|---|---|
| Header | Company, job title, dates | Project name, "Self-directed project" or context |
| Focus | Responsibilities and impact on the job | What you built and decided |
| Evidence | Metrics from the role | Metrics from the build |
| Link | Usually none | Live URL or repository |
Labeling a project as self-directed is honest and works in your favor — it signals initiative, which is exactly the trait employers look for in someone claiming a new skill. For a deeper treatment of how to frame non-traditional work, see our guide to a skills-based resume for career changers.
Describe the project so it sounds professional, not academicPermalink to “Describe the project so it sounds professional, not academic”
The most common mistake career changers make is describing a project the way a course assignment reads — passive, process-focused, and without a result. Professional descriptions are active and outcome-focused.
Lead each bullet with a strong action verb. The seven that work hardest are Led, Built, Analyzed, Improved, Designed, Launched, and Streamlined — they replace vague phrases like "worked on" and "responsible for," which recruiters skim past. Our deep dive on resume power words for career changers breaks down each verb with before-and-after examples.
Then attach a number to as many bullets as you can. "Improved reporting time by 40%" is evidence; "Improved reporting time" is a claim. If you cannot recall exact figures, use defensible ranges, because "roughly 40%" is stronger than no number at all.
A useful test: read each bullet aloud and ask whether it answers so what? If a line only describes the process ("Used Python to clean data") without a result, rewrite it until it does ("Cleaned 480,000 records in Python, cutting preprocessing time by half").
ATS and the reality of automated screeningPermalink to “ATS and the reality of automated screening”
Most resumes are read by software before a person sees them. Jobscan's 2025 analysis found that about 98% of Fortune 500 companies use an Applicant Tracking System (ATS) that scans for keywords and parses your content before a recruiter does. A few formatting choices decide whether your projects survive that screen:
- Keep entries as plain text. Avoid embedding project details inside tables, text boxes, or images; many parsers cannot read them.
- Name your tools explicitly. List the languages, frameworks, and platforms as text ("Python, SQL, Tableau") so they match the keywords in the job posting.
- Link, don't screenshot. A clickable link to a live deployment or GitHub repository is parseable and lets a curious recruiter go deeper. An image of your dashboard is invisible to the system.
- Mirror the posting's language. If the role asks for "data visualization," use that phrase rather than a synonym only you would choose.
These same principles apply to the projects themselves. If you want concrete builds that map to in-demand skills, our list of coding projects that get you hired gives eight examples with technical requirements, and our first projects for career changers into analytics is the right starting point if data is your target field.
Common mistakes to avoidPermalink to “Common mistakes to avoid”
- Listing unfinished projects. A half-built app reads as a half-finished candidate. Ship three complete projects before you add a fourth.
- Tutorial projects, unmodified. A to-do app copied line-for-line from a tutorial proves you can follow instructions, not that you can solve problems. Extend any tutorial project until most of the code and all of the decisions are yours.
- No links to live work. A recruiter who cannot click through to a deployed project treats the entry as a claim. Hosting is free; there is no reason to skip it.
- Vague, result-free bullets. "Worked on a dashboard" tells the reader nothing. Rewrite every bullet around what you built and what changed because of it.
- Overcrowding. Five strong entries beat fifteen weak ones. If you have already shown a skill once, a second project on the same skill adds length, not evidence.
For the broader question of how many pieces you need and how to sequence them, our guide to portfolio projects with no experience lays out a realistic path.
How Traecta helpsPermalink to “How Traecta helps”
A resume only converts if the projects behind it are the right ones. Traecta builds a personalized roadmap from the skills you already have to the ones your target role requires, then points you to the specific builds that close the gap — so the Projects section you write is filled with work a hiring manager recognizes as job-ready. You can pair that roadmap with a strong cover letter for a role with no experience to round out an application that leads with evidence rather than titles.
The takeawayPermalink to “The takeaway”
Present side projects on your resume as a dedicated, prominently placed section that mirrors the format of paid work: a clear name, the tech stack, the problem, action-verb bullets, and a measurable result — all as parseable text with a live link. For a career changer, that section is often the single strongest argument that you can do the job, and it deserves the same care you would give any line of work experience.
