Sr Product Designer, Foundations

📍 Job Overview

Job Title: Sr. Product Designer, Foundations

Company: Adobe

Location: San Francisco, California, United States

Job Type: Full-Time

Category: Product Design / Design Systems

Date Posted: May 04, 2026

Experience Level: 5+ Years (Senior)

Remote Status: On-site

🚀 Role Summary

• Lead the 0→1 design system efforts for an emerging team within Adobe's Document Cloud, focusing on defining system architecture, foundational primitives, and scalable patterns.

• Design, document, and maintain reusable UI components, interaction patterns, and guidelines to ensure consistency and quality across Adobe's diverse product suite.

• Collaborate closely with engineering teams to align on implementation strategies, design tokens, and component APIs, fostering a cohesive development environment.

• Champion accessibility, inclusivity, and performance as core principles within the design system, ensuring all experiences meet stringent standards.

📝 Enhancement Note: This role is critical for establishing foundational design system elements within a specific business unit (Document Cloud), requiring a blend of strategic foresight and hands-on design execution. The "Foundations" aspect implies a focus on core building blocks, design tokens, and architectural principles that will underpin future component development and product consistency.

📈 Primary Responsibilities

• Define and architect the core design system strategy, including its foundational primitives, component library, and scalable design patterns.

• Develop and maintain comprehensive design documentation for all system elements, ensuring clarity and usability for designers and engineers.

• Conduct design audits of existing product experiences to identify opportunities for systematization, consistency improvements, and component reuse.

• Partner with product managers and engineering leads in feature discovery, system architecture definition, and project scoping to ensure design system alignment.

• Establish and evolve design system principles, standards, and contribution models to support long-term scalability, governance, and adoption.

• Translate product requirements from various product designers into flexible, extensible system solutions that can be easily adopted.

• Mentor junior designers and cross-functional team members on systems thinking, component design best practices, and effective utilization of the design system.

• Champion and integrate accessibility (WCAG) and inclusivity standards into the core design system, ensuring compliance and broad usability.

📝 Enhancement Note: The emphasis on "0→1 design system efforts" and "emerging team" suggests a significant opportunity to shape the direction and architecture of a new system from its inception. This involves not just component design but also defining governance, contribution models, and adoption strategies.

🎓 Skills & Qualifications

Education: While no specific degree is mandated, a strong portfolio demonstrating equivalent practical experience and a deep understanding of design principles is paramount. Familiarity with formal design education or certifications in UX/UI is beneficial.

Experience: 5+ years of progressive experience in product design, with a significant focus on designing, building, or contributing to large-scale, cross-platform design systems.

Required Skills:

• A robust portfolio showcasing experience designing or contributing to a design system at scale, with examples of cross-platform application.

• Deep understanding and practical application of design tokens, theming, and scalable styling systems.

• Proven experience collaborating on or contributing to component libraries using tools like Storybook, Figma libraries, or similar systems.

• Thorough understanding of accessibility standards (WCAG) and demonstrated ability to apply them systematically across UI components.

• History of close, effective collaboration with design, product management, software development, and end-users throughout the product lifecycle.

• Exceptional documentation skills, capable of creating clear, concise, and scalable guidance for diverse technical and non-technical audiences.

Preferred Skills:

• Excellent communication and presentation skills, with the ability to articulate complex multi-level problem spaces and design strategies to stakeholders at all levels.

• Working knowledge of front-end technologies (HTML, CSS, JavaScript) and modern frameworks (e.g., React) to understand design system implementation in code.

• Experience defining and implementing design system governance models, contribution workflows, and adoption strategies.

• Demonstrated ability to influence without authority across multiple teams and product areas to drive system adoption.

• Experience in measuring and reporting on design system adoption rates and overall impact on product development efficiency and quality.

• Experience designing accessible and inclusive interfaces for individuals with disabilities.

• Understanding of applying WCAG conformance criteria in design, including testing comps, wireframes, and prototypes for accessibility.

