About the Company

We are a healthcare technology company providing quality, compliance, and patient safety software to healthcare organisations. Our platform supports healthcare teams in managing operational, quality, and safety processes across multiple regions and is used by thousands of frontline healthcare professionals.

We are expanding our product suite with a number of new modules designed to solve complex operational challenges within healthcare environments. These modules are being developed as new products rather than migrations of existing systems, creating opportunities to design workflows and experiences from the ground up.

The first module is already in development. The next module focuses on incident and event management-enabling care teams to report, investigate, and manage incidents, accidents

The Role

You'll be the designer for our new product modules, starting with Events. You take the MVP scope - which our PM defines from customer discovery - and turn it into user flows, wireframes and clickable prototypes that engineers can build from, fast. You work within our existing Cloda design system (you extend it, you don't replace it), and you design for the full picture: happy paths, error and empty states, permissions, mobile and desktop.

This is a hands-on, Embedded role. You report to the CTO and work most closely with our PM (who owns scope and customer discovery), our principal engineers, and the wider engineering team. You won't hand off and disappear - you'll iterate with engineers as they build, and with customers as they react, refining the product based on real feedback rather than guesswork.

Engineers start building in July, so they need build-ready screens within your first couple of weeks. Speed matters from day one. Our PM is new, so we need someone self-sufficient enough to read a spec, ask smart questions, and get moving without a lot of hand-holding.

What You'll Do

Design the Events module from the MVP spec

• Take the MVP scope for Events and turn it into user flows, wireframes and clickable prototypes that engineers can build against.
• Design the full flow, not just the happy path: error states, empty states, permission-based views (Central sees everything, franchise managers see their sites, staff see their own records), and both mobile and desktop.
• Understand the real workflow behind the screens: how care teams report incidents and accidents, often on tablets, mid-shift, with little time and varied tech confidence.

Bring the design thinking, not just the screens

• Propose design patterns that are proven to work in healthcare - patterns that aid discovery, drive engagement, and get users to the core value of the product faster.
• Make complex, regulated workflows feel simple. The win isn't a prettier form; it's a care worker getting a report done in two minutes instead of thirty.

Iterate with customers and engineers

• Test designs with real healthcare workers where we can (we can arrange access through the customer), gather feedback, and refine - don't fall in love with the first idea.
• Work shoulder to shoulder with engineers during build, handling the edge cases, error and empty states, and mobile layouts that always surface once something becomes real.

Design to be measured

• Design so we can instrument it: partner with the PM to define what user behaviour we'll measure when we ship, so we can challenge our assumptions with data rather than opinion.
• Use what the data tells us to drive the next iteration, and the conversations about what to build next.

Work within the Cloda design system

• Extend our existing React/SASS component library and patterns - don't reinvent them. Consistency across the product matters more than novelty here.
• Partner with our principal engineers on what's feasible and what fits the system. When you genuinely need a new pattern, make the case for it rather than quietly working around the system.

Design with one eye on Cloda-first

• We have a product vision called Cloda-first, where our AI chat interface becomes the starting point for everything: Ask (instant answers), Assist (guided actions like voice incident capture), Analyze (insights with "Fix It" actions) and Workspace (the full UI for complex tasks).
• You don't need to design the AI experience yet, but design the Workspace UI so it doesn't fight that future - so a 30-minute paper incident report can one day become a 2-minute voice capture without us having to redesign everything.

What We Need

• You've designed SaaS product modules from a spec before. Give you acceptance criteria and you produce MVP mockups and flows engineers can build from - without needing weeks of discovery first. The PM does discovery; you design from the spec and ask smart questions.
• You're fast - in Figma and in prototyping. You produce usable wireframes in days, and you get to clickable prototypes quickly, using AI tools (Claude Design, Claude Code, v0, Codex, Figma's AI features) to move faster rather than polishing everything by hand.
• You use AI to move faster, by default. We expect you to use AI tools to get from idea to clickable faster and deliver more value for customers. If AI isn't already part of how you work, this isn't the right role.
• You think in flows and states, not just screens. Happy path, error, empty, permissions, mobile vs desktop, the messy edge cases - and you've handled genuinely complex, business-logic-heavy flows, the kind a compliance product is full of. You're not a pure visual designer who just makes things pretty.
• You've done this in a startup or fast-moving product team. You've shipped real product fast, Embedded with engineers, without heavy process, and owned real scope end to end - not a narrow slice of someone else's product in a big, slow org. You've proven you can move - that matters to us more than a big-company logo.
• You work well inside an existing design system. You extend patterns rather than replace them, you don't get precious about your designs, and you take direct feedback without friction.
• You can design with incomplete information. Scope may still be moving when you start. You make sensible calls, flag your assumptions, and iterate - rather than waiting for perfect certainty before you put anything on a screen.

Nice to Have

• Healthcare, clinical, or regulated-industry understanding - especially designing simple, clear interfaces for lower-tech users on mobile/desktop.
• Experience designing permission-based, multi-tenant products.
• Experience with incident reporting, risk, or quality-management products specifically.
• A feel for AI-native product thinking - how chat, voice and "do it for me" actions change a workflow.