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: Full-Time

Category: Software Engineering / Design Systems

Date Posted: 2026-08-07

Experience Level: 10+ Years

Remote Status: On-site

🚀 Role Summary

• Lead the development and maintenance of a composable component architecture for OpenText's design system.

• Drive technical discussions and provide expertise on web platform solutions that benefit both the design system and consuming products.

• Champion quality standards and mentor junior team members in technical best practices.

• Collaborate with global Product Management and developer teams to deliver shared software development services.

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

📝 Enhancement Note: The "Design Systems" focus strongly suggests this role is within a GTM Operations or Product Operations context, aiming to standardize UI/UX across multiple software products for efficiency and brand consistency. This requires a blend of technical development and strategic operational thinking to ensure widespread adoption and impact.

📈 Primary Responsibilities

• Develop, maintain, test, and document the composable component architecture of the design system, ensuring it meets the needs of hundreds of internal developers across multiple products and releases.

• Provide strong technical leadership, influencing teams beyond immediate boundaries and driving multi-team initiatives.

• Understand business and design system needs to translate them into effective technical solutions and enhance client value.

• Make informed technical decisions, prioritizing client trust and long-term business strategy.

• Identify and course-correct when current paths do not align with client needs or business objectives.

• Set and enforce quality standards for technical work, including code quality, software designs, and documentation.

• Mentor and raise the skill level of less experienced team members within the design system team.

• Collaborate with UX design teams to ensure design guidelines and individual product designs are effectively implemented.

• Ensure all developed components and applications adhere to WCAG accessibility guidelines.

• Contribute to the AI-first vision by understanding and potentially integrating AI concepts into the design system or consuming applications.

📝 Enhancement Note: The responsibilities highlight a blend of hands-on development, technical leadership, strategic input, and mentorship, common in senior engineering roles focused on foundational platforms like design systems. The emphasis on "client value" and "business strategy" indicates an operational perspective where technical decisions directly impact product delivery and market competitiveness.

🎓 Skills & Qualifications

Education: While not explicitly stated, 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 previous professional software development experience.

Required Skills:

• Frontend Technologies: Expertise in React and/or Angular, along with deep proficiency in CSS, HTML, JavaScript, and TypeScript.

• Design Systems: Proven experience in creating, testing, documenting, and maintaining highly polished UI components on a reusable scale for multiple products.

• Programming Languages: Strong command of JavaScript, TypeScript, and Node.js.

• CI/CD Tools: Familiarity with CI/CD pipelines, including tools like GitLab, Jenkins, NPM, and Artifactory.

• Accessibility Standards: Working and demonstrated knowledge of developing and building components and applications compliant with WCAG guidelines.

• Leadership: Proven ability to provide strong technical and business leadership, influencing across teams.

• Problem-Solving: Ability to grasp business context quickly and identify/implement optimal technical solutions.

Preferred Skills:

• AI Concepts: Understanding of MCP, Agent definition files, and AI Skill definitions.

• Web Platform Expertise: In-depth knowledge of web platform capabilities to solve complex design system and product challenges.

• Component Architecture: Deep understanding of composable component architecture principles and best practices.

• Mentorship: Experience in raising the skill level of less experienced team members.

📝 Enhancement Note: The inclusion of AI-related skills (MCP, Agent definition files) suggests a forward-looking approach by OpenText, integrating AI into their development processes or products. For a Design Systems role, this might translate to building accessible and adaptable components that can support AI-driven features or interfaces. The experience level (8-12 years) and leadership responsibilities firmly place this in a senior/lead category.

📊 Process & Systems Portfolio Requirements

Portfolio Essentials:

• Design System Components: Showcase of reusable UI components developed for a design system, demonstrating their scalability, maintainability, and adherence to design standards.

• Frontend Project Examples: Demonstrations of complex frontend applications or features built with React or Angular, highlighting technical architecture and problem-solving approaches.

• Accessibility Implementation: Specific examples or case studies illustrating how accessibility (WCAG) was integrated into component design and development.

• CI/CD Workflow Integration: Evidence of contributions to CI/CD pipelines, showcasing automated testing, build, and deployment processes for frontend projects.

