I tracked 800 European design engineer job ads. The role barely exists as a job title.

Over the course of two months, the reporter meticulously tracked 800+ design and product engineering job postings across Europe, utilizing 11 different applicant tracking systems (ATS) to monitor the postings. This data collection process was ongoing, with the reporter checking the listings every few days to observe their appearance and removal. It is important to note that the reporter had a vested interest in this research, as they run a firm specializing in the placement of design and product engineers.

The report revealed that only 76 out of the 800+ postings could be classified as unambiguous design engineer roles. The remaining positions encompassed various related jobs that frequently overlap with the design engineer title. Some of these adjacent job titles included frontend, product engineer, founding engineer, design systems, and UI engineer. The ambiguity surrounding the job title makes it difficult to identify and track these roles effectively.

Upon analysis, the data showed that the median duration for a design engineer role to remain active on the market was 57 days, measured from the initial posting date to when the posting was removed. Comparatively, frontend engineer roles lasted an average of 41 days, product engineer roles lasted 59 days, and founding engineer roles had the longest duration at 129 days. This suggests that roles that encompass multiple disciplines tend to have longer vacancy periods.

The reporter discovered a distinct pattern in the design engineer job postings. A majority of these roles emphasized "craft, taste, and polish" over specific technical skills. In fact, 79% of the postings highlighted these qualities, while React, TypeScript, and backend or full-stack skills were mentioned less frequently. This observation was unexpected, as the reporter had presumed technical skills would be prioritized in the job descriptions.

Craft appeared nearly twice as often as React and roughly three times as often as any mention of backend work. Although the role is primarily engineering-based, nearly half of the postings required React, and a similar share demanded TypeScript knowledge. However, the core focus of these roles lies in the surface-level aspects that directly impact the end-user experience.

In an effort to clarify the nature of these roles, one company, Buena, explicitly stated that the position is not merely a frontend engineer with a design title nor a designer who simply prototypes and hands the work off. This highlights the distinct identity of the design engineer role.

The reporter found that about one in six of the job ads defined the role by what it is not, explicitly excluding the two common archetypes that frequently apply: front-end engineers with a design title and designers who primarily focus on prototyping and passing the work on to others. This indicates that companies are cautious about hiring design engineers, likely due to past negative experiences.

Furthermore, 97% of these roles were senior-level positions. This suggests that there is a limited supply of junior design engineer positions available, leaving the path for the development of future senior-level engineers more uncertain. The majority of senior-level design engineers seem to have transitioned into their roles from other backgrounds, such as frontend engineering, design, or even founding startups.

Another significant finding was the prevalence of portfolio requirements in these job postings. 46% of the ads explicitly requested a portfolio, which is a significantly higher percentage than in the case of standard engineering roles. This suggests that companies are looking for tangible evidence of an applicant's skills and design abilities rather than relying solely on a standard curriculum vitae.