Staff Frontend Engineer - Design Systems

📍 Job Overview

Job Title: Staff Frontend Engineer - Design Systems

Company: Pleo

Location: Copenhagen, Denmark; Lisbon, Portugal; London, United Kingdom

Job Type: Full-Time

Category: Frontend Engineering / Design Systems

Date Posted: August 06, 2026

Experience Level: Mid-Senior to Staff Level (Implied 5-10+ years)

Remote Status: Hybrid / Fully Remote Options Available

🚀 Role Summary

• Lead the technical direction and evolution of Pleo's Design System, "Telescope," ensuring UI consistency and quality across web and mobile platforms.

• Drive adoption of the design system by product teams, enhancing their ability to ship features faster with integrated UI, accessibility, and quality standards.

• Improve the developer and contributor experience through automation, tooling, and streamlined contribution models for the design system.

• Act as a force multiplier for product delivery and UI quality by blending strategic planning with hands-on coding and technical mentorship.

• Collaborate closely with Design and Engineering stakeholders to steward shared foundations, drive adoption, and maintain high standards for components, patterns, and documentation.

📝 Enhancement Note: This role is highly specialized within frontend engineering, focusing on the critical area of design systems. The "Staff" title indicates a senior individual contributor role with significant influence over technical strategy, architecture, and team processes. The emphasis on "force multiplier" and "leading technical direction" suggests a need for strong technical leadership and architectural vision, not just component development.

📈 Primary Responsibilities

• Set and drive the technical architecture, component standards, release practices, and quality assurance for Pleo's "Telescope" design system.

• Evolve and manage the contribution model, defining how product teams interact with and contribute to the design system.

• Own and optimize the request intake process for the design system team, including triage, prioritization, and expectation management.

• Enhance developer experience through tooling and automation, focusing on visual testing, operational support, adoption metrics, and documentation publishing workflows.

• Lead team rituals, ensuring effectiveness, alignment, and continuous improvement within the Design Systems team.

• Represent the Design Systems team in cross-functional initiatives, aligning stakeholders across Design, Product, and Engineering.

• Coach and mentor frontend engineers, fostering technical growth and leadership within the broader frontend community.

• Contribute directly to codebase development, balancing strategic initiatives with hands-on coding to deliver impactful solutions.

• Drive adoption and measure the health and effectiveness of the design system across Pleo's product portfolio.

• Ensure adherence to accessibility and performance best practices within the design system's components and patterns.

📝 Enhancement Note: The responsibilities highlight a blend of strategic leadership, process ownership, technical contribution, and community building. The emphasis on improving developer experience and contribution models is key, suggesting a need for someone who can not only build but also enable and scale the impact of the design system across a large organization.

🎓 Skills & Qualifications

Education: While no specific degree is listed, a Bachelor's or Master's degree in Computer Science, Engineering, or a related field is often preferred for Staff-level engineering roles. Equivalent practical experience will also be strongly considered.

Experience: Significant experience (likely 5-10+ years) in frontend engineering, with a proven track record of building and maintaining component libraries or platform-like products serving multiple development teams.

Required Skills:

• Deep expertise in building and maintaining scalable component libraries and platform-like products.

• Proficiency in TypeScript and modern frontend development practices.

• Strong experience with React (explicitly mentioned as a plus, indicating high value).

• Demonstrated ability to design maintainable systems with clear architectural boundaries, robust versioning, and backward compatibility strategies.

• Solid understanding and practical experience with testing methodologies and tooling (unit, integration, end-to-end testing).

• Strong commitment to quality assurance and a quality-first mindset.

• In-depth knowledge of accessibility (WCAG) and performance best practices for UI systems.

• Proven experience collaborating effectively with designers and product engineers, adept at navigating and managing tradeoffs across diverse stakeholder needs.

• Experience with modern frontend build tools and workflows. Preferred Skills:

• Hands-on experience with visual regression testing tools and frameworks.

• Familiarity with CI/CD pipelines and automation for component library development and deployment.

• Experience with documentation generation tools (e.g., Storybook, Docz).

• Understanding of design token systems and their implementation.

• Experience in a fast-paced, growing tech company environment.

• Familiarity with FinTech or SaaS product development.