Process Documentation:

• Component Development Lifecycle: Documentation outlining the process for designing, developing, testing, and releasing new components for the design system.

• Versioning and Release Management: Clear processes for managing design system versions and communicating updates and deprecations to consuming teams.

• Accessibility Compliance Procedures: Documented steps for ensuring and verifying WCAG compliance across all design system components.

• Collaboration Workflows: Defined processes for collaborating with product teams, UX designers, and other stakeholders to gather requirements and incorporate feedback.

📝 Enhancement Note: For a Lead Software Developer in Design Systems, a portfolio should emphasize not just the final code but the process of creating reusable, scalable, and accessible components. This includes demonstrating an understanding of component lifecycle management, versioning strategies, and collaborative workflows that ensure consistent adoption and impact across the organization.

💵 Compensation & Benefits

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

• 📝 Enhancement Note: This salary range is based on the provided data for the Canadian market, specifically Ontario. For a Lead Software Developer role with 8-12 years of experience in a major tech company like OpenText, this range is competitive. The actual salary will be determined by factors such as the candidate's specific skills, depth of experience, educational background, and alignment with internal equity and external market benchmarks. The explicit mention of "geographical location" in the compensation notes further supports the on-site requirement for these specific locations.

Benefits:

• Comprehensive health benefits package.

• Generous vacation entitlement.

• Paid time off (PTO).

• Variable compensation opportunities.

• Commission compensation opportunities (for eligible roles).

• 📝 Enhancement Note: The benefits are designed to support the physical, emotional, and financial well-being of employees. The inclusion of variable and commission compensation opportunities, while often more typical for sales roles, may indicate performance-based bonuses or incentives tied to project success or design system adoption metrics for this lead engineering position.

Working Hours: 40 hours per week.

• 📝 Enhancement Note: While the standard work week is 40 hours, the role's leadership and development focus may necessitate flexibility. However, the "On-site" designation implies adherence to typical business hours within the specified office locations.

🎯 Team & Company Context

🏢 Company Culture

Industry: Software & Information Management. OpenText is a global leader in Information Management, with a strong focus on AI-driven solutions. They aim to transform how businesses operate by leveraging data and knowledge.

Company Size: OpenText is a large enterprise organization (indicated by many employee numbers and global presence). This means established processes, significant resources, and broad impact opportunities, but also potentially more complex organizational structures.

Founded: OpenText was founded in 1991. This history suggests a stable company with a long track record in the software industry, now aggressively pivoting towards AI.

Team Structure:

• The role is within the "Common Components" unit of the OpenText™ Products group, which provides shared development services.

• This unit likely comprises various software developers, UX designers, technical writers, and potentially accessibility and security specialists.

• The Lead Software Developer will lead a specific team focused on the design system.

• Collaboration is expected with global Product Management and various internal developer teams across many products. Methodology:

• AI-First, Future-Driven, Human-Centered: This is the overarching company ethos, emphasizing innovation, forward-thinking, and user impact.

• Information Management: Core to OpenText's mission, focusing on organizing, managing, and leveraging data effectively.

• Composable Architecture: The design system is built on this principle, allowing for modularity and reusability.

• Agile Development: Standard for software development, likely employed within teams for iterative development and delivery.

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

📝 Enhancement Note: OpenText's emphasis on AI and Information Management provides a strategic backdrop for the Design Systems role. The design system is a critical operational component that enables consistent user experiences across diverse information management solutions, ensuring that AI-driven features are presented coherently and accessibly. The company's scale suggests that successful design system implementation can have a vast operational impact on development efficiency and product quality.

📈 Career & Growth Analysis

Operations Career Level: Lead Software Developer. This signifies a senior individual contributor role with significant technical leadership responsibilities. It's a stepping stone towards management or principal engineer roles.

Reporting Structure: The role reports to a Hiring Manager (Chris Johnson) and is part of the "Common Components" unit. The Lead will manage and mentor other developers within the design system team.

Operations Impact: The design system is a core operational asset. By standardizing UI components, it directly impacts:

• Development Efficiency: Reduces redundant work and accelerates feature delivery across product teams.

