Lead Software Developer, Design Systems

📍 Job Overview

Job Title: Lead Software Developer, Design Systems

Company: Open Text Corporation

Location: Richmond Hill, Ontario, Canada; Waterloo, Ontario, Canada

Job Type: OTHER

Category: Software Engineering / Design Systems

Date Posted: 2026-07-20

Experience Level: 10+ years

Remote Status: On-site

🚀 Role Summary

• Lead the development and maintenance of a composable component architecture, serving as a core design system for hundreds of internal engineers across multiple products and releases.

• Drive technical discussions and provide in-depth knowledge of web platform technologies to solve complex design system challenges and enhance product development.

• Champion accessibility standards (WCAG) throughout the design and development lifecycle, ensuring all components are built to be inclusive and compliant.

• Collaborate closely with UX Design, Product Management, and other development teams to translate business and design system needs into robust, scalable software solutions.

• Foster a culture of quality and technical excellence within the team, mentoring less experienced developers and raising the overall skill level of the engineering group.

📝 Enhancement Note: This role is clearly focused on establishing and scaling a design system, a critical function within larger organizations to ensure consistency, efficiency, and maintainability of user interfaces across a product portfolio. The "Lead" title implies significant technical ownership, mentorship, and cross-functional influence.

📈 Primary Responsibilities

• Architect, develop, test, and document reusable UI components within the design system, ensuring they are performant, accessible, and easy for other engineers to consume.

• Lead code reviews, establish coding standards, and implement best practices for frontend development within the design system's framework.

• Collaborate with UX designers to translate visual designs and interaction patterns into functional, high-quality code components.

• Troubleshoot and resolve complex technical issues related to the design system's architecture, performance, and integration into various product lines.

• Drive initiatives to evaluate and integrate new technologies or methodologies that can improve the design system's effectiveness, scalability, and developer experience.

• Contribute to the long-term technical strategy of the Common Components unit, advising on architectural decisions and future roadmap planning.

• Ensure adherence to web accessibility standards (WCAG) and performance best practices across all developed components.

• Support and mentor junior developers on the team, fostering their growth in frontend development, design systems, and accessibility.

📝 Enhancement Note: The responsibilities highlight a blend of hands-on development, technical leadership, and strategic contribution, typical of a Lead role in a specialized area like Design Systems. The emphasis on reusability, scalability, and cross-product impact is key.

🎓 Skills & Qualifications

Education: While not explicitly stated, a Bachelor's or Master's degree in Computer Science, Engineering, or a related field is typically expected for a Lead Software Developer role. Relevant certifications in web development or design systems could also be beneficial.

Experience: 8-12 years of progressive professional software development experience, with a significant focus on frontend development and design systems.

Required Skills:

• Frontend Frameworks: Deep expertise in at least one modern JavaScript framework such as React or Angular.

• Core Web Technologies: Proficient in HTML5, CSS3 (including preprocessors like Sass/LESS), and modern JavaScript (ES6+)/TypeScript.

• Design Systems: Proven experience in creating, maintaining, testing, and documenting reusable UI components at scale for multiple products. Understanding of design tokens, theming, and component library best practices.

• Programming Languages: Strong command of JavaScript, TypeScript, and Node.js for build tooling and potential backend integration.

• Accessibility: Demonstrated knowledge and practical experience in engineering and building components and applications that meet WCAG guidelines.

• Version Control: Proficiency with Git and collaborative development workflows.

• CI/CD Tools: Experience with continuous integration and continuous delivery pipelines, specifically GitLab, Jenkins, NPM, and Artifactory.

• Technical Leadership: Ability to lead technical discussions, mentor team members, and influence technical direction beyond immediate team boundaries.

• Problem-Solving: Strong analytical and problem-solving skills with the ability to make sound technical decisions.

Preferred Skills:

• Component Libraries: Experience with popular component library tools and patterns (e.g., Storybook, Lerna).

• Build Tools: Familiarity with module bundlers like Webpack or Vite.

• Testing Frameworks: Experience with frontend testing frameworks (e.g., Jest, React Testing Library, Cypress).

• AI Concepts: Understanding of AI concepts such as MCP, Agent definition files, and AI Skill definitions, as mentioned in the job description, suggesting potential integration points or awareness needed for broader context.

• UX Principles: Solid understanding of user experience principles and best practices.

