DOKKAEBILABS
WhatsApp us
← All posts

Dokkaebi Labs · October 11, 2026 · 6 min read

Your Poly GPA Is 4.0. Why Would You Need Tuition?

You topped your cohort. Your lecturers love you. So why are we telling you a 4.0 isn't enough? Because at NUS and NTU Computing, 4.0 is roughly what everyone else in the queue has too. Here's what actually separates you.

polytechnicstudentssingaporeuniversity-admissionsprogrammingcybersecurity

Let's get one thing out of the way.

If your poly GPA is 4.0, you are not the problem. You're doing great. Genuinely. You showed up, you did the work, you probably sacrificed more weekends than you'd like to admit, and you got the number.

So when someone suggests tuition, the natural reaction is: for what?

Fair question. Tuition is for people who are failing, right?

That's the part we want to argue with.

Quick reality check on what 4.0 actually buys you

Here are the official numbers. NUS and NTU both publish the GPAs of poly students who received offers, at the 10th and 90th percentile.

For the 2026 admissions exercise (based on AY2025/26 offers):

Programme10th percentile90th percentile
NUS Common Computer Science3.813.98
NUS Information Security3.883.98
NUS Computer Engineering3.813.99
NTU Computer Science3.783.98
NTU Data Science & AI3.894.00

Read that again.

The poly applicants who got into NUS Information Security mostly sit between 3.88 and 3.98. NTU's Data Science and AI programme has offers at a flat 4.00 at the 90th percentile.

So your 4.0 isn't a golden ticket. It's the entry fee. It puts you in the room with every other person who also has a 3.9-something and also worked every weekend and also has lecturers who love them.

You're not standing out. You're standing in line.

GPA measures one thing. You're being judged on several.

Your GPA tells the university that you can do well on poly modules. That's useful. It's also exactly what every other applicant in that table can prove.

What it doesn't show:

  • Whether you can build something nobody assigned you.
  • Whether you understand why your code works, or just that it passed the test cases.
  • Whether you'll survive a first-year module that assumes you already think in data structures.
  • Whether you can talk about your work in an interview without reciting your module descriptions.

This is where aptitude-based admissions come in. Both NUS and NTU admit a portion of students through ABA, which looks beyond grades at portfolios, interviews, competitions and projects. When you and fifty other people have the same GPA, that's the stuff that decides it.

And here's the uncomfortable part: poly modules don't really prepare you for it. They're designed to get a cohort of 200 to pass. They're not designed to make you stand out from that cohort.

"But I'll just learn it in uni"

You will. Eventually.

But talk to anyone who went poly → NUS or NTU Computing and ask them about Year 1. You'll hear some version of the same story.

Poly taught them to build things. Java, web apps, databases, maybe some Python. Practical, hands-on, good stuff.

Then uni hits them with proofs, recursion, complexity analysis, and data structures at a pace that assumes they've seen it before. The JC kids who did H2 Computing or competitive programming are fine. The poly kids, the ones with the 4.0s, are suddenly wondering why they feel slow for the first time in three years.

It's not that you're less capable. It's that you spent three years getting really good at a different game.

The people who glide through Year 1 aren't smarter. They just got there early.

The internship problem nobody mentions

Even if you're not going to uni, the same thing applies to jobs.

Your diploma comes with an internship. Great. So does everyone else's. When a hiring manager has a stack of poly CVs, they all say roughly the same thing: same modules, same school projects, same tech stack listed in the same order.

The ones that get a second look have something extra. A GitHub with a project that clearly wasn't an assignment. A CTF writeup. A small app people actually use. A blog post explaining something technical in plain English.

Grades get you filtered in. Proof of work gets you picked.

So what is tuition actually for, at 4.0?

Not remediation. You don't need someone to re-explain your lecture slides.

It's acceleration. Specifically:

Getting ahead of Year 1. Data structures, algorithms, recursion and complexity, done properly before you need them. So the first semester feels like revision instead of a fire drill.

Building a portfolio that isn't homework. One or two serious projects, scoped like real software, reviewed by someone who ships production code for a living. Something you can talk about for twenty minutes in an ABA interview without running out of things to say.

Picking a direction early. Software engineering, cybersecurity, data, AI. A 4.0 tells you you're good at poly. It doesn't tell you which of these you actually like. A few months of focused work in one of them will.

Learning how industry actually works. Version control the way teams use it. Code review. Testing. Why the "correct" answer in a module and the correct answer at work are often different.

Interview preparation. How to explain your projects. How to think out loud during a technical question. How not to freeze when someone asks "why did you do it that way?"

None of this shows up in a GPA. All of it shows up the moment you're in a room with someone deciding whether to pick you.

Who this isn't for

Honestly? If you're happy where you are, aiming for a programme where your grades clear the bar comfortably, and you don't care about standing out, you don't need us. Enjoy your holidays. You've earned them.

But if you're aiming for NUS Computing, NTU CS or Data Science and AI, a competitive internship, or a security role straight out of poly, a 4.0 is where the conversation starts. Not where it ends.

How we work with high performers

We don't do group classes and we don't do syllabus re-teaching. Every session is 1-to-1 with someone who works in the industry: software engineers who ship to production, and security practitioners who hold OSCP and beyond.

For poly students, that usually means:

  • A Year 1 head start in DSA and core CS concepts.
  • One portfolio project built properly, start to finish.
  • A cybersecurity track (home labs, CTFs, certification path) if that's your direction.
  • Mock interviews before ABA or internship applications.

We take a limited number of students each intake. If you're the kind of person who reads a blog post about getting ahead while already holding a 4.0, you're probably who we're looking for.

Polytechnic tuition → · Programming tuition → · Cybersecurity tuition →

Or message us directly on WhatsApp.


Sources: NUS Office of Admissions, Indicative Grade Profile; NTU Undergraduate Admissions, Indicative Grade Profile. Grade profiles are indicative and change every year. Always check the latest figures.

Written by people who also thought the number was the point. It isn't. The number gets you in the door. What you built gets you the seat.

ZYZ

Zhen Yu Zhang

Security Engineer · Full-Stack Developer · Founder, Dokkaebi Labs

Zhen Yu designs, secures, and deconstructs systems — then teaches others how to do it right. Based in Singapore. Trained professionals across SG, AU, and the UK.

LinkedIn →

Cybersecurity Tuition

Red team, blue team, all levels

Private 1-to-1 cybersecurity tuition for poly and uni students, career switchers, and professionals.

Explore cybersecurity tuition →

Keep reading

We take a limited number of students and clients each intake.

Start a conversation →