What People Say After Finishing the Work
Reviews, case studies and contact details — all on one page so you can form a clear picture before applying.
Back to HomeFrom the Learners
Varied reviews — not all five-star, not all glowing. Useful things people noticed about studying here.
Farid Hassan
Backend Developer, Kuala Lumpur
I came in knowing Python reasonably well and thought I would breeze through the early levels. Level two stopped me — the statistics section required me to actually understand what I was doing, not just run code. That was uncomfortable, but it was the right kind of uncomfortable. By the time I reached level five I could explain my deployment choices without guessing.
July 2025 · Six-Level Programme
Nurul Razak
Data Analyst, Penang
The data engineering module is where I spent most of my time. Weeks six and seven — keeping a pipeline running in an environment you did not set up cleanly — taught me more than the earlier weeks combined. I would have liked a bit more written guidance during those weeks, but the mentor office hours filled that gap once I worked out what to ask.
June 2025 · Data Engineering Module
Azlan Tan
Software Engineer, Ipoh
The portfolio review was not what I expected. I thought it would be mainly encouragement. Instead I got a list of twelve specific things to fix, in priority order, with an explanation for each. That list was more valuable than the session itself — I worked through it over the following month and my projects are noticeably better for it.
July 2025 · Portfolio Review
Lim Mei Shan
Research Assistant, Johor Bahru
I retook level three. That is not a complaint — the policy was clear when I enrolled. The retake meant I actually understood classical model selection before moving on, which paid off when I got to the neural networks level. The completion data on the website told me level three had a high retake rate, so I was not surprised when I hit it myself.
June 2025 · Six-Level Programme
Raju Krishnan
Systems Analyst, Selangor
What I appreciated most was that the time estimate on the programme page matched what I actually needed each week. Twelve hours is twelve hours. Other programmes I looked at gave numbers that seemed designed to make the commitment look smaller. Having an accurate number meant I could plan around it properly from the start.
May 2025 · Six-Level Programme
Wan Aishah
Junior ML Engineer, Kuala Lumpur
I finished the six-level programme in July. The final project level was where everything from the earlier levels had to connect — Python from level one, statistics from level two, the deployment decisions from level five. That integration does not happen in courses where you just complete sections. The cohort size made it possible for my mentor to give feedback that was actually about my project.
July 2025 · Six-Level Programme
Learner Journeys in Detail
Three accounts of what people faced before the programmes, how they worked through them, and what changed.
Challenge
Farid had been writing Python for three years but could not explain why a model he had trained was making certain predictions. He had completed two self-paced video courses and could copy patterns, but the reasoning behind them was unclear. He wanted to move from replicating examples to understanding what he was doing.
Through the Programme
The statistics level slowed him down in a useful way. He retook the level two assessment once. The feedback on the first attempt identified which statistical concepts he was applying without understanding. The second attempt required him to write out the reasoning, not just run the code. That difference carried through every subsequent level.
After Completion
Farid moved to a mid-level ML engineering role eight weeks after finishing the programme. He attributed the change primarily to being able to explain his technical decisions in interviews — something he had not been able to do before. Timeline: 20 weeks of study, role change at week 28.
"The retake was not a failure. It was the point where the programme became worth the commitment." — Farid Hassan, Kuala Lumpur
Challenge
Nurul was a data analyst who wanted to move toward ML engineering. She understood data well but had no experience building pipelines that fed model training. Most resources she found covered modelling without addressing the infrastructure underneath it.
Through the Module
The data engineering module gave her a seven-week project that progressed from design to live operation. By week five she had a working pipeline. Weeks six and seven — keeping it running and fixing what broke — exposed gaps in her understanding that the earlier weeks had not. She brought specific problems to mentor office hours during those weeks.
After Completion
Nurul joined an ML team at a logistics company as a junior data engineer. The portfolio she submitted for the role included the pipeline from the module as a working example. She noted that interviewers asked detailed questions about it — which she could answer. Timeline: 7-week module, new role confirmed at week 11.
"Weeks six and seven were the hardest. They were also where I learned the most. I am glad the module did not end at week five." — Nurul Razak, Penang
Challenge
Azlan had three personal projects on GitHub that he used when applying for roles. Feedback from failed applications suggested the projects existed but did not communicate clearly — the problem statements were vague, the code was inconsistently documented, and reviewers could not quickly judge the quality of the work.
Through the Session
The portfolio review covered all three projects in ninety minutes. The reviewer read them in advance. The session identified twelve specific issues across the three projects, prioritised by impact on how a technical reviewer would read the work. The written notes after the session restated the list with examples from his actual code.
After the Session
Azlan worked through the twelve-item list over four weeks. He then applied for two roles and received offers from both. He attributed the change to how the revised projects read rather than to new projects added. Timeline: 90-minute session, four weeks of revision, job offer at week seven.
"I had been applying with the same three projects for four months. After the review, the same three projects got me two offers in four weeks." — Azlan Tan, Ipoh
Some Figures Worth Knowing
3+
Years running structured AI programmes in Malaysia
280+
Learners who have enrolled across all programmes
4.6
Average rating across collected post-programme surveys
68%
Of six-level completers reported a role or project change within six months
Questions Before You Apply?
Send us a message and we will reply within one working day. Tell us your background and which programme you are considering.
Send an EnquiryPhone
+60 5 546 2718Address
33 Persiaran Greenhill, 30450 Ipoh, Perak, Malaysia
Office Hours (MYT)
Mon–Fri: 9:00 am – 6:00 pm
Mentor sessions: Mon–Fri, 8:00 pm – 10:00 pm
Ready to Start?
The next cohort is forming now. Tell us where you are and which programme interests you, and we will take it from there.
Get in Touch