📝 Enhancement Note: The "Must-haves" emphasize practical, hands-on experience with design systems and accessibility, while "Nice-to-haves" point towards strategic leadership, cross-functional influence, and technical understanding. The preferred accessibility skills highlight Adobe's commitment to inclusive design.

📊 Process & Systems Portfolio Requirements

Portfolio Essentials:

• Demonstrate end-to-end design process for complex UI challenges, highlighting problem definition, ideation, iteration, and final solution.

• Showcase specific examples of designing or contributing to a design system, detailing the architecture, component design, and interaction patterns.

• Include case studies that illustrate how system thinking was applied to solve scalability, consistency, or maintainability issues.

• Present evidence of collaboration with engineering teams, including how design systems were implemented and iterated upon.

Process Documentation:

• Provide examples of how you have documented design system components, guidelines, and best practices for various audiences.

• Showcase experience with creating and maintaining design tokens, theming strategies, or scalable styling systems.

• Illustrate how you have conducted design audits or analyzed existing product experiences for systematization opportunities.

• Detail your approach to ensuring accessibility and inclusivity within design system components and guidelines.

📝 Enhancement Note: A strong portfolio is crucial for this role, not just for showcasing design talent but for demonstrating a deep understanding of design systems, scalability, and cross-functional collaboration. The emphasis on "0→1" means candidates should highlight their ability to build and structure systems from the ground up.

💵 Compensation & Benefits

Salary Range:

• National Range: $124,600 - $234,250 annually.

• California Specific Range: $161,800 - $234,250 annually.

Explanation of Range: The salary range reflects Adobe's compensation philosophy, which considers geographic location, job-related knowledge, skills, and experience. San Francisco/California locations typically command higher compensation due to the cost of labor in those markets. The broad range allows for significant variation based on the candidate's specific experience and the precise needs of the role.

Benefits:

• Comprehensive Benefits Programs: Includes health, dental, and vision insurance, retirement savings plans (e.g., 401k), life insurance, and disability coverage.

• Annual Incentive Plan (AIP): For non-sales roles, this provides short-term incentives based on company and individual performance.

• New Hire Equity Award: Potential eligibility for long-term incentives in the form of stock options or restricted stock units, aligning employee success with company growth.

• Paid Time Off: Generous vacation, sick leave, and holiday policies.

• Employee Assistance Programs: Support for mental health, financial well-being, and other personal challenges.

Working Hours:

• Standard full-time employment is typically 40 hours per week. While the role is on-site, Adobe generally offers flexibility in daily scheduling, allowing for work-life balance, though core hours for collaboration will be expected.

📝 Enhancement Note: The provided salary ranges are explicitly stated and differentiated by location (national vs. California). The benefits list is comprehensive, highlighting standard corporate offerings alongside performance-based incentives and equity, which are typical for senior roles at large tech companies.

🎯 Team & Company Context

🏢 Company Culture

Industry: Software, Creative & Media, Technology. Adobe is a global leader in creativity and digital experiences, providing software and services that empower individuals and businesses to create, deliver, and promote digital content.

Company Size: Over 30,000 employees worldwide. This indicates a large, established organization with structured processes, ample resources, and a wide array of career development opportunities. For operations professionals, this means working within established frameworks and potentially influencing large-scale process improvements.

Founded: 1982. A long history in the tech industry signifies stability, innovation, and a deep understanding of market evolution. This longevity suggests a culture that values continuous improvement and adaptation.

Team Structure:

• Adobe Design: A multidisciplinary, global organization comprising design researchers, design engineers, experience designers, brand designers, content strategists, and program managers.

• Document Cloud Foundations Team: This specific team is emerging and focused on building the core design system. It will likely involve close collaboration with other product design teams within Document Cloud and potentially with central design system teams.

• Reporting Structure: Senior designers typically report to Design Managers or Directors. This role will likely involve significant cross-functional collaboration with Product Management, Engineering, and potentially Research.

Methodology:

• Data-Driven Design: Adobe emphasizes using data and user insights to inform design decisions and measure impact.

• Systems Thinking: A core competency for this role, focusing on creating scalable, maintainable, and consistent design solutions.

• Agile Development: Collaboration with engineering teams likely follows agile methodologies, requiring designers to be adaptable and responsive.

• User-Centricity: A commitment to understanding and meeting user needs through research and iterative design.

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

📝 Enhancement Note: Adobe's established presence and "Adobe for All" philosophy suggest a culture that values diversity, inclusion, and employee empowerment. The "Foundations" team within Document Cloud implies a strategic focus on building core infrastructure that will impact many products and users.

📈 Career & Growth Analysis

Operations Career Level: This is a Senior Product Designer role, indicating a position of significant responsibility and influence. It's a level where individuals are expected to lead initiatives, mentor others, and operate with a high degree of autonomy. For those transitioning into or advancing within operations-adjacent design roles, it represents a move towards strategic system building.

Reporting Structure: The Sr. Product Designer will likely report to a Design Manager or Director within the Document Cloud organization. They will collaborate extensively with Product Managers, Engineering Leads, and other Designers across Document Cloud and potentially central Design Systems teams.

Operations Impact: While this role is in Product Design, its focus on design systems has substantial operational implications. A well-designed and implemented system directly impacts:

• Development Efficiency: Faster iteration and development cycles by providing reusable components.

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

• Brand Integrity: Maintaining Adobe's visual identity and quality standards.

• Scalability: Enabling the company to expand its product offerings and user base without compromising quality or increasing design/dev overhead proportionally.

• Accessibility Compliance: Reducing risk and ensuring broader market reach by embedding accessibility from the start.

Growth Opportunities:

• Leadership in Design Systems: Potential to become a lead or principal designer for design systems, shaping strategy and technical direction.

• Cross-Functional Expertise: Deepen understanding of engineering processes, product management, and business strategy through close collaboration.

• Mentorship and Team Building: Opportunity to formally or informally mentor junior designers and contribute to building the design system team's capabilities.

• Specialization: Develop deep expertise in areas like design tokens, accessibility, or system architecture.

• Lateral Movement: Potential to move into other senior design roles within Adobe's broader product portfolio or even into design operations or program management roles focused on design tooling and processes.

📝 Enhancement Note: The "Foundations" aspect of this role offers a unique opportunity to shape core infrastructure, which is highly valued in operations-minded career paths. The ability to influence design and development processes at scale is a significant growth driver.

🌐 Work Environment

Office Type: Adobe operates with a hybrid work model, balancing in-office collaboration with remote flexibility. For this "On-site" role, it implies a structured office environment designed for collaboration.

Office Location(s): San Francisco, California. This is a major tech hub, offering access to a vibrant ecosystem of talent, innovation, and industry events. The specific office will likely be equipped with modern design studios and collaborative spaces.

Workspace Context:

• Collaborative Spaces: Offices are designed with meeting rooms, open collaboration areas, and private spaces to support various work styles.

• Tools & Technology: Access to Adobe's full suite of Creative Cloud tools, Figma, and other industry-standard design and prototyping software. Collaboration tools like Slack, Teams, and internal Adobe platforms will be utilized.

• Team Interaction: Opportunities for daily interaction with designers, engineers, and product managers, fostering a dynamic and iterative work environment. Regular design critiques, team syncs, and cross-functional meetings are standard.

Work Schedule: While the role is on-site, Adobe typically supports flexible working hours. However, consistent presence during core business hours is expected for effective collaboration with distributed teams and stakeholders. The 40-hour work week is standard, with potential for occasional overtime during critical project phases.

📝 Enhancement Note: The on-site requirement in a major tech hub like San Francisco suggests a dynamic, collaborative environment with access to cutting-edge tools and a rich professional network. This setting is conducive to intensive system building and cross-functional alignment.

📄 Application & Portfolio Review Process

Interview Process:

• Initial Screening: A recruiter will assess your background, portfolio, and alignment with the role's core requirements.

• Portfolio Review & Design Challenge: A session with hiring managers and/or senior designers to walk through your portfolio. This often includes a design challenge, which may be delivered live or as a take-home assignment, focused on system thinking, component design, or problem-solving within a design system context.

