Senior UX Design Engineer, Design Systems

📍 Job Overview

Job Title: Senior UX Design Engineer, Design Systems

Company: Greenhouse

Location: Ontario, Canada

Job Type: Full-Time

Category: Design Systems Engineering / Front-End Development

Date Posted: May 04, 2026

Experience Level: 5-10 Years

Remote Status: Remote OK

🚀 Role Summary

• This role is critical for bridging the gap between design intent and production code, focusing on the implementation and evolution of Greenhouse's design system.

• You will be instrumental in developing reusable, production-grade components and patterns, ensuring consistency, accessibility, and efficiency across product development.

• This position plays a key part in defining the future of product design and development at Greenhouse, with an emphasis on AI-powered tooling and an experience-first engineering approach.

• You will serve as a central resource for triad feature teams (Product, Design, Engineering), fostering collaboration and driving adoption of system-wide capabilities.

📝 Enhancement Note: This role is a "first-of-its-kind" at Greenhouse, indicating a strategic investment in design systems infrastructure and a recognized need for specialized engineering expertise to scale design and development efforts. The emphasis on AI-powered tooling suggests a forward-looking approach to design system evolution.

📈 Primary Responsibilities

• Build, maintain, and evolve production-grade UI components and patterns within the design system, ensuring robust accessibility and interaction fidelity from inception.

• Develop and manage a comprehensive documentation hub for both design and engineering teams, providing clear APIs, variants, and functional examples to facilitate self-service.

• Establish and enforce contribution standards, guardrails, and best practices to ensure the design system remains the preferred and most efficient choice for all Greenhouse product teams.

• Collaborate closely with engineering counterparts to deliver implementation-ready design patterns, thereby minimizing handoff friction and reducing the incidence of bespoke UI development across feature teams.

• Actively champion the adoption and effective utilization of the design system across the entire organization, enhancing the overall product experience through refined motion, interaction design, and brand consistency.

📝 Enhancement Note: The responsibility to "own a single documentation source of truth" implies a need for strong technical writing and API design skills, ensuring that components are not only functional but also easily understood and integrated by diverse teams.

🎓 Skills & Qualifications

Education: While no specific degree is mandated, a strong educational foundation in Computer Science, Human-Computer Interaction, or a related technical field is implicitly expected, demonstrated through experience.

Experience: A minimum of 5 years of progressive experience in front-end engineering, UX engineering, or a closely related discipline, with a proven track record in modern component-based frameworks.

Required Skills:

• Extensive experience with component architecture in a modern front-end framework, with a strong preference for React and TypeScript.

• Proficient understanding and practical application of accessibility best practices, specifically WCAG guidelines, and experience with state modeling demonstrated in shipped products.

• Fluency in working with design tokens, comprehensive layout systems, and managing interaction states.

• A demonstrated passion for visual and interaction design principles.

• A strong documentation-first mindset, capable of creating self-serve resources for technical and design audiences.

• Proven experience shipping and managing design system components at a previous organization, showcasing field-tested knowledge beyond theoretical understanding.

Preferred Skills:

• Experience with Storybook (or similar tools) for component documentation and showcase workflows.

• Familiarity with visual regression testing methodologies and the implementation of CI quality gates for design system components.

• Experience with design token pipelines and associated tooling.

📝 Enhancement Note: The explicit mention of "React + TypeScript strongly preferred" and "working knowledge of AI development tools" are critical technical requirements. The preference for "field-tested knowledge" emphasizes practical, hands-on experience rather than academic or theoretical familiarity with design systems.

📊 Process & Systems Portfolio Requirements

Portfolio Essentials:

• Showcase at least 2-3 significant projects demonstrating the design, development, and implementation of reusable UI components within a design system context.

• For each project, clearly articulate the problem statement, the design system's role in solving it, and the technical implementation details (frameworks, languages, architectural patterns).

• Quantify the impact of your design system contributions, ideally with metrics related to development efficiency, consistency improvements, or adoption rates.

