</startup link>
Technical Officer at UniMelb’s student startup programme. Internal tools and full UI redesigns for early-stage founders.
SPECIFICATIONS
| ROLE | TECHNICAL OFFICER |
|---|---|
| YEAR | 2026 |
| TYPE | ONGOING ROLE |
| STATUS | ONGOING |
| STACK | ux research · internal tools · crm · ui redesign · design systems · react · typescript · swiftui +1 more |
| LINKS | — |
| COURSE / TEAM | Startup Link, University of Melbourne · Aug 2026 to present · a committee role alongside the final year. I own the technical side of projects: what an early-stage founder actually needs, cut down to what a student team can deliver inside one semester, and built by me when the team is one person. The current client is not named on this site until they agree to be. |
“Startup Link is the University of Melbourne's student-run startup programme.”
Technical Officer, Projects at Startup Link, the University of Melbourne’s student-run startup programme, since August 2026. The role scopes technical and design engagements for early-stage founders, staffs them with student teams, and delivers them. In practice that means the surfaces a founder actually runs the company on: the internal tools and CRM screens as much as the public product, reviewed against each other and then redesigned as one system.
role & context
Startup Link, University of Melbourne · Aug 2026 to present · a committee role alongside the final year. I own the technical side of projects: what an early-stage founder actually needs, cut down to what a student team can deliver inside one semester, and built by me when the team is one person. The current client is not named on this site until they agree to be.
Startup Link is the University of Melbourne's student-run startup programme. Founders bring a problem, the programme pairs them with student teams, and somebody has to turn "we need a website and an app" into a scope a team can actually finish before the semester ends. That is the job.
The current engagement, from August 2026, is a healthcare marketplace startup. It runs on more surfaces than it looks like from outside: a marketing site, an operations portal, an iOS app, and the internal tools the team coordinates the business in. I reviewed all of them against each other, then redesigned them as one system. The client is not named here until they agree to be.
There is no single stack for the role. Each engagement picks its own, and the current one is React and Tailwind on the web with SwiftUI for the app. What carries between engagements is the method.
Findings are tied to a surface, a severity and a fix, so a review can be argued with line by line instead of taken as taste. Colour, type and spacing get declared once as tokens and printed in the gallery, which ends the "which blue" conversation before it starts. And the recommendation gets built far enough to click, because a redesign that runs can be measured against the live product, and a founder can hand it to whoever builds next.
DECISION 01
Scope to what can be shown, not to what can be promised. A founder's brief is usually three products. The engagement is the one slice that can be clicked by the end of the window, with the rest written down as labelled stubs.
DECISION 02
Redesign what they run on, not only what they sell. The marketing site is the easy half. The internal tools, the operations portal and the CRM screens are where staff spend the day, and they are usually the part nobody has looked at.
DECISION 03
Keep the client unnamed until they say otherwise. The work is mine to describe. The name is theirs.
ux research · internal tools · crm · ui redesign · design systems · react · typescript · swiftui · figma
ONGOING