Staff Frontend Engineer - Design Systems at Pleo

Closed

Staff Frontend Engineer - Design Systems at Pleo — archived role context

Pleo

Location: Remote
Advertised region: Denmark / United Kingdom / Portugal
Work arrangement: remote

This opening is not confirmed as active. Check the employer source before applying.

Role overview

This archived Staff Frontend Engineer listing names design systems as its focus. At a product company such as Pleo, a frontend design-system role commonly works on shared interface foundations that product teams can reuse across customer-facing workflows. The original vacancy is no longer present in Pleo’s live careers feed, so the examples here are informed by the title and company product, not recovered job duties.

The available record does not confirm the frontend framework, design-system maturity, team structure, accessibility standards or staff-level expectations. Confirm the current role scope and required technologies directly with Pleo.

Responsibilities

Develop and maintain reusable frontend components and patterns that product teams can apply consistently across interfaces.
Work with design and product colleagues to translate interaction and visual patterns into accessible, documented UI foundations.
Support adoption of shared components, gather feedback from consuming teams and guide improvements to the system over time.

Qualifications

Senior frontend engineering experience and examples of building or maintaining reusable UI components.
Ability to collaborate with designers and product engineers on accessibility, consistency and practical component APIs.
The original posting’s framework, years-of-experience requirement and staff-level scope are unavailable; confirm them with Pleo.

Technology in this role

No verified stack was retained for this vacancy. A design-systems title alone does not establish whether the team uses React, TypeScript, a specific component library or a particular design tool; confirm the current stack with Pleo.

Role-specific candidate guide

Preparation notes based on the employer’s stated responsibilities and qualifications.

Understanding the scope. This Staff Frontend Engineer - Design Systems position at Pleo is best assessed through the work described in the employer’s posting, rather than the title alone. The available role overview says: “This archived Staff Frontend Engineer listing names design systems as its focus. At a product company such as Pleo, a frontend design-system role commonly works on shared interface foundations that product teams can…” Read that statement together with the responsibilities below to understand the likely balance between delivery, coordination and technical decision-making. The role belongs to the frontend product area, but that label is only a guide to the work; the employer’s own requirements remain decisive. Before applying, check the original listing for reporting lines, product or team assignment, employment terms and any details that may have changed since this copy was checked. Where this page says a fact is not specified, treat it as an open question rather than an implied promise.

What the responsibilities signal. The posting specifically names “Develop and maintain reusable frontend components and patterns that product teams can apply consistently across interfaces.”; “Work with design and product colleagues to translate interaction and visual patterns into accessible, documented UI foundations.”; “Support adoption of shared components, gather feedback from consuming teams and guide improvements to the system over time.”. For each duty, identify a project where you performed comparable work and be ready to describe the context, your own contribution, constraints, decisions, and measurable result. Explain how you moved from the initial need to implementation, review, release or operational follow-through, where those stages apply. If the work involved other teams or users, distinguish your decisions from the group’s contribution. Avoid presenting a technology keyword as proof by itself: connect it to the problem you solved, the scale or complexity involved, and what changed after your work. The source may contain additional duties; review it directly before preparing your application.

How to read the requirements. The listed qualifications include “Senior frontend engineering experience and examples of building or maintaining reusable UI components.”; “Ability to collaborate with designers and product engineers on accessibility, consistency and practical component APIs.”; “The original posting’s framework, years-of-experience requirement and staff-level scope are unavailable; confirm them with Pleo.”. Mark each requirement as demonstrated, adjacent experience or a genuine gap, then use a concise example for the first two categories. A strong example explains what you personally owned, how you made trade-offs, how you validated the result and what you learned. If the posting specifies years of experience, language ability, certifications, location or eligibility, address those facts plainly in your CV or application rather than relying on the employer to infer them. Do not claim a qualification from exposure alone. For a requirement you do not meet, describe relevant transferable experience accurately and ask the recruiter whether it is mandatory.

Technology and working evidence. The technology terms associated with this listing are No verified stack was retained for this vacancy. A design-systems title alone does not establish whether the team uses React, TypeScript, a specific component library or a particular design tool; confirm the current stack with Pleo.. Treat this.

Benefits

The original posting’s benefits were not preserved. Check the employer’s current listing for compensation, leave, insurance and other benefits.

About Pleo

Pleo is a Copenhagen-founded business spend management company. Its platform combines company cards and spend controls with expense management, invoice payments, subscriptions and accounting workflows for businesses.

Pleo describes its aim as making company spending easier for employees while giving finance teams visibility and control. The Staff Frontend Engineer listing is no longer present in the live careers feed; the design-system scope below is role context inferred from the title, not a recovered employer job description.

Employer website