Junior Developer Resume With No Tech Experience: What Goes Where

List your coding training in one clear spot, then let your projects carry the weight. The training line explains how you got here. The projects get you the interview. Whether you learned through a bootcamp, an online course, a mentor or entirely on your own, a junior developer resume with no tech experience works the same way.

Key takeaways

• List your training in exactly one place: Education if you have no degree, Professional Training if you already have one.
• Your Projects section stands in for the tech job you haven't had yet. Put it above your previous career.
• Give each project 2–3 bullets that start with a verb you'd use in a standup ("Built", "Deployed", "Fixed"), never "Learned".
• Every project needs a working link, either a GitHub repo or a live deployed URL. A project a recruiter can't click is a project they won't believe.
• A certificate helps a little. Your projects decide the interview.
• Keep the whole thing to one page. For a career-changer with under two years of tech experience, that's always enough.

Should you put your coding training on your resume?

Yes. Every time.

I hear this worry from career-changers constantly. They think a bootcamp or course line marks them as "not a real developer," so they want to hide it and lead with projects alone. But hiring managers can already see you have no tech job history. Leaving the training off doesn't make you look more experienced. It leaves an unexplained gap right where your training should be.

The training line explains how you went from accountant or teacher or ops executive to someone who can build a full-stack app. That's a story, and recruiters like a story that makes sense.

Self-taught counts too. If you learned alone, you still have training to list. You just describe it differently, which we'll get to.

So the only real question is where it goes and how much space it gets.

Where each part goes, section by section

Your training touches four sections of the resume. Each one does a different job, so don't repeat yourself across them.

Education: if you don't have a degree

No university degree, or a diploma in something unrelated? Put your coding training in Education. It becomes your formal technical training.

EDUCATION
Full-Stack Web Development Bootcamp, <School>          Jan 2026 – Jun 2026

Learned through an online course or a mentor instead? Same slot, same format:

EDUCATION
Web Development, 1-on-1 mentorship with <Mentor or school>    2026
Python and Django, <Online course provider>                   2025

Program name, provider, dates. One or two lines, tops.

Professional Training: if you already have a degree

Got a degree in business, engineering or anything else? Keep the degree in Education and give your coding training its own section called "Professional Training" or "Certifications."

PROFESSIONAL TRAINING
Full-Stack Web Development, <Provider>                  2026

Your degree stays visible, and the coding training reads as recent, specialised training.

Don't list it in both sections. I've seen resumes where the same bootcamp shows up in Education, again in Certifications and a third time in the summary. It reads like padding, because it is.

Self-taught: list the work, not the hours

If you taught yourself, skip the made-up course title. Put a line in Professional Training that names what you studied and points at the evidence:

PROFESSIONAL TRAINING
Self-directed study: JavaScript, React, Node.js, PostgreSQL      2025 – 2026
4 deployed projects, 300+ commits: github.com/yourname

That second line does the work a certificate would. It's checkable.

Projects: where you actually win

This is the most important section on a career-changer's resume. Your Projects section stands in for the work experience you don't have yet.

For each project, include:

• The project name and one line on what it does
• The stack you used
• What you built, with a link

PROJECTS
Kedai Booking App · React, Node.js, PostgreSQL · live link · GitHub
  - Built table reservations with email confirmation for a real café
  - Cut page load from ~4s to under 1s by paginating the menu query

If you're short on strong projects, our guide to first coding project ideas that are actually doable will give you a few that look good on a resume without taking six months. And if everything you've built feels like a copied tutorial, work your way out of it first with escaping tutorial hell.

Free roadmap tool · 2 minutes

From learning to code to having work to show

Get a roadmap built around your goal and your week: the stage to focus on now, the projects that come next, and what you can safely leave for later.

• What to focus on right now
• What you can safely ignore for now
• A first project at your level
• A weekly plan that fits your time

Build My Free Roadmap

Free · About 2 minutes · No signup

Already learning? Check where your skills are or build a small app

Skills: written for the robots

Most companies run resumes through an applicant tracking system (ATS) before a human ever reads them. The ATS scans for keywords from the job ad. So your Skills section needs plain, scannable terms.

Group them:

SKILLS
Languages:    JavaScript, TypeScript, Python, SQL
Frameworks:   React, Node.js, Express
Tools:        Git, GitHub, PostgreSQL, Docker

The ATS gets exact keyword matches, and a human gets a two-second read of your stack.

One rule: only list what you could talk about in an interview. If you touched Docker once, leave it off. Someone will ask.

The section order that works

For a career-changer, the order of sections matters more than fonts or colours. Recruiters skim top to bottom and decide fast. Put your strongest material where their eyes land first.

Notice Projects sits above your previous job. That's deliberate. Your five years in logistics are real experience, but they aren't the experience this employer is hiring for. Lead with what matches the role.

Use a single-column layout. Fancy two-column templates with icons and skill bars look nice in Canva, then get scrambled by ATS parsers.

Do certificates help a junior developer resume?

A little. And "a little" matters more than it sounds.

Picture a recruiter with 200 applications for a junior developer role. They give each one a few seconds. Your resume says you spent six years in accounting, and nothing on it says "developer." A certificate is one line that explains the jump: you finished something structured, recently, in a modern stack.

Here's the part nobody explains clearly. A bootcamp or course certificate is usually not a government-recognised qualification like a diploma or degree. It's a private credential. Its value comes from the provider's reputation and the work you can show next to it.

What it doesn't do is pass the technical interview for you. Nobody in that room will ask to see the PDF. They'll ask why your useEffect runs twice, or how you'd structure a database for a booking app.

And it won't get you past a hard degree filter. Some large corporates, government-linked companies and multinationals screen out anyone without a degree before a human reads the resume. The US Bureau of Labor Statistics still lists a bachelor's degree as the typical entry-level education for software developers. The teams that hire career-changers, startups, agencies and product companies, mostly care whether you can do the work. They give take-home tests, and they read your GitHub.

So if you're paying for training partly for the certificate, check what's behind it first. The syllabus should match real job ads, you should ship deployed projects, and a human should review your code. This coding curriculum checklist shows what to look for.

How to describe your training on a resume

Here's the line most career-changers get wrong. It looks like this:

Learned HTML, CSS, JavaScript and React in an intensive 24-week program.

Almost everyone writes some version of it. It describes what happened to you. Employers want to know what you did.

Rewrite it around output:

Built and deployed four full-stack web apps using React, Node.js and PostgreSQL, with every pull request reviewed by a senior developer.

Same training. Completely different signal. The first sounds like a student. The second sounds like a junior developer.

Start every bullet with a verb

Built. Deployed. Designed. Refactored. Integrated. Fixed.

Then add what changed because of it. "Fixed a bug" is filler. "Fixed a race condition that double-booked tables when two people reserved at once" is a conversation starter in the interview. Never invent a number you can't explain, though. A made-up "improved performance by 40%" collapses the second someone asks how you measured it.

Your next step

Open your resume and move Projects above Experience. Then rewrite your first project bullet so it starts with a verb and ends with something a stranger can click.

Once it's ready, how to get your first developer job covers what to do with it. And if you'd like a working developer to review your resume and the projects on it, that's part of ZAM Academy's 1-on-1 mentorship.