📝 Enhancement Note: The emphasis on "Staff Engineer" implies a need for architectural thinking, strategic influence, and the ability to mentor. While React is listed as a "plus," proficiency in modern frontend frameworks and a deep understanding of component library architecture are core. The ability to "raise the bar with pragmatism and care" suggests a need for strong interpersonal skills alongside technical acumen.

📊 Process & Systems Portfolio Requirements

Portfolio Essentials:

• Demonstrable examples of building and maintaining robust component libraries or platform-like products.

• Case studies showcasing how your contributions have improved UI consistency, developer efficiency, or product quality across multiple teams.

• Evidence of designing systems with clear boundaries, versioning strategies, and backward compatibility considerations.

• Examples of implementing comprehensive testing strategies (unit, integration, E2E) for UI components.

• Documentation or examples of how you've incorporated accessibility and performance best practices into a design system. Process Documentation:

• Examples of contributions to or creation of design system contribution models.

• Documentation illustrating streamlined request intake, triage, and prioritization processes for shared components.

• Case studies detailing improvements made to developer experience through tooling, automation, or workflow enhancements within a design system context.

• Demonstrations of how you've measured and communicated design system adoption and health.

• Examples of evolving documentation publishing workflows for shared component libraries.

📝 Enhancement Note: For a Staff Engineer role, especially in Design Systems, a portfolio should emphasize architectural thinking, strategic impact, and enablement. Candidates should be prepared to showcase not just code, but also the processes, strategies, and collaborative efforts that led to successful design system implementation and adoption. Demonstrating a "force multiplier" effect through your work will be critical.

💵 Compensation & Benefits

Salary Range: As a Staff Frontend Engineer in locations like London, Copenhagen, or Lisbon, and given Pleo's growth stage and the specialized nature of this role, a competitive salary is expected. Based on industry benchmarks for Staff Frontend Engineers in these major European tech hubs, the annual salary range could be estimated between €90,000 - €140,000 (or equivalent in GBP/DKK). This estimate considers the experience level, specific expertise in design systems, and the cost of living in these high-demand cities.

Benefits:

• Your own Pleo card (eliminating out-of-pocket expenses).

• Catered meals or lunch allowance for work days.

• Comprehensive private healthcare (options include Vitality, Alan, or Médis, depending on location).

• 25 days of holiday plus public holidays.

• Hybrid and fully remote working options.

• Access to free mental health and well-being support via MyndUp.

• Paid parental leave to support family needs.

Working Hours: Full-time, with flexibility offered through hybrid and remote work options. Standard working hours are approximately 40 hours per week, with an emphasis on progress over perfection and work-life balance.

📝 Enhancement Note: Salary ranges are estimated based on industry data for Staff-level Frontend Engineers in comparable European tech hubs. Actual compensation will depend on candidate experience, specific location, and negotiation. The benefits package is robust, emphasizing employee well-being and work-life integration, which is common for progressive tech companies.

🎯 Team & Company Context

🏢 Company Culture

Industry: Fintech (specifically, spend management solutions). Pleo operates in a competitive landscape, aiming to disrupt traditional business spending processes with modern, user-friendly technology.

Company Size: 850+ employees. This indicates a mature startup or scale-up environment where processes are established but still evolving, offering opportunities for impact and influence.

Founded: 10 years ago. Pleo has a decade of experience, suggesting stability and a proven product-market fit, while still maintaining a growth-oriented mindset.

Team Structure:

• The Design Systems team is a specialized group within the broader Engineering organization. It's likely composed of engineers and designers focused on building and maintaining the "Telescope" design system.

• The Staff Engineer will report into an Engineering Manager or Head of Frontend, and will work closely with Design leadership.

• Cross-functional collaboration is essential, involving product teams, individual engineers, and designers across the company to drive adoption and gather feedback. Methodology:

• Data-driven decision-making is implied by the need to "measure and communicate adoption and system health."

• Agile methodologies are likely employed for iterative development and continuous improvement of the design system.

• A strong emphasis on collaboration, pragmatism, and user-centricity (both internal users like developers and external users like Pleo customers).

• Focus on building maintainable, scalable, and high-quality systems.

Company Website: https://www.pleo.io/

