> Markdown version of [/jobs/ext/2710895-ai-design-engineer](https://www.wearedevelopers.com/jobs/ext/2710895-ai-design-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # AI Design Engineer - **Company:** Virtuous Incorporated - **Location:** United States (Remote available) - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Cascading Style Sheets (CSS), Reverse Engineering, ReactJS, Vue.js, Material UI, Figma - **Published:** September 4, 2026 - **Apply:** https://startup.jobs/ai-design-engineer-momentum-virtuous-2-8772491 ## About the Role * 6+ years building production interfaces in a modern frontend stack, with real ownership of what shipped * Direct experience owning a design system used by multiple teams across multiple products, in production. Not a just a component library or a Figma file * A real point of view on distribution and consumption: published package, registry, source distribution, or something else. You have lived with the tradeoffs and you can defend a recommendation, including how engineers and agents each consume it * Genuine design sensibility. You don't have to be a designer, but you can tell good from not good enough, and you can hold the line on it * Strong engineering fundamentals: Vue, React, component architecture, CSS at scale, performance, and testing * Hands on with AI tooling as part of your build workflow, including prototyping * Accessibility fluency, and the instinct to solve it structurally rather than case by case * Comfort working with designers as partners, and the credibility to push back * Excellent written communication. Your documentation is part of the product Nice to have: Design token pipelines, Storybook, or equivalent. Figma fluency including Code Connect or MCP. Experience making a system consumable by AI tooling. Fundraising technology, nonprofit CRM, or the nonprofit sector. ## Description At Virtuous, the design system is the leverage point for a unified experience across the entire product surface. Done well, it means every engineer ships work that looks and behaves like it was designed, without a review gate and without slowing down., * The design system. You own it end to end: tokens, primitives, components, patterns, and documentation, in code and not just in Figma. You own how it gets distributed and consumed, and and the process for updating and maintaining. * The operating model. You decide how a team ships a pattern the system does not have yet without fragmenting everything, and how that pattern gets promoted into the core once it proves out. Stable primitives that move carefully, product patterns that move quickly, and a real path between them. * Adoption. You treat engineers as your users. The system wins when building on it is faster than building around it, so you instrument coverage, watch for drift, and drive system adoption. * Production interface work. You are in the codebase every week building real surface work, not adjacent to it. What you learn shipping is what makes the system good, and it is how you feel the lag before anyone has to report it. * The AI guardrail. You make the system the thing that keeps generated interfaces on brand. When an engineer or an agent builds a screen, the system should make the right thing the easy thing. That means the system has to be legible to a model, not just to a person. * Accessibility and the craft bar. You build accessibility into the system so what we ship is also accessible. * The bridge from design to production. You work with product designers to turn validated patterns into system defaults, and you close the gap between what was designed and what actually shipped. * Documentation and enablement. You make the system obvious. Nobody adopts what they have to reverse engineer. * Metrics. You influence the numbers that prove the system works: component coverage across surfaces, adoption, efficiency, and throughput. ## Related Videos - [Designing high quality software with AI](https://www.wearedevelopers.com/videos/100136-designing-high-quality-software-with-ai) - [Boost Productivity with AI: Figma & Playwright MCP Workflows - Aris Markogiannakis](https://www.wearedevelopers.com/videos/1768-boost-productivity-with-ai-figma-playwright-mcp-workflows-aris-markogiannakis) - [Watch Tests Go Brrrr! : Getting Started with Cypress in ReactJS](https://www.wearedevelopers.com/videos/282-watch-tests-go-brrrr-getting-started-with-cypress-in-reactjs) - [Lessons learned from building a thriving Vue.js SaaS application](https://www.wearedevelopers.com/videos/1666-lessons-learned-from-building-a-thriving-vue-js-saas-application) - [Designing the Future of Human<>Agent Collaboration](https://www.wearedevelopers.com/videos/1447-designing-the-future-of-human-agent-collaboration) - [Fireside Chat with Kris Rasmussen, CTO at Figma](https://www.wearedevelopers.com/videos/982-fireside-chat-with-kris-rasmussen-cto-at-figma) ## Related Articles - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [Never delegate the understanding](https://www.wearedevelopers.com/magazine/749-never-delegate-the-understanding) - [Dev Digest 130 - The Diablo is in the details](https://www.wearedevelopers.com/magazine/470-dev-digest-130-the-diablo-is-in-the-details) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Dev Digest 122 - Cracks in the polyfill](https://www.wearedevelopers.com/magazine/457-dev-digest-122-cracks-in-the-polyfill)