📝 Enhancement Note: The required skills are a strong indicator of the technical depth needed. The inclusion of AI concepts, while unusual for a pure design systems role, suggests OpenText is integrating AI across its product suite, and developers in core platform areas need to be aware of these technologies.

📊 Process & Systems Portfolio Requirements

Portfolio Essentials:

• Design System Case Studies: Showcase examples of design systems or component libraries you have contributed to or led. Highlight the challenges faced, the solutions implemented, and the impact on developer efficiency and product consistency.

• Component Examples: Provide links to live examples or well-documented code repositories of UI components you have built, demonstrating code quality, reusability, and adherence to accessibility standards.

• Process Documentation: Include examples of documentation you've created for design system components, covering usage guidelines, API references, and best practices for consumption.

• Impact Demonstration: Quantify the impact of your work. This could include metrics on reduced development time, increased component adoption, improved UI consistency scores, or accessibility compliance improvements.

Process Documentation:

• Workflow Design & Optimization: Demonstrate experience in designing and optimizing workflows for component development, testing, and release within a design system context.

• Implementation & Automation: Show how you've implemented and automated processes for component versioning, testing, and continuous integration/delivery using tools like GitLab, Jenkins, or similar.

• Measurement & Performance Analysis: Present examples of how you've measured the adoption, performance, and impact of design system components, using data to drive improvements.

📝 Enhancement Note: For a Lead Software Developer in Design Systems, a portfolio is crucial. It needs to go beyond just showcasing code; it must demonstrate leadership in process, impact, and the ability to articulate complex technical solutions and their business value.

💵 Compensation & Benefits

Salary Range: $118,000.00 - $168,000.00 CAD per year.

Explanation of Range: This range is provided for the specified locations (Richmond Hill and Waterloo, Ontario, Canada). The final salary will be determined based on the candidate's qualifications, including education, experience, skills, and alignment with internal equity and market benchmarks. The provided range is a guideline, and actual compensation may fall outside of it based on these factors.

Benefits:

• Holistic Wellbeing: Comprehensive support for physical, emotional, and financial wellbeing.

• Performance-Based Pay: Potential for variable compensation and commission opportunities (for eligible roles, though likely not for this specific development lead role unless it has a direct sales enablement component).

• Work-Life Balance: Generous vacation entitlement and paid time off to ensure a healthy work-life balance.

• Professional Development: Opportunities for continuous learning and skill enhancement through internal projects and potentially external training.

• Retirement Savings: Likely includes a company-sponsored retirement savings plan (e.g., RRSP matching in Canada), though not explicitly detailed.

Working Hours: The role specifies 40 hours per week, which is standard for a full-time position. While the role is on-site, there may be flexibility in daily start/end times, subject to team and business needs.

📝 Enhancement Note: The salary range is provided in CAD, reflecting the Canadian locations. The mention of "variable and commission compensation" is standard corporate language but less likely to apply directly to a pure software development role of this nature unless there are specific performance metrics tied to adoption or successful integration that impact a team bonus.

🎯 Team & Company Context

🏢 Company Culture

Industry: Software & Information Technology. OpenText is a global leader in Information Management, providing AI-powered solutions that help organizations manage their most important information. Their products span various sectors including enterprise information management, customer experience management, and business network services.

Company Size: OpenText is a large, established enterprise with thousands of employees globally. This means opportunities for broad impact and exposure to complex, large-scale systems, but also a structured corporate environment.

Founded: OpenText was founded in 1991. This long history signifies stability, deep domain expertise in information management, and a well-established presence in the market.

Team Structure:

• Common Components Unit: This team operates as a shared service provider within the OpenText™ Products group, supporting global Product Management and development teams.

• Specialization: The team focuses on User Experience Design support, Product Information, Localization, Accessibility, Performance Engineering, Product Security, and Build/Release management tools. The Design Systems team is a key part of this.

• Reporting: This Lead role will likely report to a manager or director within the Common Components or Engineering division, overseeing a specific area of the design system.

• Cross-functional Collaboration: Expect close collaboration with UX designers, product managers, and hundreds of other software engineers across various product teams who consume the design system library.

Methodology:

• AI-First Approach: OpenText is heavily invested in AI, integrating it across its product suite. This role may involve understanding how design systems can support AI-driven features or how AI influences UI/UX patterns.

