Design-järjestelmän suunnittelija

Design at Pennylane What you\'ll bring Design System Expertise - Hands-on experience contributing to a design system at scale: designing components, defining variants and APIs, modeling tokens, and maintaining Figma libraries used by 40+ designers - Strong understanding of design token systems, semantic naming, and theming / multi-brand patterns - Skilled at running design system audits, spotting inconsistencies in product surfaces, and bringing them back into the system - Experience writing component documentation that is clear for designers, engineers, and product managers - Expertise in what makes a design system interpretable and usable by AI: structured content, machine-readable patterns, AI-ready documentation conventions, and how an LLM or codegen agent consumes a design system - Solid grounding in accessibility (WCAG) and inclusive design practices Mindset - You want to push the design system toward an ambitious vision, but you know how to slice the path into small intermediate milestones that deliver value at every step, rather than waiting for the perfect end state - You are pragmatic: you don\'t overthink, you don\'t always work by the book, and you know when a \'good enough\' solution beats a perfect one - You are curious about how design systems are evolving in 2026 (AI, codegen, token automation, MCP) - You enjoy switching between deep craft work and pragmatic system-level decisions Technical Partnership - Strong technical acumen with a clear understanding of how design systems are implemented in code - Comfortable working in a production-first environment where code is the source of truth, and Figma reflects what ships - Experience partnering with engineering teams to ensure design–code parity and smooth implementation of new components Enablement & Communication - Experience supporting product designers through office hours, a support model, or peer review - Demonstrated ability to evangelize a design system, present design rationale, and translate component-level decisions for non-design stakeholders - Ability to handle complex support requests and turn recurring questions into permanent improvements (docs, lint rules, worked examples)