• Product Consistency: Ensures a unified brand experience and user journey across all OpenText products.

• Maintainability: Simplifies updates and bug fixes by centralizing component logic.

• Scalability: Enables faster integration of new features and products.

• Accessibility Compliance: Ensures all products meet regulatory and user needs for accessibility.

Growth Opportunities:

• Technical Specialization: Deepen expertise in design systems, frontend architecture, web performance, and accessibility.

• Leadership Development: Transition into formal management roles (e.g., Engineering Manager) or Principal/Staff Engineer roles focusing on broader architectural strategy.

• Cross-Functional Influence: Gain experience influencing product strategy and technical direction across multiple global teams.

• AI Integration: Opportunity to work with emerging AI technologies and explore their application within design systems and user interfaces.

• Mentorship: Develop coaching and mentoring skills by guiding junior developers.

📝 Enhancement Note: This role offers significant growth potential within a large enterprise. The "Lead" title implies a clear path for career progression, either into people management or deeper technical specialization. The focus on design systems within a major software company positions this role as strategically important for operational efficiency and product quality, offering substantial impact and visibility.

🌐 Work Environment

Office Type: Full Time In-Office. The role requires presence at one of the specified OpenText offices.

Office Location(s): Richmond Hill, Ontario, Canada; Waterloo, Ontario, Canada.

• 📝 Enhancement Note: Candidates must be able to commute to either Richmond Hill or Waterloo, Ontario. This on-site requirement is critical for fostering in-person collaboration, team cohesion, and direct mentorship, which are often prioritized for lead roles in established companies.

Workspace Context:

• Collaborative Environment: OpenText promotes collaboration. The "Common Components" team structure and the design system's cross-product nature necessitate strong teamwork and communication.

• Tools and Technology: Access to industry-standard development tools, potentially including advanced IDEs, design software integrations, and robust CI/CD infrastructure.

• Team Interaction: Frequent interaction with fellow developers, UX designers, product managers, and potentially QA engineers, fostering a dynamic and interactive work setting.

Work Schedule: Standard 40-hour work week.

• 📝 Enhancement Note: While the schedule is standard, the lead role may require some flexibility to manage project timelines, team needs, and cross-functional coordination. The on-site requirement ensures consistent team presence during core business hours.

📄 Application & Portfolio Review Process

Interview Process:

• Initial Screening: HR or Recruiter will review applications for basic qualifications and cultural fit.

• Technical Interview(s): Multiple rounds focusing on frontend development skills (React/Angular, JS/TS, CSS/HTML), design system principles, component architecture, accessibility, and problem-solving.

• Design System/System Design Interview: Focused on how to design, build, and maintain a scalable design system, including discussions on component libraries, documentation, and governance.

• Leadership/Behavioral Interview: Assessment of leadership capabilities, team mentorship, strategic thinking, decision-making, and ability to influence across teams. Hiring Manager (Chris Johnson) will likely be involved.

• Portfolio Review: Candidates will be asked to present and discuss relevant projects, showcasing their contributions to design systems, complex frontend applications, and accessibility implementations.

• Final Interview: Potentially with senior leadership or a panel to assess overall fit and strategic alignment.

Portfolio Review Tips:

• Showcase Design System Impact: Clearly articulate the purpose and impact of the design systems you've built. Quantify improvements in development speed, consistency, or user satisfaction if possible.

• Demonstrate Component Reusability: Highlight specific UI components and explain how they were designed for broad reusability, maintainability, and accessibility.

• Technical Depth: Be prepared to deep-dive into the technical architecture of your projects, including state management, styling strategies, and component composition.

• Accessibility Best Practices: Clearly explain how WCAG guidelines were incorporated into your development process and how you tested for compliance.

• Leadership and Collaboration: Use examples from your experience to demonstrate your ability to lead technical discussions, mentor junior developers, and collaborate effectively with design and product teams.

Challenge Preparation:

• Live Coding Exercise: Expect a coding challenge focused on frontend development, potentially involving building a small component or solving a UI-related problem.

• System Design Scenario: Be ready to discuss how you would architect a new feature for the design system or address a complex integration challenge.

