Advanced Specialist, Experience Design
Pearson · Little Rock, AR · 1 mo ago
RemoteRemoteArt & Creative$105k–$135k/yrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also remove "Applications will be accepted through 18th September 2026..." etc. Also remove "Who we are:" etc. Also remove "Compensation at Pearson is influenced by factors..."? Actually compensation is specific: salary range $105,000 – $135,000, eligible for annual incentive program. So we can include Pay section with that. Benefits: "Information on benefits can be found here." That's not specific content; it's a link placeholder. Should we include Benefits section? The rule: never create Benefits sections unless posting actually states them. It states "Information on benefits can be found here." That's not specific benefit details. Likely we should not include Benefits because it's not substantive. However there is mention of annual incentive program; that could be part of Pay or Benefits. But we can include Pay with salary range and annual incentive. Benefits maybe omitted.
Schedule: posting says "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 can include Schedule section with full-time, primarily remote, occasional travel.
About the role: we have Position Summary paragraph. That's suitable.
Responsibilities: we have "What You’ll Do" with subheadings Research & Insight, Design & Prototyping, Collaboration & Strategic Influence, Mentorship & Team Contribution. We can combine into Responsibilities section with lists.
Requirements: maybe "What We’re Looking For" includes Experience & Education, Skills & Competencies, Preferred Qualifications. We can separate Requirements (mandatory) and Qualifications (preferred) or Skills. The instruction: use headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We need to decide what goes where.
About the role: Position Summary paragraph.
Responsibilities: the "What You’ll Do" section (Research & Insight, Design & Prototyping, Collaboration & Strategic Influence, Mentorship & Team Contribution). We'll create
- for each bullet? The content is paragraphs; we can break into list items for each major duty. Could also keep prose but rule: Use
- for any list of duties/requirements/benefits. So we should convert duties into list items.
Requirements: maybe the mandatory 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."
Qualifications: maybe "Skills & Competencies" is skills; but we have separate Skills heading. So Qualifications could be "Preferred Qualifications". That includes experience in K-12 education sector, familiarity with AI-assisted design and research tooling, background in mixed-methods research, understanding of pedagogy and instructional design principles, familiarity with LMS.
Skills: the Skills & Competencies list.
Pay: salary range and annual incentive program.
Schedule: full-time, primarily remote, occasional travel.
We must not include boilerplate like "Applications will be accepted through..." etc. Also remove "Who we are:" etc. Also remove "Compensation at Pearson is influenced by factors including skill set, experience, and location." That's generic; we can keep the specific salary range and annual incentive. The generic sentence maybe considered boilerplate; we can drop it.
Also remove "Information on benefits can be found here." (no specifics). So we omit Benefits section entirely.
We must not repeat job title as heading. Not include Job ID etc.
Now produce HTML fragment.
Structure:
About the role
...
Responsibilities
- ... ...
- for any list of duties/requirements/benefits. So we should convert duties into list items.
Requirements: maybe the mandatory 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."
Qualifications: maybe "Skills & Competencies" is skills; but we have separate Skills heading. So Qualifications could be "Preferred Qualifications". That includes experience in K-12 education sector, familiarity with AI-assisted design and research tooling, background in mixed-methods research, understanding of pedagogy and instructional design principles, familiarity with LMS.
Skills: the Skills & Competencies list.
Pay: salary range and annual incentive program.
Schedule: full-time, primarily remote, occasional travel.
We must not include boilerplate like "Applications will be accepted through..." etc. Also remove "Who we are:" etc. Also remove "Compensation at Pearson is influenced by factors including skill set, experience, and location." That's generic; we can keep the specific salary range and annual incentive. The generic sentence maybe considered boilerplate; we can drop it.
Also remove "Information on benefits can be found here." (no specifics). So we omit Benefits section entirely.
We must not repeat job title as heading. Not include Job ID etc.
Now produce HTML fragment.
Structure: