Advanced Specialist, Experience Design
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, legal, etc. Also remove application instructions, cookie/navigation, duplicated lines.
We need to decide sections: About the role (maybe from Position Summary). Responsibilities (What You’ll Do). Requirements (What We’re Looking For). Qualifications maybe combine? But we can follow typical headings: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. However we should only include sections when posting has real specific content.
We have Position Summary -> could be About the role.
What You’ll Do -> Responsibilities (with sub-sections maybe we can keep as paragraphs or lists). The content includes bullet-like sentences but not actual bullet list markers. We could convert each duty into
- under
. But the instruction: Use - for any list of duties/requirements/benefits. So we need to identify lists. The text includes sentences separated by periods; we could treat each sentence as a list item? Might be overkill but we can group under headings.
Better: For each major duty category (Research & Insight, Design & Prototyping, Collaboration & Strategic Influence, Mentorship & Team Contribution) we could make a
? But only allowed for section headings. We could keep those as not allowed? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow that pattern. Probably we should only use those headings. So we can have sections: About the role, Responsibilities, Requirements, Skills, Pay, Schedule. Within Responsibilities we can have - items covering the duties.
Similarly Requirements could include Experience & Education, Skills & Competencies, Preferred Qualifications. But we might split into Requirements (experience/education) and Skills (competencies). The instruction says we can have Qualifications, Skills sections. We'll decide: About the role, Responsibilities, Requirements (Experience & Education), Skills (Skills & Competencies + Preferred Qualifications), Pay, Schedule.
We must not create Benefits section because no specific benefits listed.
We must not include placeholder like "commensurate with experience". Not present.
We need to preserve all substantive information: include salary range, full-time, remote, application deadline date? The posting includes "Applications will be accepted through 18th September 2026." That's substantive; we could include in Schedule or maybe a separate section? Could put in Schedule or maybe a note in About the role? Probably include in Schedule as additional info: "Applications accepted through 18th September 2026." But schedule section is about work schedule; maybe better to put in About the role? However we have no other place. Could add a short
after Schedule section? But we must not invent sections. Could add a
under Schedule? Might be okay.
But the instruction: "Prefer a few substantive sections over many thin ones." So we could add a section "Application Timeline" but not in list of allowed headings. Better to incorporate into About the role or Schedule as a paragraph.
Let's include in About the role: mention it's primarily remote, occasional travel, full-time, applications accepted through 18 Sep 2026.
Now craft HTML.
We'll start with maybe not needed; just output HTML fragment.
We'll do:
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. Applications will be accepted through 18th September 2026.
Then Responsibilities:
Responsibilities
- Research & Insight: Conduct usability tests, structured interviews, and contextual observations to validate design decisions and uncover user needs throughout the design process. 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, including product analytics, usability results, and 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 they reach production. Stay current with evaluation methods and UX best practices, sharing relevant techniques that strengthen the team’s design process.
- Design & Prototyping: 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 first concept to final handoff. Design AI-powered experiences including conversational interfaces, adaptive learning flows, generative content surfaces, and intelligent recommendation features, making complex AI and ML outputs intuitive and trustworthy for K–12 users. Think in systems: design for all states, edge cases, error conditions, and empty states, not just the happy path, so every scenario a learner encounters has an intentional, considered response. Deliver responsive designs across web and mobile, ensuring layouts and interactions hold up across devices, breakpoints, and screen sizes. Use AI tools as design accelerants, including AI design tools, to iterate on more concepts faster and bring ideas to life earlier in the process. Define and maintain interaction patterns, UX standards, and component contributions for the shared design system, ensuring consistency and quality across products. Treat accessibility as a design foundation: ensure all work meets WCAG 2.2 standards from the start, not as a late-stage check.
- Collaboration & Strategic Influence: 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, tailoring the narrative for audiences ranging from engineers to product leadership to 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, including students with disabilities, English language learners, and students in under-resourced settings, as an active voice in every product conversation.
- Mentorship & Team Contribution: Serve as a mentor across the design team, sharing expertise in design craft, research methods, and decision-making to support the growth and quality of the team. Contribute to team practices, design critique, workshop facilitation, shared documentation, and workflow improvements, that raise the efficiency and quality of the broader team. Model a standard of curiosity, rigor, and craft that sets the bar others aspire to reach.
Then 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.
- 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.
Then Skills:
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.
Preferred Qualifications could be included under Skills as extra items, but we already have many. Could add a separate section "Preferred Qualifications". But we already have Skills section; we could add another Preferred Qualifications
with list. The instruction allows Qualifications section; we have Requirements (which is like qualifications). Could add Preferred Qualifications as separate section. Let's do that.
Preferred 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.
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, legal, etc. Also remove application instructions, cookie/navigation, duplicated lines. We need to decide sections: About the role (maybe from Position Summary). Responsibilities (What You’ll Do). Requirements (What We’re Looking For). Qualifications maybe combine? But we can follow typical headings: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. However we should only include sections when posting has real specific content. We have Position Summary -> could be About the role. What You’ll Do -> Responsibilities (with sub-sections maybe we can keep as paragraphs or lists). The content includes bullet-like sentences but not actual bullet list markers. We could convert each duty into
- . But the instruction: Use
- for any list of duties/requirements/benefits. So we need to identify lists. The text includes sentences separated by periods; we could treat each sentence as a list item? Might be overkill but we can group under headings.
Better: For each major duty category (Research & Insight, Design & Prototyping, Collaboration & Strategic Influence, Mentorship & Team Contribution) we could make a
? But only
allowed for section headings. We could keep those as
not allowed? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow that pattern. Probably we should only use those headings. So we can have sections: About the role, Responsibilities, Requirements, Skills, Pay, Schedule. Within Responsibilities we can have
- items covering the duties.
Similarly Requirements could include Experience & Education, Skills & Competencies, Preferred Qualifications. But we might split into Requirements (experience/education) and Skills (competencies). The instruction says we can have Qualifications, Skills sections. We'll decide: About the role, Responsibilities, Requirements (Experience & Education), Skills (Skills & Competencies + Preferred Qualifications), Pay, Schedule.
We must not create Benefits section because no specific benefits listed.
We must not include placeholder like "commensurate with experience". Not present.
We need to preserve all substantive information: include salary range, full-time, remote, application deadline date? The posting includes "Applications will be accepted through 18th September 2026." That's substantive; we could include in Schedule or maybe a separate section? Could put in Schedule or maybe a note in About the role? Probably include in Schedule as additional info: "Applications accepted through 18th September 2026." But schedule section is about work schedule; maybe better to put in About the role? However we have no other place. Could add a short
after Schedule section? But we must not invent sections. Could add a
under Schedule? Might be okay. But the instruction: "Prefer a few substantive sections over many thin ones." So we could add a section "Application Timeline" but not in list of allowed headings. Better to incorporate into About the role or Schedule as a paragraph. Let's include in About the role: mention it's primarily remote, occasional travel, full-time, applications accepted through 18 Sep 2026. Now craft HTML. We'll start with maybe not needed; just output HTML fragment. We'll do:
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. Applications will be accepted through 18th September 2026.
Then Responsibilities:Responsibilities
- Research & Insight: Conduct usability tests, structured interviews, and contextual observations to validate design decisions and uncover user needs throughout the design process. 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, including product analytics, usability results, and 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 they reach production. Stay current with evaluation methods and UX best practices, sharing relevant techniques that strengthen the team’s design process.
- Design & Prototyping: 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 first concept to final handoff. Design AI-powered experiences including conversational interfaces, adaptive learning flows, generative content surfaces, and intelligent recommendation features, making complex AI and ML outputs intuitive and trustworthy for K–12 users. Think in systems: design for all states, edge cases, error conditions, and empty states, not just the happy path, so every scenario a learner encounters has an intentional, considered response. Deliver responsive designs across web and mobile, ensuring layouts and interactions hold up across devices, breakpoints, and screen sizes. Use AI tools as design accelerants, including AI design tools, to iterate on more concepts faster and bring ideas to life earlier in the process. Define and maintain interaction patterns, UX standards, and component contributions for the shared design system, ensuring consistency and quality across products. Treat accessibility as a design foundation: ensure all work meets WCAG 2.2 standards from the start, not as a late-stage check.
- Collaboration & Strategic Influence: 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, tailoring the narrative for audiences ranging from engineers to product leadership to 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, including students with disabilities, English language learners, and students in under-resourced settings, as an active voice in every product conversation.
- Mentorship & Team Contribution: Serve as a mentor across the design team, sharing expertise in design craft, research methods, and decision-making to support the growth and quality of the team. Contribute to team practices, design critique, workshop facilitation, shared documentation, and workflow improvements, that raise the efficiency and quality of the broader team. 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.
- 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.
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.
Preferred Qualifications
with list. The instruction allows Qualifications section; we have Requirements (which is like qualifications). Could add Preferred Qualifications as separate section. Let's do that.Preferred 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.
- items covering the duties.
Similarly Requirements could include Experience & Education, Skills & Competencies, Preferred Qualifications. But we might split into Requirements (experience/education) and Skills (competencies). The instruction says we can have Qualifications, Skills sections. We'll decide: About the role, Responsibilities, Requirements (Experience & Education), Skills (Skills & Competencies + Preferred Qualifications), Pay, Schedule.
We must not create Benefits section because no specific benefits listed.
We must not include placeholder like "commensurate with experience". Not present.
We need to preserve all substantive information: include salary range, full-time, remote, application deadline date? The posting includes "Applications will be accepted through 18th September 2026." That's substantive; we could include in Schedule or maybe a separate section? Could put in Schedule or maybe a note in About the role? Probably include in Schedule as additional info: "Applications accepted through 18th September 2026." But schedule section is about work schedule; maybe better to put in About the role? However we have no other place. Could add a short