• Behavioral Questions: Prepare STAR method (Situation, Task, Action, Result) answers for questions related to leadership, problem-solving, conflict resolution, and influencing others.

📝 Enhancement Note: The application process for a Lead role emphasizes not just technical prowess but also leadership, strategic thinking, and the ability to articulate technical decisions and their impact. A strong portfolio showcasing practical application of design system principles, accessibility, and collaborative development is crucial.

🛠 Tools & Technology Stack

Primary Tools:

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

• Languages: JavaScript, TypeScript, Node.js.

• Styling: CSS, potentially preprocessors like Sass/Less, or CSS-in-JS solutions.

• Version Control: Git.

• Package Management: NPM.

Analytics & Reporting:

• CI/CD: GitLab, Jenkins (for build and release management).

• Artifact Management: Artifactory.

• Internal Tools: OpenText likely uses internal tools for project management, code review, and documentation.

CRM & Automation:

• While not directly customer-facing for this role, understanding how design systems integrate with broader product development workflows (which might involve CRM-adjacent processes for feature requests or feedback) is beneficial.

📝 Enhancement Note: The specified tools (React, Angular, JS/TS, Node.js, CSS, Git, NPM, GitLab, Jenkins, Artifactory) are standard for modern frontend and DevOps practices. For a Design Systems role, proficiency in component architecture patterns and tooling for documentation (e.g., Storybook, although not explicitly mentioned) would be highly advantageous. The mention of AI (MCP, Agent definition files) hints at potential future integrations or uses of AI within their development ecosystem.

👥 Team Culture & Values

Operations Values:

• AI-First, Future-Driven, Human-Centered: This core philosophy drives innovation and a focus on impactful solutions.

• Trust and Character: OpenText emphasizes ethical conduct and integrity in all actions.

• Client Focus: Prioritizing client needs and delivering exceptional value is paramount.

• Collaboration and Resilience: Working effectively in teams, tackling challenges, and adapting to change.

• Innovation with Intention: Driving forward new ideas and solutions with a clear purpose and strategic direction.

• Efficiency and Optimization: Implicit in the design system's purpose, aiming to streamline development and improve product quality.

Collaboration Style:

• Cross-Functional Integration: The design system team must work closely with Product Management, UX Design, and development teams across the organization to ensure adoption and alignment.

• Proactive Communication: Regular updates, feedback loops, and transparent sharing of progress and challenges are expected.

• Knowledge Sharing: A culture that encourages sharing best practices, lessons learned, and technical expertise, especially from the Lead Developer to junior members and consuming teams.

• Data-Driven Decisions: While not explicitly stated for this role, OpenText's general approach suggests that decisions regarding the design system's evolution may be informed by usage data, feedback metrics, and performance analysis.

📝 Enhancement Note: The company's stated values directly influence the expected behaviors within the team. A Lead Developer in Design Systems needs to embody collaboration, client focus, and a drive for innovation, all while maintaining high ethical standards. The operational aspect of the design system means that efficiency and effective cross-team collaboration are key to its success.

⚡ Challenges & Growth Opportunities

Challenges:

• Widespread Adoption: Ensuring hundreds of developers across diverse products consistently adopt and correctly use the design system components can be a significant challenge. This requires strong communication, documentation, and support.

• Balancing Innovation and Stability: Keeping the design system up-to-date with modern technologies and user expectations while maintaining backward compatibility and stability for existing products.

• Managing Technical Debt: As the design system evolves, managing technical debt within the component library and ensuring it remains performant and maintainable.

• Cross-Team Dependencies: Coordinating with numerous product teams, each with its own priorities and release cycles, to roll out updates or introduce new components.

• Integrating AI Concepts: Exploring and implementing AI-related features or principles within the design system in a meaningful and practical way, aligning with OpenText's strategic direction.

Learning & Development Opportunities:

• Advanced Frontend Architecture: Deepen knowledge in areas like micro-frontends, state management patterns, and performance optimization for complex web applications.

• Design System Governance: Learn best practices for establishing and managing design system governance models, driving organizational change.

• AI and ML Integration: Gain hands-on experience with AI/ML concepts relevant to software development and user interfaces, as OpenText is an "AI-First" company.

• Technical Leadership & Mentorship: Hone leadership skills through guiding a team, mentoring junior developers, and influencing technical strategy.

• Industry Conferences & Certifications: Opportunities to attend relevant industry events (e.g., on frontend development, accessibility, design systems) and pursue certifications.

📝 Enhancement Note: The challenges are inherent to managing a foundational, organization-wide component library. The growth opportunities are substantial, particularly in leveraging OpenText's AI focus and the company's large scale to develop advanced skills in both technical leadership and emerging technologies.

💡 Interview Preparation

Strategy Questions:

• "Describe your experience leading a design system. What were your key responsibilities, and what was the impact of your work on development teams and product quality?"

  • Preparation: Focus on quantifiable achievements, specific examples of component development, documentation strategies, and how you fostered adoption.

• "How would you approach introducing a new, potentially breaking, change to a widely used component in our design system to hundreds of internal developers?"

  • Preparation: Discuss your strategy for communication, phased rollout, documentation, support, and managing resistance. Highlight your understanding of change management in a large organization.

• "Given OpenText's AI-first strategy, how might you envision AI influencing or being integrated into our design system components in the future?"

  • Preparation: Research OpenText's AI initiatives. Think about how AI could personalize interfaces, improve accessibility features, or automate design system tasks.

Company & Culture Questions:

• "What do you know about OpenText's mission and values, particularly 'AI-First, Future-Driven, Human-Centered'?"

  • Preparation: Review the company's "About Us" section and mission statement. Be ready to connect your personal values and work philosophy to these principles.

• "How do you foster collaboration and mentorship within a development team, especially when working on a shared platform like a design system?"

  • Preparation: Provide examples of successful team dynamics, knowledge sharing sessions, and mentorship initiatives you've led or participated in.

• "How do you ensure your technical decisions align with business objectives and deliver tangible client value?"

  • Preparation: Use the STAR method to illustrate how you've translated business needs into technical solutions and measured their impact.

Portfolio Presentation Strategy:

• Storytelling with Data: For each project, clearly outline the problem, your solution (the design system/component), the technical approach, and the measurable results (e.g., reduced development time, improved consistency, increased accessibility compliance).

• Demonstrate Technical Depth: Be prepared to walk through code examples, explain architectural choices, and discuss trade-offs.

• Highlight Leadership: Use your portfolio to showcase instances where you led technical initiatives, mentored others, or influenced team direction.

• Accessibility Focus: Dedicate specific time to explaining your approach to accessibility and demonstrating compliant components.

Challenge Preparation:

• Component Design Exercise: Practice building a complex, reusable UI component from scratch, focusing on accessibility, responsiveness, and clear API design.

• System Design for Scalability: Prepare for questions about architecting a design system for a large enterprise, including versioning, theming, and integration strategies.

• Code Review Simulation: Be ready to critically review code snippets for best practices, potential bugs, performance issues, and accessibility concerns.

📝 Enhancement Note: Interview preparation should focus on demonstrating not only technical proficiency but also strategic thinking, leadership potential, and a strong understanding of how design systems operate as critical GTM/Product Operations enablers within a large enterprise. Articulating the "why" behind technical choices and their business impact is key.

📌 Application Steps

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

• Submit your application through the OpenText careers portal using the provided link.

• Resume Optimization: Tailor your resume to highlight your experience with React/Angular, design systems, component architecture, accessibility (WCAG), and CI/CD tools. Quantify your achievements whenever possible, especially regarding efficiency gains or adoption rates.

• Portfolio Preparation: Curate a portfolio that showcases your most relevant design system projects. Include code samples, live demos (if applicable), and documentation that demonstrates your process, technical depth, and impact. Be ready to present and discuss these projects in detail.

• Technical Practice: Brush up on your frontend development skills (JavaScript, TypeScript, CSS, HTML) and common design system patterns. Practice coding challenges and system design questions relevant to component architecture and web platform solutions.

• Company Research: Thoroughly research OpenText, its products, its AI strategy, and its company values. Understand how the design system contributes to the company's overall goals and operational efficiency.

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