Yes, but it is the harder version of the switch, so plan for twelve to eighteen months of steady work and a first role that may not be glamorous. Without a degree, your proof has to be stronger: real projects, a clear specialism, and a route in that uses the experience you already have.
What people tell me
I am around 30, I never finished a degree, and I have worked for years in a job that has nothing to do with software. I have been learning to code in the evenings and I enjoy it, but every job post seems to ask for a computer science degree, and I see much younger graduates struggling to get hired. I have financial responsibilities, so I cannot quit and study full time. I want to know whether this is realistic or whether I am fooling myself.
A composite of the messages behind this question, with personal details left out.
Key takeaways
- It is realistic, but expect twelve to eighteen months at steady part-time hours, not a quick change.
- Without a degree, projects and public proof carry more weight, so build fewer, stronger ones.
- Your previous career is an asset: target software for an industry you already know.
- Keep your income while you learn; switch when you have an offer, not before.
- Some employers and visa routes do require degrees; check before you target them.
Two questions, one answer
People usually ask two separate things: am I too old to start, and can I get in without a CS degree. Each has its own page. When both apply at once, the honest answer is still yes, but the path needs more planning, because you have less room for trial and error and fewer default doors.
What is working against you
Let me be straight about the obstacles, because pretending they do not exist is how people lose two years:
- Screening filters. Some employers, especially large enterprises and some government and banking roles, require a degree. You will be filtered out of those automatically.
- Visa routes. If you hope to work abroad later, many work visas are much easier with a degree. Check the rules of any country you care about before planning around it.
- Competition. At entry level you compete with graduates who have internships and university networks.
- Time and money. At 30 you often have rent, family or other commitments, so a full-time study gap is risky.
What is working for you
- You have worked. You know how to show up, handle deadlines, communicate with clients or managers, and deal with pressure. Many graduates do not.
- Domain knowledge. Years in logistics, healthcare, retail, finance, teaching or anything else is valuable to companies that build software for that industry.
- Focus. Adults who switch tend to be deliberate. You are not learning to pass an exam.
- Many employers now hire on skills. Plenty of startups, agencies and product companies care about what you can build more than where you studied.
A realistic plan
| Phase | Months | Goal |
|---|---|---|
| Foundations | 1 to 4 | One language properly, Git, HTTP, SQL. The programming roadmap covers this order |
| Specialise | 4 to 8 | One direction, usually web or backend, where junior openings are most common. Try the full stack roadmap |
| Proof | 6 to 12 | Two real projects, one of them for the industry you know |
| Search | 10 to 18 | Targeted applications, referrals and freelance or contract work |
At eight to twelve hours a week alongside a job, this is a twelve to eighteen month path for most people. Some move faster; many take longer. Plan for the longer end and be pleasantly surprised.
Use your past, do not hide it
The strongest move for a career switcher is to combine old and new. If you worked in a pharmacy, build an inventory or prescription tracking tool. If you worked in sales, build a small CRM or reporting dashboard. Then apply first to companies that build software for that industry. You become "the developer who understands our customers", which no fresh graduate can claim.
Look through the companies directory for employers in your old industry, and the FYP ideas library for scoped project problems you can adapt.
Ways in that do not need a degree
- Internal moves. If your current employer has a tech team, ask about automation or tooling work. It is often the easiest first step.
- Freelance and small contracts. Small paid projects for local businesses build a portfolio and references.
- Adjacent roles. QA automation, technical support, implementation and data roles can lead into development.
- Apprenticeships and returner programmes, where they exist in your country.
Protect your income
Do not quit your job to study unless you have savings for at least a year and a clear plan. The switch works best when you keep working, learn in fixed evening and weekend slots, and resign only after signing an offer.
If you are still stuck
Read how do I learn to code while working a full-time non-tech job. If you want a plan that fits your hours and your past experience, join Sefism and, as a member, book a 1:1 session.
Was this answer helpful?
Read next
- Moving Into Tech From a Commerce Degree: Which Paths Actually PayTech jobs for commerce graduates that actually pay: data analyst, business analyst, ERP consultant and fintech roles compared, a six month data analyst plan, finance portfolio ideas and how to switch without quitting.
- How to Start Your Career as a Software EngineerHow to start a career in software engineering in 2026: pick one language, build past the tutorial, learn five fundamentals, get real feedback and apply earlier than you feel ready. With a twelve month plan and an honest market read.
Your situation is not quite this one?
Members get written answers to their own questions, a roadmap built for them and feedback on their projects. Early access is open: sign up and your account is active shortly after. Prefer to talk? A free call works too.