Assembled
Software Engineer, Design Systems
About this role
Assembled is seeking a Software Engineer to spearhead the development of a new design system and enhance AI-driven workflows. This role will involve architecting the system, modernizing frontend foundations, and establishing best practices to improve user experiences across the organization.
What you'll do
- Lead the technical direction of the design system
- Define component APIs and documentation for AI coding agents
- Modernize frontend architecture and development patterns
- Ensure high standards of frontend quality and performance
- Build and maintain robust infrastructure for reliability
- Guide product decisions with technical insights
What they're looking for
- 3+ years in frontend product development
- Experience evolving design systems
- Expertise in TypeScript and component architecture
- Enhancing product quality in performance and accessibility
- Strong design and product instincts
- Effective communication and collaboration across teams
- Interest in AI-assisted development workflows
Benefits
- Comprehensive medical, dental, and vision plans
- Flexible time off policy
- Monthly professional development credits
- Paid parental leave
- Daily catered lunches and stocked office
- 401(k) plan availability
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Assembled
Assembled builds AI-driven customer support software with forecasting, scheduling, and workforce optimization capabilities designed to predict support volume and optimize agent staffing at scale. The company is hiring Software Engineers to develop its design system, frontend product experiences, ML-powered interfaces, and AI-enhanced workflows across engineering and design teams.
- Website
- assembled.com
Likely interview questions
- Walk us through a design system you've owned or significantly evolved. What were the key architectural decisions you made, and how did you drive adoption across multiple teams?
- How do you approach designing component APIs and token architecture to be flexible enough for product needs while also being AI-friendly for code generation?