UX / CX Designer

We need to output HTML fragment only, with sections for headings where there is real content. Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. From posting: - About the role: description: "Steampunk is seeking a UX/CX Designer to lead digital customer experience measurement and accessibility conformance for a large federal advisory program, guiding the client through our Design Intelligence® framework. You'll plan and execute CX initiatives from discovery through measurement — research, testing, and iteration — serving as the voice of the user to ensure their needs are reflected in every recommendation." That's a paragraph. - Responsibilities: list of bullet points: "Deliver a Digital CX Measurement and Reporting Plan aligned to OMB Circular A-11 Section 280", "Conduct user workshops and interviews to frame pain points, validate hypotheses, and inform priority journey maps", "Establish a CX measurement baseline and priority journey maps for client-selected services, expanding to 100% of designated services in later performance periods", "Conduct user research and testing to translate user needs into CX measurement priorities and recommendations", "Own the pre-release accessibility checklist, verifying Section 508/WCAG 2.1 conformance before release rather than remediating after", "Support Paperwork Reduction Act (PRA)-compliant survey design for CX measurement", "Collaborate and communicate stakeholder and user needs across a cross-functional Agile team", "Contribute to executive dashboard design supporting stated satisfaction and accuracy targets", "Ensure all deliverables are produced at consistent, high quality across assigned workstreams". That's responsibilities. - Required Qualifications: list: "Ability to obtain and maintain a U.S. government security clearance", "Bachelor's degree, preferably in HCD, HCI, UX/CX Design, or a related field", "5+ years of UX/CX research and design experience", "Portfolio demonstrating UX/CX research process, methods, and craft", "Demonstrated knowledge of Section 508/WCAG 2.1 accessibility standards and experience embedding them into a production workflow", "Experience conducting user research techniques such as interviews, co-creation workshops, heuristic evaluation, and card sorting to inform journey maps and experience measurement", "Experience conducting moderated and unmoderated usability and accessibility testing", "Experience with journey mapping and experience-analytics methods", "Experience working within an Agile delivery framework, integrating research and measurement activities into program cadences", "Excellent written communication and presentation skills to convey CX findings and recommendations", "Experience collaborating within a multidisciplinary delivery team, including service designers, data specialists, and change-management professionals". That's required qualifications. - Preferred: "Familiarity with OMB Circular A-11 Section 280 CX measurement requirements", "Federal digital services experience", "Previous experience working as a consultant". Could be a separate section "Preferred Qualifications" but we only have headings list: Skills, Benefits, Pay, Schedule, Qualifications, Requirements. We could treat "Preferred" as part of Qualifications or Requirements? Probably we can include a "Preferred Qualifications" under Qualifications heading? But the instruction says use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have "About the role" (intro paragraph). "Responsibilities" (list). "Requirements" maybe for required qualifications? Or "Qualifications" for required? The list includes both Requirements and Qualifications headings. We need to decide which to use. Typically "Requirements" could be required qualifications, and "Qualifications" could be preferred? But we have both required and preferred. We could put required under "Requirements" and preferred under "Qualifications". Or we could combine required and preferred under "Qualifications" and leave Requirements empty? But we must not emit a heading with filler/placeholder text. So we need to ensure each heading we output has real content. Thus we can output:

About the role

...

Responsibilities

...

Requirements

...

(for required qualifications)

Qualifications

...

(for preferred qualifications) We don't have Skills, Benefits, Pay, Schedule content. So we omit those sections. Check that we don't repeat job title as heading. Good. We must not include boilerplate like EEO, etc. We removed. We need to preserve all substantive information. Ensure we include everything from About the role, Responsibilities, Required Qualifications, Preferred. Check that we didn't miss any details: The "About Steampunk" paragraph includes salary range and benefits link, identity statement, etc. That's boilerplate? The salary range is substantive: "The projected compensation range for this position is $75,000 to $140,000." That's Pay info. So we should include a Pay section with that range. Also benefits: "Learn more about additional Steampunk benefits here." That's a link but we might not need to include as it's just a reference. The identity statement about camera, etc. Might be considered boilerplate? It's part of the posting but not necessarily required to keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Identity statement about being on camera and taking picture to verify identity might be considered part of application instructions? It's about interview process. Might be considered application instructions? Possibly we should remove it as it's about interview process. The "Identity Statement" seems like a requirement for application process; could be considered application instructions. Safer to remove. Also "About Steampunk" includes description of company, mission, etc. That's substantive about the company; we could keep as part of About the role? Might be better to include under About the role? The posting already had an "About Steampunk" paragraph after the job description. That's substantive about the company. We could include that as part of About the role or maybe a separate section? There's no heading for company overview. We could incorporate into About the role paragraph. We also have salary range and benefits link. So we need a Pay section with the salary range. Benefits: we have a link to learn more about benefits; but no specific benefits listed. So we should not create a Benefits section unless there are actual benefits listed. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It states salary range, so Pay section is okay. Benefits: only a link to learn more, not actual benefits listed. So we should not create Benefits section. Schedule: not mentioned. Skills: not explicitly listed as a separate section; we could treat skills as part of qualifications but we already have Requirements and Qualifications. So we omit Skills. Thus final HTML:

