Giorgio Wilson Wong
Start manual, then automate
I started by filming things, then editing them, then building the things themselves.
What happened in between is easier to show than to explain.
I test software for a living and I make things for the pleasure of it. Those two habits turn out to be the same habit: take something apart carefully enough to understand why it behaves the way it does, then put it back together better.
The rule I work by is that I learn a process by hand before I let anything automate it. It is slower at the start and it has never once been the wrong call — you cannot judge what a tool got wrong if you never knew what right looked like.
My journey
Not a list of what I made. The moments that decided how I make anything — including the one where the right answer was to stop.
'23
Content Creator intern at NIEC, then two weeks of social-media work at HOKIbank. The first time the brief came from someone who was not me.
Turns out making things for other people is more fun than making them for myself.
'23–'25
71 posts across two blogs — research, storyboards, location plans, edit breakdowns, and the bits that went wrong.
I would rather show the whole process than just the finished poster.
'24
Thompsonia — a first-person maze in Unreal Engine for STEM Week. Environment, interactions, collectibles, level flow and UI, all solo.
Games are just another thing you can make, and I want to make more of them.
'24
Revora — techpack, printed prototype, website, and a proposal I presented to the school office myself.
Knowing when a thing is not good enough yet is its own useful skill.
'25
Finished at Regents in May, started a B.Sc. in Computer Science at BINUS in August, and kept making things throughout.
I did not want to choose between the creative side and the technical one, so I did not.
'26
Software QA/QC at Five Digital since July. Testing, reproducible reports, and an internal Help Center built in a single workday.
Breaking software on purpose is a genuinely fun way to learn how it is built.
'26
A fellowship site growing across regions, and an apparel line for the Bali youth. Both running now, both unfinished.
The best version of this is making things that land with people I know.
Selected work
Professional, academic and personal work. Where credit is shared, it says so on the card.
01A live website for a real organisation. Visual direction, information architecture, how the creative work is presented, and round after round of UX changes made with the people who actually use it.
Design and build
Open Revival Fellowship Indonesia (opens in a new tab)
02Requested one morning, searchable and responsive and live before 6 PM the same day. The real one is internal, so the link opens an unrelated fictional recreation built to show the same craft.
Sole builder
Open Internal Help Center (opens in a new tab)
03A clothing label taken from techpack to printed prototype, with a website and a proposal I presented to the school office myself. Pre-launch — and it stopped there on purpose.
Techpack, print coordination, web, pitch
Open Revora Apparel (opens in a new tab)
A narrative film, a wedding cut during the event itself, a documentary, and the shorter pieces around them. All on the channel.
Director, camera and editor across the set — some credits shared
A first-person horror maze in Unreal Engine, built alone for STEM Week — environment, interactions, collectibles, level flow and UI. Made before I had ever used AI to write code.
Sole developer
Playable build held locally — not published
A design system and a jacket for the Bali youth. The first batch has been sampled and previews have gone to the Singapore and Netherlands assemblies. Production and selling are the plan, not the past tense.
Design system, garment design, decks
First batch sampled — no public storefront yet
07A university HCI study — PACT analysis, accessibility and privacy thinking, user segmentation, and a full interface designed around them. Static screens, not a working app.
Individual assignment
Open FitBuddy (opens in a new tab)How I work
Learn the process by hand, find where it breaks, automate only the repetition, and say plainly which parts are finished.
01
I do the process manually until I understand why each step exists. You cannot review what a tool produced if you never knew what correct looked like.
02
Testing is not clicking through the happy path. I go looking for the edge that nobody specified, then write it up so a developer can reproduce it without asking me anything.
03
Once the shape of the work is clear, AI takes the parts that are repetitive and mechanical — never the parts that need a decision.
04
Finished, in progress and intended are three different things. I label which is which, in my reports and on this site.
What I can do
Each of these is backed by work you can open, not by a self-assessment.
Functional and usability testing, bug discovery and reproduction, and issue reports a developer can act on without a follow-up conversation.
Proved by Software QA/QC at Five Digital, current role
Directing and editing, mostly by instinct — I cut until it lands rather than working from theory. Deciding what the story is, and what to leave out, is the part I am good at.
Proved by Beyond the Belt, Newman's Plot, Leave the Door Open, wedding same-day film
Building sites and the documentation that makes them usable — design, information architecture, AI-assisted implementation and iteration with the people who use it.
Proved by Revival Fellowship site, one-workday Help Center, Revora
I am employed full time. Availability for anything beyond that is to be discussed following role confirmation and coordination with my current employer.
Tools
Credentials
Including the parts that are still in progress, and the one that proves less than it sounds like.
Pick any of these to see the detail and the certificate.
FAQ
The things people actually ask, answered without the sales voice.
Yes — my current role involves work I cannot show, and the way this site handles it is the honest answer to the question. The Help Center I built is real and internal, so instead of showing it I built an unrelated fictional recreation to demonstrate the same craft, and I say so on the card rather than letting you assume. I am comfortable signing an NDA before we discuss anything specific.
The degree at BINUS is active and expected in 2030, and I work full time at Five Digital alongside it. It is not a coincidence that both are possible — the coursework is data structures, algorithms and statistics, and the job is testing software. They feed each other more than they compete. I have been running both since starting the role.
Functional and usability testing, finding the edge nobody specified, and writing it up so a senior developer can reproduce it without coming back to ask me questions. The reports are the part people underrate — a bug nobody can reproduce is not a finding, it is a rumour.
The opposite, and it is the principle the whole site is built on: I learn a process by hand before I let anything automate it. I spent my first weeks doing the manual QA workflow before wiring AI into any of it. You cannot review what a tool produced if you never knew what correct looked like. AI removes the repetition; the judgement stays mine.
Because the habit is the same one. A 12-hour edit, a techpack that has to survive a printer, and a bug report a developer can act on are all the same exercise: understand the thing well enough to know what breaks it. The Media Studies archive is 71 posts of that working-out done in public, including the parts that failed.
Every card says. Where credit is shared it names the person — the editing credit on Beyond the Belt, the script on Newman's Plot, the digipak on Leave the Door Open. Thompsonia and the Help Center were solo. I would rather tell you exactly where my part ended than round it up.
I am employed full time, so anything beyond that is to be discussed following role confirmation and coordination with my current employer. If you are hiring rather than commissioning, that conversation is much simpler — WhatsApp is the fastest way to reach me.
Two things outside the job. The Revival Fellowship site is growing from one site into something meant to serve several regions, with leaders managing their own content. And an apparel line for the Bali youth — the design system and the 2026 jacket are done and the first batch has been sampled. Production and selling are the plan, not something I have already done.
WhatsApp is the fastest way to reach me.
