How to Get a Job Without Experience (A Practical Guide That Actually Works)
By STEMLaunch Editorial Team · Updated 26 September 2026 · 9 min read
Fact checking: source-led editorial review
Everyone tells you to “gain experience” without telling you how. Here’s a real, step-by-step guide to landing your first job with no work history, including STEM roles that hire beginners.

Key takeaways
- Proof you can do the job. Experience is just the most common form of proof. But a portfolio, a personal project, a certification, or a volunteering role can provide the same proof if presented correctly.
- Proof you won’t need excessive hand-holding. Employers worry that hiring someone with no experience means months of training before they’re useful. Showing that you’re self-directed and can figure things out on your own directly addresses this.
- Proof you understand the role. A lot of applicants don’t actually know what the job involves day to day. Showing that you do, through research, industry knowledge, or relevant projects, immediately separates you from most of the competition.
- Tech and coding: build a small app, a website, or a script that solves a real problem. Put it on GitHub with a clear readme.
- Data and analytics: download a public dataset (Kaggle is full of them) and analyse it. Write up your findings. Publish it somewhere.
Getting your first job without experience is one of the most genuinely unfair parts of early career life.
You apply. You get rejected. The feedback, if you get any, says something like “we’re looking for someone with more experience.” You didn’t get the job because you haven’t done the job. Which is circular and unhelpful.
But here’s the reality: plenty of people get jobs every day with little or no work history. They do it by understanding what employers are actually looking for, and finding creative ways to demonstrate it.
This guide breaks down exactly how to do that. Step by step. No generic advice about “networking” and “being yourself.” Actual tactics that work.
What this guide covers
Why experience isn’t always what employers actually care about, how to build something that substitutes for it, where to look for roles that genuinely welcome beginners, how to write an application with nothing on your CV, how to perform in interviews when you have no examples to draw on, and the STEM-specific routes that make experience less of a barrier.
What employers actually want
When an employer says they want “experience,” what they usually mean is one of three things:
- Proof you can do the job. Experience is just the most common form of proof. But a portfolio, a personal project, a certification, or a volunteering role can provide the same proof if presented correctly.
- Proof you won’t need excessive hand-holding. Employers worry that hiring someone with no experience means months of training before they’re useful. Showing that you’re self-directed and can figure things out on your own directly addresses this.
- Proof you understand the role. A lot of applicants don’t actually know what the job involves day to day. Showing that you do, through research, industry knowledge, or relevant projects, immediately separates you from most of the competition.
Once you understand this, the strategy becomes clear: your job isn’t to pretend you have experience. It’s to provide alternative evidence of the same things experience would show.
Step 1: Build something before you apply
The single most effective thing you can do before sending a single application is to create something you can point to.
What “something” looks like depends on the field:
- Tech and coding: build a small app, a website, or a script that solves a real problem. Put it on GitHub with a clear readme.
- Data and analytics: download a public dataset (Kaggle is full of them) and analyse it. Write up your findings. Publish it somewhere.
- UX and design: redesign an existing app or website. Document your process. Explain the decisions you made.
- Science communication: start a blog, a YouTube channel, or a newsletter explaining something you find interesting. One good post is enough to prove you can do it.
- Engineering and technical roles: document a project you’ve built at home, whether that’s electronics, a vehicle repair, or anything physical. Photos, process notes, what you learned.
- Healthcare and support roles: volunteer at a care home, a hospital, a mental health charity, or a youth organisation. Even a few shifts provides something concrete to talk about.
The project doesn’t need to be impressive. It needs to exist. An employer who can see that you built something, anything, knows you’re the kind of person who does rather than waits.
Step 2: Get certified (strategically)
Certifications don’t replace a degree, but in a lot of STEM fields, they’re the fastest way to prove a specific, job-relevant skill to someone who’s never met you.
Some of the most employer-recognised free or low-cost certifications:
| Certification | Field | Cost |
|---|---|---|
| Google Data Analytics Certificate | Data / Analytics | ~$200 / £170 (Coursera) |
| Google Cybersecurity Certificate | Cybersecurity | ~$200 / £170 (Coursera) |
| Google UX Design Certificate | UX / Design | ~$200 / £170 (Coursera) |
| CompTIA A+ / Security+ | IT Support / Cyber | $250–$400 / £200–£320 |
| CS50 (Harvard, edX) | Computer Science | Free to audit |
| AWS Cloud Practitioner | Cloud / Tech | $100 / £85 (exam only) |
| freeCodeCamp Certifications | Web Development | Free |
Not sure which career to work towards?
Take our free 3-minute career quiz and get four STEM careers matched to your interests and strengths.
Take our career quizStep 3: Find the right places to apply
Not every employer is equally open to beginners. Focus your energy on the ones that are.
Apprenticeship programmes
These are specifically designed for people without experience. In the UK, US, Canada, and Australia, major employers in tech, engineering, healthcare, and science all run apprenticeships. You earn a salary from day one, receive structured training, and often come out with a qualification. They are genuinely underused by young people who don’t know they exist.
Startups and small businesses
Smaller companies often can’t compete on salary with large employers, so they compensate with flexibility and the willingness to take a chance on someone with potential. A startup that gives you responsibility early can build your portfolio faster than any graduate scheme.
Graduate schemes with degree-alternatives
Many large companies, including Google, Deloitte, PwC, and the NHS, now explicitly accept non-graduates into schemes previously reserved for degree holders. Check the eligibility criteria before assuming you’re excluded.
Volunteering and internships
Unpaid work is controversial for good reason, it favours people who can afford to work without pay. But even a few weeks of relevant volunteering gives you something real to talk about and someone who can vouch for you. Prioritise paid internships where they exist.
Remote roles
Remote work has opened up the job market significantly. You’re no longer competing only with people in your city, but you’re also now accessible to employers in cities and countries where your skills might be in higher demand.
Step 4: Write a CV that works without work history
A CV without work experience isn’t empty, it just needs to be structured differently.
- Lead with a strong personal statement. Two or three sentences explaining who you are, what you’re looking for, and what you bring. Be specific. “I’m a self-taught web developer with three projects on GitHub, looking for a junior role where I can build production experience” is infinitely better than “I’m a motivated individual seeking opportunities.”
- Put your projects and certifications front and centre. If you’ve built something or earned a certification, it goes near the top, not buried at the bottom under an empty work history section.
- Include education, even if it’s incomplete. Current studies count. Online courses count. Anything that shows you’re actively learning is relevant.
- List transferable skills with context. Don’t just write “communication skills.” Write “communicated complex information clearly to audiences of up to 30 people as a volunteer youth leader.” Context is everything.
- Keep it to one page. With limited experience, there’s no justification for two pages. One tight, well-structured page beats two pages of padding every time.
Step 5: Ace the interview without examples
Most interview questions ask for examples from your work history. When you don’t have one, you need alternatives. Here’s how:
Use personal projects as examples
“Tell me about a time you solved a difficult problem.” Your answer can be about debugging your first app, figuring out why your data analysis was returning incorrect results, or working through a tricky chemistry problem in your studies. It doesn’t need to be from a paid job.
Use hypothetical situations thoughtfully
Some interviewers accept “I haven’t faced this situation at work, but here’s how I’d approach it.” This works if your answer is specific and well-reasoned. Don’t use it as a fallback for every question.
Show that you know the role inside out
Research the company, the team, the tools they use, the problems they’re trying to solve. Candidates who clearly understand what the job involves are taken more seriously than those with more experience but less curiosity.
Ask good questions
The questions you ask at the end of an interview reveal more about you than most of your answers. Ask about how the team works, what success looks like in the first three months, and what challenges the role is trying to solve. Don’t ask about salary in a first interview.
The STEM-specific advantage
STEM fields have something that a lot of other industries don’t: a culture of building things. In tech especially, a strong portfolio consistently beats a polished CV. In science and engineering, apprenticeships and on-the-job training routes are well established and genuinely accessible.
If you’re aiming for a STEM career, the experience barrier is lower than in many other fields, provided you’re willing to put in the self-directed effort to build something worth showing.
The jobs are there. The routes in are real. The question is just whether you’re going to start.
The bottom line
Getting a job without experience is genuinely possible. But it requires a different approach than sending out CVs and hoping for the best.
The short version
- Build something before you apply
- Get certified in something specific and relevant
- Target employers who are open to beginners: apprenticeships, startups, remote roles
- Write a CV that leads with what you’ve built, not where you’ve worked
- In interviews, replace work examples with project examples and show you know the role inside out
None of this is easy. But none of it requires experience you don’t have yet.
Read next on STEMLaunch
Get practical STEM guides in your inbox
Sign up to the STEMLaunch newsletter for honest, practical guides to getting started in STEM, wherever you are in the world.

About the STEMLaunch Editorial Team
STEMLaunch is an independent UK careers education publication. Our editorial team researches career routes, qualifications and pay using official and primary sources.
Get Weekly Insights
Fresh UK STEM career guides, routes and opportunities, delivered once a week.
Free · No spam · Unsubscribe anytime
Related Articles
Further reading and useful tools
- Institute for Apprenticeships standards ↗Every approved apprenticeship standard and its level.
- Find an apprenticeship (GOV.UK) ↗Official search for live UK apprenticeship vacancies.
- National Careers Service job profiles ↗Government profiles with pay, hours and entry requirements.
- Browse all STEM career guidesEntry routes, pay and qualifications, by topic.