About the role

Steampunk is seeking a UX/CX Designer to lead digital customer experience measurement and accessibility conformance for a large federal advisory program, guiding the client through our Design Intelligence® framework. You'll plan and execute CX initiatives from discovery through measurement — research, testing, and iteration — serving as the voice of the user to ensure their needs are reflected in every recommendation. About Steampunk: Steampunk relies on several factors to determine salary, including but not limited to geographic location, contractual requirements, education, knowledge, skills, competencies, and experience. The projected compensation range for this position is $75,000 to $140,000. The estimate displayed represents a typical annual salary range for this position. Annual salary is just one aspect of Steampunk’s total compensation package for employees. Learn more about additional Steampunk benefits here. Steampunk is a Change Agent in the Federal contracting industry, bringing new thinking to clients in the Homeland, Federal Civilian, Health and DoD sectors. Through our Design Intelligence™ process, we are fundamentally changing the expectations our Federal clients have for true shared accountability in solving their toughest mission challenges. If you want to learn more about our story, visit http://www.steampunk.com.

But we need to separate Pay section. So we should move salary range to Pay section. The About the role paragraph should not include salary range. Let's extract salary range to Pay. Thus:

About the role

Steampunk is seeking a UX/CX Designer to lead digital customer experience measurement and accessibility conformance for a large federal advisory program, guiding the client through our Design Intelligence® framework. You'll plan and execute CX initiatives from discovery through measurement — research, testing, and iteration — serving as the voice of the user to ensure their needs are reflected in every recommendation. About Steampunk: Steampunk relies on several factors to determine salary, including but not limited to geographic location, contractual requirements, education, knowledge, skills, competencies, and experience. Steampunk is a Change Agent in the Federal contracting industry, bringing new thinking to clients in the Homeland, Federal Civilian, Health and DoD sectors. Through our Design Intelligence™ process, we are fundamentally changing the expectations our Federal clients have for true shared accountability in solving their toughest mission challenges. If you want to learn more about our story, visit http://www.steampunk.com.

Responsibilities

...

Requirements

...

(required qualifications)

Qualifications

...

(preferred)

Pay

The projected compensation range for this position is $75,000 to $140,000.

We also have benefits link; we could include a short sentence about benefits link but not a section. Could add to About the role paragraph: "Learn more about additional Steampunk benefits here." That's okay. Now ensure we didn't include any boilerplate like EEO, etc. We removed. Check that we didn't include duplicated lines. Now produce HTML fragment only. Let's craft the lists precisely. Responsibilities list items: - Deliver a Digital CX Measurement and Reporting Plan aligned to OMB Circular A-11 Section 280 - Conduct user workshops and interviews to frame pain points, validate hypotheses, and inform priority journey maps - Establish a CX measurement baseline and priority journey maps for client-selected services, expanding to 100% of designated services in later performance periods - Conduct user research and testing to translate user needs into CX measurement priorities and recommendations - Own the pre-release accessibility checklist, verifying Section 508/WCAG 2.1 conformance before release rather than remediating after - Support Paperwork Reduction Act (PRA)-compliant survey design for CX measurement - Collaborate and communicate stakeholder and user needs across a cross-functional Agile team - Contribute to executive dashboard design supporting stated satisfaction and accuracy targets - Ensure all deliverables are produced at consistent, high quality across assigned workstreams Required Qualifications list: - Ability to obtain and maintain a U.S. government security clearance - Bachelor's degree, preferably in HCD, HCI, UX/CX Design, or a related field - 5+ years of UX/CX research and design experience - Portfolio demonstrating UX/CX research process, methods, and craft - Demonstrated knowledge of Section 508/WCAG 2.1 accessibility standards and experience embedding them into a production workflow - Experience conducting user research techniques such as interviews, co-creation workshops, heuristic evaluation, and card sorting to inform journey maps and experience measurement - Experience conducting moderated and unmoderated usability and accessibility testing - Experience with journey mapping and experience-analytics methods - Experience working within an Agile delivery framework, integrating research and measurement activities into program cadences - Excellent written communication and presentation skills to convey CX findings and recommendations - Experience collaborating within a multidisciplinary delivery team, including service designers, data specialists, and change-management professionals Preferred Qualifications list: