From Developers Who've Worked Through the Programmes
Unedited feedback from engineers and teams who completed Nuvex programmes — including what helped and what they found worth noting.
Back to Home200+
Developers completed a programme
18
Teams coached
4.7/5
Average satisfaction score
MY
Delivered from George Town, Penang
What Programme Participants Say
Ahmad Taufiq
ML Engineer, Penang
The Concepts Track gave me something I hadn't been able to piece together from documentation alone — a way of looking at a profiler output and knowing where to start asking questions. The chapter structure is genuinely useful; I still refer back to the notes months later.
Tuning Concepts Track — May 2025
Lee Wei Xian
Software Engineer, Kuala Lumpur
I went into the Lab Series thinking I'd pick things up quickly because I'd done a lot of reading beforehand. The sandbox exercises surfaced gaps I didn't know I had. Running the workloads and seeing the profiling numbers shift as I made changes was more instructive than any written explanation I'd found.
Hands-On Lab Series — April 2025
Nurulain Roslan
Engineering Manager, Penang
We ran the team coaching programme across three weeks with a team of five. What I noticed by the end was that when someone raised a performance concern in a review, the conversation was faster — people knew what evidence to look for rather than arguing about intuitions. The handbook stays on the shared drive.
Team Coaching Programme — March 2025
Kavindra Pillai
Backend Developer, Selangor
The Concepts Track is written in a way that assumes you're a developer, not a hardware specialist. I found that the most useful thing — no jargon for the sake of it. The exercises made the difference between having read something and actually understanding when it applies.
Tuning Concepts Track — May 2025
Siti Zulaikha
AI Systems Engineer, Penang
I've used the Lab Series as a supplement to the Concepts Track and found the progression natural. One thing I'd mention: the discussion prompts at the end of each lab session were more valuable than I expected — they pushed me to articulate what I'd observed rather than just move on.
Hands-On Lab Series — April 2025
Danial Lim
Tech Lead, Kuala Lumpur
The scoping call before the team programme was straightforward — they asked sensible questions about what we were actually trying to accomplish, not just what package we wanted. The sessions were facilitated at a pace that worked for a mixed team. The handbook is a solid reference document.
Team Coaching Programme — February 2025
Programme Outcomes in Practice
Penang-Based ML Team: Reducing Time Spent on Performance Investigations
Challenge
A team of four engineers was spending 30–40% of sprint time on unstructured performance investigations — often repeated work because findings weren't captured in a reusable way. The team lacked a shared framework for what to look at first.
Approach
The team completed the three-week Team Coaching Programme. Sessions were structured around their actual workloads, with the facilitator guiding observation exercises using their own profiling data. The handbook was tailored to include patterns relevant to their stack.
Outcome
Performance investigations moved to a documented format, reducing repeated context-setting. The team noted faster alignment during code reviews when performance was discussed — referencing shared terminology from the programme.
"The biggest difference is that now when someone raises a profiling observation in a review, we have a shared starting point for the conversation instead of going back to basics every time."
— Engineering Manager, Penang
Individual Developer: Moving from Reading to Practising
Challenge
A backend developer had read extensively about GPU performance but found that when facing actual profiling output at work, the reading didn't translate to useful action. Concepts felt understood in isolation but not connected to each other.
Approach
Completed the Concepts Track followed by the Lab Series. The sequential structure — reading concepts then applying them in the sandbox — provided the connection between theory and observable evidence that had been missing.
Outcome
Reported being able to form initial hypotheses from profiler output independently — something that previously required asking a colleague. The reference notes from both programmes remain in use alongside regular work.
KL-Based Team: Building Common Language Across Mixed Experience Levels
Challenge
A team of six included engineers with very different levels of familiarity with GPU performance. Discussions about workload behaviour were difficult because team members were working from different mental models and vocabulary.
Approach
The Team Coaching Programme was run remotely over four weeks. Sessions were structured to surface different perspectives rather than assume a common baseline — the facilitator used the gap in team knowledge as material for discussion exercises.
Outcome
The team developed a shared observation protocol that they applied to subsequent workload reviews. More experienced team members noted it helped them explain their reasoning in a structured way, not just in intuitive leaps.
Reach the Nuvex Team
Phone
+60 4-657 2914Address
Jalan Dato Keramat 142, 10150 George Town, Penang
Hours
Mon–Fri 9am–6pm
Sat 10am–2pm
Find the Programme That Fits Where You Are
Whether you're starting from scratch or want to deepen applied experience — there's a clear path from here.