Full Stack Software Engineer

About Zenith Education Studio

Zenith is an MOE-registered centre committed to delivering high-quality, holistic education to Primary, Secondary, and JC students. Our educators and teams are dedicated to empowering students to realise their full potential and become the best versions of themselves.

If you’re passionate about transforming education and making a real impact, we want to hear from you.

About the Role

Most software in education was old ten years ago. Timetables held together by spreadsheets, portals nobody has touched since launch, processes that only work because somebody remembers the workaround.

Zenith is building what a modern learning centre should have had all along. The platform our students learn on. Systems our tutors and staff reach for rather than tolerate. Automation that clears away the work nobody should still be doing by hand.

We want an exceptional full stack engineer to build it with us, and we will be direct about what we are hiring for, because it is unusual.

The best engineers of the next decade will not be the ones who write the most code. Agents already write plenty. They will be the ones with the judgment to know what is worth building and the discipline to know when it is wrong.

That is the bar. We hire people who verify their own work, who know where their own judgment runs out, and who ask before assuming. Experience on top of that is welcome. It is not what we filter on.

What You'll Do

Three questions sit behind everything we build. Is a student learning better because of this? Is a tutor's day easier because of it? Are our back-office processes better or faster because of it?

The learning platform, the CRM that the team works in, our public sites, the automation running between them, these are how we answer those questions at the moment. They are not the point in themselves.

Your job is to keep answering them. Features end to end, from the interface through to the database, in whichever system the problem happens to live. The judgment to work out which problem is worth solving next. And the ownership to see it hold up once real people depend on it.

And the craft underneath. Bugs traced to a real root cause rather than patched over. Clear answers for the colleagues who do not write code. Runbooks written so that nothing has to be worked out twice.

What We're Looking For

• You work across the full stack and care about both ends of it. The interface a student or tutor actually has to use, and the system underneath that has to stay correct and fast as it grows.

• You can say why. Not just what your code does, but why you designed it that way and what you would do differently now.