Principal Design Systems Designer - 6 months contract

📍 Job Overview

Job Title: Principal Design Systems Designer (6-Month Contract)

Company: Malwarebytes

Location: Tallinn, Estonia; Sweden; Italy; Spain; Portugal; Finland

Job Type: Contract

Category: Design Operations / Product Design

Date Posted: May 06, 2026

Experience Level: Senior / Principal (10+ years implied)

Remote Status: Remote OK

🚀 Role Summary

• Lead the comprehensive rebuild and strategic evolution of Malwarebytes' design ecosystem across mobile, desktop, and web platforms.

• Act as the primary owner for the design system's architecture, setting foundational standards and driving key decisions for scalability and consistency.

• Define and champion the unified visual design language and principles that will govern all product interfaces.

• Develop and maintain a robust, scalable component library within Figma, ensuring seamless integration for both design and engineering teams.

• Establish and manage the design system's change management processes, including contribution models, versioning, and deprecation workflows.

📝 Enhancement Note: While the title is "Principal Design Systems Designer," the core responsibilities and experience requirements strongly indicate a leadership role focused on building and architecting a design system from the ground up. This isn't just about contributing to an existing system, but defining its very structure and future. The contract nature (6 months) suggests a project-based initiative with a clear, high-impact objective. The "Remote OK" status across multiple European countries indicates flexibility but also the need for strong remote collaboration and time zone management.

📈 Primary Responsibilities

• Spearhead the end-to-end rebuild of the design ecosystem, unifying the user experience across Malwarebytes' mobile app, desktop client, and web services.

• Own the architectural decisions and strategic direction for the design system, including component structure, design tokens, and overall system governance.

• Define and implement the visual design language and core principles for desktop, web, iOS, and Android platforms.

• Construct and meticulously maintain a standardized, scalable component library in Figma, from inception, to serve both design and engineering needs effectively.

• Establish and oversee the change management process for the design system, encompassing contribution models, versioning strategies, and deprecation workflows.

• Develop and maintain comprehensive design system documentation to empower designers and engineers in building consistently and autonomously.

• Act as the internal authority and primary advocate for design systems, setting standards and guiding adoption best practices across cross-functional teams.

• Collaborate closely with engineering teams to develop well-documented, production-ready components that directly translate into high-quality code.

• Define UI visual quality standards and conduct rigorous quality assurance to ensure consistency and polish across all Malwarebytes products.

• Champion and embed accessibility best practices throughout all layers of the design system.

• Proactively identify and address gaps, inconsistencies, and opportunities for improvement across the entire product ecosystem.

• Develop comprehensive design guidelines that embody the Malwarebytes brand and elevate overall product quality standards.

📝 Enhancement Note: The responsibilities go beyond typical design system maintenance. They emphasize "end-to-end rebuild," "from first principles," and "owning architectural decisions," highlighting a significant foundational project. The focus on "setting standards," "governance," and "change management" points to a strategic, process-oriented leadership role within the design domain, akin to operations in its structural and systemic impact.

🎓 Skills & Qualifications

Education: While not explicitly stated, a Bachelor's or Master's degree in Design, HCI, Computer Science, or a related field is typically expected for a Principal-level role. Relevant certifications in design systems or UX are a plus.

Experience:

• 8+ years of progressive experience in UX/Product Design, with a strong emphasis on complex B2C and B2B systems and platforms.

• 5+ years of dedicated, hands-on experience in building and leading design systems within product-focused organizations.

Required Skills:

• Expertise in Figma, including advanced capabilities such as component libraries, variables, auto-layout, and tokenization.

• Proven ability to architect and own design system decisions, not merely contribute to existing frameworks.

• Deep understanding of design tokens, component governance, versioning strategies, and comprehensive system documentation.

• Exceptional cross-functional collaboration skills, with a strong history of partnership with engineering and product leadership.

• Demonstrated capacity to influence and drive alignment across teams, even without direct reporting authority.

• Passion for design systems and their strategic impact on product quality, consistency, and team velocity.

• Ability to work autonomously, demonstrate adaptability, and thrive in a fast-paced, ambiguous environment.

• Pragmatic, organized, and capable of effective prioritization and meeting deadlines.

Preferred Skills:

• Experience with design system contribution models and change management processes.

• Familiarity with accessibility standards (WCAG) and their implementation in design systems.

• Experience in defining and enforcing UI visual quality standards.

• Understanding of how design systems translate into production-ready code.

• Experience with design system governance frameworks and community building.

📝 Enhancement Note: The experience requirement of "8+ years in UX/product design" and "5+ years building design systems" clearly positions this as a senior to principal-level engagement. The emphasis on "making and owning architectural decisions" and "building from scratch" is key. The AI-derived "10+" years experience level aligns with this Principal designation.

📊 Process & Systems Portfolio Requirements

Portfolio Essentials:

• A dedicated section showcasing your experience in building or leading the rebuild of design systems, with a focus on foundational architecture and strategic decision-making.

• Detailed case studies demonstrating your work on component libraries, design tokens, and system governance frameworks.

• Examples of how you have defined and implemented visual design languages across multiple platforms (web, mobile, desktop).

• Evidence of your ability to create comprehensive design system documentation and guidelines.

Process Documentation:

• Showcase examples of how you've documented design system processes, including change management, contribution models, versioning, and deprecation workflows.

• Illustrate your approach to establishing and enforcing UI visual quality standards and QA processes.

• Present your methodology for embedding accessibility best practices into a design system.

📝 Enhancement Note: A candidate's portfolio is paramount for this role. It needs to go beyond showcasing UI design skills and explicitly demonstrate the strategic and architectural capabilities required for building a design system from the ground up. The focus should be on process, governance, and cross-functional enablement, mirroring the operational aspects of managing a complex system.

💵 Compensation & Benefits

Salary Range: Given the contract nature, senior-principal level expertise, and remote availability across multiple European countries, a competitive hourly or daily rate is expected. Based on industry benchmarks for Principal Design System roles in Western Europe, the estimated range could be:

• Hourly Rate: €60 - €100+ per hour (or equivalent in local currency)

• Daily Rate: €480 - €800+ per day (or equivalent in local currency)

This estimation is based on market research for senior design system specialists in locations like Tallinn, Sweden, Italy, Spain, and Portugal, considering the contract duration and the high-impact nature of rebuilding a core design ecosystem.

Benefits: As a 6-month contract role, benefits may differ from full-time employment. Typically, contractors receive:

• Competitive hourly/daily rate reflecting their specialized skills.

• Potential for contract extension based on project performance and company needs.

• Opportunity to work on a high-impact, foundational project with significant autonomy.

• Flexibility in work location within the specified European countries (remote).

• Exposure to leading cybersecurity technology and a dynamic product suite.

Working Hours: A standard full-time engagement is implied, likely around 40 hours per week. The role requires significant autonomy and collaboration, necessitating effective time management and availability during core business hours across various European time zones.

📝 Enhancement Note: Salary estimation for contract roles requires careful consideration of hourly/daily rates rather than annual. The provided range reflects the seniority and specialized nature of a Principal Design Systems Designer, especially for a rebuilding initiative. Benefits are typically more limited for contractors, focusing on the rate and project opportunity.

🎯 Team & Company Context

🏢 Company Culture

Industry: Cybersecurity / Software. Malwarebytes is a leading cybersecurity company focused on protecting individuals and organizations from advanced threats. This context implies a need for robust, secure, and user-friendly interfaces, especially for complex security products.

Company Size: Malwarebytes is a medium-to-large enterprise, likely employing several hundred to over a thousand employees globally. This size suggests established product teams and a need for scalable design systems to maintain consistency across a growing product portfolio.

Founded: Malwarebytes was founded in 2004. This history indicates a mature company with established products and a current phase of significant product development or modernization, making a design system rebuild a logical strategic initiative.

Team Structure:

• The Principal Design Systems Designer will likely be part of the core Product Design or UX team.

• This role will report to a Director or VP of Design/Product.

• Close collaboration is expected with Product Management, Engineering (front-end developers, UI engineers), and potentially Brand/Marketing teams.

Methodology:

• Data Analysis & Insights: The role will require analyzing user feedback, product analytics, and adoption metrics to inform design system improvements and demonstrate impact.

• Workflow Planning & Optimization: Developing efficient contribution models, review processes, and adoption strategies for the design system is crucial.

• Automation & Efficiency: The design system itself is a tool for automation and efficiency, enabling faster and more consistent product development.

Company Website: https://www.malwarebytes.com/

📝 Enhancement Note: The company's industry (cybersecurity) suggests that user experience must be both intuitive and trustworthy. The scale of Malwarebytes implies that a robust, well-managed design system is not just a convenience but a necessity for efficient product development and consistent brand experience across a diverse product suite.

📈 Career & Growth Analysis

Operations Career Level: This role represents a Principal-level individual contributor. It is a highly specialized and senior position focused on architectural leadership within the design domain, akin to a principal engineer or architect in software development. The impact is strategic, influencing product development velocity, consistency, and overall user experience quality.

Reporting Structure: The Principal Designer will likely report to a senior design leader (e.g., Director of Design, VP of Product). While not a management role in terms of direct reports, it requires significant leadership in influencing and guiding cross-functional teams.

Operations Impact: The design system directly impacts the efficiency of design and engineering teams, reduces development time, ensures brand consistency, improves user experience quality, and can accelerate time-to-market for new features and products. This role has a direct impact on operational efficiency within product development.

Growth Opportunities:

• Specialization: Deepen expertise in design systems, component architecture, and cross-platform design strategies.

• Leadership: Transition to a Design Systems Manager role if the contract is extended or if opportunities arise, leading a dedicated team.

• Strategic Influence: Further influence product strategy and development processes through the successful implementation and adoption of the design system.

• Mentorship: Mentor other designers and engineers on design system best practices and implementation.

📝 Enhancement Note: This contract role is a significant opportunity for a seasoned designer to make a profound impact by building a foundational system. Growth potential exists in leadership and deeper strategic influence within design operations.

🌐 Work Environment

Office Type: While the role is "Remote OK," Malwarebytes has physical office locations. The specific team's working model (fully remote, hybrid within a specific location, or distributed across the listed countries) will determine the immediate office environment. However, the emphasis on remote collaboration tools and practices is paramount.

Office Location(s): The role is open to candidates in Tallinn (Estonia), Sweden, Italy, Spain, and Portugal. This broad geographical spread necessitates robust remote collaboration infrastructure and practices.

Workspace Context:

• Collaborative Environment: Expect a highly collaborative remote environment, leveraging tools like Slack, Zoom, Figma, and project management software.

• Operations Tools & Technology: Access to industry-standard design tools (Figma), communication platforms, and potentially project management or documentation tools will be provided or expected.

• Team Interaction: Regular virtual meetings, design reviews, and collaborative working sessions will be key to success.

Work Schedule: A standard 40-hour work week is typical. However, candidates should be prepared for potential flexibility to accommodate cross-team collaboration across different European time zones. Proactive communication and asynchronous work practices will be essential for a distributed team.

📝 Enhancement Note: The distributed nature of this role across multiple countries requires a strong emphasis on asynchronous communication, clear documentation, and effective use of remote collaboration tools. Time zone management will be a critical aspect of the work environment.

📄 Application & Portfolio Review Process

Interview Process:

• Initial Screening: A review of your resume and portfolio, focusing on direct experience in building design systems from scratch and leadership capabilities.

• Portfolio Presentation & Technical Interview: A deep dive into your portfolio, with a focus on your strategic approach to design system architecture, component development, governance, and cross-functional collaboration. Expect to discuss specific case studies.

• Cross-Functional Interviews: Sessions with Product Managers and Engineering leads to assess collaboration style, technical understanding, and ability to influence.

• Leadership/Culture Fit Interview: Discussion with senior design or product leadership to evaluate strategic thinking, autonomy, and alignment with Malwarebytes' culture.

Portfolio Review Tips:

• Highlight "From Scratch" Experience: Clearly showcase projects where you were instrumental in building or rebuilding a design system, emphasizing architectural decisions and strategic ownership.

• Demonstrate Systemic Thinking: Present how you've approached component structure, design tokens, and system governance. Use diagrams or visual aids to explain your framework.

• Showcase Collaboration & Influence: Provide examples of how you've worked with engineering and product teams, and how you've driven adoption and alignment.

• Quantify Impact: Where possible, use metrics to demonstrate the impact of your design system work (e.g., increased design/development velocity, improved consistency, reduced bugs).

• Address Platform Diversity: Explicitly show how your design system approach can scale across mobile, desktop, and web.

Challenge Preparation:

• Be prepared to discuss your approach to defining design principles, establishing a component taxonomy, and managing design debt.

• Anticipate questions about how you would onboard new teams to a design system and measure its adoption and success.

• Think about how you would handle conflicting design or engineering requirements within the context of a design system.

📝 Enhancement Note: The interview process will heavily scrutinize your portfolio for evidence of foundational design system building and strategic leadership. Be ready to articulate your decision-making process, not just the final output.

🛠 Tools & Technology Stack

Primary Tools:

• Figma: Essential for component library creation, prototyping, and collaboration. Advanced proficiency with variables, auto-layout, and design tokens is critical.

• Design System Management Tools: Potentially tools like Zeroheight, Storybook (for developer documentation integration), or other platforms for organizing and disseminating design system information.

Analytics & Reporting:

• Product Analytics Platforms: Tools like Amplitude, Mixpanel, or Google Analytics (or similar) to track design system adoption and impact on user behavior.

• User Feedback Tools: Platforms for collecting and analyzing user feedback to identify areas for design system improvement.

CRM & Automation:

• Project Management Software: Tools like Jira, Asana, or Trello for tracking design system tasks, bug fixes, and feature requests.

• Communication Platforms: Slack, Microsoft Teams, or similar for daily team communication and collaboration.

• Documentation Tools: Confluence, Notion, or internal wikis for comprehensive design system documentation.

📝 Enhancement Note: Figma is explicitly mentioned and is the core tool. The role necessitates familiarity with the broader ecosystem of tools that support design system development, documentation, and adoption, particularly those used for collaboration and tracking impact.

👥 Team Culture & Values

Operations Values:

• User-Centricity: A strong focus on understanding and meeting user needs through consistent and high-quality experiences.

• Collaboration: Emphasizing cross-functional teamwork and open communication between design, product, and engineering.

• Excellence & Quality: A commitment to high standards in design, development, and overall product polish.

• Efficiency & Velocity: Driving processes and tools that enable faster, more effective product development.

• Innovation: A culture that encourages creative problem-solving and continuous improvement.

Collaboration Style:

• Partnership: Working as a peer and strategic partner with Product Management and Engineering leads.

• Empowerment: Enabling other designers and engineers to leverage the design system effectively.

• Feedback-Driven: Open to constructive feedback and iterative development of the design system.

• Knowledge Sharing: Actively sharing knowledge and best practices related to design systems.

📝 Enhancement Note: While specific company values aren't listed, the nature of a design system role implies a culture that values consistency, efficiency, collaboration, and a commitment to quality. The "Principal" title suggests a leadership style that is collaborative and empowering rather than purely directive.

⚡ Challenges & Growth Opportunities

Challenges:

• Building from Scratch: Rebuilding a design system from the ground up is a significant undertaking, requiring strong strategic vision and execution.

• Cross-Platform Consistency: Ensuring a unified experience across vastly different platforms (mobile, desktop, web) presents complex technical and design challenges.

• Adoption & Governance: Getting buy-in and ensuring consistent adoption from diverse design and engineering teams can be difficult.

• Ambiguity & Pace: Operating in a fast-paced, contract environment with potential for evolving requirements.

• Remote Collaboration: Managing communication and collaboration effectively across multiple time zones and diverse teams.

Learning & Development Opportunities:

• Advanced Design System Architecture: Opportunity to refine and expand expertise in complex design system structures.

• Cross-Functional Leadership: Developing skills in influencing and leading without direct authority across product and engineering.

• Strategic Impact: Gaining experience in driving significant, foundational changes within a product organization.

• Diverse Platform Experience: Deepening understanding of design and development nuances across mobile, desktop, and web.

📝 Enhancement Note: The primary challenge is the scope and impact of rebuilding a core system. The growth opportunities lie in deepening expertise within this specialized field and honing leadership skills in a cross-functional, distributed environment.

💡 Interview Preparation

Strategy Questions:

• "Describe your approach to architecting a design system for a complex product suite like Malwarebytes, covering mobile, desktop, and web."

• "How would you define and implement design tokens to ensure consistency and scalability across platforms?"

• "What strategies would you employ to ensure successful adoption of the new design system by both design and engineering teams?"

• "How do you balance the need for consistency with the need for product-specific innovation within a design system?"

Company & Culture Questions:

• "Why are you interested in Malwarebytes and our mission?"

• "How do you approach working autonomously and managing your time effectively in a remote contract role?"

• "What does 'user-centricity' mean to you in the context of cybersecurity products?"

Portfolio Presentation Strategy:

• Structure: Organize your portfolio to clearly highlight your design system building experience. Use case studies that detail the problem, your strategic approach (architecture, components, governance), the execution, and the outcome/impact.

• Visuals: Use clear, concise visuals. Show examples of components, design tokens, documentation, and how they've been applied in products.

• Narrative: Tell a compelling story about your process, decisions, and the challenges you overcame. Emphasize your leadership and collaborative abilities.

• Demonstrate Technical Understanding: Be prepared to discuss how your design system components translate to code and integrate with engineering workflows.

📝 Enhancement Note: Interview preparation should focus on articulating your strategic thinking, architectural decision-making, and experience in building foundational systems. Be ready to "show, don't just tell" through your portfolio.

📌 Application Steps

To apply for this operations position:

• Submit your application through the provided link on the rippling.com careers portal.

• Tailor your resume: Highlight your experience in building and leading design systems from scratch, emphasizing architectural ownership, cross-platform experience, and Figma proficiency. Use keywords from the job description.

• Curate your portfolio: Ensure it prominently features your design system work, with clear case studies detailing your strategic decisions, process, and impact. Focus on architectural contributions, component libraries, and governance.

• Prepare for a portfolio presentation: Be ready to walk through your design system projects, explaining your rationale, challenges, and successful outcomes to design and engineering stakeholders.

• Research Malwarebytes: Understand their product suite, mission (cybersecurity), and target audience to tailor your responses and demonstrate cultural fit and strategic alignment.

⚠️ Important Notice: This enhanced job description includes AI-generated insights and operations industry-standard assumptions. All details should be verified directly with the hiring organization before making application decisions.