📝 Enhancement Note: Pleo positions itself as a progressive, kind, and ambitious company. The "more than you'd expect" mantra suggests a culture that values innovation and exceeding expectations. For operations candidates, this means a dynamic environment where contributions are visible and impactful, but also requires adaptability and a proactive approach to process improvement and problem-solving.

📈 Career & Growth Analysis

Operations Career Level: Staff Engineer. This is a senior individual contributor role, recognized for deep technical expertise, architectural influence, and the ability to drive significant technical initiatives. It's a step above Senior Engineer, often involving mentorship, technical strategy, and cross-team impact.

Reporting Structure: The Staff Frontend Engineer will likely report to an Engineering Manager or Director of Engineering, with a strong dotted line to Design leadership. They will collaborate closely with product teams and senior engineers across the organization.

Operations Impact: This role has a direct and significant impact on product delivery speed, UI/UX consistency, and overall engineering efficiency. By enabling product teams through a robust design system, the Staff Engineer contributes to faster feature releases, improved customer experience, and reduced development overhead.

Growth Opportunities:

• Technical Leadership: Deepen expertise in frontend architecture, design systems, and scaling complex UIs. Opportunity to define future technical direction for frontend at Pleo.

• Mentorship & Coaching: Grow leadership skills by mentoring junior and mid-level engineers, contributing to the overall growth of Pleo's frontend community.

• Strategic Influence: Play a key role in shaping product development strategy through the design system's capabilities and adoption.

• Cross-functional Impact: Gain broad exposure to different product areas and engineering challenges across Pleo.

• Potential for Principal/Architect Roles: Long-term progression could lead to Principal Engineer or Architect roles, focusing on even broader technical strategy and innovation.

📝 Enhancement Note: The "Staff" title signifies a high level of technical contribution and influence. Growth opportunities are focused on deepening technical expertise, expanding leadership capabilities through mentorship, and increasing strategic impact within the organization. This is a role for an engineer who wants to be a technical leader and a driver of best practices.

🌐 Work Environment

Office Type: Pleo offers hybrid and fully remote options, suggesting a modern, flexible work environment. Their physical office spaces in Copenhagen, Lisbon, and London are likely designed to foster collaboration and community.

Office Location(s):

• Copenhagen, Denmark

• Lisbon, Portugal

• London, United Kingdom

These are major European tech hubs, offering vibrant working environments and excellent connectivity.

Workspace Context:

• Collaborative Environment: The emphasis on hybrid and remote work, coupled with the need for cross-functional collaboration, implies a culture that supports both focused individual work and effective team interaction, utilizing digital collaboration tools extensively.

• Operations Tools & Technology: Access to modern development tools, collaboration platforms (e.g., Slack, Jira, Confluence), and potentially sophisticated design and prototyping tools. The design system itself is a key technological asset.

• Team Interaction: Regular interactions with designers, product managers, and frontend engineers through meetings, code reviews, and collaborative sessions. The role involves being a central point of contact for design system-related queries and guidance.

Work Schedule: Full-time, with flexibility. While core hours or team syncs may be required, the hybrid/remote nature allows for some autonomy in managing the daily schedule, balancing deep work with team collaboration and personal needs.

📝 Enhancement Note: The hybrid and remote options are a significant aspect of the work environment, catering to diverse employee needs. The company culture emphasizes collaboration and community, which will be facilitated through digital tools and intentional in-person gatherings where applicable.

📄 Application & Portfolio Review Process

Interview Process:

• Application Submission: Submit application via the Ashby portal, ensuring all required information is provided in English.

• Initial Screening: Talent team reviews applications for alignment with core requirements.

• Technical Interview(s): Likely involves discussions on frontend architecture, design systems, problem-solving, and potentially coding challenges. Expect questions on TypeScript, React, component library design, testing, and performance.

• Design Systems Deep Dive: Focused interview with the Design Systems team and potentially Design leads to assess understanding of design system principles, contribution models, and collaboration strategies.

• Staff-Level Interview: Assessment of technical leadership, strategic thinking, mentorship capabilities, and ability to influence across teams. This may involve behavioral questions and scenario-based problem-solving.

• Final Interview/Meet the Team: Opportunity to meet with senior leadership or key stakeholders to discuss vision, culture fit, and final alignment.

