Lead Product Design, Design Systems & Experience

We need to output HTML fragment with sections: About the role? The posting includes description paragraphs. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First paragraph: "At Brightspeed, we are reimagining..." That's about the company and role overview. Could be "About the role". We'll put that in

. Then "Job Description The Lead Product Designer, Design Systems & Experience Quality is an advanced individual contributor ..." That's also role description; could be part of About the role. We need to separate sections: Responsibilities: list of duties from "Key Responsibilities" bullet list. We'll extract each bullet. Qualifications: Education & Experience bullet list. Skills & Competencies: bullet list. Preferred Qualifications: maybe part of Qualifications? Could be separate but we can include under Qualifications or maybe separate "Preferred Qualifications" but not a standard heading; we can include under Qualifications as extra bullet. Benefits: The posting mentions "We Offer Competitive Compensation And Comprehensive Benefits." then details: competitive medical, dental, vision, life insurance; employee assistance program; 401K plan with company match; voluntary benefits; inclusion etc. Also "We aspire to contemporary ways of working." etc. So we have benefits content. Pay: Not specified explicitly; only "Competitive Compensation". That's vague; we should not create Pay section unless posting actually states them. It says "Competitive Compensation" but not specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits, so we can include Benefits. Pay: only "Competitive Compensation" is vague; maybe we should not create Pay section because it's not specific. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits, so Benefits ok. Pay: not specific; we should omit. Schedule: Not specified; we have mention of remote/hybrid/office/field-based, occasional additional hours. That's schedule info? Could be considered schedule. The posting says: "We also invest in technology that enables our entire team to stay connected." and "At Brightspeed, we have roles that are designated as remote, hybrid, office or field-based, depending on the position, business needs and individual circumstances." Also "Occasional additional hours may be required to support project deadlines". That's schedule info. Should we create Schedule section? It does state schedule info (remote/hybrid etc). So we can include Schedule. But we need to avoid filler like "not specified". We have specifics. Thus sections: About the role, Responsibilities, Qualifications (including Education & Experience and Preferred Qualifications maybe), Skills, Benefits, Schedule. We need to use

for each section heading. Inside each section, use

for prose,

• for lists. We must not repeat job title as heading. Not include Job ID. We must preserve all substantive information; do not invent or summarize away detail. We need to include all details from the posting, but we can condense into prose/lists while preserving meaning. Must not omit substantive info. Let's extract. About the role: combine first paragraph and job description paragraph. First paragraph: "At Brightspeed, we are reimagining how people live, work, play and connect by providing fast, reliable internet connections and an awesome customer experience in twenty states throughout the Midwest and South. Backed by funds managed by Apollo Global Management, our vision is to accelerate the upgrade of copper to fiber optic technologies, bringing faster and more reliable internet service to many rural markets traditionally underserved by broadband providers, while delivering best-in-class customer experience. Be a part of the team that will make this vision a reality….designing and building a world class fiber network and creating a customer experience second to none. Check us out on the web!" Second paragraph (Job Description): "The Lead Product Designer, Design Systems & Experience Quality is an advanced individual contributor responsible for creating and maintaining the reusable components, interaction patterns, standards, documentation, and reference experiences that support Brightspeed’s digital products. This role translates approved product and experience strategies into scalable design solutions that improve consistency, accessibility, implementation quality, and delivery efficiency across Brightspeed’s digital ecosystem, including AI-supported and agent-based experiences." We'll combine into a couple paragraphs. Responsibilities: list from "Key Responsibilities". Let's extract each bullet: - Design, document, and maintain reusable components, interaction patterns, templates, and standards that support consistent and scalable digital experiences across Brightspeed. - Define component anatomy, properties, variants, states, responsive behavior, accessibility requirements, content guidance, and intended usage. - Maintain high-quality Figma libraries, component documentation, contribution standards, reference designs, prototypes, and other supporting design-system artifacts. - Identify gaps, duplication, inconsistencies, and implementation drift across customer experiences and recommend scalable design-system solutions. - Create practical standards for interaction behavior, visual hierarchy, responsive design, accessibility, content presentation, and design annotations. - Design and validate complex components, interaction models, prototypes, and reference flows that require advanced systems thinking and technical collaboration. - Develop prototypes and reference experiences that demonstrate how approved components and interaction patterns should work together across complex customer journeys. - Review design work for consistency with Brightspeed’s design system, accessibility standards, responsive requirements, and documented interaction patterns. - Support alignment between Figma components, design tokens, coded components, and front-end documentation in partnership with design and technology teams. - Develop reusable components, interaction patterns, behavioral documentation, reference prototypes, and quality criteria for AI-enabled, conversational, and agent-based experiences. - Establish AI experience patterns that clearly communicate when customers are interacting with AI, what the system can do, what information it uses, when customer confirmation is required, and how escalation or human handoff occurs. - Develop reusable patterns for AI feedback, confirmation, error handling, escalation, failure states, and human handoff to promote consistent, accessible, and understandable customer experiences. - Provide craft-focused guidance on design-system usage, interaction patterns, accessibility, AI behavior, responsive design, and implementation quality. - Facilitate design-system working sessions and workshops to improve adoption, consistency, and effective use of shared standards and components. - Partner with design leadership to help prioritize design-system investments based on customer impact, delivery efficiency, adoption, and business needs, while operating within product strategy and priorities established by design and product leadership. - Lead through specialized expertise and influence across cross-functional teams without direct people-management or performance-management responsibilities. - May perform other duties as assigned. We'll keep all. Qualifications: Education & Experience bullet list: - Bachelor’s degree in Design, User Experience (UX), Human-Computer Interaction (HCI), Human Factors, Visual Communication, Product Design, or a related field, or equivalent practical experience. - Eight or more years of experience in product design, interaction design, design systems, UX/UI design, digital product design, or a related discipline. - Demonstrated experience designing, building, or maintaining scalable design systems, reusable components, interaction patterns, and supporting documentation. - Practical experience designing or prototyping AI-enabled experiences, including AI interaction patterns, agent workflows, prototypes, or reusable design solutions. - Portfolio demonstrating component architecture, reusable interaction patterns, accessibility, responsive design, systems thinking, documentation, and implementation quality. Preferred Qualifications bullet list (maybe include under Qualifications as separate subsection? Could be separate heading but not standard; we can include under Qualifications as additional bullet list labeled "Preferred Qualifications". But we must not create new headings not in list; but we can embed as prose or as a sublist under Qualifications. The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. We can put Preferred Qualifications inside Qualifications section as a

  or

  with a note. That's okay. Skills & Competencies bullet list: - Advanced knowledge of design systems, component architecture, interaction design, responsive design, accessibility, prototyping, and digital experience quality. - Strong proficiency with Figma and experience creating and maintaining component libraries, design-system documentation, prototypes, and reference designs. - Understanding of how design tokens, coded components, and front-end implementation relate to design-system standards and Figma components. - Understanding of AI-enabled experience considerations, including model behavior, prompts, system instructions, tool use, data access, confidence, latency, failure states, privacy, security, and human oversight. - Ability to translate established product and experience strategies into scalable design patterns, standards, and implementation guidance. - Strong systems thinking and ability to identify patterns, inconsistencies, dependencies, and opportunities for reuse across complex digital experiences. - Strong collaboration, communication, facilitation, and influencing skills, with the ability to provide specialized design guidance across product, design, and technology teams. - Ability to lead through expertise and influence while working within product strategy, priorities, and design direction established by product and design leadership. - English proficiency required; bilingual Spanish skills are a plus. Benefits: from "We Offer Competitive Compensation And Comprehensive Benefits." and following: - Competitive medical, dental, vision, and life insurance - Employee assistance program - 401K plan with company match - Host of voluntary benefits - Inclusion and belonging are at the center of our grounding belief in Being Real. When we bring our authentic selves to work, everyone is better as a result. A diverse team helps us be fierce advocates for more accessible, inclusive and high-quality internet, because we believe doing so promotes equity in the communities we serve. - Brightspeed is an Equal Opportunity Employer that is committed to inclusion of all qualified individuals, including individuals with a disability/veterans. If you require reasonable accommodation to complete a job application or to otherwise participate in the hiring process, please contact taaccommodationrequests@brightspeed.com to initiate the accommodations process. For all applicants, please take a moment to review our Privacy Notices: Brightspeed’s Privacy Notice for California Residents Brightspeed’s Privacy Notice But we need to remove EEO/equal-opportunity boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove EEO statement and accommodation request and privacy notices? Those are legal/EEO boilerplate. So we should strip those. Keep benefits: medical, dental, vision, life insurance; employee assistance program; 401K plan with company match; voluntary benefits; inclusion and belonging statement maybe okay as it's part of culture not EEO? The inclusion statement is about diversity; might be considered part of benefits/culture. We'll keep it but remove the EEO employer line and accommodation request and privacy notices. Thus Benefits section content: competitive medical, dental, vision, life insurance; employee assistance program; 401K plan with company match; host of voluntary benefits; inclusion and belonging are at the center of our grounding belief in Being Real... etc. Schedule: from "Physical Demands & Work Conditions" and hybrid info. We have: - Work is primarily performed indoors from a home or company office, with regular use of a computer and standard office productivity tools. - Ability to perform typical office-based activities for extended periods, including computer-based design, documentation, and virtual collaboration. - Occasional additional hours may be required to support project deadlines, business priorities, or critical deliverables. - At Brightspeed, we have roles that are designated as remote, hybrid, office or field-based, depending on the position, business needs and individual circumstances. - We also invest in technology that enables our entire team to stay connected. We can put these as a list or prose. Now we need to output only HTML fragment. Let's craft. We'll start with

  About the role

  then

  ... maybe two paragraphs. Then

  Responsibilities

  with each
  • . Then

    Qualifications

    we can have

    Education & Experience: