Changing career to tech at 40.
In our own records, 8% of the people who enrol and pay are 40 or over and the oldest is 62. You would be a minority in the room, not an anomaly. Here is what the switch actually costs at this age, and why the usual route is the wrong one for you.
Students aged 40+
8%
20% are 35 or over
Time to first offer
9–14 mo
Part-time, from zero
Junior pay
RM 3.5k–9k
The dip is bigger at 40
The distribution
A minority, and not a rounding error.
Age distribution of enrolled, paying students in our own records (n=130 of 553 with an age recorded).
| Age band | Students | Share |
|---|---|---|
| Under 25 | 38 | 29% |
| 25 to 29 | 37 | 28% |
| 30 to 34 | 30 | 23% |
| 35 to 39 | 15 | 12% |
| 40 and over | 10 | 8% |
Pages like this usually open with reassurance. A distribution is more useful. 8% of the people who enrolled and paid are 40 or over, and 20% are 35 or over. The oldest is 62, and at the application stage the range runs to 67.
Read that honestly in both directions. You would not be the oldest person anyone has seen do this, and the idea that retraining is something only 22-year-olds attempt is plainly false. But you would also be in the smallest band on the table, which means the standard advice was not written for you. That is the actual problem with switching at 40, and it is a strategy problem rather than a capability one.
The rest of the picture holds across every age band: 68% came from a job outside technology and 56% had never written a line of code when they paid. Starting from zero is the normal case here. Starting from zero at 40 is the less common case. Those are different statements and only the second one is about you.
Methodology, definitions and the underlying counts are in our research on career switchers. We publish composition data only, and no placement or employment-outcome figures.
The costs
Three constraints that are genuinely harder at 40.
None of these are about whether you can learn. All three are about what the switch costs you specifically, and all three are worse at 40 than at 25.
- The pay dip is bigger. Junior bands run roughly RM 3,500 to RM 9,000 depending on employer type, and that is the band a genuine career changer enters at whatever their previous seniority. Falling into it from a 40-year-old salary is a much steeper drop than falling into it from a graduate one, and at 40 there are usually dependents attached to the difference.
- Time is the binding constraint. In our application data, 75% of people say they have under 25 hours a week available. At 40 that number tends to be lower and less predictable than at 25, because it is competing with a mortgage, children and a job that already has a claim on your evenings.
- Hiring bias is real in one specific place. It shows up most in high-volume junior hiring, where a recruiter screening hundreds of near-identical applications defaults to the cheapest and most available candidate. It is much weaker where a domain is required, in smaller teams hiring for judgement, and in internal moves.
Notice that the third constraint is not evenly distributed. It concentrates almost entirely in one route, which happens to be the route most career changers default to. The single highest-leverage decision at 40 is refusing to enter as a generic junior.
The strategy
Do not reset. Combine.
Four ways in, ranked by how well they use what a 40-year-old already has.
| Route | What it looks like | Fit at 40 |
|---|---|---|
| Generic junior applications | Compete against 22-year-olds on price and availability | Weakest at 40 |
| Internal move | Become the technical person in the team you already work in | Cheapest and fastest |
| Domain-first switch | Build software for the industry you already understand | Strongest at 40 |
| Adjacent technical roles | Solutions engineering, technical PM, automation, internal tooling | Underrated |
The mistake is treating a career change as a reset: erasing 15 or 20 years of accumulated knowledge and starting again at the bottom of a queue, competing on the exact dimension where you are weakest. A 22-year-old has time and price on their side. You have something they cannot acquire for two decades, which is a deep understanding of how some real industry actually works.
Software is overwhelmingly built for industries by people who do not understand them. Insurance, logistics, manufacturing, clinics, construction, education, property, agriculture: every one of these has software that is bad in ways that are obvious to a practitioner and invisible to a developer. Someone who has spent 15 years inside the domain and can also build is a genuinely rare combination, and it is priced as one.
The cheapest version of this is the internal move, and it is consistently underrated. You already have the domain, the relationships and a reputation for delivering. Becoming the person in your department who automates the reporting, builds the internal tool, and wires the systems together converts all of that into a technical role without a job search, without a competitive junior process, and frequently without a pay reset. Many people who set out to change careers end up changing jobs instead, and are better off for it.
The plan
What the year actually looks like.
Assume you keep working. Almost everyone in this population does: part-time and self-paced formats account for the majority of enrolments, and nobody is quitting to study full time.
- Protect the hours before you start. Decide which specific blocks in your week belong to this and defend them. The people who finish are not the ones with more time; they are the ones whose time was scheduled rather than found.
- Learn to build, not to study. The gap between people who get hired and people who complete courses is whether they have shipped anything real. Deployed projects that other people can use are the only portfolio that answers the question an employer is actually asking.
- Point it at your own industry from month three. Do not build a generic to-do app. Build the thing your current workplace does badly. It is more motivating, it is more impressive, and it is the artefact that makes the domain-first route possible.
- Test the internal move first. Before you enter the external market, find out whether the technical role you want exists inside the organisation that already trusts you. It is the shortest path and the one with the least bias in it.
- Then go external, positioned properly. Not as a career changer starting over, but as someone with 15 years in an industry who can now build. Those are the same person and very different candidates.
Underneath all of it is one thing, and it is the same thing at 40 as at 20. The foundation, being able to structure a problem, build, debug, ship and operate real software, with AI fluency and the judgement to catch what the model gets wrong, is what makes the internal move possible, what makes the domain-first switch credible, and what makes an adjacent technical role available to you. Whichever of the four routes you end up taking, none of that learning is wasted, which is why it is worth starting before you have decided which one it will be.
The Sigmaschool programme is that foundation, built around shipping real deployed projects rather than tutorials, and designed to be done part-time around a job. The free trial is a week of it at no cost, which is the cheapest way to find out whether this suits you before committing a year to it.
FAQ
Common questions.
Is 40 too old to change careers to tech in Malaysia?
No, but be honest about the distribution rather than taking encouragement at face value. In our own enrolment records, 8% of students are 40 or over and 20% are 35 or over, with a median age of 28 and an oldest student of 62. So at 40 you are a minority in the room, not an anomaly. The real constraints at this age are time, the size of the pay dip, and hiring bias, none of which are about capability, and all of which are manageable if you plan around them instead of pretending they are not there.
How long does it take to switch to tech at 40 in Malaysia?
The same as at any other age: realistically 9 to 14 months of consistent part-time study from zero to a first offer, assuming you keep working while you learn. Age does not change the learning curve. What changes at 40 is the number of competing obligations, which is why the plan matters more than the pace, and why people who protect a fixed number of hours each week finish and people who study when they feel like it usually do not.
Will I have to take a pay cut switching to tech at 40?
Usually yes, and it is a larger cut at 40 than at 25 because you are leaving a higher salary rather than a lower one. Junior developer bands in Malaysia run roughly RM 3,500 to RM 6,500 at local companies and RM 7,500 to RM 9,000 at multinationals, and that is the range a genuine career changer enters at regardless of previous seniority. The mitigation is not to enter as a generic junior: people who combine 15 years of industry knowledge with building skill frequently skip that band entirely by moving into a role where the domain expertise is the scarce half.
Is age discrimination real in Malaysian tech hiring?
It exists and it is not evenly distributed. It is most visible in high-volume junior hiring, where employers are filtering hundreds of similar applications and default to the cheapest and most available candidate. It is far weaker in roles where a specific domain is required, in smaller companies hiring for judgement, and in internal moves where people already know your work. That pattern is the whole argument for not applying as a generic junior at 40: the route where the bias bites hardest is also the route where your actual advantage counts for least.
What is the best route into tech at 40?
The one that uses what you already have. The cheapest switch is an internal move: become the person in your current department who automates things and builds internal tools, which converts your existing reputation and domain knowledge into a technical role without a job search or a pay reset. The next best is a domain-first switch, building software for the industry you spent 15 years in, where your understanding of the problem is worth more than another year of practice at syntax. Generic junior applications are the most common approach and the weakest one at this age.
Can I learn to code at 40 while working full time?
It is the normal way this is done. In our application data, 75% of people say they have under 25 hours a week to give to retraining, and among enrolled students the part-time and self-paced formats together account for the majority of enrolments. Nobody in this population is quitting their job to study. The realistic model is a protected block of hours each week, held for about a year, alongside work and family, which is demanding but is also the only version most people can actually afford.
Fifteen years of domain knowledge is an asset, not a sunk cost.
The switch that works at 40 combines rather than resets.
Learn to build, point it at the industry you already understand, and you are a rare candidate instead of a late one. Start with a week of the programme, free.