Senior Product Designer

We need to output HTML fragment with sections: About the Team & Opportunity, How You'll Make an Impact (maybe split into subsections? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. The posting includes: About the Team & Opportunity (that's like About the role). Then "How You'll Make an Impact" includes problem, who you'll partner with, what success looks like, key projects. Could be considered Responsibilities? Might be better to have sections: About the Team & Opportunity (About the role), Responsibilities (How You'll Make an Impact), Requirements (What We're Looking For), Qualifications (maybe Preferred Qualifications), Skills (maybe Required Skills & Experience). Benefits? Not present. Pay: Salary Transparency present. Schedule: not present. So we include Pay section. We must not include headings with filler. So we include only sections with real content. We need to preserve all substantive info, not invent or summarize away detail. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to remove boilerplate: cookie/navigation/legal/EEO etc. There's Inclusion & Belonging paragraph at end; that's EEO? It's about inclusion; maybe considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The Inclusion & Belonging paragraph is likely EEO boilerplate; we should remove it. Also remove duplicated lines. We need to keep Salary Transparency paragraph. We need to keep "About the Team & Opportunity" content. We need to keep "How You'll Make an Impact" content. We need to keep "What We're Looking For" (Required Skills & Experience (Must-Haves) and Preferred Qualifications (Nice-to-Haves)). We'll split into Requirements (must-haves) and Qualifications (nice-to-haves). Also maybe Skills section for required skills? But we can combine. We need to ensure we don't repeat job title as heading (the page already shows it). So no heading for Senior Product Designer. We need to output only HTML fragment. Let's extract content. Original text: "Clever is on a mission to connect every student to a world of learning. As the leading identity platform for education, more than 111,000 schools worldwide use Clever to power secure digital learning experiences. With Clever’s layered security solutions, schools can protect access and identities for all staff, teachers, and students. With a secure identity platform for schools and a network of leading application providers, Clever is committed to advancing education with technology that works for students everywhere. Clever, a Kahoot! company, has an office in San Francisco, CA, but you can visit us at clever.com anytime. About the Team & OpportunityThe District Dashboard team is responsible for the "front door" experience for our School Organization Administrators. As a Senior Product Designer on this team, you’ll be the design lead for the most critical interface in our ecosystem—the place where administrators manage digital learning for entire districts. You’ll join a high-performing "quad" (Product Manager, Engineering Manager, and Product Marketing Manager) to solve complex architectural challenges. Because many teams at Clever build features within this dashboard, you will act as the primary steward of the user experience, ensuring that every new addition fits into a cohesive, intuitive whole. How You’ll Make an ImpactThe Problem You’ll Solve: You will oversee the "birds-eye view" of the School Organization Dashboard, evolving a scalable information architecture as we introduce new features. You will tackle foundational challenges like reimagining Role-Based Access Control (RBAC) and strengthening app governance and compliance frameworks. You will also be the primary owner of our design system, Dewey--maintaining, delegating tasks, and leading its AI-powered evolution in close partnership with Engineering. Additionally, you will lead the charge in remediating accessibility issues to ensure our tools are inclusive for all administrators.Who You’ll Partner With: You’ll work in close collaboration with your dedicated quad (Product Designer, Product Manager, Engineering Manager, Product Marketing Manager) and serve as a bridge between various product teams to ensure design consistency across the platform.What Success Looks Like: Success means maintaining a high bar for craft while scaling our design system. You will also be a key visionary, exploring how to evolve the School Organization Dashboard with value-add AI solutions that could fundamentally change how our product works in the long term. Key Projects You’ll Lead: You will lead the "Long Term Vision" for the dashboard with high-level prototyping of AI-driven troubleshooting workflows that help School Organization Admins minimize digital learning disruptions. You’ll also manage the roadmap for our design system evolution. What We’re Looking ForRequired Skills & Experience (Must-Haves):Experience: Significant experience in product design, specifically managing complex information architecture and B2B/Enterprise workflows.Design Systems Ownership: Proven experience maintaining and evolving design systems, including the ability to delegate design tasks and collaborate with Engineering on implementation.Strong User Research Skills: You are comfortable leading discovery, conducting interviews, and translating user insights into architectural changes.AI Tooling & Prototyping: Direct experience using AI tools for design and development, specifically including prototyping with Claude Code. Accessibility Expertise: A deep understanding of WCAG standards and experience remediating accessibility issues in complex web products. Preferred Qualifications (Nice-to-Haves):Previous experience in the EdTech space or building products for school administrators.Previous experience with Cybersecurity productsExperience working in a "quad" model (Product Designer, Product Manager, Engineering Manager, Product Marketing Manager). Salary TransparencyThe range of our base salary cash compensation for this role for candidates living in the United States, besides NYC and San Francisco, CA, is between $149,000-$175,000. For candidates living in NYC and San Francisco, CA, it's between $165,000-$192,000. All final offers are determined using multiple factors, including experience and level of expertise. Inclusion & BelongingClever believes classrooms and our company should be diverse and inclusive. We celebrate actions that build diverse teams, include every voice, and create safe spaces for everyone to bring their authentic selves to work." We need to strip the initial mission paragraph? That's about company; maybe considered boilerplate? It's not a section heading; it's prose before About the Team & Opportunity. Should we keep it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The mission paragraph is substantive about company. It's not a heading; we can keep as

  before sections. However, we need to avoid cookie/navigation/legal/EEO boilerplate. The mission paragraph is not boilerplate; it's okay. But we also have "Clever, a Kahoot! company, has an office in San Francisco, CA, but you can visit us at clever.com anytime." That's also company info; keep. Thus we will have opening paragraph(s) about company. Then

  About the Team & Opportunity

  with its content. Then

  How You’ll Make an Impact

  with its content (maybe break into subpoints? But we can keep as prose with lists for bullet points? The content includes several bullet-like sentences but not explicit list. We could convert to
  • for each distinct responsibility? The instruction: use
    • for any list of duties/requirements/benefits. The content includes multiple duties: oversee birds-eye view, evolve IA, tackle RBAC, strengthen app governance, be primary owner of design system Dewey, lead AI-powered evolution, lead charge in remediating accessibility issues, work with quad, serve as bridge, maintain high bar for craft while scaling design system, be key visionary exploring AI solutions, lead Long Term Vision with AI-driven troubleshooting workflows, manage roadmap for design system evolution. That's a list of duties. So we can make a
      with each duty as
      • . However we need to preserve the exact wording? We should not invent or summarize away detail. We can keep each sentence as list item, preserving the content. Similarly for "Who You’ll Partner With" and "What Success Looks Like" and "Key Projects You’ll Lead" could be separate subheadings? But we only allowed headings from the list; we could keep them as prose within the section. But we could also make sublists. Simplify: Keep the section as prose with paragraphs; but we have lists of duties, we can convert to
        . Let's parse the How You’ll Make an Impact section: "The Problem You’ll Solve: You will oversee the "birds-eye view" of the School Organization Dashboard, evolving a scalable information architecture as we introduce new features. You will tackle foundational challenges like reimagining Role-Based Access Control (RBAC) and strengthening app governance and compliance frameworks. You will also be the primary owner of our design system, Dewey--maintaining, delegating tasks, and leading its AI-powered evolution in close partnership with Engineering. Additionally, you will lead the charge in remediating accessibility issues to ensure our tools are inclusive for all administrators. Who You’ll Partner With: You’ll work in close collaboration with your dedicated quad (Product Designer, Product Manager, Engineering Manager, Product Marketing Manager) and serve as a bridge between various product teams to ensure design consistency across the platform. What Success Looks Like: Success means maintaining a high bar for craft while scaling our design system. You will also be a key visionary, exploring how to evolve the School Organization Dashboard with value-add AI solutions that could fundamentally change how our product works in the long term. Key Projects You’ll Lead: You will lead the "Long Term Vision" for the dashboard with high-level prototyping of AI-driven troubleshooting workflows that help School Organization Admins minimize digital learning disruptions. You’ll also manage the roadmap for our design system evolution." We could treat each bullet as a duty: oversee birds-eye view..., tackle RBAC..., primary owner of design system..., lead charge in remediating accessibility..., work with quad..., serve as bridge..., maintain high bar for craft..., be key visionary exploring AI..., lead Long Term Vision..., manage roadmap... But some are more like partner, success, projects. Might be okay to keep as prose with paragraphs. Given instruction: "Use
        • for any list of duties/requirements/benefits". The duties are enumerated in the Problem You’ll Solve and Key Projects You’ll Lead. The other parts are not strictly lists. We could create a
          for duties under Problem You’ll Solve and Key Projects You’ll Lead combined. But to be safe, we can keep the section as paragraphs (

          ) and not use lists unless we have explicit list items. However the instruction says to use

          • for any list of duties/requirements/benefits. If we don't use list, we might be violating if there is a list. The content does contain a list of duties (multiple sentences). It's ambiguous. I'll decide to convert the duties into a
            • list for clarity. Similarly for Requirements (Must-Haves) we have a list: Experience..., Design Systems Ownership..., Strong User Research Skills..., AI Tooling & Prototyping..., Accessibility Expertise:. That's clearly a list; we should use
              • . Preferred Qualifications (Nice-to-Haves) also list: Previous experience in EdTech..., Previous experience with Cybersecurity..., Experience working in a "quad" model... Thus we will have sections: - About the Team & Opportunity (as

                ) with paragraph(s) (maybe two paragraphs: company intro and team description). Actually we have company intro before About the Team & Opportunity; we could keep that as opening

                s. - How You’ll Make an Impact (

                ) with a

                • list of duties/responsibilities. - Requirements (

                  ) with

                  • list of must-haves. - Qualifications (

                    ) with

                    • list of nice-to-haves. - Pay (

                      ) with paragraph(s