Can I get a developer job without a degree?

Many companies hire developers without degrees, especially for web and mobile roles, though some employers and visa routes do require one. Your resume's job is to make the evidence of your skill impossible to miss.

Should I write “self-taught” on my resume?

You don't need to. Your projects and experience show it. If you want to mention it, a cover letter or LinkedIn summary is a better place than the resume.

Do certifications help a self-taught developer?

A few relevant ones can help, especially cloud certifications for DevOps roles. They don't replace projects, so keep them short and near the bottom.

How do I say self-taught on a resume?

You usually don't need to. Let projects and experience speak, and list courses or bootcamps under Education. If you want to mention it, a phrase like “independent study in web development” in your education section works.

How do I add self-taught skills to my resume?

List them in your skills section like any other skill, and back each one with a project or job bullet where you used it. A skill with evidence counts the same however you learned it.

A resume for a self-taught developer with no CS degree

By Mubeen Jawed, founder of ResumeForDev · Updated November 7, 2026

Short answer

A self-taught developer's resume should lead with evidence of shipped work: Projects (and any freelance, contract or open-source work) go at the top, each with a tech stack, real users or a live URL, and specific bullets. Put a short Education section at the bottom listing whatever you have (another degree, a bootcamp, relevant certifications, or nothing) without apologising for it. Recruiters hiring self-taught developers are looking for proof you can build and ship, so every line should be concrete and checkable.

Key points

Projects or freelance work first, Education last.
Show users, a live link, a repository, or a client. Proof beats claims.
Treat freelance and open-source work as real experience, because it is.
Skip the summary that explains you're self-taught; let the work say it.

Section order without a degree

Header: name, email, phone, LinkedIn, GitHub, portfolio site.
Experience: any paid development work, including freelance, contract, agency or part-time.
Projects: two to four, each with a stack line and 1–3 specific bullets.
Technical Skills: grouped (Languages, Frameworks, Tools).
Education: a non-CS degree, bootcamp, or courses you finished, briefly. Leave it out if there's nothing relevant.

If you have no paid work at all, put Projects first and rename nothing. A clear “Projects” heading reads better than calling side projects “Experience”.

What makes a self-taught project convincing

Signals reviewers look for in self-taught developers' projects
Signal	Example
Real users	“Used by 140 members of a local climbing gym to book sessions”
Something deployed	A live URL, an app store listing, a published package
A non-trivial problem	Auth, payments, background jobs, real-time sync, caching
Code someone can read	A public repository with a README that explains decisions
Work for someone else	A site or tool built for a client, a non-profit, or a friend's business

Before and after

Before:Built an e-commerce website using the MERN stack.

After:Built and run the online store for a local bakery in React, Node.js and MongoDB with Stripe checkout, handling 300+ orders a month and replacing phone orders entirely.

Freelance or favour, it's real work with a real outcome.

Handling the education section

A degree in another field still counts. List it plainly.
Bootcamps: name, dates, and one line on the capstone if it's strong.
Online courses: only a few, only if finished, and only if relevant. A long certificate list looks like padding.
No formal education to list? Leave the section out. Nobody needs your high school on a developer resume.

Common mistakes

Listing tutorial projects (to-do app, weather app, calculator) as the main evidence.
A summary that says “passionate self-taught developer eager to learn”.
Listing 30 technologies after six months of learning.
Hiding the lack of a degree with vague wording. Confidence in the work reads better.

ResumeForDev's follow-up interview is useful here: it asks the questions that turn a side project into evidence, like how many people use it, what it's built with, and what changed because of it. Then it writes only from your answers. See also how to put GitHub projects on your resume.

Frequently asked questions

Can I get a developer job without a degree?: Many companies hire developers without degrees, especially for web and mobile roles, though some employers and visa routes do require one. Your resume's job is to make the evidence of your skill impossible to miss.
Should I write “self-taught” on my resume?: You don't need to. Your projects and experience show it. If you want to mention it, a cover letter or LinkedIn summary is a better place than the resume.
Do certifications help a self-taught developer?: A few relevant ones can help, especially cloud certifications for DevOps roles. They don't replace projects, so keep them short and near the bottom.
How do I say self-taught on a resume?: You usually don't need to. Let projects and experience speak, and list courses or bootcamps under Education. If you want to mention it, a phrase like “independent study in web development” in your education section works.
How do I add self-taught skills to my resume?: List them in your skills section like any other skill, and back each one with a project or job bullet where you used it. A skill with evidence counts the same however you learned it.