Feedback from engineers who completed one or more tracks. Names and details shared with permission.
210+
Track enrolments
4.6
Avg. satisfaction
out of 5
4
Years running
cohorts
3
Practising engineers
on mentoring panel
Learner Feedback
Mohd Hakim
Network engineer · Kuching
Signal Basics was the first time I actually understood what a pipeline does end-to-end, rather than just running someone else's notebook. The exercises are not easy — particularly the data structure work in weeks four and five — but that is the point. The mentor feedback was specific enough to be actionable rather than just confirming that something was wrong.
Signal Basics Track · June 2025
Shirley Lim
Software developer · Miri
I was already writing Python in production so I joined the Modelling track directly. The entry calibration was good — the work started roughly where I expected. The ablation report was harder than I anticipated; writing it forced me to think clearly about what the model actually does versus what I wanted it to do. That friction was probably the most useful part.
Instrumented Modelling Track · May 2025
Razlan Zainudin
Embedded systems eng. · Bintulu
The Deployment track is not short and it is not light — fifteen hours a week is a genuine commitment on top of a full-time job. What made it workable was that all the live sessions are in Malaysian time. I did not have to rearrange my schedule around calls at seven in the morning. The incident simulation exercises were uncomfortable in exactly the right way.
Deployment & Reliability Track · July 2025
Nurul Tasha
Scientific computing · UNIMAS
I came from a scientific computing background and was not sure whether Signal Basics would be too elementary. It moved faster than I expected through the Python side and spent more time on the pipeline structure, which is where I actually needed work. The completion record described exactly what we covered, which was what I needed to show colleagues why I was allocating nine weeks to this.
Signal Basics Track · June 2025
Bernard Kueh
ML engineer · Kuching
The peer review circles on the Modelling track were something I did not expect to find valuable, but the feedback from other learners was often more pointed than I anticipated. Having to defend my experiment design to someone at a similar level is a different kind of pressure than getting comments from a mentor. The architecture reviews on the Deployment track were similarly useful — two experienced engineers reading my design and noting what they would change.
Deployment & Reliability Track · April 2025
Farah Azizah
Network ops · Sibu
I appreciated that the school is clear about what it does not do. I asked during the enquiry process about job placement and got a direct answer that this is outside their scope. That straightforwardness made me more confident about enrolling, not less. The track itself delivered what the specification said it would.
Signal Basics Track · July 2025
Case Studies
Case Study 01 · Signal Basics + Modelling
Challenge
A network operations engineer in Kuching had built regex-based log parsers for fault detection. They wanted to move to a model-based approach but did not have a path into the ML toolchain from a telco background.
Approach
Completed Signal Basics to establish the pipeline fundamentals, then moved directly into the Instrumented Modelling track. Focused the second-track project on text classification using the log data they already worked with.
Outcome
Built and documented a classifier that reduced manual review time on a subset of fault alerts by roughly 40% in internal testing. The ablation report became part of the documentation submitted to their team lead for review.
"The ablation report I wrote in the modelling track became the document I used to present the classifier to my team. Having to explain what it doesn't do was more useful than explaining what it does."
Case Study 02 · Deployment Track
Challenge
An ML engineer at a Kuching logistics company had a model in production but no serving infrastructure — just a Flask wrapper with no monitoring, no rollback plan and no runbook. When the model degraded, detection was manual.
Approach
Completed the Deployment track with the capstone built around a version of their actual serving problem. Worked through the incident simulation exercises with scenarios drawn from the kinds of failures they had already experienced.
Outcome
The capstone system ran for four weeks under observation with two simulated incidents. The monitoring dashboard and rollback procedure were adopted for the production system. The detailed completion record described the system and its failure modes.
"The architecture reviews were the part I underestimated. Having a practising engineer read my design and point to the latency assumptions I hadn't tested — that's not something a recorded course can give you."
Case Study 03 · Signal Basics
Challenge
A Bintulu-based engineer working on industrial sensor systems wanted to understand how ML predictions could be integrated into their existing monitoring pipeline, but had no prior Python experience.
Approach
Enrolled in Signal Basics with nine hours per week available. The twice-weekly sessions helped pace the material against a demanding shift schedule. Five exercises across the nine weeks, with feedback on each.
Outcome
Completed the pipeline project with a model that processed sensor readings from their own work environment. The completion record documented this specifically, which they used as a reference point for further self-study.
"I wasn't sure nine hours a week was achievable around shift work. It wasn't always comfortable, but the sessions were at a reasonable hour and the recorded material covered anything I missed."
Reach Us
If you have questions about track fit, cohort dates or entry expectations, send us a message. We respond within one business day.
Send a MessageReview the full track specifications, check the entry expectations, then send us a question if anything is unclear.