Location
Melbourne, Sydney
Employment Type
Full time
Location Type
Hybrid
Department
Design
The Role
We're looking for a product designer who designs, prototypes, and ships — and knows the difference between software that works and software that makes someone smile.
Clinicians use Heidi to get away from keyboards and back to patients. We want the product to feel as considered as the best software you've ever used — cohesive, quiet, and precise across every surface. When a clinician's tools feel right, they spend less time fighting software and more time with patients. That's the job.
You'll own the connective tissue of the product — shared patterns, consistent feel, the details that make software feel like one product. You'll partner directly with engineers, push code when it makes sense, and care about the 3px padding issue as much as the information architecture.
This role is based in Sydney or Melbourne. If you're somewhere else and you're exceptional, we'll make it work.
We don't care about logos. Show us what you've made, and tell us why it's good.
What you'll do
* Own design quality across the product — catch what's inconsistent and fix it before it ships
* Design, prototype, and ship features alongside engineers, without handoffs
* Explore what AI-powered clinical software should look and feel like, not just maintain what exists
* Contribute to a design system built as a floor, not a ceiling — components, tokens, and patterns that make consistency the default
* Push CSS fixes, build prototypes in Cursor or Claude, and open PRs for polish that shouldn't wait for a sprint
* Share work early, give honest critique, and help the team raise its bar for craft
What you'll need
* A portfolio where craft is visible — we want to feel something when we look at your work, not just follow the UX flow
* Comfortable designing in Figma and shipping in code — you've used Cursor, Claude, or similar tools to push real fixes, not just mockups
* Preferences about easing curves, opinions on optical vs mathematical alignment, a habit of stress‐testing components at their edge cases
* Strong opinions about design, loosely held — you can explain what separates considered software from lazy software at a component level
* When you see a broken pattern in production, you fix it, you don't file a ticket and wait
If you answer 'no' to these, this may not be the job for you:
* Are you geeky about software? Have you picked up a new tool in the last two weeks and gotten excited about it?
* Does inconsistent spacing in a shipped product genuinely bother you?
* Can you defend a design decision without referencing user testing?
* Are you able to ship without a design system team, governance structure, and research coordinators at your beck and call?
* Does the prospect of turning clinical chaos into something quiet, precise, and beautiful make you feel fuzzy inside?
Benefits
* Generous $500 annual development budget and serious equity.
* We don't track hours; focus on outcomes, not process theatre.
* Priority on mental health and flexible schedule.
* If the role description has scared you off, it was meant to.
#J-18808-Ljbffr