Miro

Staff Design Engineer

Remote Design Engineering role with clear candidate location fit.

PostedJul 2, 2026

Eligible countries2 accepted countries

Seniority signalSenior

Work settingRemote

Accepted candidate locations

DenmarkUnited Kingdom

Role overview

Readable role content extracted into sections for faster review.

Own the core interaction layer of the canvas, responsiveness, rendering, input handling, and spatial transitions, working on the things users feel before they name.
Design and build the multiplayer moments that make working alongside someone in Miro feel genuinely different from working alone: presence, cursors, conflict, and co-creation.
Define what it means to have an AI collaborator in a visual, multiplayer space — shaping how AI outputs land on the canvas, how suggestions feel without being intrusive, and how generative results become part of a team's work.
Craft the moments of delight and magic that make Miro memorable, animations, micro-interactions, and transitions where the tool disappears and the thinking takes over.
Build the patterns, prototypes, and shared tooling that make the broader design and engineering organisation faster and more confident.
Write things down, teach by doing, and set a quality standard that propagates, contributing to coherence across the canvas, not just within your own area.
Collaborate closely with product designers, engineers, PMs, and researchers across Miro's canvas and AI portfolio.

Fluency in React, TypeScript, and CSS, you have strong architectural opinions that come from shipping, not reading.
Hands-on experience with canvas and graphics technologies: WebGL, Canvas API, SVG, and complex layout systems.
Deep craft in motion and timing, easing curves, transition timing, hover states, and frame budgets are as deliberate for you as layout decisions.
Experience designing real-time multiplayer systems: you've thought about presence, conflict, and co-authorship as UX problems, not just engineering ones.
Experience designing AI experiences, you understand the difference between putting a text input on a page and designing around probabilistic, latent AI outputs.
The instinct to prototype in code first: you reach for the browser before Figma when exploring a new interaction, and you're fast enough that prototyping doesn't feel like a cost.
Systems thinking across a large product surface, you connect patterns, design with awareness of implications elsewhere, and contribute to coherence.
Experience with streaming APIs, structured outputs, and the UX patterns that make probabilistic systems feel reliable and worth trusting.
The ability to influence the quality of work around you, through written communication, mentorship, and setting standards that others build on.