Portfolio - 2026Singapore · Remote-friendly

IT support & software QA

IT diploma graduate with a year of technical work: setup, troubleshooting, testing, and documentation for a VR training system. I trace problems to the root cause and document the fix. Looking for IT support and service desk roles; software QA is the second lane, since I read and write code.

Résumé ↗Get in touch

1yr: Technical experience: setup, troubleshooting, testing, and docs at CEMS.
70+: Tests behind my open-source tool, written test-first.
50%: Of that tool's code removed in a refactor, with no regressions - the tests caught them.

About

I find the root cause, then write it down so it stays fixed.

I just finished an IT diploma at Singapore Polytechnic (2026) and have a year of technical work behind it: at a maritime research centre I set up and troubleshot a VR training system, ran user testing, reproduced and tracked issues, and wrote the guides so other staff could run it without me.

I'm aiming for IT support and service desk roles, with software QA a close second. The difference from most manual testers is that I read and write code - 70+ tests on my own tool - so I can test from the inside. The part I like most is debugging: staying with a stack trace until the real cause shows up, not the line that happened to throw.

Experience

Centre of Excellence in Maritime Safety (CEMS)

QA & Support/Singapore

Apr 2025 – Feb 2026

Set up, configured, and troubleshot a Unity VR training system on Meta Quest 3 headsets and bHaptics gloves, keeping user sessions running.
Ran testing end to end: designed and ran user testing sessions, and turned the findings into reports for the dev team.
Reproduced reported issues with exact steps, tracked them to resolution, and wrote setup and troubleshooting guides so other staff could run the system without me.

Stack

TroubleshootingUser TestingQATechnical WritingUnity / C#

Projects

Tokey

Developer & Maintainer/Command-line tool

View on GitHub↗

Problem

I use it constantly, so a wrong number is worse than no number at all: I would read it, believe it, and act on bad math without noticing. I did not want a tool I had to babysit.

Solution

I wrote the tests first, covering the token math and the session-discovery path, then built the tool on top of them. They act as the spec, so a later refactor cannot quietly change what the counts mean.

Result

That let me delete about half the original code, dropping a fragile transcript dependency for direct session discovery, with nothing regressing. I have run it daily since without rechecking its math by hand.

Built with

PythonRichStandard libraryMIT

What it proves

01Wrote the test suite before the tool was usable, not after it shipped.
02Leaned on it to swap a fragile transcript dependency for direct session discovery.
03Zero-config, MIT-licensed, and runs on both Windows and Linux.

Skills

IT Support

Troubleshooting & issue diagnosisIssue reproduction & defect trackingUser support & technical documentationWindows (daily use) · Linux (CLI, scripting)

Software QA

End-to-end, functional & user testingTest case design & UATpytest & test-driven developmentReads & writes code - tests from the inside

Code & tools

PythonReact & TypeScriptGit (clean, atomic history)

Currently learning

SQL (SQLBolt)Computer networking (Coursera)Azure Fundamentals (AZ-900)

Résumé

The full résumé is a one-page PDF: education, coursework, and the work, ready to forward.

Kept current, written for IT support / service desk roles.

Download PDF ↗Ask a question

Education: Diploma in Information Technology - Singapore Polytechnic, 2026
Target: IT Support / Service Desk · Software QA
Stack: Python · React + TypeScript · Linux · Git
Based: Singapore / remote-friendly
Status: Fresh grad · open to opportunities