How to Get Experience When Every Job Requires Experience

To get experience when every job asks for it, create work that looks like the job before anyone hires you: projects for real users, freelance or contract gigs, internships, apprenticeships, volunteering, open source or a small side business. Then present it as evidence, with links and results. Many "2 to 3 years required" lines are softer than they read.

Definition: The experience paradox is the loop where you need a job to get experience and experience to get a job. In practice, employers want proof that you have done the core tasks before, under real conditions. Years on a payroll are only one way to show that.

Why every job seems to require experience

It isn't your imagination. The bottom rung has narrowed, and by Indeed's data tech is one of the places it narrowed most.

Indeed Hiring Lab, which treats entry level as roughly 0 to 1 years, found entry-level postings down 7.5 percent year over year as of May 2026, while senior postings were up 13.5 percent versus January 2025. In the first quarter of 2026, entry-level roles were 91.3 percent of postings in personal care and home health, and 4.5 percent in software development.

A separate Indeed Hiring Lab analysis found only 18 percent of US tech postings that mentioned experience were open to people with a year or less in the second quarter of 2025, while the share asking for five or more years rose from 37 to 42 percent since mid-2022. Other occupations eased over the same period.

Then add volume. Ashby's 2026 recruiter productivity report, built on about 109 million applications from January 2021 to March 2026, found applications per hire roughly tripled from 2021 to 2024 and stayed above 300 on average through 2025. With 300 resumes in the pile, years of experience is the quickest filter a recruiter has.

New graduates feel it most. The New York Fed put unemployment for recent college graduates (ages 22 to 27) at about 5.6 percent in the second quarter of 2026, with 42 percent underemployed.

The door isn't shut. But a resume with only coursework on it now competes with resumes that show work.

What "2 to 3 years of experience required" really means

Read a requirement as a question, not a rule. Behind "2 to 3 years" there is usually one question: has this person done the main tasks, without hand-holding, where mistakes had consequences?

Years are a proxy for that. If you can answer the question another way, many hiring managers will listen.

Some investors are nudging their startups the same way. Nate Hirsch, head of talent at Pear VC, argued in a 2026 post that AI coding tools have shrunk the premium once paid for two to four years of execution experience, and that early teams should screen new grads for how fast they grow rather than what they already know. One way to sort a posting:

Hard requirements: licences, clearances, work authorization, degrees in regulated fields. These rarely flex.
Core skills: the three or four tasks the description keeps returning to. Point your proof here.
Wish-list items: years, long tool lists, nice-to-haves. These often flex for a strong candidate, especially at startups.

Should you apply if you don't meet every requirement?

In our view, often yes: if you meet the hard requirements, can prove most core skills and are within shouting distance of the years asked. Eight years asked against zero is a different job.

A myth tags along here. You may have seen the line that men apply at 60 percent of the qualifications and women only at 100 percent. Tara Mohr's 2014 Harvard Business Review article traced it to a Hewlett Packard internal report, which, as far as we can find, has not been made public. So treat the exact numbers as folklore. In Mohr's own survey of more than 1,000 professionals, only about 10 percent of women and 12 percent of men said their top reason for not applying was doubting they could do the job.

Behavioral data is stronger. LinkedIn's 2019 Gender Insights report, built on 2018 member activity, found women were 14 percent less likely than men to apply after viewing a job, yet 16 percent more likely to be hired once they did apply. Our read for everyone: self-screening costs people interviews they could have won.

How to get experience with no experience: ten ways that count

You don't need all ten. Two or three that match your target role usually change how a resume reads.

1. Build a project for a real user

Build a dashboard for a club's finances or a small app that saves a friend's shop an hour a week, then write one page on the problem, what you built and what changed. The real user is what turns practice into experience. Paul Graham makes a related point in his 2023 essay How to Do Great Work: ambitious work often starts as a project of your own, not an assignment someone handed you.

2. Freelance small, paid gigs

Two or three paid jobs, from a marketplace or your network, give you clients, deadlines and a reference. A lower price can win the first reviews. Paid work also answers the quiet question behind most requirements: has anyone trusted you with real stakes?

3. Take contract or temp work

Contract roles, agency placements and fixed-term jobs are often less picky than permanent roles because the commitment is smaller. Three months of QA testing or data cleanup at a software company is experience in every sense a recruiter means it.

4. Volunteer with a scope and a result

Volunteering counts when it looks like work: a defined project, a deliverable, someone who can vouch for you. A 2013 study by the Corporation for National and Community Service (now AmeriCorps) found unemployed people who volunteered had 27 percent higher odds of being employed a year later. That is a correlation, not proof of cause.

5. Get an internship, at any age

Internships are probably the most recognized pre-job experience, and many convert. NACE's 2026 Internship and Co-op Survey found employers converted 63.1 percent of their 2024 to 2025 interns into full-time hires, the highest rate in five years. Some companies also run returnships for adults. Our guide on how to get a tech internship covers timelines and where to look.

6. Join an apprenticeship

Registered apprenticeships pay you while you train. Per a 2025 US Government Accountability Office report, about 940,000 people took part in fiscal year 2024, and completers earned about $80,000 on average in their first year after finishing (April 2022 to March 2023 data). Construction dominates, but IT and cybersecurity apprenticeships exist.

7. Contribute to open source

A merged pull request is public, timestamped and reviewed by strangers, about as verifiable as experience gets. Start with docs, tests or newcomer-tagged issues in a tool you use. Three merged contributions to one project read better than one each in ten.

8. Run a small side business

Selling anything teaches pricing, service and marketing at once. A side business with $3,000 in a year and twelve repeat customers is a strong story for sales or operations roles. Be honest about its size; the scrappiness is the point.

9. Stretch inside the job you already have

The cheapest experience is often at your current employer. Take the analytics project, automate a report, join the product team's planning. Internal transfers also tend to care less about years because the hiring manager can ask your boss.

10. Do a work sample for a company you want to join

Do a small, useful piece of a target company's work unasked: an onboarding teardown, three support macros, an account plan for one prospect. Send it to someone on the team with a two-line note. Startups tend to respond well, in our view; some offer a paid trial. Our guide on how to get a job at a startup goes deeper on that route.

Which experience counts most for your target role?

Here is how we'd compare the main routes. The ratings are our view, not data.

Route	Time to first result	How credible to screeners	Best for
Internship or apprenticeship	2 to 6 months, recruiting cycles apply	High	Students, career starters, trades and IT
Freelance or contract	Weeks	High if paid and referenced	Design, writing, marketing, QA, data
Project for a real user	3 to 6 weeks	Medium to high with a write-up	Engineering, data, product
Open source	Weeks	High for technical roles	Engineering, technical writing
Volunteering or side business	Weeks to months	Medium, rises with results	Operations, marketing, sales, nonprofit

A useful test: could a stranger check it in five minutes? A link, a reference or a merged commit passes.

How to present experience you created yourself

Give it a real section. A Relevant Experience or Projects and Freelance heading can sit above unrelated jobs, near the top where skimmers look.

Write it like a job. Role, organization, dates and two or three bullets with results. Freelance Data Analyst, self-employed, is fine if it is true.

Lead with outcomes, not effort.

Weak: "Learned SQL and built a dashboard."
Stronger: "Built a sales dashboard in SQL and Looker Studio for a 6-person bakery; owner now reviews weekly margins in 10 minutes instead of 2 hours."

Link everything. Portfolio, repository, live app or client testimonial.

Don't inflate. Calling a class project an internship can unravel in one reference check. Honest framing of small things beats big claims that crack. For layout and templates, see our sibling guide on how to write a resume with no experience.

A worked example: from no experience to a credible application in 90 days

An illustrative plan for a junior data analyst target with about 10 hours a week.

Weeks 1 to 2 (20 hours). Read 30 recent postings and list the four core skills that repeat most (say SQL, spreadsheets, a BI tool and written summaries).

Weeks 3 to 6 (40 hours). Build a dashboard for a local nonprofit's donor data, with a one-page memo and a reference from them.

Weeks 7 to 10 (40 hours). Land two small paid freelance analyses through your network or a marketplace. Even modest fees prove someone paid for the work.

Weeks 11 to 13 (30 hours). Rebuild the resume around those three pieces and apply to 8 to 10 matched roles a week, each with a short note.

That is 130 hours over 13 weeks, ending with one project with a named user, two paid engagements and a reference: roughly what a screener means by some experience for a junior role. To find roles at that level, filter the 1752vc careers board by Entry level and Past 7 days, and apply while postings are fresh.

"Unpaid work is just free labor"

It's a fair objection. Unpaid internships and endless trial projects can be exploitative, and they favor people who can afford to work for nothing.

The law draws some lines. The US Department of Labor's Fact Sheet 71 applies a seven-factor primary beneficiary test to unpaid internships at for-profit companies, including whether the work displaces paid staff and whether it ties to education. Volunteering for public sector and nonprofit charitable organizations is generally permissible.

But.

Creating experience doesn't have to mean donating labor to a company that profits from it. Most of the ten routes are paid or are work you own. Where you do give time free, we'd keep it short, scoped and yours: a deliverable you can show, not open-ended hours.

Common mistakes

Collecting courses instead of output. Certificates show you studied, not that you shipped.
Self-rejecting on years. If you meet the hard requirements and can prove the core skills, apply.
Hiding non-tech work. Managing a store or running events shows judgment; translate it into results.
Applying to stale postings. A thin resume has better odds on fresh roles. The 1752vc careers board shows each employer's own posting date, so you can sort by newest and skip old listings.

Where we land

The experience requirement is real, and in tech it has tightened. In our view it is mostly a request for evidence, and evidence is something you can make.

Our suggestion: one target role, two or three routes that fit it, and about three months to turn them into results a stranger can check. Then apply early, with a note. That's our answer, not the only one; your field and finances will shape which routes fit. If you are aiming at tech specifically, our sibling guide on how to get a tech job with no experience maps the roles that hire beginners, and how to get a job in tech covers the wider search.

The bottom line

Nobody hands out the first year of experience.

You build it on the side, then hand it to them.

Key takeaways

Entry-level tech postings are scarce (4.5 percent of software development postings in Q1 2026, per Indeed Hiring Lab), so proof of work matters more.
"2 to 3 years required" usually means "show me you've done the core tasks"; years are one proxy, not the only one.
Ten routes create credible experience: real-user projects, freelance, contract work, volunteering, internships, apprenticeships, open source, a side business, stretch work in your current job and work samples.
Pick two or three routes that match one target role and aim for results a stranger can verify in five minutes.
Present created experience as real work with dates, outcomes and links, and don't inflate titles.

Frequently asked questions

How do you get experience when every job requires experience?

Create work that resembles the job before you are hired. Freelance gigs, contract roles, internships, apprenticeships, volunteering with a defined deliverable, open source contributions and projects built for real users all count. Choose two or three that match your target role, aim for verifiable results, and list them on your resume as real experience with dates, outcomes and links.

Should I apply if I don't meet the years of experience required?

Often, yes. Years of experience are usually a proxy for having done the core tasks, so if you meet any hard requirements (licences, work authorization) and can show proof for most core skills, applying is reasonable. LinkedIn's 2019 data suggests holding back costs people chances: women applied less often after viewing jobs, yet were hired at higher rates once they did apply.

Does volunteer work count as work experience on a resume?

Yes, when it looks like work. List it like a job, with your role, the organization, dates and results, and put it under a heading such as Relevant Experience if it matches the role. A defined project, a measurable outcome and a supervisor who can vouch for you make volunteer work far more convincing to a recruiter.

How do I find a job when I have no experience at all?

Start with roles that genuinely hire beginners, such as support, sales development, operations, apprenticeships and internships. Build one or two pieces of proof for the role you want, apply to fresh postings within days of their going up, and send a short note to someone on each team. Referrals and direct outreach tend to get a thin resume read.

Do personal projects count as experience for entry-level jobs?

They can, especially for technical, data, design and product roles. A project counts more when it has a real user, a clear problem, a write-up of your choices and a measurable result. Tutorial clones and unfinished repositories count for little. Put the strongest project near the top of your resume with a link a recruiter can open.

Sources

Disclaimer: This guide is for general education only and is not legal, tax or investment advice. Laws, market data and program terms change, so it may not reflect the latest developments or fit your situation. Treat it as a starting point, not a source of truth, and talk to a qualified lawyer, accountant or financial adviser before you make decisions.