Advanced Specialist, Experience Design
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content.
We have Position Summary (About the role). Then "What You’ll Do" includes Research & Insight, Design & Prototyping, Collaboration & Strategic Influence, Mentorship & Team Contribution. That's responsibilities.
Then "What We’re Looking For" includes Experience & Education, Skills & Competencies, Preferred Qualifications. Could be Requirements/Qualifications/Skills.
Compensation: salary range $105,000 – $135,000, eligible for annual incentive program. Benefits: "Information on benefits can be found here." Not specific details, so we should not create Benefits section unless posting actually states them. It only says info can be found here, not actual benefits. So we should not include Benefits section.
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, remote. So we can include Schedule section.
Pay: we have salary range, so include Pay section.
We need to avoid repeating job title as heading. No Job ID etc.
We need to remove boilerplate: EEO, etc.
We need to preserve all substantive info.
We need to use - for any list of duties/requirements/benefits. For prose use
.
We need to decide which sections to include: About the role (position summary), Responsibilities (What You’ll Do), Requirements (Experience & Education maybe), Qualifications (maybe Skills & Competencies?), Skills (maybe Skills & Competencies?), but we need to avoid duplication. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple sections but only if content.
We have content for About the role (position summary). Responsibilities (What You’ll Do). Requirements (Experience & Education). Qualifications (maybe Preferred Qualifications? Or we could combine Requirements and Qualifications? But we need to follow instruction: include a section ONLY when posting has real, specific content for it. So we can have both Requirements and Qualifications if we have distinct content.
We have Skills & Competencies section. That could map to Skills heading.
We have Pay heading.
We have Schedule heading.
We should not include Benefits.
We need to ensure we don't create empty sections.
Let's extract content.
About the role: The position summary paragraph(s). Let's capture:
"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's the About the role.
Responsibilities: Under "What You’ll Do" with subheadings Research & Insight, Design & Prototyping, Collaboration & Strategic Influence, Mentorship & Team Contribution. We need to capture bullet points? The text is prose paragraphs under each subheading. We can treat each subheading as a list item? The instruction: Use
- for any list of duties/requirements/benefits. So we can create a
with each duty as - . We need to extract duties.
Let's list duties:
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 can combine all into a single
list of duties, or we could have subheadings inside? The instruction only says use for section headings, and - for any list of duties/requirements/benefits. It doesn't forbid having headings inside the list? Probably better to just have a single
list under Responsibilities heading.
Now Requirements: Experience & Education section.
Content:
"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 can turn each line into - under Requirements.
Qualifications: maybe we treat Skills & Competencies as Qualifications? But we also have Preferred Qualifications section. Let's see.
Skills & Competencies: list of 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."
We could map this to Skills heading.
Preferred Qualifications: list:
"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 could map to Qualifications heading (or maybe also Skills). But we already have Skills heading for Skills & Competencies. We could have Qualifications for Preferred Qualifications. Or we could combine Requirements and Qualifications? The instruction says we can have sections Requirements, Qualifications, Skills. So we can assign:
- Requirements: Experience & Education (mandatory)
- Qualifications: Preferred Qualifications (optional but we have content)
- Skills: Skills & Competencies
That seems reasonable.
Now Pay: salary range $105,000 – $135,000, plus annual incentive program. We'll include that.
Schedule: full-time, remote, occasional travel. We'll include that.
We must not include Benefits.
Now produce HTML fragment:
About the role
... (the paragraph)
Responsibilities
- ... each duty
...
Requirements
- ... each line
...
Qualifications
- ... each preferred qualification
...
Skills
- ... each skill competency
...
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.
Schedule
This is a primarily remote role with occasional travel for in-person collaboration; the position is full-time.
We
. We need to decide which sections to include: About the role (position summary), Responsibilities (What You’ll Do), Requirements (Experience & Education maybe), Qualifications (maybe Skills & Competencies?), Skills (maybe Skills & Competencies?), but we need to avoid duplication. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple sections but only if content. We have content for About the role (position summary). Responsibilities (What You’ll Do). Requirements (Experience & Education). Qualifications (maybe Preferred Qualifications? Or we could combine Requirements and Qualifications? But we need to follow instruction: include a section ONLY when posting has real, specific content for it. So we can have both Requirements and Qualifications if we have distinct content. We have Skills & Competencies section. That could map to Skills heading. We have Pay heading. We have Schedule heading. We should not include Benefits. We need to ensure we don't create empty sections. Let's extract content. About the role: The position summary paragraph(s). Let's capture: "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's the About the role. Responsibilities: Under "What You’ll Do" with subheadings Research & Insight, Design & Prototyping, Collaboration & Strategic Influence, Mentorship & Team Contribution. We need to capture bullet points? The text is prose paragraphs under each subheading. We can treat each subheading as a list item? The instruction: Use
- for any list of duties/requirements/benefits. So we can create a
- with each duty as
- . We need to extract duties.
Let's list duties:
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 can combine all into a single
- list of duties, or we could have subheadings inside? The instruction only says use
- for any list of duties/requirements/benefits. It doesn't forbid having headings inside the list? Probably better to just have a single
- list under Responsibilities heading.
Now Requirements: Experience & Education section.
Content:
"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 can turn each line into
- under Requirements.
Qualifications: maybe we treat Skills & Competencies as Qualifications? But we also have Preferred Qualifications section. Let's see.
Skills & Competencies: list of 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."
We could map this to Skills heading.
Preferred Qualifications: list:
"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 could map to Qualifications heading (or maybe also Skills). But we already have Skills heading for Skills & Competencies. We could have Qualifications for Preferred Qualifications. Or we could combine Requirements and Qualifications? The instruction says we can have sections Requirements, Qualifications, Skills. So we can assign:
- Requirements: Experience & Education (mandatory)
- Qualifications: Preferred Qualifications (optional but we have content)
- Skills: Skills & Competencies
That seems reasonable.
Now Pay: salary range $105,000 – $135,000, plus annual incentive program. We'll include that.
Schedule: full-time, remote, occasional travel. We'll include that.
We must not include Benefits.
Now produce HTML fragment:
About the role
... (the paragraph)
Responsibilities
- ... each duty ...
Requirements
- ... each line ...
Qualifications
- ... each preferred qualification ...
Skills
- ... each skill competency ...
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.
Schedule
This is a primarily remote role with occasional travel for in-person collaboration; the position is full-time.
We
- under Requirements.
Qualifications: maybe we treat Skills & Competencies as Qualifications? But we also have Preferred Qualifications section. Let's see.
Skills & Competencies: list of 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."
We could map this to Skills heading.
Preferred Qualifications: list:
"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 could map to Qualifications heading (or maybe also Skills). But we already have Skills heading for Skills & Competencies. We could have Qualifications for Preferred Qualifications. Or we could combine Requirements and Qualifications? The instruction says we can have sections Requirements, Qualifications, Skills. So we can assign:
- Requirements: Experience & Education (mandatory)
- Qualifications: Preferred Qualifications (optional but we have content)
- Skills: Skills & Competencies
That seems reasonable.
Now Pay: salary range $105,000 – $135,000, plus annual incentive program. We'll include that.
Schedule: full-time, remote, occasional travel. We'll include that.
We must not include Benefits.
Now produce HTML fragment:
for section headings, and
- for any list of duties/requirements/benefits. It doesn't forbid having headings inside the list? Probably better to just have a single
- . We need to extract duties.
Let's list duties:
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 can combine all into a single