Is 40 too old to change careers?

No. At 40 you likely have 20-25 working years ahead - in many cases longer than you’ve worked so far - which is enough time for a full second career, not just a job change. What’s true is that switching at 40 should look different from switching at 25: instead of discarding your experience, switch into something that compounds it. The professionals who do this best pair their 15+ years of domain knowledge with a new technical skill, which makes them rarer - and often better paid - than either alone.

Can I learn to code at 40?

Yes - and the evidence is people, not pep talk: career-switchers in their late 30s and 40s learn to code and get hired regularly, including through our own programme. Age changes how you learn (less raw memorisation speed, better discipline and pattern recognition), and AI tooling has shifted the skill toward exactly what experienced adults are good at - judgement, precision, and directing work - rather than memorising syntax. Consistency of hours predicts success far better than age does.

Is 40 too old to become a software developer?

No, but be strategic about the entry. A pure junior-developer route works and people take it - though ageism at some employers is real, so target skills-first companies, remote roles, and portfolio-led applications. The stronger play at 40 is domain+code: entering tech through your existing industry (its vendors, its internal tools, its automation problems), where your experience is an advantage no younger developer can match rather than a CV anomaly to explain.

How do I change careers at 40 without going back to university?

Skip the degree route - at 40 the maths rarely works, and skills-first hiring means you usually don’t need it. The efficient path: test the field free for two weeks, then 4-6 months of structured part-time training (10-15 hours a week, keeping your income), then a portfolio of real projects aimed at your own industry. Structured programmes with mentorship compress the timeline; ours runs 12 weeks and is built to fit around a full-time job.

Should I switch careers at 40 or stay put?

Switch if your field is shrinking (check your role’s AI exposure honestly), if you’ve wanted out for years rather than months, and if you can fund the transition without touching your safety net. Stay - or upskill in place - if you mostly like the work and the problem is one employer, or if your role is durable and the itch is boredom rather than decline. At 40 the worst move isn’t switching or staying; it’s spending five more years deciding.

All posts

Career switching · Careers · Learning to code

Career switch at 40: harder than at 25, better armed than at 25.

The honest answer first: 40 is not too late - you likely have 20–25 working years left, enough for an entire second career. But switching at 40 should be done differently than at 25: not by discarding your experience, but by switching into something that compoundsit. Here’s the version with the fears taken seriously.

Deric Yee Updated 24 August 2026 10 min read

Most articles about changing careers at 40 are written like birthday cards - age is just a number!- and they don’t survive contact with a mortgage. If you’re 40 and reading this, you don’t need cheerleading. You need someone to take the objections seriously, do the maths honestly, and tell you what actually works - including the parts that are genuinely harder at 40. So that’s what this is. (If you’re closer to 30, we wrote that version separately - the maths is even more forgiving there.)

Start with the number that reframes everything. At 40, with retirement realistically at 60–65, you have 20 to 25 working years ahead of you. That’s longer than you’ve been working if you started at 23. Nobody looks at a 23-year-old and says “too late to build a career” - yet the 40-year-old with the same runway ahead, plus two decades of professional skill in the bank, talks themselves out of it. The runway isn’t the problem. The strategy is what changes.

The one-line strategy for 40:don’t start over - stack. A switch that throws away 15+ years of domain knowledge is a 25-year-old’s move. A switch that adds a scarce new skill on top of that knowledge makes you rarer, not junior.

The three fears, taken seriously

Each of these is partly true. Here’s what’s real, and the counter-move that works.

Ageism

Real, and pretending otherwise insults you. Some employers quietly prefer 25-year-olds they can underpay, and a 40-year-old career-switcher CV gets filtered by lazy recruiters.

The counter: The counter is to route around the filter: portfolio-first applications (work that speaks before your birth year does), skills-first employers and remote roles that hire on output, and the domain+code positioning below - where your 15+ years become the selling point instead of the liability. Switchers who lead with what they can build get interviews that CVs alone never would.

Money and obligations

At 40 there may be a mortgage, kids, ageing parents. A student’s "quit and figure it out" plan isn’t irresponsible at 40 - it’s unavailable.

The counter: So the plan is built around never dropping income: learning part-time at 10-15 protected hours a week while employed, switching only once the new field makes a real offer. It takes longer than the full-time route - months, not years longer - and it removes the scenario your family actually fears.

“Can I still learn this?”

The quiet fear underneath the other two: that a 40-year-old brain can’t absorb something as alien as code.

The counter: What we see in practice: 40-year-olds learn differently, not worse. Less raw memorisation speed, far better discipline, pattern recognition, and tolerance for frustration - which happen to be the skills that actually matter now that AI handles the memorisation-heavy parts. The learners who struggle most are rarely the oldest; they’re the least consistent, at any age.

The 40-year-old’s unfair advantage: domain + code

Here’s the argument this whole article rests on. A 25-year-old developer knows how to build software. A 40-year-old professional knows how an industry actually works - where the money leaks, which processes are broken, what the software vendors keep getting wrong. Almost nobody knows both. The person who does is not a junior anything - they’re a category of one.

And this combination just became dramatically more reachable. With AI handling much of the code generation, the years of grind that used to stand between a working adult and useful building ability have collapsed into months. What AI can’t supply is exactly what you have: judgement about what’s worth building and deep knowledge of a real industry. We’ve made the broader case in how to future-proof your career - at 40, it applies with interest.

What domain + code looks like in practice

Take your first career, add the ability to build:

Logistics / supply chain manager
Builds the routing and tracking automations their industry buys from vendors today - or joins the vendor, as the only person on the team who has actually run a warehouse.
Finance / accounting professional
Builds reconciliation and reporting tools with 15 years of knowing exactly where the numbers go wrong. Fintechs hire this combination on sight.
HR / operations lead
Automates the workflows they spent a career doing manually - and becomes the rare product person who knows how companies actually run inside.
Sales / business development
Builds their own tools, prototypes their own product ideas, and becomes the technical founder-type every non-technical salesperson wishes they were.

Can you actually learn to code at 40?

Yes - and we say that from watching it happen, not from optimism. Career-switchers well into their 30s and 40s go through our programme starting from zero: Amir Arif was a medical doctor and is now a presale architect at a cloud consultancy. Khor Chuan Nam was a mechanical engineer and is now a frontend developer at Liva Healthcare. Yuna Winaya ran operations and now builds software. Izzat Muzhaffarmanaged buildings and is now a frontend developer at Softinn. None of these are 22-year-olds with empty calendars - they’re professionals who learned around real lives.

What’s honestly different at 40: you memorise a little slower, and your hours are scarcer. What’s honestly better: discipline, pattern recognition from two decades of work, and the precision to direct AI tools well - which is where the job has moved anyway. The learners who fail aren’t the old ones; they’re the inconsistent ones, at every age. If the deeper question nagging you is “how long will this take,” the honest timelines are in how long does it take to learn coding - they apply unchanged at 40.

The switch plan that never drops your income

Built for someone with obligations. No resignation letters until there’s an offer.

Weeks 1–2
Test for free before telling anyone
No resignation, no payment, no announcement. Spend two weeks building small real things with free resources and notice honestly whether the work pulls you in. At 40 the cost of a wrong switch is higher - so the test matters more, not less.
Months 1–5
Part-time structured learning, income untouched
Roughly 10–15 protected hours a week around the job: early mornings, two evenings, a weekend block. Structure and mentorship matter more at 40 than at 25 - your hours are scarcer, so the wasted ones cost more. This is exactly the pace our part-time students run.
Months 4–6
Build in your own domain
Your portfolio shouldn’t look like a 22-year-old’s. Build tools that solve problems from your industry - the ones you’ve watched people struggle with for 15 years. That portfolio positions you as domain+code, not "junior, but older."
Months 6–9
Switch - or build sideways
Apply while employed, targeting skills-first companies, your own industry’s tech vendors, and remote roles. And know the second path: many 40-something switchers don’t take a junior job at all - they build automations or a product inside their field, as consultants or founders. At 40 you have the network for it.

The free first steps: the 2-minute Career Compass quiz for direction, and 6 Projects in 6 Days to test-drive building software for a week. If it’s a degree-shaped worry, the skills-first route is documented in becoming a software engineer without a degree.

When not to switch at 40

Honesty cuts both ways, so here’s the other side. If you fundamentally like your field and the misery is one employer - change employers; it’s ten times cheaper than changing careers. If your role is durable and well paid and the itch is restlessness, upskilling in place (including learning to build AI tools insideyour current role) may capture most of the upside with a fraction of the risk. And if the transition maths requires touching your family’s safety net - wait, save the bridge fund first, then move.

The way to decide with data instead of 2am anxiety: check how exposed your current role actually is with the free AI job-risk check, and read career change because of AI if the pressure you’re feeling is technological rather than personal. If you do decide to move, the 12-week AI-Native Software Development Programme is paced at 10–15 focused hours a week precisely so working adults can run it without resigning - and it carries a money-back guarantee, because a switch at 40 deserves a safety net.

FAQ

Is 40 too old to change careers?
No. At 40 you likely have 20-25 working years ahead - in many cases longer than you’ve worked so far - which is enough time for a full second career, not just a job change. What’s true is that switching at 40 should look different from switching at 25: instead of discarding your experience, switch into something that compounds it. The professionals who do this best pair their 15+ years of domain knowledge with a new technical skill, which makes them rarer - and often better paid - than either alone.
Can I learn to code at 40?
Yes - and the evidence is people, not pep talk: career-switchers in their late 30s and 40s learn to code and get hired regularly, including through our own programme. Age changes how you learn (less raw memorisation speed, better discipline and pattern recognition), and AI tooling has shifted the skill toward exactly what experienced adults are good at - judgement, precision, and directing work - rather than memorising syntax. Consistency of hours predicts success far better than age does.
Is 40 too old to become a software developer?
No, but be strategic about the entry. A pure junior-developer route works and people take it - though ageism at some employers is real, so target skills-first companies, remote roles, and portfolio-led applications. The stronger play at 40 is domain+code: entering tech through your existing industry (its vendors, its internal tools, its automation problems), where your experience is an advantage no younger developer can match rather than a CV anomaly to explain.
How do I change careers at 40 without going back to university?
Skip the degree route - at 40 the maths rarely works, and skills-first hiring means you usually don’t need it. The efficient path: test the field free for two weeks, then 4-6 months of structured part-time training (10-15 hours a week, keeping your income), then a portfolio of real projects aimed at your own industry. Structured programmes with mentorship compress the timeline; ours runs 12 weeks and is built to fit around a full-time job.
Should I switch careers at 40 or stay put?
Switch if your field is shrinking (check your role’s AI exposure honestly), if you’ve wanted out for years rather than months, and if you can fund the transition without touching your safety net. Stay - or upskill in place - if you mostly like the work and the problem is one employer, or if your role is durable and the itch is boredom rather than decline. At 40 the worst move isn’t switching or staying; it’s spending five more years deciding.

Back to all posts Closer to 30? Read that guide →

20 more years. Make them the good ones.
Start free, decide with data.

Test the water with 6 free projects in 6 days, check your current role's AI exposure, and if the maths says move - the 12-week AI-Native Software Development Programme is built to run alongside a full-time job, obligations and all.

See the programme Take the free career quiz