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 Development / Design Systems Engineering

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 for a design system, serving hundreds of internal engineers across multiple products.

• Drive technical discussions and provide expertise on web platform technologies to enhance the design system and consuming products.

• Set quality standards for technical work, including code and software designs, and mentor less experienced team members.

• Collaborate with Product Management and development teams to deliver shared software engineering services, including UX design support, documentation, localization, accessibility, performance, and security.

• Contribute to OpenText's AI-first, future-driven, and human-centered mission by developing innovative Information Management Solutions.

📝 Enhancement Note: This role is positioned as a "Lead Software Developer" with a focus on "Design Systems." While the provided description and keywords lean heavily into front-end development and UI component architecture, the "Lead" aspect implies significant responsibility beyond individual contribution, including technical leadership, mentorship, and driving cross-team initiatives. The "AI" mentions in the company description and "What you need to Succeed" section, though brief, suggest an awareness or foundational understanding of AI concepts is beneficial, aligning with OpenText's broader AI strategy. The "DSP4" job code level suggests a senior, potentially principal-level individual contributor or team lead role.

📈 Primary Responsibilities

• Develop, test, document, and maintain a composable component architecture for the OpenText design system, ensuring reusability and scalability across various products and releases.

• Provide strong technical leadership and influence, extending beyond the immediate team to drive multi-team initiatives and enhance customer value.

• Actively participate in and lead technical discussions, sharing deep knowledge of web platform technologies to solve complex design system and product integration challenges.

• Establish and enforce high-quality standards for all technical deliverables, including code quality, software design, and documentation.

• Mentor and elevate the technical skills of junior developers within the team, fostering a culture of continuous learning and improvement.

• Collaborate closely with UX designers, product managers, and other engineering teams to understand business needs and translate them into effective design system solutions.

• Ensure all developed components adhere to accessibility guidelines (WCAG) and contribute to the creation of VPAT documentation where applicable.

• Contribute to the CI/CD pipeline using tools like GitLab and Jenkins to streamline the build, test, and deployment processes for design system assets.

📝 Enhancement Note: The primary responsibilities have been inferred and expanded based on the "Lead" title and the focus on "Design Systems." This includes emphasizing leadership, mentorship, cross-functional collaboration, and quality assurance, which are typical expectations for a lead role in a shared services unit like "Common Components." The mention of "composable component architecture" and "reusable scale for multiple products" directly informs the need for robust documentation, testing, and maintenance responsibilities.

🎓 Skills & Qualifications

Education: While no specific degree is listed, a Bachelor's or Master's degree in Computer Science, Software Engineering, or a related field is typically expected for a Lead Software Developer role.

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

Required Skills:

• Extensive experience with modern frontend frameworks such as React and/or Angular.

• Deep understanding and practical application of HTML, CSS, and JavaScript/TypeScript.

• Proven ability to create, test, document, and maintain highly polished UI components at a reusable scale for multiple products within a design system context.

• Proficiency in programming languages: JavaScript, TypeScript, and Node.js.

• Experience with CI/CD tools and processes, including GitLab, Jenkins, NPM, and Artifactory.

• Demonstrated working knowledge of accessibility standards and engineering practices for WCAG compliance.

• Strong technical leadership capabilities, with the ability to influence technical and business decisions. Preferred Skills:

• Experience contributing to or leading design system initiatives in large enterprise environments.

• Familiarity with AI concepts, MCP, Agent definition files, and AI Skill definitions, aligning with OpenText's strategic direction.

• Experience with performance engineering and product security best practices.

• Knowledge of build and release management tools and services.

• Understanding of UX design principles and user-centered design methodologies.

📝 Enhancement Note: The "Required Skills" have been directly extracted and organized from the "What you need to Succeed" section. "Preferred Skills" are inferred based on the company's strategic focus (AI), the role's context within "Common Components" (performance, security, build/release), and general best practices for a lead design systems role (UX principles). The experience level of "8-12 years" is explicitly stated.

📊 Process & Systems Portfolio Requirements

Portfolio Essentials:

• Showcase of successful design system implementations, demonstrating the creation and maintenance of reusable UI components across multiple projects.

• Examples of architectural patterns and best practices applied to build scalable and maintainable component libraries.

