Advanced Specialist, Experience Design
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Sections:
- About the role: The Position Summary paragraph(s) before "What You’ll Do". That includes description of role, remote, occasional travel. So we can put that under About the role.
- Responsibilities: The "What You’ll Do" section with subparts: Research & Insight, Design & Prototyping, Collaboration & Strategic Influence, Mentorship & Team Contribution. Should we break into subheadings? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only those top-level headings. Within Responsibilities we can use - for list items. Could also include paragraphs.
We need to preserve all substantive info. So we need to capture bullet points from each subpart.
We can create a
with - items each containing the content.
Similarly Requirements: maybe "What We’re Looking For" includes Experience & Education, Skills & Competencies, Preferred Qualifications. The instruction says we can have Requirements and Qualifications sections separate. But we need to decide mapping.
We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to include only those with real content.
We have:
- About the role: yes.
- Responsibilities: yes (What You’ll Do).
- Requirements: maybe Experience & Education (7+ years, portfolio, etc.) could be Requirements.
- Qualifications: maybe Skills & Competencies? Or Preferred Qualifications? The instruction list includes both Requirements and Qualifications as possible headings. We need to decide what goes where.
We could put:
Requirements: Experience & Education (mandatory).
Qualifications: Skills & Competencies (mandatory) plus Preferred Qualifications (optional). But we need to avoid filler.
Better: Use Requirements for mandatory experience/education. Use Qualifications for skills & competencies (maybe also preferred). But we have also Skills section separate. The instruction list includes Skills as a separate heading. So we could map:
- Requirements: Experience & Education.
- Qualifications: Skills & Competencies (maybe also Preferred Qualifications? but we could put Preferred Qualifications under Qualifications as extra bullet).
- Skills: maybe we could treat Skills as separate for technical proficiencies (Figma, AI literacy, data fluency, etc.) but that overlaps with Skills & Competencies. However the instruction list includes Skills as a possible heading; we could put the bullet list of skills there.
But we need to avoid duplication. Let's think: The posting has "Skills & Competencies" with many bullet points. That could be the Skills section. Then "Experience & Education" could be Requirements. Then "Preferred Qualifications" could be Qualifications.
Thus:
- About the role: Position Summary.
- Responsibilities: What You’ll Do (with subpoints).
- Requirements: Experience & Education (mandatory).
- Qualifications: Preferred Qualifications.
- Skills: Skills & Competencies.
- Benefits: The posting mentions "Information on benefits can be found here." No actual benefits listed. So we should NOT create Benefits section because no specific benefits listed. The rule: never create Benefits sections unless posting actually states them. It only says "Information on benefits can be found here." That's not stating benefits. So omit Benefits.
- Pay: The posting includes "Compensation at Pearson is influenced by factors including skill set, experience, and location. The full-time salary range for this role is $105,000 – $135,000. This position is eligible to participate in an annual incentive program." That's pay info. So we need Pay section.
- Schedule: The posting includes "This is a primarily remote role, with occasional travel for in-person collaboration with colleagues and customers." Also later: "Schedule: FULL_TIME Workplace Type: Remote". So we have schedule info: full-time, remote, occasional travel. So we can create Schedule section.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay, Schedule.
We must not include Benefits.
Now we need to format.
Use
for each section heading.
Inside each section, use
for prose,
- for lists.
We need to preserve all substantive info, not invent or summarize away detail.
We need to be careful to not include boilerplate like EEO, etc.
We need to exclude duplicated lines, cookie/navigation/legal etc.
We need to exclude application instructions (like "Applications will be accepted through 18th September 2026.") That's application instruction? It's a deadline; maybe considered application instruction. The instruction says remove application instructions. So we should omit that line.
Also remove "Apply today and imagine the impact you can make." etc.
Also remove "Who we are:" etc.
Also remove "Job: Design Job Family: PRODUCT Organization: Virtual Learning Schedule: FULL_TIME Workplace Type: Remote Req ID: 25597 #location". That's metadata; we should not put Job ID etc as headings; we can fold minor metadata into a short
or drop it. Since we already have Schedule section covering remote/full-time, we can drop the rest.
Now let's extract content.
About the role: The Position Summary paragraph(s) before "What You’ll Do". Let's copy:
"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."
We should keep that as prose under About the role.
Now Responsibilities: "What You’ll Do" with subheadings.
We need to capture all bullet points under each subheading.
Let's extract:
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.
We need to put these as list items. Could group under subheadings but we only have h3 for main sections. Inside Responsibilities we could use
- and maybe include for subheadings? Not prohibited. We'll just list all items as
- . Might be long but okay.
Now Requirements: Experience & Education.
Extract:
"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 need to preserve all. We'll put as
- .
Now Qualifications: Preferred Qualifications.
Extract:
"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."
We'll put as
- .
Now Skills: Skills & Competencies.
Extract:
"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
- for list items. Could also include paragraphs.
We need to preserve all substantive info. So we need to capture bullet points from each subpart.
We can create a
- with
- items each containing the content.
Similarly Requirements: maybe "What We’re Looking For" includes Experience & Education, Skills & Competencies, Preferred Qualifications. The instruction says we can have Requirements and Qualifications sections separate. But we need to decide mapping.
We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to include only those with real content.
We have:
- About the role: yes.
- Responsibilities: yes (What You’ll Do).
- Requirements: maybe Experience & Education (7+ years, portfolio, etc.) could be Requirements.
- Qualifications: maybe Skills & Competencies? Or Preferred Qualifications? The instruction list includes both Requirements and Qualifications as possible headings. We need to decide what goes where.
We could put:
Requirements: Experience & Education (mandatory).
Qualifications: Skills & Competencies (mandatory) plus Preferred Qualifications (optional). But we need to avoid filler.
Better: Use Requirements for mandatory experience/education. Use Qualifications for skills & competencies (maybe also preferred). But we have also Skills section separate. The instruction list includes Skills as a separate heading. So we could map:
- Requirements: Experience & Education.
- Qualifications: Skills & Competencies (maybe also Preferred Qualifications? but we could put Preferred Qualifications under Qualifications as extra bullet).
- Skills: maybe we could treat Skills as separate for technical proficiencies (Figma, AI literacy, data fluency, etc.) but that overlaps with Skills & Competencies. However the instruction list includes Skills as a possible heading; we could put the bullet list of skills there.
But we need to avoid duplication. Let's think: The posting has "Skills & Competencies" with many bullet points. That could be the Skills section. Then "Experience & Education" could be Requirements. Then "Preferred Qualifications" could be Qualifications.
Thus:
- About the role: Position Summary.
- Responsibilities: What You’ll Do (with subpoints).
- Requirements: Experience & Education (mandatory).
- Qualifications: Preferred Qualifications.
- Skills: Skills & Competencies.
- Benefits: The posting mentions "Information on benefits can be found here." No actual benefits listed. So we should NOT create Benefits section because no specific benefits listed. The rule: never create Benefits sections unless posting actually states them. It only says "Information on benefits can be found here." That's not stating benefits. So omit Benefits.
- Pay: The posting includes "Compensation at Pearson is influenced by factors including skill set, experience, and location. The full-time salary range for this role is $105,000 – $135,000. This position is eligible to participate in an annual incentive program." That's pay info. So we need Pay section.
- Schedule: The posting includes "This is a primarily remote role, with occasional travel for in-person collaboration with colleagues and customers." Also later: "Schedule: FULL_TIME Workplace Type: Remote". So we have schedule info: full-time, remote, occasional travel. So we can create Schedule section.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay, Schedule.
We must not include Benefits.
Now we need to format.
Use
for each section heading. Inside each section, use
for prose,
- for lists.
We need to preserve all substantive info, not invent or summarize away detail.
We need to be careful to not include boilerplate like EEO, etc.
We need to exclude duplicated lines, cookie/navigation/legal etc.
We need to exclude application instructions (like "Applications will be accepted through 18th September 2026.") That's application instruction? It's a deadline; maybe considered application instruction. The instruction says remove application instructions. So we should omit that line.
Also remove "Apply today and imagine the impact you can make." etc.
Also remove "Who we are:" etc.
Also remove "Job: Design Job Family: PRODUCT Organization: Virtual Learning Schedule: FULL_TIME Workplace Type: Remote Req ID: 25597 #location". That's metadata; we should not put Job ID etc as headings; we can fold minor metadata into a short
or drop it. Since we already have Schedule section covering remote/full-time, we can drop the rest. Now let's extract content. About the role: The Position Summary paragraph(s) before "What You’ll Do". Let's copy: "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." We should keep that as prose under About the role. Now Responsibilities: "What You’ll Do" with subheadings. We need to capture all bullet points under each subheading. Let's extract: 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. We need to put these as list items. Could group under subheadings but we only have h3 for main sections. Inside Responsibilities we could use
- and maybe include for subheadings? Not prohibited. We'll just list all items as
- . Might be long but okay. Now Requirements: Experience & Education. Extract: "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 need to preserve all. We'll put as
- .
Now Qualifications: Preferred Qualifications.
Extract:
"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."
We'll put as
- . Now Skills: Skills & Competencies. Extract: "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
- . Might be long but okay. Now Requirements: Experience & Education. Extract: "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 need to preserve all. We'll put as
- and maybe include for subheadings? Not prohibited. We'll just list all items as
- for lists.
We need to preserve all substantive info, not invent or summarize away detail.
We need to be careful to not include boilerplate like EEO, etc.
We need to exclude duplicated lines, cookie/navigation/legal etc.
We need to exclude application instructions (like "Applications will be accepted through 18th September 2026.") That's application instruction? It's a deadline; maybe considered application instruction. The instruction says remove application instructions. So we should omit that line.
Also remove "Apply today and imagine the impact you can make." etc.
Also remove "Who we are:" etc.
Also remove "Job: Design Job Family: PRODUCT Organization: Virtual Learning Schedule: FULL_TIME Workplace Type: Remote Req ID: 25597 #location". That's metadata; we should not put Job ID etc as headings; we can fold minor metadata into a short
- items each containing the content.
Similarly Requirements: maybe "What We’re Looking For" includes Experience & Education, Skills & Competencies, Preferred Qualifications. The instruction says we can have Requirements and Qualifications sections separate. But we need to decide mapping.
We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to include only those with real content.
We have:
- About the role: yes.
- Responsibilities: yes (What You’ll Do).
- Requirements: maybe Experience & Education (7+ years, portfolio, etc.) could be Requirements.
- Qualifications: maybe Skills & Competencies? Or Preferred Qualifications? The instruction list includes both Requirements and Qualifications as possible headings. We need to decide what goes where.
We could put:
Requirements: Experience & Education (mandatory).
Qualifications: Skills & Competencies (mandatory) plus Preferred Qualifications (optional). But we need to avoid filler.
Better: Use Requirements for mandatory experience/education. Use Qualifications for skills & competencies (maybe also preferred). But we have also Skills section separate. The instruction list includes Skills as a separate heading. So we could map:
- Requirements: Experience & Education.
- Qualifications: Skills & Competencies (maybe also Preferred Qualifications? but we could put Preferred Qualifications under Qualifications as extra bullet).
- Skills: maybe we could treat Skills as separate for technical proficiencies (Figma, AI literacy, data fluency, etc.) but that overlaps with Skills & Competencies. However the instruction list includes Skills as a possible heading; we could put the bullet list of skills there.
But we need to avoid duplication. Let's think: The posting has "Skills & Competencies" with many bullet points. That could be the Skills section. Then "Experience & Education" could be Requirements. Then "Preferred Qualifications" could be Qualifications.
Thus:
- About the role: Position Summary.
- Responsibilities: What You’ll Do (with subpoints).
- Requirements: Experience & Education (mandatory).
- Qualifications: Preferred Qualifications.
- Skills: Skills & Competencies.
- Benefits: The posting mentions "Information on benefits can be found here." No actual benefits listed. So we should NOT create Benefits section because no specific benefits listed. The rule: never create Benefits sections unless posting actually states them. It only says "Information on benefits can be found here." That's not stating benefits. So omit Benefits.
- Pay: The posting includes "Compensation at Pearson is influenced by factors including skill set, experience, and location. The full-time salary range for this role is $105,000 – $135,000. This position is eligible to participate in an annual incentive program." That's pay info. So we need Pay section.
- Schedule: The posting includes "This is a primarily remote role, with occasional travel for in-person collaboration with colleagues and customers." Also later: "Schedule: FULL_TIME Workplace Type: Remote". So we have schedule info: full-time, remote, occasional travel. So we can create Schedule section.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay, Schedule.
We must not include Benefits.
Now we need to format.
Use