• Agile Development: While not explicitly stated, most modern software development organizations of this size operate with Agile methodologies (Scrum, Kanban), focusing on iterative development, continuous feedback, and rapid iteration.

• Data-Driven Decisions: The company emphasizes making timely decisions and course-correcting based on customer needs, suggesting a data-informed approach to product development and process improvement.

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

📝 Enhancement Note: OpenText's positioning as an "AI-First" company is a significant differentiator. For a Design Systems role, this implies a need to consider how AI features will be integrated into UIs and how the design system can facilitate this by providing flexible, adaptable components.

📈 Career & Growth Analysis

Operations Career Level: This position is a "Lead Software Developer" (DSP4 Job Code Level), indicating a senior individual contributor role with significant technical leadership responsibilities. It's a step above a standard Senior Developer, requiring influence, mentorship, and the ability to drive initiatives beyond a single team.

Reporting Structure: The Lead Software Developer will report to a manager within the Common Components unit. They will work closely with product management, UX design, and other engineering teams, acting as a central point of expertise for the design system.

Operations Impact: The design system developed by this role has a broad impact across OpenText's product portfolio. By providing a consistent, high-quality, and accessible set of UI components, this role directly influences the user experience of countless end-users, improves developer productivity across hundreds of engineers, and ensures brand consistency. This contributes significantly to the overall quality and marketability of OpenText's Information Management Solutions.

Growth Opportunities:

• Technical Specialization: Deepen expertise in design systems, frontend architecture, web performance, and accessibility, becoming a recognized subject matter expert within OpenText.

• Leadership Progression: Advance into roles such as Principal Engineer, Architect, or potentially a management track leading a team of developers focused on platform or core services.

• Cross-functional Influence: Expand influence across multiple product lines, contributing to strategic technical decisions and driving adoption of best practices.

• AI Integration: Gain experience in how design systems support AI functionalities and contribute to OpenText's AI-first strategy.

• Mentorship: Develop strong leadership and mentoring skills, guiding junior engineers and contributing to the overall technical growth of the engineering organization.

📝 Enhancement Note: The DSP4 Job Code Level suggests a senior individual contributor path focused on technical leadership and impact, rather than immediate management. The growth opportunities are geared towards deepening technical expertise and expanding influence.

🌐 Work Environment

Office Type: On-site. The role is based in Open Text's Canadian offices in Richmond Hill or Waterloo, Ontario. This suggests a traditional office environment with opportunities for in-person collaboration.

Office Location(s): Richmond Hill, Ontario, Canada; Waterloo, Ontario, Canada. These locations offer access to tech talent pools and are established business hubs.

Workspace Context:

• Collaborative Environment: The emphasis on shared services and cross-functional collaboration indicates an environment where teamwork and communication are highly valued. Expect regular meetings, design reviews, and code-sharing sessions.

• Tools & Technology: Access to standard enterprise development tools, including robust CI/CD infrastructure (GitLab, Jenkins), version control, and potentially advanced design and development software.

• Team Interaction: Opportunities to interact directly with UX designers, product managers, and fellow software engineers, fostering a dynamic and supportive work atmosphere.

Work Schedule: A standard 40-hour work week is expected. While the role is on-site, some flexibility in daily hours may be available, subject to team coordination and project deadlines. The focus is on delivering results and maintaining high-quality output.

📝 Enhancement Note: The on-site requirement suggests a preference for in-person collaboration, which can be beneficial for highly interactive roles like design systems development and mentorship.

📄 Application & Portfolio Review Process

Interview Process:

• Initial Screening: A recruiter or HR representative will likely conduct an initial phone screen to assess basic qualifications, experience, and cultural fit.

• Technical Interview(s): Expect multiple rounds of technical interviews. These will likely include:

  • Frontend Fundamentals: Questions on JavaScript, TypeScript, HTML, CSS, and your chosen framework (React/Angular).
  • Design System Deep Dive: Discussions about your experience building and maintaining design systems, component architecture, accessibility, and tooling.
  • System Design/Architecture: A problem-solving session where you'll design a solution for a complex frontend challenge, potentially related to the design system or a new feature.
  • Behavioral/Leadership: Questions assessing your leadership style, ability to mentor, handle conflict, and drive initiatives, aligning with the "Lead" aspect of the role.