• Evidence of contributions to CI/CD pipelines for design system assets, highlighting efficiency gains and deployment strategies.

• Documentation samples that illustrate clear, concise, and comprehensive guidelines for component usage, accessibility, and theming.

• Case studies detailing how design system adoption has positively impacted development velocity, consistency, and user experience across different products. Process Documentation:

• Detailed documentation of the design system's development lifecycle, from component ideation and design to implementation, testing, and release.

• Workflows for component contribution, review, and adoption by internal product teams.

• Procedures for ensuring adherence to accessibility standards (WCAG) and for addressing accessibility issues.

• Strategies for versioning, dependency management, and backward compatibility of design system components.

• Processes for gathering feedback from consuming teams and iterating on the design system to meet evolving needs.

📝 Enhancement Note: This section is entirely inferred, as no explicit portfolio requirements were provided. For a "Lead Software Developer, Design Systems" role, a strong portfolio showcasing practical application of skills is crucial. The requirements focus on demonstrating leadership in design system development, process optimization, and technical documentation, aligning with the responsibilities of a lead role.

💵 Compensation & Benefits

Salary Range: $118,000.00 - $168,000.00 CAD per year. Note: This range is provided by the employer and may vary based on candidate qualifications, experience, skills, and geographical location, as well as internal equity and market alignment.

Benefits:

• Comprehensive support for physical wellbeing.

• Resources and programs for emotional wellbeing.

• Financial wellbeing support.

• Generous vacation entitlement.

• Paid time off.

• Additional details on variable pay, commission opportunities (for eligible roles), and specific time-off policies will be provided during the hiring process.

Working Hours: 40 hours per week.

Note: While the standard work week is 40 hours, flexibility may be available, and specific team practices will be discussed during the interview process.

📝 Enhancement Note: The salary range and core benefits are directly extracted from the provided text. The working hours are also explicitly stated. The note about salary variation is included as per the original text. The CAD currency is inferred from the Canadian locations.

🎯 Team & Company Context

🏢 Company Culture

Industry: Software & Information Technology, specializing in Enterprise Information Management solutions. OpenText is a significant player in the SaaS and AI-driven technology space.

Company Size: OpenText is a large enterprise, indicated by its global presence and the nature of its products and services. This scale means operations and development teams are often structured to support complex, multi-product environments.

Founded: OpenText was founded in 1991. Its long history suggests a stable yet evolving organization that has adapted to technological shifts, including the current AI revolution.

Team Structure:

• The "Common Components" unit operates as a shared services team, providing foundational software engineering services to numerous global product teams.

• This unit likely comprises specialized engineers in areas such as UX design support, product documentation, localization, accessibility governance, performance engineering, and product security.

• The Lead Software Developer will be part of the design system common components team, reporting to a manager within this unit, and will collaborate extensively with product development teams across OpenText. Methodology:

• Data-Driven Development: Emphasis on understanding business context and customer needs to drive significant customer value and influence longer-term business strategy.

• AI-First Approach: Integration of AI into core product development and operational strategies, powering innovation and transforming work.

• Agile & Collaborative: Encouragement of collaboration, innovation, and personal growth within teams. The mention of "composable component architecture" implies an agile development approach for the design system.

• Quality & Standards: A strong focus on setting and maintaining high-quality standards in technical work, from code to software design.

Company Website: https://careers.opentext.com/us/en

📝 Enhancement Note: Company information like industry, size, and founding date is derived from the company name and general knowledge of OpenText. The "Common Components" unit description is taken directly from the job posting. The methodology section infers operational approaches based on the company's stated values ("AI-First. Future-Driven. Human-Centered.") and the role's responsibilities (data-driven decisions, quality standards).

📈 Career & Growth Analysis

Operations Career Level: This role is classified as a Lead Software Developer (DSP4), indicating a senior individual contributor or team lead position. It requires a blend of deep technical expertise in design systems and front-end development, coupled with strong leadership, mentorship, and strategic influence capabilities. The role is expected to drive initiatives beyond immediate team boundaries and significantly impact customer value.

Reporting Structure: The Lead Software Developer will likely report to a manager or director within the "Common Components" unit, specifically overseeing the design system team. They will work closely with product managers, UX designers, and other development teams across OpenText, fostering a collaborative, cross-functional environment.

