Without a degree you need to supply the evidence a degree was standing in for. That means demonstrable work someone can inspect, a way to prove your skills that does not depend on your history, and targeting employers whose process assesses ability rather than credentials.
- A degree is a proxy. Your job is to supply better evidence than the proxy, not to apologise for its absence.
- One substantial piece of work beats five small ones. Depth is legible; breadth reads as dabbling.
- Lead with what you built and what it does, not with your education section.
- Filter for employers whose process assesses skills — applying to credential-gated roles is not persistence.
- Answer the degree question in one sentence, without apology, then redirect to evidence.
The framing that helps
A degree requirement is a proxy. Employers use it because it bundles a few things they want — baseline reasoning, persistence through long structured work, sometimes specific knowledge — into one cheap signal.
That reframes your problem usefully. You are not trying to overcome a disadvantage or persuade anyone to make an exception. You are supplying better evidence than the proxy provides. A proxy is a guess; a demonstration is not. That is a strong position, and it is worth internalising, because the way you talk about this shapes how it is received.
Employers are also increasingly moving this way for their own reasons — see dropping the degree requirement. You are pushing on a door that is already opening in places. Your job is to find those places and arrive with evidence.
Build one thing that is genuinely substantial
The most common mistake is a portfolio of small tutorial-shaped projects. Five weekend projects read as dabbling. One thing with real depth reads as an engineer.
What makes a project count:
- It solves a real problem — ideally one you or someone you know actually had. Real problems have awkward constraints, and awkward constraints are where judgement becomes visible.
- It was maintained over time. Three months of commits, or a business run for a year, demonstrates exactly the persistence a degree was standing in for.
- It has users, even a few. Ten real users generate feedback, bugs and priority decisions that a tutorial cannot.
- It handles failure. What happens when the API is down, the input is malformed, the disk fills? This is the single clearest separator between hobbyist and professional work.
- It is documented. A README that explains the problem, the approach and the trade-offs demonstrates written communication — which most employers assess and few candidates evidence.
- You can explain every decision. This matters more than the code. Being able to say "I chose this because, and the cost was that" is what senior people do.
Non-software equivalents work the same way: a designer with a case study showing the problem, iterations and outcome; a marketer with a campaign and real numbers; a data analyst with an analysis of a public dataset that reaches a non-obvious conclusion; an operations candidate with a documented process they redesigned.
Restructure the document
Your CV is not obliged to lead with education.
Lead with Selected Work or Projects. For each: what it is, the problem, your decisions, the outcome, and a link. Two to four lines each. Put the strongest first.
Then experience, including non-linear paths. Retail, hospitality, warehouse, military, care work — these demonstrate reliability, pressure tolerance and customer judgement. Describe them in terms of responsibility and outcomes rather than apologising for them.
Then skills, using the vocabulary of the roles you are targeting.
Then education, brief and honest. If you did not finish, say what you studied and for how long. Do not omit the section entirely — a missing education section reads as concealment, and a reader who notices a gap fills it with something worse than the truth.
Formatting matters mechanically too: single column, standard headings, real text. See what actually happens to your résumé — and note that the two most common automatic rejections come from screening-question answers and parsing failures, neither of which is about your credentials.
Target deliberately
This is where most effort is wasted. Applying to roles with hard credential gates is not persistence; it is volume without a hypothesis.
Green flags in a job ad:
- "Degree or equivalent practical experience", and no degree in the requirements list
- A described assessment process — work sample, structured interview, skills test
- Requirements phrased as demonstrable abilities rather than years and credentials
- A published salary range and a clear first-quarter outcome
Red flags:
- A specific degree class or named institutions
- A long requirements list with no described assessment
- "Top-tier university" or "brand-name background" phrasing
- Regulated roles where the qualification is a legal precondition — respect these; they are not gatekeeping
Where to look: companies that publish their interview process; roles at companies whose product you can study and comment on intelligently; smaller companies where a hiring manager reads applications directly; platforms that assess skills before looking at background.
Also: apply early. Recency is a common sort order, and a strong application on day nine of a 400-application posting is at a structural disadvantage.
Handle the question in one sentence
It will come up. The mechanics of answering it well:
Short, factual, no apology. "I started working at nineteen and learned this on the job."
Then redirect to evidence. "Here's what I've built — happy to go as deep as you like on any of it."
Then stop talking. Long explanations signal that you think it is a problem, which invites the interviewer to treat it as one. A short answer plus a concrete offer closes the topic and moves to ground where you are strong.
What not to do: disparage degrees (defensive, and often insulting to the person interviewing you), volunteer it unprompted in the first minute, or over-explain the circumstances. Your gap is not interesting. Your work is.
Prove the skill independently
The strongest move available is evidence that does not depend on your history at all: a verified assessment of what you can do, obtained under conditions an employer trusts.
That inverts the whole dynamic. Instead of asking an employer to look past your background, you hand them the thing they were trying to infer from your background in the first place.
How CalHire is built for this
CalHire exists to remove exactly this problem:
- There is no education field in the evaluation. No degree input, and no résumé-match component in the score. Employers cannot filter you on a credential they never receive.
- You prove your skills once. One AI-generated, cheat-resistant assessment — a skills test plus a text interview — produces a verified composite score from test, interview and role-fit. Valid 90 days, retake-able after 30, and portable across every application on the platform. No re-testing per employer.
- You apply anonymously. Employers see your verified score and skills, never your name, photo, age, school or employers. You are ranked on ability alone under an opaque handle.
- Nothing is auto-rejected. Below-threshold applicants are flagged for human review; a person makes every decision.
- You always get an answer. Every application returns a growth-framed report card showing where you stood and the specific thing to improve — which, over a few applications, is a genuine development plan.
- Your identity is yours until you agree. It unlocks only when an employer advances you and you consent, for that one employer, logged immutably.
- It is free for candidates, always.
Start at for candidates, or read what skills-based hiring actually is for the employer's side of the same argument.
The practical summary: build one substantial thing, lead with it, prove your skills in a form that does not reference your past, and spend your applications on employers whose process will actually look. That is a strategy. Applying to 200 credential-gated roles is not.
Frequently asked questions
- Can you get a good job without a degree?
- Yes, and it is more achievable in fields where work can be inspected directly — software, design, data, sales, trades, operations, content. The constraint is not usually capability; it is that the standard application format asks for credentials, so you need an alternative form of evidence and employers whose process will look at it.
- What should I put on my CV instead of a degree?
- Lead with a projects or selected-work section: what you built, the problem it solved, the decisions you made, and the outcome. Add any verified skills assessments or certifications relevant to the role. Keep an education section, brief and honest — omitting it entirely reads as concealment, which is worse than a short line.
- How do I answer "why don’t you have a degree?"
- One sentence, no apology, then redirect to evidence. "I started working at nineteen and learned this on the job — here is what I have built, and I am happy to go as deep as you like on any of it." Defensiveness invites more questions; a short answer plus a concrete offer closes the topic.
- Are certifications worth it?
- Selectively. A recognised certification that employers in your target field actually list is a real signal, particularly in cloud infrastructure, security, networking and some regulated fields. Broad, unrecognised certificates are usually worth less than a single substantial piece of work someone can inspect. Check real job ads in your target market before paying for anything.