• Technical & Behavioral Interviews: Discussions with team members (designers, engineers, PMs) to assess technical skills, systems thinking, collaboration style, and cultural fit. Expect questions about your experience with design systems, accessibility, and handling ambiguity.

• Final Interview: Typically with senior leadership to discuss strategic alignment, leadership potential, and overall fit within Adobe Design.

Portfolio Review Tips:

• Highlight Design System Expertise: Dedicate specific sections or case studies to your experience with design systems. Clearly articulate your role, the system's architecture, and your specific contributions (components, patterns, tokens, documentation).

• Showcase "0→1" Experience: If possible, include projects where you were involved in establishing a system from its early stages, demonstrating your ability to define strategy and build foundational elements.

• Emphasize Process & Rationale: For each project, explain your design process, the problems you solved, the decisions you made, and why. For system work, detail the underlying principles and scalability considerations.

• Demonstrate Collaboration: Include examples of how you worked with engineering and product teams, showcasing your ability to translate requirements and align on implementation.

• Accessibility Integration: Clearly show how accessibility was incorporated into your design process and system components.

• Metrics & Impact: Quantify the impact of your work whenever possible (e.g., improved efficiency, reduced design debt, increased consistency).

Challenge Preparation:

• Systems Thinking: Practice breaking down complex problems into smaller, manageable parts and thinking about how they relate to a larger system.

• Component Design: Be prepared to design a new component or improve an existing one, considering reusability, flexibility, states, and accessibility.

• Design Tokens & Theming: Understand how design tokens work and how they enable theming and scalability.

• Accessibility Standards: Review WCAG guidelines and be ready to apply them to design scenarios.

• Documentation: Think about how you would document a new component or pattern for a design system.

📝 Enhancement Note: The interview process heavily emphasizes practical application of design system principles and a proven ability to collaborate. A strong portfolio that clearly articulates system architecture, component design, and impact is paramount.

🛠 Tools & Technology Stack

Primary Tools:

• Design & Prototyping: Figma (primary tool for UI design, prototyping, and component libraries), Adobe Creative Cloud Suite (Photoshop, Illustrator, XD - though Figma is likely dominant for system work).

• Design System Management: Figma Libraries, Storybook (or similar component documentation/development platforms), Zeplin (for handoff, though less critical for system-level design).

• Collaboration & Communication: Slack, Microsoft Teams, Adobe Connect, Jira, Confluence.

• Documentation: Confluence, Notion, or internal Adobe documentation platforms.

Analytics & Reporting: While not directly a design system tool, understanding how design system usage is tracked and measured might involve tools like Google Analytics, Amplitude, or internal Adobe analytics platforms.

CRM & Automation: Generally not directly used by product designers, but an understanding of how design systems integrate with development workflows that utilize these systems is beneficial.

📝 Enhancement Note: Proficiency in Figma is almost certainly a baseline requirement for this role, given its prevalence in modern design system development. Experience with tools like Storybook demonstrates an understanding of bridging design and development.

👥 Team Culture & Values

Operations Values:

• Customer Focus: Designing experiences that meet user needs and provide value.

• Collaboration: Working effectively across teams (Design, Engineering, Product Management) to achieve shared goals.

• Innovation: Continuously seeking new and better ways to solve problems and improve experiences.

• Excellence: Striving for high quality in design, documentation, and execution.

• Inclusivity & Accessibility: Ensuring all products are usable and welcoming to everyone.

• Efficiency: Building scalable systems that streamline development and improve productivity.

Collaboration Style:

• Cross-Functional Partnership: Strong emphasis on working closely with engineering and product management to ensure design systems are technically feasible, adopted, and impactful.

• Iterative Design: Embracing feedback and iterating on designs based on critiques and user testing.

• Knowledge Sharing: Actively participating in design reviews, knowledge-sharing sessions, and contributing to internal design communities.

• Data-Informed Decision Making: Using research and analytics to guide design choices and measure success.

📝 Enhancement Note: Adobe's stated values ("People, Purpose, Community," "Adobe for All") suggest a culture that prioritizes employee well-being, diversity, and making a positive impact. For a design systems role, this translates to building a system that is inclusive, well-documented, and collaboratively developed.

⚡ Challenges & Growth Opportunities

Challenges:

• Establishing a New System (0→1): Building a design system from scratch involves significant ambiguity, the need for strong foundational decisions, and potential resistance to adoption.

• Balancing System Needs vs. Product Needs: Ensuring the design system is flexible enough to meet diverse product requirements while maintaining consistency and scalability.

• Driving Adoption: Convincing multiple product teams to adopt and contribute to the design system requires strong influence and clear value demonstration.

• Maintaining Governance: Evolving and maintaining the system over time, including managing contributions, updates, and versioning, requires robust processes.

• Cross-Platform Complexity: Designing a system that works seamlessly across web, desktop, and potentially mobile platforms.

Learning & Development Opportunities:

• Deep Expertise in Design Systems: Become a recognized expert in design system architecture, implementation, and strategy.

• Leadership Development: Gain experience in influencing teams and stakeholders without direct authority, crucial for senior roles.

• Technical Acumen: Enhance understanding of front-end development principles and how design systems are coded.

• Accessibility Specialization: Develop deep knowledge and practical application of accessibility standards.

• Mentorship: Opportunity to guide and mentor emerging designers within the organization.

📝 Enhancement Note: The primary challenge is the "0→1" nature of the system, requiring strategic thinking and strong leadership to overcome initial hurdles. Growth opportunities are substantial for those who excel in building and scaling design systems.

💡 Interview Preparation

Strategy Questions:

• "Describe your process for defining foundational elements (primitives, tokens, core components) for a new design system."

• "How would you approach auditing an existing product suite to identify opportunities for systematization and component reuse?"

• "Walk us through a time you had to influence multiple teams to adopt a new design system or a significant change within an existing one. What was your strategy?"

• "How do you balance the need for system consistency with the unique requirements of individual products?"

Company & Culture Questions:

• "What interests you specifically about Adobe's Document Cloud and this 'Foundations' role?"

• "How do you see a design system contributing to Adobe's overall mission of empowering creativity?"

• "Describe your ideal collaboration model with engineering and product management teams."

Portfolio Presentation Strategy:

• Structure: Organize your portfolio around key themes: Design Systems, Problem Solving, Collaboration, Accessibility. Start with your most relevant design system work.

• Storytelling: For each case study, clearly articulate the problem, your role, your process, the solution (especially system components), and the outcome/impact. Use visuals effectively.

• System Deep Dive: Be prepared to spend significant time detailing your design system projects – the architecture, the component breakdown, the rationale behind decisions, and how you handled implementation and documentation.

• Interactive Elements: If presenting live, be ready to answer detailed questions about your design choices and system logic. Be prepared to sketch or whiteboard concepts if asked.

• Focus on "Foundations": Emphasize your ability to build core, scalable structures.

📝 Enhancement Note: Be ready to demonstrate not just design skills but strategic thinking, leadership potential, and a deep understanding of the operational impact of design systems. The "Foundations" aspect means showcasing your ability to build robust, scalable core elements.

📌 Application Steps

To apply for this Sr. Product Designer, Foundations position:

• Submit your application through the Adobe careers portal via the provided link.

• Portfolio Customization: Tailor your resume and portfolio to prominently feature your experience with design systems, component design, design tokens, and accessibility. Highlight any "0→1" system-building experiences.

• Resume Optimization: Ensure your resume clearly outlines your 5+ years of relevant experience, using keywords from the job description such as "design system," "UI components," "accessibility (WCAG)," "Figma," and "cross-platform design." Quantify achievements where possible.

• Interview Preparation: Practice articulating your design process, system architecture decisions, and collaboration strategies. Prepare specific examples for behavioral questions and be ready to present your portfolio effectively.

• Company Research: Familiarize yourself with Adobe's products, particularly Document Cloud, and understand their design philosophy and commitment to accessibility by reviewing their website and design blogs.

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

---