• Portfolio Review: A dedicated session to walk through your portfolio, discussing specific projects, your contributions, technical decisions, and the impact of your work. Be prepared to articulate your process and rationale clearly.

• Hiring Manager Interview: A final interview with Chris Johnson (Hiring Manager) to discuss your fit for the team, role expectations, and overall career aspirations.

Portfolio Review Tips:

• Curate Selectively: Focus on 2-3 of your strongest projects that best showcase your design systems expertise, leadership, and impact.

• Tell a Story: For each project, clearly articulate the problem, your role, the technical approach, key challenges, solutions, and quantifiable results. Use the STAR method (Situation, Task, Action, Result).

• Highlight Design System Specifics: Emphasize your contributions to component architecture, documentation, testing, accessibility implementation, and adoption strategies.

• Demonstrate Leadership: Explain how you influenced technical direction, mentored team members, or drove cross-functional alignment.

• Prepare for Technical Questions: Be ready to discuss the code, architectural decisions, and trade-offs made in your portfolio projects.

Challenge Preparation:

• Coding Challenge: You might be given a live coding exercise or a take-home assignment focusing on building a UI component or solving a frontend problem, testing your practical skills and adherence to standards.

• Design System Scenario: Prepare for scenarios where you need to design a new component, refactor an existing one, or address an accessibility issue within a hypothetical design system.

• Whiteboarding/System Design: Practice articulating your thought process for designing scalable, maintainable frontend architectures and component libraries on a whiteboard or shared canvas. Be ready to discuss trade-offs and justify your design choices.

📝 Enhancement Note: The interview process will likely be rigorous, emphasizing both deep technical skills and leadership capabilities. A strong portfolio with clear, quantifiable achievements is paramount.

🛠 Tools & Technology Stack

Primary Tools:

• Frontend Frameworks: React, Angular (expertise in at least one required).

• Languages: JavaScript, TypeScript, Node.js.

• Styling: CSS, potentially CSS preprocessors (Sass/LESS).

• Design System Tools: Experience with component development, testing, and documentation platforms (e.g., Storybook, Lerna is highly probable).

• Version Control: Git.

Analytics & Reporting:

• CI/CD: GitLab, Jenkins.

• Package Management: NPM.

• Artifact Repository: Artifactory.

• Accessibility Auditing Tools: Tools that help in testing WCAG compliance (e.g., Axe, Lighthouse).

CRM & Automation: While not directly listed as primary tools for this role, awareness of how the design system integrates with broader enterprise systems is beneficial. Understanding of how CRM data might influence UI design patterns could be a plus.

📝 Enhancement Note: The provided list covers core development tools. For a Lead role, familiarity with build tools (Webpack/Vite), testing frameworks (Jest), and potentially design token management tools would be expected.

👥 Team Culture & Values

Operations Values:

• AI-First. Future-Driven. Human-Centered: This overarching philosophy guides OpenText's innovation. For a design systems role, it means building components that are not only functional but also intuitive, accessible, and capable of supporting AI-driven features.

• Customer Focus: "Always put our customers first." This translates to building robust, user-friendly components that enhance the customer experience and provide significant value.

• Collaboration and Resilience: "Help teams succeed through collaboration, tackle challenges with resilience." Expect a team environment that values shared problem-solving and perseverance through complex technical hurdles.

• Ethical Conduct and Trust: "Act ethically, care deeply about people." This underpins all business operations, including software development, emphasizing integrity and respect.

• Quality and Engineering Mindset: "Cultivate an engineering mindset, driving the creation of innovative software solutions." This implies a commitment to high-quality code, best practices, and continuous improvement.

Collaboration Style:

• Cross-functional Integration: The Common Components team's purpose is to serve other product teams, necessitating a highly collaborative style with UX, Product Management, and engineering peers.

• Knowledge Sharing: As a lead, you'll be expected to share your expertise, mentor others, and contribute to a culture of learning and continuous improvement.

• Feedback Loops: Expect regular feedback sessions, code reviews, and design critiques to ensure alignment and maintain high standards.

📝 Enhancement Note: OpenText's stated values are foundational. A candidate's ability to demonstrate alignment with these, particularly customer-centricity, ethical conduct, and collaborative problem-solving, will be key during the interview process.

⚡ Challenges & Growth Opportunities

Challenges:

