/ TEAMS · Specialist engineering · Design Systems
Source engineers experienced in Accessible components, design tokens, multi-product UI consistency and visual testing. for business-critical production systems, safe integrations and measurable technical ownership.
2,000+ engineers in our active talent network · Regional recruiters
/ SYSTEM STACK
accessible component APIs
React/Vue UI primitives
design tokens
Storybook
visual regression
/ AVAILABLE TO HIRE
Profiles show the experience we can source. Individual candidate availability is confirmed after enquiry.
Senior Design Systems Engineer
Inquire availability10+ years of experience · Poland
Design Systems Engineer with 10 years in production systems, focused on accessible component APIs and React/Vue UI primitives.
Languages: Polish, English B2+
Mid-level Design Systems Engineer
Available3+ years of experience · Czechia
Design Systems Engineer with 3 years in production systems, focused on React/Vue UI primitives and design tokens.
Languages: Czech, English B2+
Mid+ Design Systems Engineer
Available6+ years of experience · Serbia
Design Systems Engineer with 6 years in production systems, focused on design tokens and Storybook.
Languages: Serbian, English B2+
Senior Design Systems Engineer
Available11+ years of experience · Romania
Design Systems Engineer with 11 years in production systems, focused on Storybook and visual regression.
Languages: Romanian, English B2+
/ Engineering teams
Onectus uses its active engineering network and regional recruiting partners to search against concrete systems, environments and responsibilities. We evaluate practical experience rather than treating a framework mention or certification as proof of delivery. Particular availability and engagement terms are confirmed after an enquiry. For this role, practical knowledge of accessible component APIs, React/Vue UI primitives, design tokens helps define the engineering search.
/ Technical specializations
The right profile depends on your actual architecture, performance constraints, integration boundaries and operational responsibilities.
Design Systems responsibilities include accessible component apis, related react/vue ui primitives, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
Design Systems responsibilities include react/vue ui primitives, related design tokens, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
Design Systems responsibilities include design tokens, related storybook, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
Design Systems responsibilities include storybook, related visual regression, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
Design Systems responsibilities include visual regression, related theming, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
Design Systems responsibilities include theming, related accessible component apis, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
/ Project scenarios
Unify fragmented frontend component libraries. Define constraints around accessible component apis, map dependencies and test how the proposed implementation behaves under real operating conditions.
Improve keyboard and screen-reader support. Define constraints around react/vue ui primitives, map dependencies and test how the proposed implementation behaves under real operating conditions.
Build scalable theme and token contracts. Define constraints around design tokens, map dependencies and test how the proposed implementation behaves under real operating conditions.
Reduce visual regressions across products. Define constraints around storybook, map dependencies and test how the proposed implementation behaves under real operating conditions.
/ Practical evaluation
A senior engineering interview should surface directly relevant implementation details, debugging history and operational judgment.
Describe a production issue involving accessible component APIs and what evidence led to a fix.
Which decisions around React/Vue UI primitives and design tokens were you personally accountable for?
Describe a production issue involving design tokens and what evidence led to a fix.
Which decisions around Storybook and visual regression were you personally accountable for?
/ Sourcing process
Define platform versions, deployment constraints, traffic patterns, required integrations and ownership.
Search the active network and partner channels for platform-specific engineering experience.
Discuss real systems, code or configuration decisions, troubleshooting and change control.
Confirm role boundaries, location or remote access, availability, security and interviews.
Profiles, availability and engagement terms are confirmed for each request.
/ Questions
Yes. Tell us the relevant versions, operational environment and the responsibilities connected to accessible component APIs. We qualify hands-on experience during each search.
These can be included when central to the project. We distinguish practical implementation work from general familiarity and ask about failure scenarios and testing.
We look at production decisions, trade-offs, incident diagnosis, code or infrastructure ownership and the ability to explain decisions without relying on a technology checklist.
Share your architecture, technical constraints, collaboration model and priorities. We can then discuss relevant sourcing channels, evaluation criteria and next steps.
/ Onectus · TEAMS
Tell us the technology, production responsibilities, experience level and working model. We'll activate the appropriate engineering sourcing channels.
