## school_stats_output
3
Structured programmes
4.6
Average participant rating
MY
Based in Kuala Lumpur
2d
Response time for enquiries
## testimonials # programme_participants
Zulaikha Hassan
Data Engineer · Kuala Lumpur
I did the data handling course after two years of cleaning data at work and still not feeling confident that I was doing it correctly. The exercises were genuinely tricky — one file had timestamps in four formats in the same column. The written feedback on the exercises was more useful than I expected; the comments explained why something was a problem rather than just flagging it.
Data Handling Course · June 2025
Rajan Nair
Product Manager · Petaling Jaya
The evaluation seminar was three hours and covered more ground than I thought was possible in that time. I came in as a PM who reads code but mostly watches engineers do the evaluation work. By the end I could at least ask sharper questions and read the reports my team produces. The report template has been used twice since then.
Evaluation Seminar · July 2025
Chen Li Wei
Software Engineer · Penang
I completed the development track in January. The workload is real — I would not describe 12 hours a week alongside a full-time job as easy — but the structure is sensible. Project reviews were the most valuable part. My reviewer commented on things like variable naming and the way I handled edge cases, not just whether the code ran.
AI Systems Dev Track · Completed Jan 2025
Nurul Farhana
ML Engineer · Cyberjaya
The data course is narrow and that is a good thing. I had taken broader AI courses before and always felt like I was being shown a lot without being taught to do any of it well. Five weeks on data preparation specifically — and with exercises that actually required me to fix things — was more useful than those broader courses combined. The dataset documentation template is something I use regularly now.
Data Handling Course · May 2025
Ahmad Syafiq
Data Analyst · Shah Alam
The pre-enrolment conversation for the development track was actually reassuring rather than intimidating. It felt like they were trying to figure out whether I would get value from the track, not testing me. The technical conversation was about 20 minutes and straightforward. I was admitted and the track lived up to what was described on the page.
AI Systems Dev Track · Completed Mar 2025
Priya Krishnan
Backend Engineer · Kuala Lumpur
I attended the evaluation seminar as someone who was sceptical that a three-hour session would teach me anything I did not already know. I was wrong about that. The section on model-as-grader failure modes and the discussion of statistical significance on small samples were both more nuanced than I had expected for an introductory event.
Evaluation Seminar · June 2025
## case_studies
Two participant journeys in more detail
# case_study_01 · data_handling_course · 5_weeks
## challenge
A data engineer at a logistics company was spending the majority of each sprint on data cleaning, with no documented process. Results from three months prior could not be reproduced because the preprocessing steps were not recorded.
## approach
Took the five-week data handling course, working through exercises on schema validation, versioning and documentation using files from her own work (with employer permission) as supplementary practice material.
## outcome
Introduced dataset documentation to her team's workflow. Preprocessing steps for new datasets are now version-controlled. She describes the dataset documentation template from the course as the starting point for what her team now uses.
# case_study_02 · ai_systems_dev_track · 24_weeks
## challenge
A backend engineer wanted to work on AI systems rather than just the infrastructure around them, but had no structured path to build that knowledge part-time without switching jobs or pursuing a full-time course.
## approach
Enrolled in the six-month development track, committing 12–14 hours per week across evenings and Saturday mornings. Built a retrieval-augmented document assistant as the capstone, with evaluation harness and cost monitoring.
## outcome
Completed the track and passed the independent capstone review. The capstone repository is public and was used as a portfolio piece. He describes the office hours as the part of the track that kept him from going in the wrong direction on projects.
## contact_details_output
telephone
+60 3-2163 5482
address
61 Jalan Ampang, 50450 Kuala Lumpur
office_hours
Mon–Fri 10:00–18:00 MYT
## enquiry_cta
Thinking about one of the programmes?
Send us a message. Writing to us starts a conversation, not an enrolment.