Portfolio Review Tips:

• Focus on Impact: Showcase projects where your design system work led to measurable improvements in development speed, consistency, or quality. Quantify where possible (e.g., "reduced component development time by X%", "increased adoption by Y%").

• Highlight Architecture & Strategy: For a Staff role, demonstrate your thinking around system architecture, versioning, contribution models, and scalability.

• Showcase Collaboration: Include examples of how you've partnered effectively with designers and engineers, managed feedback, and navigated tradeoffs.

• Detail Technical Rigor: Present examples of your testing strategies, performance optimizations, and accessibility implementations.

• Use Case Studies: Structure your portfolio around case studies that tell a story: problem, your approach, technical details, challenges, and outcomes.

Challenge Preparation:

• Technical Challenges: Be prepared for live coding or take-home challenges focusing on building reusable components, implementing tests, or architecting a small system.

• System Design: Expect questions about designing a scalable design system, its contribution model, or how to handle versioning and deprecation.

• Behavioral & Situational: Prepare for questions about how you handle conflict, mentor others, prioritize work, and drive consensus. Use the STAR method (Situation, Task, Action, Result).

• Design System Specifics: Be ready to discuss your philosophy on design systems, best practices, and how you'd approach specific challenges at Pleo (e.g., driving adoption, improving contributor experience).

📝 Enhancement Note: The application process emphasizes a thorough evaluation of technical skills, strategic thinking, and collaborative ability, fitting for a Staff Engineer role. A strong portfolio that demonstrates impact and architectural vision is crucial. The company's commitment to diversity and inclusion means candidates should feel empowered to highlight their unique experiences.

🛠 Tools & Technology Stack

Primary Tools:

• Frontend Framework: React (highly valued), with modern JavaScript/TypeScript experience.

• Component Library Development: Tools like Storybook for documentation, development, and testing.

• TypeScript: Essential for robust, scalable frontend code.

• Version Control: Git and platforms like GitHub/GitLab.

• Build Tools: Webpack, Vite, or similar for efficient build processes.

Analytics & Reporting:

• Design System Metrics: Tools or custom solutions for tracking component usage, adoption rates, and contribution frequency.

• Performance Monitoring: Tools like Lighthouse, WebPageTest, or integrated APM solutions.

• CI/CD: Jenkins, GitHub Actions, GitLab CI, or similar for automated testing and deployment of design system components.

CRM & Automation:

• While not directly part of the frontend role, understanding how the design system integrates with broader product development workflows (which might involve CRM data visibility for customer-facing applications) is beneficial.

• Automation Tools: For build processes, testing, documentation publishing, and potentially release management.

📝 Enhancement Note: The technology stack is heavily focused on modern frontend development and the tooling required for effective design system creation and maintenance. Proficiency in React and TypeScript is paramount, along with a strong understanding of the ecosystem surrounding component libraries and developer tooling.

👥 Team Culture & Values

Operations Values:

• Progress over Perfection: Embracing iterative development and continuous improvement, while maintaining a high bar for quality.

• Pragmatism and Care: Applying practical solutions with genuine consideration for users (developers, designers, customers).

• Clarity and Collaboration: Communicating effectively, listening actively, and bringing others along in decision-making processes.

• Problem Solving: Enjoying the process of breaking down complex issues, gathering input, and driving towards well-considered solutions.

• Growth Mindset: Fostering an environment where engineers can learn, grow, and develop technical leadership.

• Customer Centricity: Ultimately building solutions that empower businesses and make spend management surprisingly effective.

Collaboration Style:

• Cross-functional Integration: Working seamlessly with Design, Product, and various Engineering teams to ensure the design system meets diverse needs and drives adoption.

• Open Communication: Encouraging transparent discussions, feedback loops, and knowledge sharing within the team and across the organization.

• Empowerment: Creating an environment where team members feel empowered to contribute, experiment, and take ownership.

• Building Bridges: Acting as a liaison between design intent and engineering execution, ensuring alignment and shared understanding.

📝 Enhancement Note: Pleo's stated values of pragmatism, care, clarity, and collaboration are central to how the team operates. For this role, it means being a proactive communicator, a supportive team member, and someone who can balance technical rigor with the human element of software development.

