How do I get a software job without a CS degree?
Learn one path well, build a few real projects that other people use, and write directly to the engineering managers who hire. Plenty of working developers don't have a computer science degree. It's still a hard market for beginners, so your goal is to give someone clear evidence that you can do the work.
Be honest about the market
Entry-level software hiring has been tough, and AI is changing what junior developers do. Here's what the evidence says about how AI is changing software engineering jobs.
That doesn't mean you can't do it. It means a course certificate alone probably won't be enough, and it may take longer than ads for bootcamps suggest. Be careful with any program that promises a job, and read the fine print before you pay.
Pick one path
Don't try to learn everything. Choose one direction and stay with it long enough to get good:
- Web development: JavaScript or TypeScript, plus a common framework.
- Backend: Python, Java or Go, along with databases.
- Data engineering or analytics: SQL and Python.
- Mobile: Swift or Kotlin.
- QA or test automation: often a realistic way into a software team.
Look at twenty job posts near you and see which skills keep appearing. Let that guide you.
Learn the fundamentals too
Skills that matter regardless of language:
- Using Git and working from a shared codebase.
- Databases and basic SQL.
- How the web and APIs work.
- Reading other people's code and debugging it.
- Basic data structures and algorithms, which many interviews still test.
Use AI tools as you learn, since most teams do. But make sure you can explain every line you submit. If AI wrote it and you can't explain it, you haven't learned it yet.
Build things people actually use
One useful project beats ten tutorial clones. Look for a real problem:
- A scheduling tool for a friend's business.
- A small app for your community group.
- An automation for a tedious task at your current job.
- A fix or improvement to an open source project.
Put it online, write a clear README, and be ready to explain what you chose, what broke and what you'd change. Here is how to choose projects to show.
Use your previous career
Your background can be what sets you apart. A former accountant building finance tools, or a nurse working on healthcare software, understands the problem in a way other junior developers don't. Look for software companies in the world you came from. Here is how to move your skills into a different industry.
The easiest move may be inside your current company. Offer to automate something or help the technical team, and ask about an internal transfer.
Write your resume around proof
Put projects and skills near the top. You don't need to apologize for your education. A made-up example:
"Self-taught backend developer and former logistics coordinator. Built a shipment tracking tool in Python and PostgreSQL now used daily by a four-person team."
Only claim what's true, because technical interviews will test it.
Reach out directly
An application without a degree can be filtered out before a person ever reads it. A note to an engineering manager gets around that:
"Hi Priya, I spent six years in logistics before moving into software. I built a shipment tracker my old team still uses, and I saw your company works on freight data. Could I show you what I built? I'd value your honest take."
The name and details are made up. Here is how to email an engineering manager. You can also see who's hiring in engineering.
Consider stepping stones
Your first technical role may not have "software engineer" in the title. Support engineer, QA, implementation specialist, data analyst or IT roles can all get you closer. Smaller companies and startups may also care less about credentials.
Stay in it
Practice coding interviews regularly, keep building, and keep talking to people. A career change like this usually takes a while. If you need income in the meantime, keeping your current job while you learn is a perfectly good plan.