• Include examples of well-documented components, demonstrating your ability to create clear APIs, usage guidelines, and variant examples.

Process Documentation:

• Demonstrate a structured approach to component development, including version control, testing strategies (unit, integration, visual regression), and deployment pipelines.

• Illustrate experience in defining and implementing design token systems and layout grids that ensure consistency and scalability.

• Provide evidence of contributing to or managing documentation platforms (e.g., Storybook) with a focus on enabling self-service for other teams.

• Show an understanding of how to integrate AI development tools into the design-to-code workflow for efficiency gains.

📝 Enhancement Note: Given the role's focus on bridging design and engineering, the portfolio should highlight a strong hybrid skill set. It needs to showcase not just coding proficiency but also a deep understanding of design principles, accessibility, and the strategic importance of a design system for scaling product development.

💵 Compensation & Benefits

Salary Range: The national pay range for this role in Canada is $105,800 - $158,800 CAD per year. Individual compensation will be determined by the candidate's experience, qualifications, and alignment with the role's requirements.

Benefits:

• Stock Option Awards: Opportunity to gain equity in a growing company.

• Bonuses: Performance-based financial incentives.

• Merit Increases: Structured salary adjustments based on performance and contributions.

• Performance Review Program: A commitment to providing actionable feedback for professional development.

• Potential for additional compensation based on specific role eligibility, including sales commissions if applicable to certain positions.

Working Hours: While not explicitly stated, a standard full-time work week is implied, likely around 40 hours. The "Remote OK" status suggests flexibility in work hours, provided core responsibilities and collaborative needs are met.

📝 Enhancement Note: The salary range provided is a national benchmark for Canada. Actual compensation may vary based on specific location within Canada, the candidate's demonstrated expertise, and Greenhouse's internal compensation bands. The inclusion of Stock Option Awards is a significant benefit for a Senior-level role.

🎯 Team & Company Context

🏢 Company Culture

Industry: Technology (SaaS - Hiring Software)

Company Size: Greenhouse is a well-established company, indicated by its award-winning culture and significant presence, though the exact employee count isn't provided here. However, the need for a dedicated central Design System team suggests a mature product organization.

Founded: Greenhouse was founded with a mission to improve hiring processes, and its continuous growth and awards suggest a stable and innovative environment.

Team Structure:

• The Design System team operates as a centralized, shared infrastructure team supporting multiple "triad feature teams" (Product, Design, Engineering).

• This role reports to the Staff Designer & Manager, Design Systems, indicating a leadership presence within the Design Systems function.

Methodology:

• A "documentation-first" approach is central, emphasizing self-service and clear communication.

• The team focuses on building reusable, production-grade capabilities that compound in value.

• There's a strong emphasis on an "experience-first" engineering mindset, prioritizing user workflows and ideal outcomes.

• The role is positioned to explore and integrate AI-powered tooling for design and development efficiency.

Company Website: https://www.greenhouse.com

📝 Enhancement Note: Greenhouse's emphasis on using its own product for hiring and its award-winning culture ("Fortune’s Best Places to Work," "Inc.’s Best Workplaces") suggest a company that values its employees, fosters a positive work environment, and is committed to operational excellence.

📈 Career & Growth Analysis

Operations Career Level: Senior UX Design Engineer (Design Systems) - This is a senior individual contributor role with significant influence. It requires deep technical expertise in front-end development and design systems, coupled with strategic thinking about how to scale design and development through reusable components and well-defined processes.

Reporting Structure: You will report to the Staff Designer & Manager, Design Systems. This structure places you within a specialized team focused on a critical aspect of product development, with direct leadership overseeing design systems strategy and implementation.

Operations Impact: This role has a direct and significant impact on operational efficiency and product quality. By creating and maintaining a robust design system, you will:

• Accelerate product development cycles by providing ready-to-use components.

• Ensure brand consistency and a high-quality user experience across all Greenhouse products.