Operations Impact: The design system developed by this role has a broad impact across OpenText's product portfolio. By providing a standardized, reusable component architecture, it enhances:

• Development Efficiency: Enabling hundreds of engineers to build features faster and more consistently.

• Product Consistency: Ensuring a unified user experience across all OpenText products.

• Quality & Accessibility: Driving higher standards for UI quality and WCAG compliance.

• Innovation: Freeing up development resources to focus on core product innovation rather than reinventing UI elements.

• AI Integration: Facilitating the consistent integration of AI-powered features into user interfaces.

Growth Opportunities:

• Technical Specialization: Deepen expertise in design systems, front-end architecture, and web platform technologies.

• Leadership Development: Grow into a formal management role or a principal engineer/architect position with broader technical oversight.

• Cross-Functional Impact: Gain exposure to various product lines and collaborate with diverse teams, understanding different business needs.

• Mentorship: Develop coaching and mentoring skills by guiding junior developers and influencing engineering practices across the organization.

• Strategic Influence: Contribute to setting the long-term technical strategy for design systems and common components at OpenText.

📝 Enhancement Note: This analysis is based on the "Lead" title, the "DSP4" job code level inference, and the description of the "Common Components" unit. The "Operations Impact" section details how a design system role contributes indirectly to "operations" by improving development efficiency and product consistency, which are key GTM and operational goals.

🌐 Work Environment

Office Type: The role is on-site, implying a traditional office environment with dedicated workspaces. OpenText likely offers modern office facilities that support collaboration and productivity.

Office Location(s):

• Richmond Hill, Ontario, Canada

• Waterloo, Ontario, Canada

These locations are within the Greater Toronto Area and the Kitchener-Waterloo tech hub, respectively, suggesting access to a strong talent pool and a vibrant tech community.

Workspace Context:

• Collaborative Environment: The role requires close collaboration with UX designers, product managers, and other software developers, suggesting an open or semi-open office layout designed to facilitate team interaction and knowledge sharing.

• Tooling & Technology: Access to standard enterprise development tools, including high-performance workstations, development environments, and communication platforms necessary for working with a distributed design system.

• Team Interaction: Frequent opportunities for face-to-face discussions, whiteboarding sessions, and pair programming with team members and stakeholders.

Work Schedule: The standard work schedule is 40 hours per week. While on-site, there may be some flexibility in start and end times, subject to team needs and manager approval. The focus on delivering value and meeting project deadlines is paramount.

📝 Enhancement Note: The "Office Type" and "Workspace Context" are inferred based on the "On-site" designation and the nature of a Lead Software Developer role in a large enterprise. The mention of specific locations (Richmond Hill, Waterloo) is used to describe the regional context.

📄 Application & Portfolio Review Process

Interview Process:

1. Initial Screening: A recruiter or hiring manager will review your application and resume, focusing on relevant experience in design systems, front-end development, and leadership.

2. Technical Interview: Expect in-depth technical questions covering your expertise in React/Angular, TypeScript, CSS, HTML, component architecture, accessibility (WCAG), and CI/CD tools. You may be asked to discuss specific design system challenges you've faced and how you solved them.

3. Design System Deep Dive / Portfolio Review: A session dedicated to reviewing your portfolio. Be prepared to walk through specific examples of design systems you've built or significantly contributed to, explaining your design decisions, technical implementation, testing strategies, and the impact of your work.

4. Leadership & Collaboration Interview: This stage assesses your leadership style, mentorship capabilities, ability to drive cross-team initiatives, and how you handle technical disagreements or prioritize tasks. Behavioral questions will be common.

5. Hiring Manager Interview: A final discussion with the hiring manager (Chris Johnson) to assess overall fit, strategic alignment, and confirm your understanding of the role's impact and expectations.

Portfolio Review Tips:

• Curate Selectively: Choose 3-4 of your strongest design system projects that best showcase your end-to-end contributions and leadership.

• Structure Your Narrative: For each project, clearly articulate the problem, your solution (technical approach, design decisions), the tools and technologies used, your specific role and contributions, and the measurable outcomes (e.g., improved consistency, reduced development time, enhanced accessibility).

• Highlight Leadership: Emphasize instances where you led technical discussions, mentored team members, or influenced broader engineering practices.

