Duration: 12 months + extensions Location: 1-2x/week onsite Toronto Rate: 60-77hr

Required Skills & Experience

4–7 years of product design experience, including at least 1 year focused on design systems or component‑library work

Strong interest in design‑to‑code workflows and emerging technologies that improve design‑system implementation and flexibility

Hands‑on experience contributing to or maintaining a design system within a multi‑team organization

Front‑end fluency: comfortable with HTML, CSS, and JavaScript; able to build and maintain design‑token tooling (e.g., Style Dictionary, Tokens Studio, or similar)

Deep proficiency with Figma libraries, variables, and token workflows

Strong attention to detail, documentation habits, and systems thinking from the token level upward

Collaborative working style; able to take direction on pattern priorities while independently owning execution

Experience in regulated or healthcare‑adjacent domains is an asset

Job Description

Audit and consolidate Health design patterns, components, and assets across products into a cohesive platform‑level library

Maintain and evolve the Health design foundation: tokens, components, patterns, and documentation tailored to domain‑specific needs (clinical content, regulated flows, accessibility)

Build and maintain the design‑token pipeline, ensuring smooth translation from Figma variables to engineering‑consumable formats

Collaborate closely with the Health Platform team and Conversational Design Lead to ensure the foundation supports conversational and agentic UI patterns, including streaming responses, citations, and uncertainty states

Partner with adjacent design‑system teams to align on shared patterns and avoid duplicative work

Manage the relationship with the enterprise design system by tracking inheritance, documenting extensions, and identifying when intentional branching is appropriate

Prototype components in code when doing so accelerates validation or improves engineering handoff

Establish contribution and adoption workflows so product designers can use and extend the foundation without friction

Document rationale, decisions, and system architecture to ensure continuity beyond the contract term