⚡ Challenges & Growth Opportunities

Challenges:

• Driving Adoption: Ensuring widespread and consistent adoption of the design system across numerous product teams, each with their own priorities and workflows.

• Balancing Innovation & Stability: Evolving the design system with new components and patterns while maintaining backward compatibility and stability for existing implementations.

• Managing Contributions: Establishing and refining a contribution model that encourages external input while maintaining quality and architectural integrity.

• Scaling with Growth: Ensuring the design system can scale effectively as Pleo continues to grow its product offerings and engineering teams.

• Measuring Impact: Developing robust metrics to accurately track the value and ROI of the design system.

Learning & Development Opportunities:

• Advanced Frontend Architecture: Deep dive into complex frontend system design, performance optimization, and scalable component architectures.

• Design Systems Strategy: Develop expertise in the strategic planning, governance, and long-term vision of design systems.

• Leadership & Mentorship: Hone skills in coaching, mentoring, and technical leadership through direct involvement with the engineering community.

• Cross-functional Exposure: Gain valuable experience working across different product domains and engineering disciplines within Pleo.

• Industry Best Practices: Stay at the forefront of design system trends, tooling, and methodologies through continuous learning and community engagement.

📝 Enhancement Note: The challenges presented are typical for a senior role in a growing organization, offering significant opportunities for problem-solving and skill development. The growth opportunities are geared towards advancing technical leadership and strategic impact.

💡 Interview Preparation

Strategy Questions:

• "Describe a complex component library you've built or significantly contributed to. What were the architectural decisions, and why?" (Focus on system design, boundaries, versioning)

• "How would you approach evolving a design system's contribution model to encourage more adoption and contributions from product teams?" (Focus on process, collaboration, developer experience)

• "Imagine a product team is resistant to adopting the design system. How would you address their concerns and encourage adoption?" (Focus on stakeholder management, value proposition, empathy)

• "What are your strategies for ensuring accessibility and performance are baked into a design system from the start?" (Focus on best practices, testing, tooling) Company & Culture Questions:

• "What interests you about Pleo's mission and our approach to spend management?" (Research Pleo's product, values, and market position)

• "How do you embody Pleo's values of pragmatism, care, clarity, and collaboration in your work?" (Prepare specific examples)

• "Describe your experience mentoring junior engineers or helping to grow a frontend community." (Highlight leadership and coaching style) Portfolio Presentation Strategy:

• Structure: Organize your portfolio around 2-3 key projects that best demonstrate your capabilities as a Staff Frontend Engineer in Design Systems. Use a clear narrative for each: problem, solution, your role, technical details, and outcomes.

• Quantify Impact: Wherever possible, use metrics to illustrate the success of your work (e.g., adoption rates, efficiency gains, reduction in bugs).

• Highlight Architecture: Be prepared to walk through the architectural decisions, trade-offs, and reasoning behind your design system implementations.

• Showcase Collaboration: Explain how you partnered with designers and other engineers, managed feedback, and navigated stakeholder expectations.

• Address Challenges: Be open about challenges faced and how you overcame them. This demonstrates resilience and problem-solving skills.

📝 Enhancement Note: Preparation should focus on demonstrating not just technical skill, but also strategic thinking, leadership potential, and a collaborative mindset aligned with Pleo's values. Quantifiable results and clear articulation of architectural decisions will be key differentiators.

📌 Application Steps

To apply for this Staff Frontend Engineer position:

• Submit your application through the Pleo careers portal (https://jobs.ashbyhq.com/pleo/e0f0059b-fb60-4d94-8d10-5fe347872a4f).

• Customize Your Resume: Tailor your resume to highlight experience with design systems, component libraries, TypeScript, React, accessibility, performance, and technical leadership. Use keywords from the job description.

• Prepare Your Portfolio: Curate a portfolio that showcases your most impactful design system projects. Focus on architectural decisions, collaboration, and measurable outcomes. Be ready to present 2-3 key case studies.

• Research Pleo: Understand Pleo's product, mission, target audience, and company values. This will help you articulate your interest and cultural fit.

• Practice Interview Answers: Prepare for behavioral and technical questions, using the STAR method for behavioral responses and being ready to discuss your portfolio in detail.

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