Senior Product Designer, Platform Design

📍 Job Overview

Job Title: Senior Product Designer, Platform Design

Company: Epicor Software Corporation

Location: Hyderabad, Telangana, India

Job Type: Full-time

Category: Product Design / UX Design (Focus on Design Systems)

Date Posted: 2026-08-28

Experience Level: Senior (5-8 years)

Remote Status: Hybrid

🚀 Role Summary

• Lead the design and evolution of core component libraries and pattern architecture within the LUX design system, ensuring consistency and usability across Epicor's product portfolio.

• Own and meticulously manage the Figma design system library, including component structure, variants, variables, semantic tokens, and auto-layout configurations.

• Drive the strategic implementation of design tokens to establish a seamless connection between design specifications and coded components, ensuring design-code parity.

• Collaborate closely with UX Platform engineers to maintain alignment between design specifications in Figma and their implementation in code, particularly within Storybook.

• Develop and maintain comprehensive, living documentation for components and patterns using zeroheight, serving as the single source of truth for design and development teams.

📝 Enhancement Note: While the title is "Senior Product Designer, Platform Design," the core responsibilities and required skills strongly indicate a specialized role focused on Design Systems and UX Platform Design. This role is crucial for establishing and maintaining the foundational design language and reusable components that underpin Epicor's entire software suite, impacting thousands of users and internal design/development teams. The emphasis on Figma library ownership, token architecture, and Storybook review positions this as a critical role for operationalizing design at scale.

📈 Primary Responsibilities

• Lead the design of core LUX components, meticulously defining their anatomy, variants, states, behavior, and ensuring adherence to WCAG accessibility standards from inception.

• Own the end-to-end management of the LUX Figma libraries, focusing on robust component architecture, dynamic variables, semantic token implementation, and efficient auto-layout utilization.

• Champion and drive the token strategy in close partnership with UX Platform engineers to ensure design specifications translate cleanly and consistently into code.

• Conduct thorough reviews of built components within Storybook, rigorously comparing them against design specifications and actively resolving any design-development parity gaps.

• Author and maintain high-quality, up-to-date component documentation within zeroheight, ensuring clear guidance for designers and developers.

• Manage the contribution and governance process for the design system, including triaging requests, making informed decisions on what enters the system, and clearly documenting the rationale behind these decisions.

• Embed WCAG accessibility as a non-negotiable design constraint throughout the component design process.

• Mentor junior designers through constructive critique sessions and actively set and maintain a high standard for systems design craft across the team.

📝 Enhancement Note: The responsibilities highlight a significant ownership and leadership component, moving beyond individual component design to encompass the strategic governance and evolution of the entire design system. The emphasis on "closing design-dev parity gaps" and "token strategy" points to a role that requires deep technical understanding and strong collaboration with engineering.

🎓 Skills & Qualifications

Education: Bachelor's degree in Design, Human-Computer Interaction, Computer Science, or a related field, or equivalent practical experience.

Experience: 5 to 8 years of progressive product design experience, with a substantial and demonstrable track record of hands-on design system work on systems actively used by multiple product teams.

Required Skills:

• Design Systems Expertise: Proven experience in designing, building, and maintaining complex design systems.

• Figma Proficiency: Expert-level skills in Figma, including component architecture, variants, auto-layout, variables, and library management.

• Storybook Experience: Hands-on experience with Storybook for reviewing, specifying, and quality assurance of components against implemented code. This is a required skill.

• Zeroheight Experience: Proven ability to author and maintain living system documentation using zeroheight. This is a required skill.

• Design Tokens: A strong working command of design tokens and understanding of how token pipelines connect design specifications to code.

• Developer Collaboration: Fluency in working collaboratively with engineers on component APIs, states, and understanding framework constraints.

• Governance & Judgment: Demonstrated ability to exercise sound judgment in design system governance, including the ability to extend, adapt, or reject contributions with clear rationale.

• Technical Writing: Clear, concise, and effective written communication skills, essential for documentation and rationale.

• Accessibility Standards: Deep understanding and practical application of WCAG accessibility guidelines.

Preferred Skills:

• Agentic/AI Workflows: Experience with AI-assisted design workflows, generative UI, or making design systems consumable by AI agents.

• Multi-Framework Experience: Familiarity with designing for multiple front-end frameworks (e.g., Web Components, React, Angular, Blazor).

