Here’s what the work looks like day-to-day:

• Bringing designs to life (UI): Applying the ever-expanding design system to prototypes, creating beautiful user interface experiences. This includes re-drawing medical content (graphs, icons, infographics,) so they look good whilst meeting pharmaceutical regulatory requirements (yes, it's possible!).

• Making it work everywhere. You'll design responsive experiences that adapt seamlessly across devices and prepare designs for localisation across multiple markets. This means thinking about text expansion, naming conventions, and version control from the start. We use Crowdin for translation workflows, and you'll sync designs with translated content.

• Building and maintaining the system: You'll contribute to our design system, ensuring consistency across all programme elements whilst documenting country-specific variations and regulatory requirements. This is a flexible living system that you'll help evolve.

• Collaboration: You'll work directly with senior designers, programme leads, and where required, developers to ensure design consistency.

• Client communications: Join and contribute to client meetings and touchpoints.

About you:

• You have 1-3 years of design experience, working on digital experiences (sites, microsites, landing pages), either in-house or at an agency. 

• Your portfolio shows your eye for detail. We're particularly interested in how you approach different projects and represent technical or scientific information. Graphs, infographics, data visualisation. The things that are easy to make boring but shouldn't be. 

• You're comfortable around Figma. Component libraries and complex design systems don't intimidate you; you know how to build and maintain them. 

• You have knowledge of user-centred design principles and best practices. 

• You can explain your thinking clearly, give and receive feedback constructively, and work well as part of a team. 

• You know the basics about web-development constraints. No actual development experience needed, but basic knowledge that helps you understand what's possible and what's painful for developers. 

• You've worked on localisation before (or you're keen to learn!). This is a big part of the role, and we need someone who can learn why it matters and how to design for it. Think multiple countries, languages and alphabets. 

• Formal design qualifications are nice but not essential. Your portfolio and past experiences are more important to us. 

We value character as much as capability. If you think you're close but don't tick every box, still get in touch. We'd rather talk to someone with the right mindset than someone who just matches a list.