• Scalability and Consistency: Maintaining a single source of truth for UI components that serves hundreds of engineers across diverse products, often with varying release cycles and technical stacks, is a significant challenge. Ensuring consistent adoption and adherence to standards requires strong governance and communication.

• Evolving Technologies: The frontend landscape and design system best practices are constantly evolving. Staying current with new technologies, frameworks, and accessibility standards while ensuring backward compatibility and stability is an ongoing challenge.

• Balancing Innovation and Stability: Introducing new components or features while ensuring the core design system remains stable, performant, and backward-compatible requires careful planning and execution.

• Integration with AI Features: As OpenText adopts an "AI-First" strategy, the design system will need to adapt to support AI-driven user interfaces, which may present new design and technical challenges.

Learning & Development Opportunities:

• Advanced Frontend Architecture: Opportunities to delve deeper into complex frontend architectures, micro-frontends, and state management patterns.

• Design System Strategy: Contribute to the strategic vision and roadmap of OpenText's design system, influencing its evolution.

• Accessibility Expertise: Become a go-to expert for accessibility within the organization, helping to set standards and provide guidance.

• Cross-Product Exposure: Gain deep insights into how various OpenText products are built and how the design system impacts their user experience.

• Leadership Development: Hone leadership skills through mentoring, technical guidance, and driving cross-team initiatives.

📝 Enhancement Note: The challenges are inherent to large-scale design system initiatives. The growth opportunities are substantial for someone looking to build deep expertise in this specialized and critical area of software development.

💡 Interview Preparation

Strategy Questions:

• Design System Philosophy: "What are the core principles of a successful design system, and how do you ensure adoption across diverse teams?" Be prepared to discuss your approach to component design, documentation, governance, and developer experience.

• Technical Leadership: "Describe a time you led a complex technical initiative or mentored junior developers. What was your approach, and what was the outcome?" Focus on your ability to influence, guide, and elevate technical quality.

• Problem-Solving: "How would you approach designing a new component for our design system that needs to be highly flexible and support potential AI integrations?" Be ready to think aloud, discuss trade-offs, and articulate your design process.

Company & Culture Questions:

• AI Integration: "How do you see design systems supporting an 'AI-First' strategy? What considerations are important?" Research OpenText's AI initiatives and think about how UI/UX can facilitate AI features.

• Team Collaboration: "How do you typically collaborate with UX designers and product managers? Describe a situation where you had a disagreement and how you resolved it." Highlight your communication and cross-functional partnership skills.

• Impact Measurement: "How would you measure the success and impact of a design system component? What metrics would you track?" Focus on quantifiable outcomes and how you demonstrate value.

Portfolio Presentation Strategy:

• Structure Your Narrative: For each portfolio piece, clearly outline the context, your specific contributions, technical challenges, chosen solutions, and the measurable impact.

• Focus on Design System Principles: When discussing projects, emphasize aspects like reusability, scalability, maintainability, accessibility, and developer experience.

• Be Ready for Deep Dives: Anticipate detailed questions about your code, architectural decisions, testing strategies, and how you handled specific implementation challenges.

• Showcase Leadership: Use examples from your projects to illustrate instances where you provided technical leadership, mentored others, or drove consensus.

📝 Enhancement Note: Interview preparation should focus on demonstrating not only technical proficiency but also strategic thinking, leadership potential, and a deep understanding of design system principles and their business impact.

📌 Application Steps

To apply for this Lead Software Developer, Design Systems position:

• Submit your application through the provided link on the OpenText careers website.

• Tailor Your Resume: Emphasize your experience with React/Angular, TypeScript, CSS, HTML, and specifically your work on design systems, reusable components, and accessibility (WCAG). Quantify your achievements with metrics where possible (e.g., "Reduced component development time by X%", "Increased adoption of library by Y%").

• Prepare Your Portfolio: Curate a portfolio showcasing 2-3 key design system projects. Ensure it highlights your technical contributions, leadership, process improvements, and quantifiable impact. Have links or well-organized documentation ready.

• Practice Your Pitch: Rehearse your ability to clearly articulate your experience, technical decisions, and the value you bring, especially during portfolio presentations and technical discussions. Prepare to discuss your leadership approach and mentoring experience.

• Research OpenText: Understand OpenText's mission, "AI-First. Future-Driven. Human-Centered," and how design systems fit into their broader strategy. Familiarize yourself with their products and market position.

⚠️ 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.