• Reduce development debt and maintenance overhead by minimizing bespoke UI.

• Enable designers and engineers to focus on higher-value, feature-specific work.

Growth Opportunities:

• Deep Specialization: Become a recognized expert in design systems engineering, a highly sought-after skill.

• Technical Leadership: Grow into a lead or architect role within the design systems function, guiding technical strategy and mentoring other engineers.

• Cross-functional Influence: Expand influence across product, design, and engineering teams, shaping product development processes.

• AI & Emerging Tech: Gain hands-on experience with cutting-edge AI tools and their application in design and development workflows.

• Career Pathing: Potential to move into roles managing design systems teams, product engineering leadership, or specialized UX architecture roles.

📝 Enhancement Note: The "first-of-its-kind" nature of this role suggests a high potential for impact and the opportunity to shape the direction of design systems at Greenhouse, offering significant career growth and influence.

🌐 Work Environment

Office Type: Greenhouse operates as a "remote-first" company. While they have shared office spaces in New York City and Ireland, and optional co-working spaces, the Senior UX Design Engineer role is identified as "Remote OK," indicating that working from a remote location within Canada is fully supported.

Office Location(s):

• Shared office spaces: New York City, USA; Ireland.

• Optional co-working spaces available.

Workspace Context:

• Collaborative Environment: Expect a highly collaborative atmosphere, particularly with the central Design System team and the triad feature teams. Communication and partnership are key.

• Tools & Technology: Access to modern development tools and technologies will be essential. The role specifically mentions React, TypeScript, AI development tools, and Storybook.

• Team Interaction: Regular virtual meetings, code reviews, documentation collaboration, and potentially some in-person gatherings (if desired/feasible) will foster team interaction.

Work Schedule: As a remote-first company, Greenhouse likely offers a degree of flexibility in work hours, as long as core responsibilities are met and collaboration with teams in different time zones is managed effectively. A standard 40-hour work week is a typical expectation for full-time roles.

📝 Enhancement Note: The "remote-first" approach combined with the "Remote OK" designation for this role means candidates can expect a work environment that prioritizes asynchronous communication, digital collaboration tools, and autonomy, while still maintaining strong team connections.

📄 Application & Portfolio Review Process

Interview Process:

• Initial Screening: A recruiter will likely review your application and resume, focusing on keyword alignment and core qualifications.

• Hiring Manager/Team Interview: Expect a discussion with the Staff Designer & Manager, Design Systems, and potentially other members of the design systems or product engineering team. This will focus on your experience, approach to design systems, technical skills, and cultural fit.

• Technical Assessment/Portfolio Review: This is a crucial stage. You will likely present your portfolio, discussing specific projects, your contributions, technical solutions, and the impact of your work. This may include a live coding exercise or a take-home challenge related to component development or design system principles.

• Cross-functional Interviews: You may meet with engineers and designers from feature teams to assess your collaboration style and ability to support diverse needs.

• Final Interview: Potentially with a senior leader to discuss your overall fit and long-term vision.

Portfolio Review Tips:

• Highlight Design Systems Impact: Clearly showcase projects where you built or significantly contributed to a design system. Emphasize how your work improved efficiency, consistency, or developer experience.

• Demonstrate Hybrid Skills: Show examples of both your design thinking (e.g., understanding user needs, interaction design) and your engineering prowess (e.g., clean code, architecture, testing, documentation).

• Quantify Achievements: Use metrics wherever possible. For example, "Reduced component development time by X%," "Increased adoption of system components by Y teams," or "Achieved 100% WCAG AA compliance for Z components."

• Code Quality & Documentation: Be prepared to discuss the code behind your components and how you approach documentation. Clean, well-commented code and clear, comprehensive documentation are key.

• Storytelling: Frame your portfolio pieces as stories: the problem, your solution, the implementation, and the outcome. Explain your decision-making process.

