Product Designer

Date - JobBoardly X Webflow Template
Posted on:
 
November 20, 2026

Job description

About the Role

We are looking for a Product Designer with a passion for health and excitement about building our expanding healthcare platform. You enjoy working in dynamic environments, solving complex problems, and creating thoughtful, user-centred design solutions that make a real impact.

In this role, you will:

  • Own features and flows within a problem area someone has framed. New builds or evolutions of what exists. You make them clear, usable and well built.
  • Research it, design it, write it, test it, ship it, learn.
  • Move a feature-level metric. You know what your work is trying to move, and why.
  • Create designs that build trust and hold up in a regulated market.

What good looks like

  • Scope: you own features and flows end to end.
  • Impact: your work moved a feature metric. You can show the before and after.
  • Influence: you raise your own craft fast. You show up sharp in critique. You are becoming someone others learn from.

Responsibilities

What We Are Looking For

You're a talented Designer with a passion for health and excitement about building our expanding healthcare platform. You enjoy working in dynamic environments, solving complex problems, and creating thoughtful, user-centred design solutions that make a real impact.

Skills & Experience

Typically 3 to 5 years in product design, ideally in a fast-paced, product-led environment.

  • Problem definition. You solve the problem in front of you well, and you start to ask if it is the right one. You break work into pieces that ship.
  • Visual craft. Non-negotiable. Typography, spacing, colour, motion and micro-interactions. Weak craft is a no, whatever the strategy talk.
  • Accessibility. You design for the full range of users by default, not as a final pass. The basics are second nature.
  • Systems thinking. You design with the system, not against it, across web and mobile. You use and extend components rather than reinventing them.
  • Product sense. You connect your work to a metric. Research and data sit next to the design.
  • Communication. Clear and specific. You say what you decided and why, and you are starting to explain what you chose not to do. Vague writing is vague thinking.
  • Working in the open. You share work early and rough, and you invite critique instead of defending it. You get better in public.

Behaviours & Attitude

  • Patient-first mindset: You put patient outcomes above all else, ensuring every decision balances business growth with clinical excellence and exceptional care. You deeply understand and advocate for user needs. You can translate complex health journeys into intuitive, accessible, and emotionally resonant experiences.
  • Collaborative creation: You thrive in cross-functional environments, effectively communicating design decisions and incorporating feedback from product, engineering, and clinical teams without compromising your design vision.

How you work with AI

  • LLMs are in your loop as standard. You use them to move faster and think wider, not for show.
  • You are starting to prototype in tools like Claude Code and Cursor. We will help you go further.
  • The signal is workflow, not tool count.

Job requirements

The full stack

We expect you to work end to end, from problem definition and research to information architecture and UX writing.

  • Your own usability testing and basic research.
  • You help set up experiments and read them honestly.
  • You write your own interface copy. Clear and compliant.
  • You break problems down into pieces the team can build.

Your portfolio

Show real problem solving, not just finished screens, including how you used and extended the design system, and where AI shaped your process. We want to see work that moved something real, even at feature level, with craft that holds up: considered, polished, cared for. How you write it says as much as what you show. Concise and clear is a signal of how you communicate. Applications without a portfolio will not be considered.