Should I remove my old jobs from my resume?

No. Keep them with dates and rewrite the bullets around transferable work. Removing them leaves a gap that needs explaining.

Do I need a CS degree to become a software engineer?

Many companies hire engineers without one, and deployed projects and a clear story carry the most weight on the resume. Some employers do still filter by degree.

Should I list a bootcamp under Education?

Yes, with the dates and the main project you built there.

What should a career change resume summary say?

What you do now in tech, your stack, and one concrete result, then the past career as a strength. For example: “Software engineer moving from 6 years in logistics. Builds full stack TypeScript apps; automated reporting now used by 40 staff.”

Should a career changer use a resume objective?

A short summary works better than an objective because it leads with what you offer. If you use an objective, keep it to one line and pair it with proof. More in resume summary examples.

How to write a career change resume for software engineering

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

Short answer

Lead with proof that you can build software, and treat your past career as a strength. Put a two-line summary at the top saying what you're moving into, then Projects above Experience: two or three deployed projects with links, stacks and numbers. Keep your previous jobs, but rewrite the bullets around the work that transfers, such as automation you built, data you analyzed or tools you set up. Knowledge of your old field counts for a lot at companies in that field.

Key points

A two-line summary is worth it here because it explains the switch.
Put Projects above Experience until you have a tech role.
Rewrite past jobs around technical, transferable work.
Aim at companies in your old industry, where your domain knowledge counts.

Section order for career changers

Header with GitHub and portfolio links
Summary: two lines on your new direction and your background
Projects: two or three deployed, with links and numbers
Technical Skills
Experience: your previous roles, rewritten
Education, including any bootcamp or certificates

Rewriting your old job for tech

Most careers include work that's closer to engineering than it looks: spreadsheets you automated, reports you built, systems you configured, processes you documented. Bullets about that work show you solve problems with tools, and reviewers notice.

Before and after

Before:Managed inventory for three warehouse locations.

After:Wrote Python scripts and Google Sheets automations that reconciled inventory across 3 warehouses every night, replacing about 6 hours of manual counting a week.

Same job, but the bullet now shows code, a system and a result.

A summary that explains the switch

Most developers should skip the summary. Career changers are the exception, and two lines are enough:

Projects that prove you can ship

Pick projects that look like real work: deployed, used by someone, with tests and a README. A project that solves a problem from your old field is the strongest kind, because you can talk about its users and domain in depth. See how to put GitHub projects on a resume and a resume for a self-taught developer.

ResumeForDev asks follow-up questions about each project and past role, then writes bullets from your answers, so transferable work is described in technical terms without inventing anything.

Frequently asked questions

Should I remove my old jobs from my resume?: No. Keep them with dates and rewrite the bullets around transferable work. Removing them leaves a gap that needs explaining.
Do I need a CS degree to become a software engineer?: Many companies hire engineers without one, and deployed projects and a clear story carry the most weight on the resume. Some employers do still filter by degree.
Should I list a bootcamp under Education?: Yes, with the dates and the main project you built there.
What should a career change resume summary say?: What you do now in tech, your stack, and one concrete result, then the past career as a strength. For example: “Software engineer moving from 6 years in logistics. Builds full stack TypeScript apps; automated reporting now used by 40 staff.”
Should a career changer use a resume objective?: A short summary works better than an objective because it leads with what you offer. If you use an objective, keep it to one line and pair it with proof. More in resume summary examples.