• AI Tooling Integration: If you have examples of using AI tools for code generation or efficiency gains within a design system context, be sure to include and discuss them.

Challenge Preparation:

• Component Development: Be ready to build a component from scratch, or refactor an existing one, adhering to specific requirements (e.g., accessibility, responsiveness, theming).

• Design System Principles: Prepare to discuss core design system concepts, such as component architecture, design tokens, API design, versioning, and contribution workflows.

• Problem-Solving Scenarios: Anticipate questions about how you would handle common design system challenges, like feature team adoption, contribution conflicts, or evolving requirements.

• Accessibility & State Management: Be prepared to demonstrate your understanding and application of accessibility standards and complex state modeling in code.

📝 Enhancement Note: The emphasis on a "documentation-first" approach and "self-serve" resources means your portfolio presentation should explicitly cover how you document your work and empower others. The "first-of-its-kind" nature of the role suggests the hiring team will be keen to see proactive problem-solving and strategic thinking in your portfolio.

🛠 Tools & Technology Stack

Primary Tools:

• Front-end Framework: React (Strongly Preferred).

• Language: TypeScript (Strongly Preferred).

• Component Documentation: Storybook (Preferred), or similar tools for showcasing and documenting components.

• Design System Infrastructure: Tools for managing design tokens, layout systems, and interaction states.

• AI Development Tools: Claude, MCP, Code Sandbox, or similar platforms for code-ready output generation.

Analytics & Reporting:

CRM & Automation:

Other Relevant Technologies:

• Version Control: Git (implied).

• CI/CD tools for build and deployment pipelines.

• Visual Regression Testing tools.

📝 Enhancement Note: The core technical stack revolves around modern front-end development (React, TypeScript) and design system tooling. The inclusion of AI development tools signifies Greenhouse's intent to leverage emerging technologies for efficiency.

👥 Team Culture & Values

Operations Values:

• Collaboration & Partnership: A strong emphasis on working closely with product, design, and engineering teams to co-own solutions and drive adoption.

• System-Mindedness: Viewing individual UI requests as opportunities to build reusable, scalable system capabilities.

• Experience-First Approach: Prioritizing ideal user workflows and product experiences when building technical solutions.

• Documentation-First: Valuing clear, comprehensive documentation as a fundamental enabler for self-service and efficient collaboration.

• Innovation & Future-Thinking: Staying abreast of and incorporating advancements like AI-powered design tooling to shape the future of product development.

• Inclusivity & Accessibility: Building components that are usable by everyone, adhering to WCAG standards.

Collaboration Style:

• Cross-functional Integration: The role is designed to be an integral part of the product development lifecycle, working seamlessly across disciplines.

• Proactive Support: Aiming to provide shared infrastructure that enables feature teams to ship faster and more consistently, requiring proactive engagement and support.

• Knowledge Sharing: Actively contributing to a culture of sharing best practices and learnings related to design systems and component development.

• Feedback Loops: Openness to feedback from users of the design system to drive continuous improvement and ensure it meets evolving needs.

📝 Enhancement Note: Greenhouse's stated values of collaboration, inclusivity, and transparency are directly reflected in the requirements for this role, emphasizing the importance of cross-functional partnership and a shared commitment to their mission.

⚡ Challenges & Growth Opportunities

Challenges:

• Driving Adoption: Persuading and enabling diverse product teams to consistently adopt and correctly use the design system can be an ongoing challenge.

• Balancing System Needs vs. Feature Needs: Navigating requests for bespoke UI solutions that may conflict with system standards, while still ensuring feature teams can meet their deadlines.

• Evolving Technology Landscape: Keeping pace with rapid advancements in front-end technologies, AI tooling, and design system best practices.

• Maintaining Documentation: Ensuring documentation remains accurate, comprehensive, and up-to-date as the system evolves.

• Defining Contribution Standards: Establishing clear, effective, and manageable processes for how external teams can contribute to or request changes in the design system.

Learning & Development Opportunities:

