Advanced Specialist, Experience Design
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do not repeat job title as heading. Do not put Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. Preserve all substantive info; do not invent or summarize away detail. Remove boilerplate like cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Key sections:
- Position Summary (intro) -> could be "About the role" maybe.
- What You’ll Do: includes Research & Insight, Design & Prototyping, Collaboration & Strategic Influence, Mentorship & Team Contribution. That's responsibilities.
- What We’re Looking For: includes Experience & Education, Skills & Competencies, Preferred Qualifications.
- Compensation: salary range $105,000 – $135,000, eligible for annual incentive program. Benefits: "Information on benefits can be found here." Not specific benefits listed. So we cannot create Benefits section unless posting actually states them. It only says "Information on benefits can be found here." That's not specific content; we should not create Benefits section because it's not substantive. So we omit Benefits.
- Pay: we have salary range. So we can create Pay section with that info.
- Schedule: The posting mentions "This is a primarily remote role, with occasional travel for in-person collaboration". Also later: "Schedule: FULL_TIME Workplace Type: Remote". So we have schedule info: full-time, primarily remote with occasional travel. So we can create Schedule section.
- Qualifications: maybe combine Experience & Education and Preferred Qualifications? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content.
We have:
- About the role: Position Summary paragraph.
- Responsibilities: What You’ll Do (with subparts). Could be a list.
- Requirements: maybe Experience & Education (minimum requirements). Could be a list.
- Skills: Skills & Competencies (maybe also Preferred Qualifications). Could be a list.
- Pay: salary range.
- Schedule: full-time, remote, occasional travel.
We should not create Requirements if content is vague? We have Experience & Education: 7+ years experience, portfolio, etc. That's specific. So we can include Requirements.
Qualifications: maybe we could treat Preferred Qualifications as Qualifications? But we already have Requirements for mandatory; Qualifications could be preferred. However instruction says use headings for sections like ... Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid having both Requirements and Qualifications. We'll include both if we have content.
We have Skills & Competencies (list). That's Skills.
Preferred Qualifications: list of items (K-12 education sector, AI-assisted design tooling, mixed-methods research, pedagogy, LMS). That could go under Qualifications (preferred). Or we could merge with Skills. But better to separate: Requirements (mandatory experience/education), Qualifications (preferred), Skills (competencies). However there is overlap; but we can follow.
We must not create sections with filler text. Ensure each heading has substantive content.
Now we need to strip boilerplate: EEO, equal opportunity, etc. Also remove "Applications will be accepted through 18th September 2026." That's application instruction; remove. Also "Apply today and imagine the impact you can make." Remove. Also "Who we are: At Pearson..." etc. Remove. Also "Job: Design Job Family: PRODUCT Organization: Virtual Learning Schedule: FULL_TIME Workplace Type: Remote Req ID: 25597 #location" - we can fold minor metadata into short p or drop. We'll incorporate schedule info already; we can drop Job ID etc.
Now produce HTML.
Structure:
About the role
Pearson Virtual Schools is seeking a Senior UX Designer to lead the design of AI-powered learning experiences for students, teachers, and families across our K–12 virtual school platforms. In this role, you will work end-to-end, from framing design problems and contributing to user research through prototyping and validating high-fidelity experiences that reach hundreds of thousands of learners. You will partner closely with Product Management, Engineering, Data Analytics, and UX Research to translate learner insights and business goals into intuitive, accessible, and engaging product experiences, including interfaces that make AI-driven features legible and trustworthy for students and educators. This is a role for someone who moves fluidly between ambiguity and precision: contributing to the research needed to frame a problem clearly, then execute with craft and rigor to solve it well. You will influence product strategy and roadmap decisions, contribute to our shared design system, and raise the quality bar for the team around you. We are looking for candidates who are excited by hard questions about how people learn, motivated by improving learning outcomes, and ready to design for a generation of learners whose expectations of digital experiences are higher than ever. This is a primarily remote role, with occasional travel for in-person collaboration with colleagues and customers.
That covers About the role.
Now Responsibilities: we can list bullet points summarizing each major area: Research & Insight, Design & Prototyping, Collaboration & Strategic Influence, Mentorship & Team Contribution. Each bullet can contain subpoints? We can keep as - with maybe
inside? But spec says use
- for any list of duties/requirements/benefits. So we can have each duty as
- containing the description (maybe multiple sentences). That's fine.
We'll produce:
Responsibilities
- Conduct usability tests, structured interviews, and contextual observations to validate design decisions and uncover user needs; partner with Product and UX Research to contribute to study design, synthesize findings, and translate insights into clear design direction; interpret qualitative and quantitative signals (product analytics, usability results, A/B test outcomes) to inform and validate design decisions; identify usability and engagement gaps through prototype testing and ongoing user feedback, resolving issues before production; stay current with evaluation methods and UX best practices, sharing relevant techniques that strengthen the team’s design process.
- Own end-to-end product design from user flows and rough concepts through wireframes, high-fidelity designs, and developer-ready specifications, driving an iterative process from concept to final handoff; design AI-powered experiences including conversational interfaces, adaptive learning flows, generative content surfaces, and intelligent recommendation features, making complex AI/ML outputs intuitive and trustworthy for K–12 users; think in systems: design for all states, edge cases, error conditions, and empty states; deliver responsive designs across web and mobile; use AI tools as design accelerants; define and maintain interaction patterns, UX standards, and component contributions for the shared design system; ensure accessibility as a design foundation meeting WCAG 2.2 standards from the start.
- Partner with Product Management, Engineering, and Data Analytics to shape product direction, influence roadmap prioritization, and support investment decisions with design rationale grounded in user insight; communicate research findings and design decisions in compelling, story‑driven ways tailored for engineers, product leadership, and business stakeholders; balance user needs, business goals, and delivery constraints to advocate for decisions that move the product forward without compromising the learner experience; champion underserved user groups (students with disabilities, English language learners, students in under‑resourced settings) as an active voice in every product conversation.
- Serve as a mentor across the design team, sharing expertise in design craft, research methods, and decision‑making to support team growth and quality; contribute to team practices, design critique, workshop facilitation, shared documentation, and workflow improvements that raise efficiency and quality; model a standard of curiosity, rigor, and craft that sets the bar others aspire to reach.
Now Requirements (Experience & Education):
Requirements
- 7+ years of experience in UX design or a closely related discipline, with a portfolio demonstrating end‑to‑end ownership of complex, shipped products and measurable impact on user outcomes.
... etc.
We need to include all bullet points from Experience & Education:
- 7+ years of experience in UX design or a closely related discipline, with a portfolio demonstrating end-to-end ownership of complex, shipped products and measurable impact on user outcomes.
- Experience conducting usability tests and mixed-method research activities, gathering insights through interviews, contextual inquiry, and usability studies, and translating findings into actionable design decisions.
- Experience designing for AI-powered product features, such as conversational interfaces, adaptive systems, generative content surfaces, or ML-driven recommendations.
- A strong portfolio and track record matter most to us.
- A Bachelor’s degree in HCI, interaction design, cognitive science, or a related field is welcomed, but candidates from all educational backgrounds, including bootcamp graduates and self-taught designers, are equally encouraged to apply.
- Experience working in Agile or Lean UX environments, collaborating closely with engineering and product throughout the delivery cycle.
We'll put each as - .
Now Qualifications (Preferred Qualifications):
Qualifications
- Experience in the K–12 education sector, with a working understanding of the needs of students, families, and educators.
- Familiarity with AI-assisted design and research tooling, including prompt engineering for design workflows.
- Background in mixed-methods research, including behavioral analytics and quantitative study design.
- Understanding of pedagogy and instructional design principles, and how they inform the design of effective K–12 learning experiences.
- Familiarity with learning management systems (LMS) and how students and educators interact with them in a virtual school environment.
.
Now Skills (Skills & Competencies):
Skills
- Expert proficiency in Figma for design and prototyping; familiarity with research and testing tools such as User Testing or similar.
- AI literacy, comfortable applying AI tools to design workflows and designing for AI-powered product experiences, including generative and adaptive interfaces.
- Data fluency, comfortable working with product analytics platforms, interpreting A/B test results, and using quantitative signal to inform and validate design decisions.
- Strong information architecture, user journey mapping, and interaction design skills, including interaction patterns, micro-interactions, and transitions, across web and mobile platforms.
- Solid grasp of visual design fundamentals, including typography, color theory, and visual hierarchy, to create interfaces that are polished, legible, and build user trust.
- Deep understanding of accessibility standards (WCAG 2.2 and Section 508) and inclusive design principles, with experience embedding both into the design process from the start, particularly for diverse and underserved learner populations.
- Experience contributing to or maintaining a shared design system, with an understanding of component-level design consistency at scale.
- Excellent communication and storytelling skills, able to present design rationale and research findings persuasively to audiences ranging from engineers to product leadership.
- Demonstrated ability to navigate competing priorities, align cross-functional partners, and influence roadmap decisions with design rationale grounded in user insight.
Now Pay:
Pay
The full-time salary range for this role is $105,000 – $135,000. This position is eligible to participate in an annual incentive program.
Now Schedule:
Schedule
Full‑time position; primarily remote with occasional travel for in‑person collaboration with colleagues and customers
for prose. Do not repeat job title as heading. Do not put Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. Preserve all substantive info; do not invent or summarize away detail. Remove boilerplate like cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Key sections: - Position Summary (intro) -> could be "About the role" maybe. - What You’ll Do: includes Research & Insight, Design & Prototyping, Collaboration & Strategic Influence, Mentorship & Team Contribution. That's responsibilities. - What We’re Looking For: includes Experience & Education, Skills & Competencies, Preferred Qualifications. - Compensation: salary range $105,000 – $135,000, eligible for annual incentive program. Benefits: "Information on benefits can be found here." Not specific benefits listed. So we cannot create Benefits section unless posting actually states them. It only says "Information on benefits can be found here." That's not specific content; we should not create Benefits section because it's not substantive. So we omit Benefits. - Pay: we have salary range. So we can create Pay section with that info. - Schedule: The posting mentions "This is a primarily remote role, with occasional travel for in-person collaboration". Also later: "Schedule: FULL_TIME Workplace Type: Remote". So we have schedule info: full-time, primarily remote with occasional travel. So we can create Schedule section. - Qualifications: maybe combine Experience & Education and Preferred Qualifications? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have: - About the role: Position Summary paragraph. - Responsibilities: What You’ll Do (with subparts). Could be a list. - Requirements: maybe Experience & Education (minimum requirements). Could be a list. - Skills: Skills & Competencies (maybe also Preferred Qualifications). Could be a list. - Pay: salary range. - Schedule: full-time, remote, occasional travel. We should not create Requirements if content is vague? We have Experience & Education: 7+ years experience, portfolio, etc. That's specific. So we can include Requirements. Qualifications: maybe we could treat Preferred Qualifications as Qualifications? But we already have Requirements for mandatory; Qualifications could be preferred. However instruction says use headings for sections like ... Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid having both Requirements and Qualifications. We'll include both if we have content. We have Skills & Competencies (list). That's Skills. Preferred Qualifications: list of items (K-12 education sector, AI-assisted design tooling, mixed-methods research, pedagogy, LMS). That could go under Qualifications (preferred). Or we could merge with Skills. But better to separate: Requirements (mandatory experience/education), Qualifications (preferred), Skills (competencies). However there is overlap; but we can follow. We must not create sections with filler text. Ensure each heading has substantive content. Now we need to strip boilerplate: EEO, equal opportunity, etc. Also remove "Applications will be accepted through 18th September 2026." That's application instruction; remove. Also "Apply today and imagine the impact you can make." Remove. Also "Who we are: At Pearson..." etc. Remove. Also "Job: Design Job Family: PRODUCT Organization: Virtual Learning Schedule: FULL_TIME Workplace Type: Remote Req ID: 25597 #location" - we can fold minor metadata into short p or drop. We'll incorporate schedule info already; we can drop Job ID etc. Now produce HTML. Structure:
About the role
Pearson Virtual Schools is seeking a Senior UX Designer to lead the design of AI-powered learning experiences for students, teachers, and families across our K–12 virtual school platforms. In this role, you will work end-to-end, from framing design problems and contributing to user research through prototyping and validating high-fidelity experiences that reach hundreds of thousands of learners. You will partner closely with Product Management, Engineering, Data Analytics, and UX Research to translate learner insights and business goals into intuitive, accessible, and engaging product experiences, including interfaces that make AI-driven features legible and trustworthy for students and educators. This is a role for someone who moves fluidly between ambiguity and precision: contributing to the research needed to frame a problem clearly, then execute with craft and rigor to solve it well. You will influence product strategy and roadmap decisions, contribute to our shared design system, and raise the quality bar for the team around you. We are looking for candidates who are excited by hard questions about how people learn, motivated by improving learning outcomes, and ready to design for a generation of learners whose expectations of digital experiences are higher than ever. This is a primarily remote role, with occasional travel for in-person collaboration with colleagues and customers.
That covers About the role. Now Responsibilities: we can list bullet points summarizing each major area: Research & Insight, Design & Prototyping, Collaboration & Strategic Influence, Mentorship & Team Contribution. Each bullet can contain subpoints? We can keep as- with maybe
inside? But spec says use
- for any list of duties/requirements/benefits. So we can have each duty as
- containing the description (maybe multiple sentences). That's fine.
We'll produce:
Responsibilities
- Conduct usability tests, structured interviews, and contextual observations to validate design decisions and uncover user needs; partner with Product and UX Research to contribute to study design, synthesize findings, and translate insights into clear design direction; interpret qualitative and quantitative signals (product analytics, usability results, A/B test outcomes) to inform and validate design decisions; identify usability and engagement gaps through prototype testing and ongoing user feedback, resolving issues before production; stay current with evaluation methods and UX best practices, sharing relevant techniques that strengthen the team’s design process.
- Own end-to-end product design from user flows and rough concepts through wireframes, high-fidelity designs, and developer-ready specifications, driving an iterative process from concept to final handoff; design AI-powered experiences including conversational interfaces, adaptive learning flows, generative content surfaces, and intelligent recommendation features, making complex AI/ML outputs intuitive and trustworthy for K–12 users; think in systems: design for all states, edge cases, error conditions, and empty states; deliver responsive designs across web and mobile; use AI tools as design accelerants; define and maintain interaction patterns, UX standards, and component contributions for the shared design system; ensure accessibility as a design foundation meeting WCAG 2.2 standards from the start.
- Partner with Product Management, Engineering, and Data Analytics to shape product direction, influence roadmap prioritization, and support investment decisions with design rationale grounded in user insight; communicate research findings and design decisions in compelling, story‑driven ways tailored for engineers, product leadership, and business stakeholders; balance user needs, business goals, and delivery constraints to advocate for decisions that move the product forward without compromising the learner experience; champion underserved user groups (students with disabilities, English language learners, students in under‑resourced settings) as an active voice in every product conversation.
- Serve as a mentor across the design team, sharing expertise in design craft, research methods, and decision‑making to support team growth and quality; contribute to team practices, design critique, workshop facilitation, shared documentation, and workflow improvements that raise efficiency and quality; model a standard of curiosity, rigor, and craft that sets the bar others aspire to reach.
Requirements
- 7+ years of experience in UX design or a closely related discipline, with a portfolio demonstrating end‑to‑end ownership of complex, shipped products and measurable impact on user outcomes.
... etc.
We need to include all bullet points from Experience & Education:
- 7+ years of experience in UX design or a closely related discipline, with a portfolio demonstrating end-to-end ownership of complex, shipped products and measurable impact on user outcomes.
- Experience conducting usability tests and mixed-method research activities, gathering insights through interviews, contextual inquiry, and usability studies, and translating findings into actionable design decisions.
- Experience designing for AI-powered product features, such as conversational interfaces, adaptive systems, generative content surfaces, or ML-driven recommendations.
- A strong portfolio and track record matter most to us.
- A Bachelor’s degree in HCI, interaction design, cognitive science, or a related field is welcomed, but candidates from all educational backgrounds, including bootcamp graduates and self-taught designers, are equally encouraged to apply.
- Experience working in Agile or Lean UX environments, collaborating closely with engineering and product throughout the delivery cycle.
We'll put each as - .
Now Qualifications (Preferred Qualifications):
Qualifications
- Experience in the K–12 education sector, with a working understanding of the needs of students, families, and educators.
- Familiarity with AI-assisted design and research tooling, including prompt engineering for design workflows.
- Background in mixed-methods research, including behavioral analytics and quantitative study design.
- Understanding of pedagogy and instructional design principles, and how they inform the design of effective K–12 learning experiences.
- Familiarity with learning management systems (LMS) and how students and educators interact with them in a virtual school environment. . Now Skills (Skills & Competencies):
- Expert proficiency in Figma for design and prototyping; familiarity with research and testing tools such as User Testing or similar.
- AI literacy, comfortable applying AI tools to design workflows and designing for AI-powered product experiences, including generative and adaptive interfaces.
- Data fluency, comfortable working with product analytics platforms, interpreting A/B test results, and using quantitative signal to inform and validate design decisions.
- Strong information architecture, user journey mapping, and interaction design skills, including interaction patterns, micro-interactions, and transitions, across web and mobile platforms.
- Solid grasp of visual design fundamentals, including typography, color theory, and visual hierarchy, to create interfaces that are polished, legible, and build user trust.
- Deep understanding of accessibility standards (WCAG 2.2 and Section 508) and inclusive design principles, with experience embedding both into the design process from the start, particularly for diverse and underserved learner populations.
- Experience contributing to or maintaining a shared design system, with an understanding of component-level design consistency at scale.
- Excellent communication and storytelling skills, able to present design rationale and research findings persuasively to audiences ranging from engineers to product leadership.
- Demonstrated ability to navigate competing priorities, align cross-functional partners, and influence roadmap decisions with design rationale grounded in user insight.
Skills
Pay
The full-time salary range for this role is $105,000 – $135,000. This position is eligible to participate in an annual incentive program.
Now Schedule:Schedule
Full‑time position; primarily remote with occasional travel for in‑person collaboration with colleagues and customers