• Demonstrate Process: Show examples of your documentation, testing methodologies, and CI/CD integration related to design systems.

• Be Ready for Deep Dives: Anticipate questions about your architectural choices, trade-offs made, and how you ensured scalability and maintainability.

Challenge Preparation:

• System Design Challenge: You might be given a hypothetical scenario to design a new component or a set of components for a design system, or asked to outline a strategy for improving an existing one. Focus on modularity, accessibility, theming, and scalability.

• Code Challenge: A practical coding exercise focusing on front-end development, potentially involving creating a React/Angular component that meets specific requirements, including accessibility.

• Problem-Solving Scenarios: Prepare to discuss how you would address common design system challenges, such as component drift, adoption issues, or integrating new technologies.

📝 Enhancement Note: This section is entirely inferred based on standard interview processes for Lead Software Developer roles, with specific emphasis on the design system and leadership aspects. The advice is tailored to help candidates prepare for the unique requirements of this specialized role.

🛠 Tools & Technology Stack

Primary Tools:

• Frontend Frameworks: React, Angular (deep expertise required in at least one, familiarity with both is beneficial).

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

• Component Architecture: Deep understanding and practical experience with building reusable, composable UI components.

• Version Control: Git, with experience in platforms like GitLab.

• Build Tools & Package Management: NPM, Artifactory, Webpack/Vite (implied for modern frontend development).

Analytics & Reporting:

• CI/CD Tools: GitLab CI, Jenkins (for automated builds, testing, and deployments).

• Testing Frameworks: Jest, React Testing Library, Cypress, or similar for unit, integration, and end-to-end testing of components.

• Documentation Tools: Tools for generating and hosting design system documentation (e.g., Storybook, Styleguidist).

CRM & Automation:

• AI Platforms/Concepts: Understanding of MCP, Agent definition files, AI Skill definitions (as mentioned in "What you need to Succeed").

• Collaboration Tools: Jira, Confluence, Slack, Microsoft Teams (standard enterprise tools for project management and communication).

📝 Enhancement Note: The "Primary Tools" are directly extracted from the "What you need to Succeed" section. Additional "Analytics & Reporting" and "CRM & Automation" tools are inferred based on industry best practices for design system development and CI/CD processes within a large enterprise, as well as the specific mention of AI concepts.

👥 Team Culture & Values

Operations Values:

• AI-First, Future-Driven, Human-Centered: This overarching philosophy permeates all aspects of OpenText's work, emphasizing innovation, forward-thinking solutions, and a focus on empowering users through technology.

• Trust & Character: Acting ethically and with integrity is fundamental, building trust with customers and colleagues.

• Purpose & Impact: A drive to solve meaningful, real-world problems, contributing to areas like sustainable supply chains, refugee support, and medical information access.

• Collaboration & Resilience: Working effectively in teams, tackling challenges with a determined spirit, and supporting each other's success.

• Innovation & Intention: Encouraging creative thinking and developing solutions with clear purpose and impact.

Collaboration Style:

• Cross-Functional Integration: The design system team works closely with product management, UX design, and numerous development teams, requiring strong communication and partnership skills to ensure alignment and adoption.

• Knowledge Sharing: A culture that encourages sharing technical expertise, best practices, and learnings, particularly through mentorship and technical discussions.

• Feedback-Driven Improvement: Embracing feedback from consuming teams to continuously iterate and improve the design system, fostering a collaborative improvement cycle.

• Quality-Focused: A shared commitment to high standards in code, design, and documentation, with a collective responsibility for the quality of the design system.

📝 Enhancement Note: The "Operations Values" are directly extracted from the company's stated mission and values. The "Collaboration Style" is inferred from the role's position within a shared services unit and the need for extensive cross-functional interaction, as well as the emphasis on mentorship and quality.

⚡ Challenges & Growth Opportunities

Challenges:

• Adoption & Governance: Ensuring widespread adoption of the design system across diverse product teams with varying technical stacks and priorities. Establishing effective governance processes to maintain consistency and manage contributions.

• Scalability & Evolution: Keeping the design system scalable and adaptable to new technologies, UI patterns, and the evolving needs of OpenText's broad product portfolio.

• Balancing Standardization with Flexibility: Creating components that are flexible enough to meet unique product requirements while maintaining the integrity and consistency of the design system.

• Cross-Team Dependency Management: Managing dependencies and communication with numerous product teams that consume the design system, ensuring smooth integration and timely updates.

• Integrating AI Components: Developing and standardizing components that effectively and intuitively integrate AI-powered features into user interfaces.

Learning & Development Opportunities:

• Advanced Design System Architecture: Opportunities to explore and implement cutting-edge patterns in component architecture, state management, and theming.

• Web Performance Optimization: Deepen expertise in optimizing frontend performance for large-scale applications and design systems.

• Accessibility Leadership: Become a subject matter expert in web accessibility, influencing best practices across the organization.

• AI Integration Strategies: Learn how to effectively design and build user interfaces for AI-driven features, contributing to OpenText's AI strategy.

• Mentorship and Coaching: Develop strong leadership skills through mentoring junior developers and influencing engineering culture.

• Industry Conferences & Certifications: Potential opportunities to attend relevant conferences (e.g., design systems, front-end development) and pursue certifications.

📝 Enhancement Note: Challenges are inferred based on the nature of design system roles in large enterprises, common adoption hurdles, and the specific context of AI integration. Growth opportunities are derived from the role's responsibilities and the company's strategic focus.

💡 Interview Preparation

Strategy Questions:

• "Describe a time you led the development of a design system or a significant set of reusable UI components. What were the biggest challenges, and how did you overcome them?" (Focus on leadership, problem-solving, and process.)

• "How do you ensure that a design system remains relevant and adopted by multiple product teams? What strategies do you employ for governance and feedback?" (Focus on adoption, collaboration, and continuous improvement.)

• "Walk me through your process for ensuring accessibility (WCAG compliance) in UI components. What tools and techniques do you use?" (Focus on technical depth in accessibility.)

• "How would you approach integrating AI-powered features into a design system? What are the key considerations for UI components related to AI?" (Focus on strategic thinking and AI awareness.) Company & Culture Questions:

• "Based on your understanding of OpenText's 'AI-First. Future-Driven. Human-Centered.' mission, how do you see this role contributing to that vision?" (Demonstrate research and alignment.)

• "How do you handle technical disagreements with other developers or stakeholders regarding design system implementation or standards?" (Assess conflict resolution and collaboration skills.)

• "Describe your experience mentoring junior engineers. What is your approach to helping them grow their skills?" (Evaluate leadership and team development capabilities.) Portfolio Presentation Strategy:

• Storytelling: Frame your portfolio projects as compelling stories. Start with the problem, detail your role and actions, and conclude with the positive impact and lessons learned.

• Quantify Impact: Wherever possible, use metrics to demonstrate the value of your work (e.g., "reduced development time by X%", "achieved Y% WCAG compliance out-of-the-box," "improved UI consistency scores by Z%").

• Technical Deep Dive: Be prepared to discuss the technical architecture of your components, trade-offs made, testing strategies, and how you handled scalability and maintainability.

• Focus on Leadership: Highlight instances where you took initiative, influenced decisions, or mentored others within your projects.

• Interactive Elements: If possible, use live demos or interactive prototypes to showcase your work, rather than static screenshots.

📝 Enhancement Note: These interview questions and preparation tips are tailored to the "Lead Software Developer, Design Systems" role, focusing on the blend of technical expertise, leadership, and strategic thinking required. The emphasis on design systems, accessibility, and AI integration is specific to OpenText's context.

📌 Application Steps

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

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

• Customize Your Resume: Tailor your resume to highlight your 8-12 years of experience in front-end development, design systems, UI component architecture, and technical leadership. Use keywords from the job description, such as React, Angular, TypeScript, CSS, HTML, WCAG, CI/CD, and design systems.

• Prepare Your Portfolio: Curate a selection of your strongest design system projects. Ensure you can articulate the problem, your solution, your specific contributions, the technologies used, and the measurable impact of each project.

• Practice Your Narrative: Rehearse presenting your portfolio projects and answering common interview questions, focusing on demonstrating leadership, technical depth, and problem-solving skills. Prepare to discuss your experience with accessibility and CI/CD.

• Research OpenText: Familiarize yourself with OpenText's mission, products, and its "AI-First. Future-Driven. Human-Centered." philosophy. Understand how the design system contributes to the company's overall goals.

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

---