• Mastering Design Systems: Deepen expertise in component architecture, design token management, accessibility, and interaction design within a large-scale system.

• AI & Automation: Gain hands-on experience and expertise in applying AI tools to streamline design-to-code workflows.

• Technical Leadership: Opportunity to influence technical direction, mentor junior engineers, and potentially lead aspects of the design system's technical roadmap.

• Cross-functional Acumen: Develop a nuanced understanding of product development processes across different teams and contribute to strategic product decisions.

• Industry Engagement: Potential to represent Greenhouse at industry conferences or contribute to open-source design system efforts.

📝 Enhancement Note: The "first-of-its-kind" nature of this role means there's a significant opportunity to define processes and set standards, which can be both a challenge and a major growth opportunity for an ambitious individual.

💡 Interview Preparation

Strategy Questions:

• "Describe your approach to building a reusable component library within a design system. What are the key architectural considerations?" (Focus on modularity, state management, accessibility, theming, and API design.)

• "How do you balance the need for a consistent design system with the unique requirements of individual product teams?" (Discuss contribution models, flexibility within guardrails, and negotiation strategies.)

• "Walk me through a time you successfully championed the adoption of a design system or a new component. What were the challenges, and how did you overcome them?" (Highlight communication, education, and demonstrating value.)

Company & Culture Questions:

• "What excites you about Greenhouse's mission to make hiring work for everyone?" (Connect your values to the company's purpose.)

• "How do you align with Greenhouse's 'remote-first' culture and collaborative work style?" (Discuss your experience with remote work, asynchronous communication, and cross-functional teamwork.)

Portfolio Presentation Strategy:

• Structure: Organize your portfolio by project, clearly stating the problem, your role, the solution (technical and design), and the outcome/impact.

• Technical Depth: Be ready to dive into code specifics, architectural decisions, and the reasoning behind your implementation choices.

• Design System Focus: Emphasize how each project contributes to or exemplifies strong design system principles. Highlight reusable patterns, documentation, and accessibility.

• Quantify Impact: Use metrics to demonstrate the success of your work (e.g., efficiency gains, adoption rates, consistency improvements).

• AI Tooling Examples: If you have examples of using AI for code generation or similar tasks, be prepared to demonstrate their application and benefits.

• Storytelling: Weave a narrative that highlights your problem-solving skills, technical expertise, and collaborative spirit.

📝 Enhancement Note: Given this is a new role, interviewers will likely probe for proactive problem-solving, strategic thinking, and a clear vision for how you would establish and grow the design system's engineering function at Greenhouse.

📌 Application Steps

To apply for this Senior UX Design Engineer, Design Systems position:

• Submit your application through the Greenhouse job portal link provided.

• Tailor your Resume: Ensure your resume highlights keywords from the job description, particularly "React," "TypeScript," "Design Systems," "UX Engineering," "Accessibility (WCAG)," and experience with component architecture and AI development tools. Quantify achievements where possible.

• Curate Your Portfolio: Select 2-3 of your most impactful design systems or front-end engineering projects. Focus on showcasing reusable components, documentation practices, accessibility implementation, and the impact of your work. Be prepared to discuss the technical details and strategic rationale behind your projects.

• Craft a Compelling Cover Letter: Briefly explain why you are an excellent fit for this specific role, highlighting your passion for design systems, your hybrid design/engineering skill set, and your understanding of Greenhouse's mission. Address the "first-of-its-kind" nature of the role and how you envision contributing.

• Prepare for Technical Discussions: Review core concepts of React, TypeScript, component architecture, design systems, accessibility, and state management. Be ready to articulate your thought process for building and maintaining scalable component libraries.

• Research Greenhouse: Familiarize yourself with Greenhouse's product, mission, and company culture. Understand their "remote-first" approach and award-winning environment.

⚠️ Important Notice: This enhanced job description includes AI-generated insights and operations industry-standard assumptions. All details should be verified directly with the hiring organization before making application decisions.