• Token Pipeline Tooling: Experience with token pipeline tools such as Style Dictionary.

• Assistive Technology Testing: In-depth experience with accessibility testing using assistive technologies.

• Enterprise/B2B Software: Background in designing for enterprise or B2B software environments.

📝 Enhancement Note: The emphasis on "Required" for Storybook and zeroheight indicates these are critical gatekeepers for applications. The preferred skills, particularly around AI and multi-framework experience, suggest Epicor is forward-thinking and values adaptability in its design platform team. The distinction between required and preferred skills is crucial for candidates to understand where to focus their application.

📊 Process & Systems Portfolio Requirements

Portfolio Essentials:

• Systems Focus: Your portfolio is required and must showcase significant design systems work, including components, tokens, and associated documentation. Applications without a portfolio link will be disqualified.

• Component Architecture: Detailed examples demonstrating how you structure and build reusable components within Figma, including variants, states, and properties.

• Token Implementation: Visualizations and explanations of your approach to semantic design tokens and their connection to code.

• Documentation Samples: Examples of clear, concise, and comprehensive documentation created for design systems, ideally using zeroheight.

• Cross-functional Collaboration: Evidence of how you have collaborated with engineering teams to ensure design-code parity and successful implementation of system elements.

Process Documentation:

• Workflow Design: Showcase your process for defining component behavior, states, and interactions, including accessibility considerations.

• Governance Framework: Illustrate your approach to managing design system contributions, including intake, review, and decision-making processes.

• Measurement & Analysis: Provide examples of how you measure the impact and adoption of design system components and track design-dev parity.

📝 Enhancement Note: The explicit requirement for a portfolio with a focus on "systems work" is a critical differentiator. Candidates must curate their portfolios to highlight these specific skills. The emphasis on documentation and governance suggests that the ability to articulate design decisions and manage a growing system is as important as the visual design itself.

💵 Compensation & Benefits

Salary Range: Given the Senior Product Designer title, 5-8 years of experience, and the Hyderabad, India location, a competitive salary range would typically fall between INR 20,00,000 to INR 35,00,000 per annum. This estimate is based on industry benchmarks for senior design roles in major Indian tech hubs, considering the specialized nature of design systems work and Epicor's position as an enterprise software provider.

Benefits:

• Health and Wellness: Comprehensive health and wellness benefits designed to support overall well-being.

• Internal Mobility: Opportunities for mentorship, continuing education, and focused career goal setting, with a notable 25% of positions filled internally.

• Career Development: Access to free LinkedIn Learning licenses for all employees, complemented by a dedicated Mentoring Program to foster personal and professional growth.

• Education Support: Geographically specific programs designed to balance the cost of education with the benefits of continued learning and personal development.

• Inclusive Workplace: Opportunity to collaborate with a diverse global team in an inclusive environment that fosters innovation and celebrates partnership.

• Work-Life Balance: Policies built on mutual trust and support, encouraging time off to rest, recharge, and reconnect.

• Global Mobility: Comprehensive support for international relocations and permanent residency processes.

Working Hours: Standard full-time hours, likely around 40 hours per week, with a hybrid work arrangement. Flexibility is implied through policies supporting work-life balance, but specific daily schedules will need to align with team collaboration needs, particularly with UX Platform engineers.

📝 Enhancement Note: The salary range is an estimation based on general market data for senior design roles in Hyderabad, India. Specific compensation will depend on the candidate's exact experience, skills, and negotiation. The provided benefits are extensive and highlight Epicor's commitment to employee development and well-being, which are strong selling points for experienced professionals.

🎯 Team & Company Context

🏢 Company Culture

Industry: Enterprise Resource Planning (ERP) Software, Business Management Software, Cognitive ERP. Epicor operates in a competitive B2B software market, providing critical solutions for businesses in manufacturing, distribution, retail, and services sectors. This context means the design system must support complex workflows and diverse user needs within these industries.

Company Size: Over 5,000 talented professionals globally. This indicates a well-established, medium-to-large enterprise with structured processes and significant resources, allowing for dedicated teams like the UX Platform and design systems group.

Founded: While the founding date isn't explicitly stated in the provided text, Epicor has a long history in the ERP space, suggesting a mature company with evolving technology stacks and a commitment to ongoing innovation.

Team Structure:

• LUX Team: This role is part of the LUX team, which focuses on the user experience platform. This team likely includes UX Platform engineers, product designers specializing in systems, and potentially UX researchers.

• Reporting Structure: The Senior Product Designer will report to a Design Lead or Manager within the UX Platform group, with close collaboration across product design, engineering, and potentially product management.

• Cross-functional Collaboration: The role demands tight collaboration with UX Platform engineers, other product designers who will be consumers of the design system, and potentially front-end developers.

Methodology:

• Data-Driven Design: The company emphasizes "data, AI, and cognitive ERP," suggesting that design decisions are informed by data analysis and performance metrics.

• Agile Development: While not explicitly stated, large software companies typically employ agile methodologies, meaning the design system evolves iteratively in sprints.

• Design-Code Parity: A core methodology is ensuring design and code are synchronized, facilitated by tools like Storybook and shared token architectures.

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

📝 Enhancement Note: Understanding Epicor's B2B focus is key. Design systems in this context need to prioritize efficiency, scalability, and robustness over fleeting trends. The mention of "cognitive ERP" and "AI" suggests the design system may need to accommodate future AI-driven features and interfaces.

📈 Career & Growth Analysis

Operations Career Level: This role is positioned as a Senior individual contributor. It signifies a level of expertise where the designer is expected to lead significant design efforts, mentor others, and influence strategy within their domain (design systems). The pathway extends from Senior to Principal and beyond, indicating clear opportunities for technical specialization and leadership within the design platform.

Reporting Structure: The designer will likely report to a Design Manager or Lead within the UX Platform team. They will work closely with UX Platform Engineers and collaborate with other Product Designers across various product teams who utilize the LUX design system. This structure allows for both focused system development and broad application impact.

Operations Impact: The Senior Product Designer's work has a compounding impact across "every product Epicor ships." By owning the core components and token architecture, this role directly influences the user experience, development efficiency, and brand consistency of all Epicor products. A well-maintained design system accelerates development, reduces redundant work, and ensures a cohesive user journey for thousands of businesses.

Growth Opportunities:

• Technical Specialization: Deepen expertise in design systems, component architecture, design tokens, accessibility, and potentially AI-driven design tools, progressing towards a Principal or Staff Designer role.

• Leadership & Mentorship: Grow into a leadership role by mentoring junior designers, leading system initiatives, and potentially managing aspects of the design system governance process.

• Cross-functional Expertise: Develop a strong understanding of software development lifecycles, framework constraints (React, Angular, Blazor, etc.), and the unique needs of enterprise software users.

• Strategic Influence: Contribute to the strategic direction of the LUX design system and its integration into Epicor's product development roadmap.

📝 Enhancement Note: The "compounding impact" statement is a strong indicator of the role's strategic importance. Candidates should prepare to articulate how their design system contributions drive efficiency and quality across a broad product suite, aligning with the company's goal of creating "a world of better business."

🌐 Work Environment

Office Type: The role is designated as Hybrid, implying a blend of remote work and in-office presence. This suggests a modern work environment that balances flexibility with the need for in-person collaboration.

Office Location(s): The primary location is Hyderabad, Telangana, India. This specific office will serve as the hub for hybrid work, requiring regular attendance for team meetings, design critiques, and collaborative sessions.

Workspace Context:

• Collaborative Environment: The hybrid model and team structure necessitate a collaborative workspace. Expect opportunities to engage with fellow designers and engineers in person for focused work sessions, brainstorming, and problem-solving.

• Tools & Technology: Access to industry-standard design tools (Figma), documentation platforms (zeroheight), component development environments (Storybook), and potentially advanced AI design tools. A robust IT infrastructure will support both remote and in-office work.

• Team Interaction: Regular opportunities for interaction with the UX Platform team, including design critiques, knowledge-sharing sessions, and project-specific syncs. The role also involves engaging with product teams who are consumers of the design system.

Work Schedule: A standard full-time schedule (approximately 40 hours per week) is expected, with the hybrid arrangement offering some flexibility. Core working hours will likely be established to facilitate collaboration across different time zones and with on-site colleagues.

📝 Enhancement Note: For a hybrid role, candidates should consider their comfort level with balancing remote autonomy with in-office collaboration. The Hyderabad location will be the primary touchpoint for team interactions.

📄 Application & Portfolio Review Process

Interview Process:

• Initial Screening: A review of your resume and, critically, your portfolio. Ensure your portfolio clearly demonstrates design systems experience, including components, tokens, documentation, and ideally, collaboration with developers. Applications without a portfolio link will be disqualified.

• Technical Interview(s): Expect in-depth discussions about your design systems philosophy, experience with Figma, Storybook, zeroheight, and design tokens. You may be asked to walk through specific case studies from your portfolio.

• Design Challenge/Case Study Presentation: A common step for design roles. You might be given a specific system-related problem to solve or asked to present a detailed case study from your portfolio, focusing on your process, decision-making, and impact.

• Collaboration & Culture Fit: Interviews with team members and potentially hiring managers to assess your collaboration style, communication skills, and alignment with Epicor's values (Proactive, Proud, Partners).

• Final Interview: Typically with senior leadership to discuss your overall fit and long-term potential.

Portfolio Review Tips:

• Show, Don't Just Tell: Go beyond static mockups. Show interactive components, explain your Figma architecture (variants, auto-layout), and demonstrate how your tokens work.

• Quantify Impact: Where possible, highlight the impact of your design system work – e.g., reduced development time, improved consistency, increased adoption rates.

• Document Your Process: Clearly articulate your thought process, the challenges you faced, and how you arrived at solutions, especially concerning governance and developer collaboration.

• Highlight System Thinking: Emphasize your understanding of how individual components fit into a larger system and how the system scales.

• Tailor to the Role: Ensure your portfolio prominently features experience with Figma, Storybook, zeroheight, and design tokens as requested.

Challenge Preparation:

• System Design Fundamentals: Revisit core principles of component design, atomic design, and design token methodologies.

• Accessibility: Be ready to discuss WCAG compliance and how you integrate accessibility into system design.

• Developer Collaboration Scenarios: Prepare to discuss how you handle design-dev handoffs, resolve API discrepancies, and work within engineering constraints.

• Governance: Think about how you would manage contributions, prioritize requests, and maintain consistency in a growing design system.

📝 Enhancement Note: The explicit disqualification for applications without a portfolio link cannot be stressed enough. Candidates must actively curate their portfolios to meet these specific requirements, focusing on systems work, not just general UI design.

🛠 Tools & Technology Stack

Primary Tools:

• Figma: The core tool for design system creation, component architecture, variants, variables, and library management. Expertise is mandatory.

• Storybook: Essential for reviewing, specifying, and QA'ing coded components. Proficiency is required.

• Zeroheight: The platform for authoring and maintaining living design system documentation. Proficiency is required.

Analytics & Reporting:

• Internal Analytics Tools: Likely used to track design system adoption and component usage across products.

• Performance Monitoring: Tools to assess the impact of design system changes on user experience and development efficiency.

CRM & Automation:

• Internal Ticketing/Project Management: Tools like Jira or similar for managing design system requests, bug tracking, and workflow governance.

• Collaboration Platforms: Slack, Microsoft Teams, or similar for day-to-day communication and team coordination.

📝 Enhancement Note: The explicit mention of Figma, Storybook, and Zeroheight as "Required" skills emphasizes their central role in this position. Candidates should be prepared to demonstrate deep proficiency in these tools.

👥 Team Culture & Values

Operations Values:

• Proactive: Encourages taking initiative, anticipating needs, and driving improvements without explicit direction. For this role, it means proactively identifying areas for design system enhancement or potential issues.

• Proud: Fosters a sense of ownership and commitment to high-quality work. Designers are expected to take pride in the craft and the impact of the design system.

• Partners: Emphasizes strong collaborative relationships, both internally within the UX Platform team and externally with engineering and product teams. This means working as a trusted partner to development and product stakeholders.

• Data-Driven: Decisions are informed by data, user feedback, and performance metrics.

• Efficiency & Craftsmanship: A balance between delivering functional, well-documented components efficiently and maintaining a high standard of design quality and accessibility.

Collaboration Style:

• Partnership-Oriented: Works closely with UX Platform engineers to ensure design-code alignment, treating engineers as key collaborators.

• Systemic Thinking: Encourages a holistic view of the design system, understanding how individual elements contribute to the overall user experience and development efficiency.

• Knowledge Sharing: Actively shares knowledge through documentation, critiques, and mentoring to uplift the design and development teams.

• Feedback Loop: Embraces a culture of constructive feedback, both giving and receiving, to continuously improve the design system.

📝 Enhancement Note: The "Proactive, Proud, Partners" slogan is a strong indicator of the desired work ethic. Candidates should be prepared to demonstrate how they embody these values in their approach to design systems work.

⚡ Challenges & Growth Opportunities

Challenges:

• Scaling the Design System: Ensuring the design system remains robust, maintainable, and adaptable as Epicor's product portfolio and feature set grow.

• Balancing Design Vision with Development Constraints: Navigating the technical limitations and framework specifics of various platforms while maintaining design integrity and user experience quality.

• Driving Adoption and Governance: Encouraging widespread adoption of the design system across diverse product teams and managing contributions effectively to prevent fragmentation.

• Keeping Pace with Technology: Integrating emerging technologies like AI into the design system and workflows, and adapting to new design and development tools.

Learning & Development Opportunities:

• Deepening Systems Expertise: Advanced training in design token methodologies, component architecture patterns, and accessibility best practices.

• AI & Agentic Design: Opportunities to explore and implement AI-assisted workflows and generative UI within the design system context.

• Cross-Framework Understanding: Gaining practical experience with different front-end frameworks (React, Angular, Blazor) and their implications for design systems.

• Leadership Development: Formal and informal mentorship, project leadership opportunities, and potential pathways to Principal or Staff Designer roles.

• Industry Engagement: Participation in design system conferences, workshops, and community events.

📝 Enhancement Note: The challenges highlight the dynamic nature of design systems work in a large enterprise. The growth opportunities are substantial, offering a clear path for career advancement for a dedicated design systems professional.

💡 Interview Preparation

Strategy Questions:

• "Describe your approach to designing a new core component for a design system. Walk me through the process from initial concept to documentation and developer handoff." (Focus on anatomy, variants, states, accessibility, documentation, and collaboration with engineers.)

• "How do you manage contributions to a design system, and what's your strategy for saying 'no' or adapting a proposed change?" (Prepare to discuss governance processes, triage, and decision-making rationale.)

• "Imagine a situation where a product team is not adopting a core component from the LUX system. How would you investigate and address this issue?" (Focus on understanding adoption barriers, communication, and support strategies.) Company & Culture Questions:

• "Based on what you know about Epicor and this role, how do you see yourself embodying our values of Proactive, Proud, Partners?" (Relate your past experiences to these values.)

• "How do you approach collaboration with engineers, especially when there are technical constraints or disagreements on component implementation?" (Highlight your partnership approach and communication skills.)

• "How do you measure the success and impact of a design system?" (Prepare to discuss metrics like adoption rates, development velocity, consistency, and user satisfaction.) Portfolio Presentation Strategy:

• Structure for Impact: Start with a high-level overview of the system's purpose and your role, then dive into 2-3 detailed case studies.

• Component Deep Dive: For each case study, clearly explain the problem, your design process, the Figma architecture (show variants, auto-layout), your token strategy, and how you documented it in zeroheight.

• Developer Collaboration Focus: Explicitly discuss your interactions with developers, how you ensured design-code parity (using Storybook examples if possible), and any challenges overcome.

• Quantify and Qualify: Use data and concrete examples to demonstrate the impact of your work. Explain the "why" behind your design decisions.

• Conciseness: Be mindful of time. Practice presenting your portfolio efficiently, hitting the key points that align with the job requirements.

📝 Enhancement Note: Candidates should prepare to articulate their systems thinking and design process in detail, with specific examples that align with the required tools and responsibilities. The emphasis on "systems work" means general UI portfolio pieces will not suffice.

📌 Application Steps

To apply for this Senior Product Designer, Platform Design position:

• Submit your application through the provided link on Epicor's Workday job portal.

• Curate your Portfolio: Ensure your portfolio is readily accessible via a link in your application. It must prominently feature detailed examples of your design systems work, including component architecture in Figma, design token implementation, documentation (ideally zeroheight), and your experience with Storybook. Applications without this specific focus will be disqualified.

• Optimize Your Resume: Tailor your resume to highlight your 5-8 years of experience in product design, specifically emphasizing your design systems contributions, proficiency with Figma, Storybook, and zeroheight, and your experience with accessibility and developer collaboration. Use keywords from the job description.

• Prepare Your Presentation: Practice walking through your portfolio case studies, focusing on your process, decision-making, and the impact of your design systems work. Be ready to discuss your approach to governance, accessibility, and collaboration with engineers.

• Research Epicor: Understand Epicor's business, its target industries, and its commitment to "data, AI, and cognitive ERP." Consider how your design system work contributes to these broader company 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.