How to Build a Project Portfolio With No Job Experience
Self-directed builds, volunteer work and coursework all count as evidence — what matters is how you scope each piece, finish it, and show the decisions behind it.
By Ananya Rao · Sep 30, 2026 · 12 min read
You build a portfolio with no job experience by picking one target role, then producing three or four finished pieces of work that someone hiring for that role would recognise as real. The work does not have to be paid. It does have to be complete, documented and easy to open.
This guide covers when to start, the order to do things in, what to say when you ask someone for a real problem to solve, and what to change if the portfolio is not getting you interviews.
When to do it, and when to wait
Start building now if any of these apply:
- Job ads for your target role ask for samples, a GitHub link, a reel or a case study. If the application form has a portfolio field, the portfolio is part of the screen, not a bonus.
- You are changing fields and your resume has nothing from the new field on it. Projects are the fastest way to put relevant nouns and verbs on the page. Employers increasingly screen entry-level candidates on demonstrated skills rather than credentials alone — the NACE Job Outlook 2026 survey, as reported by The Interview Guys, put skills-based hiring for entry-level positions at 70% of employers.
- You finished a course or certificate and have only the completion badge to show. A credential says you sat the material. A project says you can use it when nobody hands you the instructions.
- You are being rejected before any human conversation. If you never reach a screening call, the problem is the evidence on the page, and a portfolio is evidence you can create yourself this month.
- Someone in the field offered to look at your work. That offer expires. Having something imperfect to send beats having nothing.
Not yet: if you cannot name one role title you are aiming at, wait. Building before you choose produces a folder of unrelated demos that impresses nobody, because reviewers judge against a specific job. Spend a week reading job ads and talking to two people who do the work, then start.
Step by step
- Collect ten job ads for one role title and paste them into a single document. Highlight every tool, deliverable and responsibility that appears three or more times. Prepare: a shortlist of two or three role titles, and a job board or two you trust. Lead time: one to two evenings.
- Write a master resume — a single document listing every skill, task, accomplishment and piece of training you have, paid or unpaid (CareerOneStop describes exactly this kind of document). Include a volunteering and activities section, which CareerOneStop recommends for volunteer or community work plus other activities that show responsibility. Prepare: old course notes, club roles, freelance favours, anything you organised. Lead time: three to five hours, spread over a week.
- Map three project ideas against the highlighted skills so each project covers two or three of them and no project repeats another. Write one sentence per project naming the problem, the user and the deliverable. Prepare: your highlighted ad document. Lead time: two to three days of thinking, one hour of writing.
- Close the biggest skill gap with a structured curriculum rather than scattered videos. freeCodeCamp's curriculum offers eleven certifications, each designed to take roughly 300 hours (freeCodeCamp, 2022). Google Career Certificates are built for people with no degree or prior experience and are designed to be completed in three to six months; ACT-IAC lists the price as $49 per month on Coursera after a seven-day free trial, and notes that many learners finish in three to six months at about ten hours of study a week. U.S. News & World Report lists the Google IT Automation certificate at $39 per month after the free trial, or $234 for a six-month run. Prepare: a fixed weekly study slot and your own deadline. Lead time: three to six months at around ten hours a week; longer if you study fewer hours.
- Find one real user for at least one project. Talk to a club treasurer, a small charity coordinator, a local trader, a lecturer or a community group organiser. Real constraints produce the stories interviewers actually probe. Prepare: the spoken script in the next section and a one-page scope you can show them. Lead time: one to three weeks to get a yes; two to six weeks to deliver something small.
- Document each project as a one-page case study or README: the problem, who it was for, the constraints, what you decided and why, what you would change next. Add screenshots or a short screen recording. Prepare: notes taken while you worked, not reconstructed afterwards. Lead time: two to four hours per project.
- Publish everything somewhere a stranger can open in one click. GitHub Pages is a common choice for a simple, free portfolio site (recommended on Medium by developer Steve Jones); a well-organised folder of PDFs, a Notion page or a free site builder works too, as long as nothing is behind a login. Test every link on a phone. Prepare: consistent file names, alt text, and a contact line. Lead time: a weekend for a first version.
- Ask one practitioner and one non-specialist to review it before you attach it to applications. The practitioner checks whether the work is credible; the non-specialist checks whether the first ten seconds make sense. Prepare: three specific questions, not "any feedback?". Lead time: one to two weeks to get responses, then a few hours of edits.
What to say
Two situations need words: asking an organisation for a real problem to work on, and asking someone in the field to look at what you built.
Asking a club, charity or small business for a real project (spoken)
In person or on a call
"Hi [name], I'm [your name] — I'm training as a [target role] and I'm looking for one real problem to work on rather than a practice exercise. I noticed [specific thing: your booking sheet is manual / your event photos aren't anywhere public / your stock list lives in one person's head].
Here's what I'd offer: I'd do [specific deliverable] for free, in about [two to four] weeks, and you'd own it either way. All I'd ask in return is twenty minutes at the start to understand what you need, a quick check-in halfway, and permission to show the finished work in my portfolio — with anything sensitive removed.
If it turns out you want more than that afterwards, I'd quote it separately at [$X] per [hour/project], but there's no obligation. Would it help if I sent you a one-page outline first?"
If they hesitate, narrow the ask rather than defending it: "Would a smaller version help — just [single page / single report / single process] — so you can see the quality before committing?"
Asking a practitioner to review your portfolio (email)
Subject: Quick review of two [target role] projects?
Hi [name],
I'm moving into [target role] and I've built three projects to stand in for paid experience: [project one, one line] and [project two, one line]. They're here: [link].
I'm not asking you to review everything. Three specific questions, and any one answer would help:
1. Which project would you cut, and why? 2. Does the [specific choice: data model / layout / method] in [project] look like something you'd accept from a junior on your team? 3. What's missing that you'd expect to see for a [role title] application at [type of employer]?
Ten minutes of typing is plenty — no call needed unless you'd prefer one. Happy to send a short summary of what I changed afterwards, if that's of interest.
Thanks either way, [your name] — [portfolio link]
Following up once (email)
Subject: Re: Quick review of two [target role] projects?
Hi [name],
Following up once on the below, then I'll leave it. If you're stretched, question 1 alone — which project to cut — would still be useful.
If it's easier, I've since rewritten the summary on [project] after feedback from [person or group], so the link is a bit clearer than it was.
Thanks, [your name]
Mistakes to avoid
| Mistake | Why it backfires |
|---|---|
| Building the same tutorial project everyone else builds | Reviewers have seen it dozens of times, and they cannot tell your work from the instructor's. It also gives you nothing to say when asked what you decided and why. |
| Leaving projects undeployed, half-finished or behind a login | A reviewer spends well under a minute per candidate. A broken link or a "coming soon" page is read as the standard of work you would bring to the job. |
| Posting the artefact with no write-up | Without the problem, the users, the constraints and the outcome, nobody can judge whether the work was hard or trivial. The case study is the part that gets read. |
| Starting with one enormous flagship project | It absorbs months, is never finished, and you apply for jobs with nothing to attach. Ship something small first, then extend it. |
| Implying unpaid projects were paid client work | It surfaces in interview probing and reference checks, and it converts a credibility gap into a dishonesty problem. Label work plainly as self-initiated, volunteer or coursework. |
| Collecting certificates instead of finished work | Credentials show you covered material; a badge alone does not answer "what have you made?" Pair any course with one project that goes beyond its capstone. |
If the answer is no
If the portfolio is published and applications still go nowhere, treat it as a diagnosis problem rather than an effort problem, and work to a timetable.
- First 48 hours after a rejection: reply once, briefly, asking whether the gap was the portfolio, the experience level or the fit. Most will not answer. One in ten will, and that answer is worth more than a week of guessing.
- Week 1: re-read ten current ads for the role and mark every requirement your portfolio does not evidence. If the same tool or deliverable appears repeatedly and you have no sample of it, that is your next project, not a general "improve the portfolio" task.
- Weeks 2–4: replace your weakest project with one that has a real user, using the spoken script above. One project done for an actual person, with a named constraint and a result, usually outperforms two self-set exercises.
- Weeks 4–12: add a structured credential if a specific tool keeps blocking you. Google Career Certificates are designed for completion in three to six months at around ten hours a week (Grow with Google; ACT-IAC), and freeCodeCamp's eleven certifications are each designed around roughly 300 hours (freeCodeCamp, 2022), so plan the calendar before you pay or enrol.
- Months 2–3: change the channel, not just the content. Ask two practitioners for a review, contribute to an open project, volunteer with an organisation that needs the exact skill, or take small scoped work. Record every one of these on your master resume as you go, including the volunteering and activities entries CareerOneStop recommends.
- Months 3–6: widen the target. Look at adjacent titles — support, operations, coordinator, assistant and analyst variants of the same function — and at employers who hire in cohorts. Check the current duties, entry routes and typical requirements for those titles in an official source such as the BLS Occupational Outlook Handbook in the US, or your national labour market or careers service elsewhere.
- At six months: decide honestly whether the block is the portfolio at all. It may be location, sector hiring conditions, or right-to-work questions that no project fixes. For anything involving visas or employment law, get advice from an official government source or a qualified adviser rather than from forums.
Frequently asked questions
How much should I ask for if a portfolio project turns into paid work?
Decide the structure before the number. Small first jobs are usually priced either hourly, as a fixed fee for a defined deliverable, or as a day rate; fixed fees protect you from scope creep only if the scope is written down. For the number itself, look at what similar work is advertised at locally on job boards and freelance marketplaces, ask one practitioner privately what the floor is for junior work in your area, and check official pay data for the occupation — for example the BLS Occupational Outlook Handbook in the US, or your country's national statistics or careers service. Quote a range for anything vague, and put the deliverable, revision count and payment timing in writing.
How many projects do I need, and how long should each take?
Three to four is the usual working answer: one small piece that shows craft, one with a real user and real constraints, and one that shows the specific tool the job ads keep naming. Small pieces take a weekend to two weeks; a real-user project takes two to six weeks, mostly because other people are slow to reply. The spread is driven by how much you are learning as you build and how much the user changes their mind.
When should I start showing the portfolio — before it is finished?
Show it once one project is complete, documented and live. Waiting for all four keeps you out of the market for months. Add the rest in public, and put the strongest piece first, because reviewers rarely reach the bottom of the page. Do not publish a page consisting only of placeholders.
How do I follow up after asking someone to review my work?
Follow up once, after five to seven working days, and narrow the ask to a single question. If there is still no reply, stop and ask someone else — silence is usually workload, not judgement. When someone does reply, send a short note within two weeks saying what you changed. That is what turns a one-off favour into a contact who remembers you.
Is a paid certificate worth it, or should I just build projects?
Use a course when a specific tool keeps blocking you, and build projects to prove you can use it. Costs are published and modest per month rather than per course: ACT-IAC lists Google Career Certificates at $49 per month on Coursera after a seven-day free trial, and U.S. News & World Report lists the Google IT Automation certificate at $39 per month, or $234 for six months, while freeCodeCamp's eleven certifications are free and each designed around roughly 300 hours (freeCodeCamp, 2022). GMAC reports that three quarters of learners experience positive career outcomes after completing Google Career Certificates, but no programme guarantees a hire — check the current price, length and terms on the provider's own page before you enrol, since monthly pricing means slow progress costs more.
Sources
- Indeed — Portfolio vs. Resume: What They Include and When to Use Them
- The Interview Guys — How to Make a Portfolio Website That Actually Gets You Hired (2026 Guide)
- freeCodeCamp — freeCodeCamp Certifications (2022-03-17)
- Grow with Google (Google) — Professional Google Career Certificates - Grow with Google
- ACT-IAC — Google Career Certificates
- Community College of Philadelphia — Google Career Certificates
- U.S. News & World Report — What You Need to Know About Google Career Certificates
- GMAC — Are Google Career Certificates Worth It?
- CareerOneStop — Your master resume
- CareerOneStop — Resumes
- Medium (Steve Jones) — Hosting a Portfolio Website with GitHub Pages
