UX Designer / Researcher (Hybrid)

We need to output HTML fragment with sections: About the role? The description includes intro about DXC, but we should not repeat job title. We need sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We have content: Clearance, Work Environment (Hybrid, on-site 2-3 days, Cristal City, Arlington, VA). That could go under "About the role" maybe? Or we could put a short paragraph about role and environment. Responsibilities: many bullet points. Requirements: bullet list. Desired Skills: could be under Skills or Qualifications. The posting has "Desired Skills". We could put under Skills. Additional Information includes clearance repeated, work environment repeated, compensation range, benefits description. So we have Pay: compensation range $73,400 - $136,300. Benefits: description of benefits program. Schedule: hybrid on-site 2-3 days. We should not duplicate. Also we should remove boilerplate like EEO, legal, scam warning, etc. We need to preserve all substantive info. So include clearance, work environment, responsibilities, requirements, desired skills, compensation, benefits, schedule. We must not repeat job title as heading. Use

for each section heading. We need to decide which sections to include: About the role (maybe includes overview of DXC and role context). Could include the introductory paragraph about DXC and the role's purpose? The job description starts with "Job Description DXC Technology ..." then description of company. That's substantive but not exactly role. Could be considered About the role. We'll include that. Responsibilities: list. Requirements: list. Skills: desired skills list. Pay: compensation range. Benefits: description. Schedule: hybrid on-site 2-3 days, Cristal City, Arlington, VA. Clearance: maybe include under About the role or as its own? There's no specific heading for clearance; we could fold into About the role paragraph. We must not create sections with filler text. All sections have content. We must not include duplicated lines. Ensure we don't repeat same bullet. We need to output only HTML fragment. Let's craft:

About the role

DXC Technology helps global companies run mission-critical systems while modernizing IT, optimizing data architectures, and ensuring security and scalability across public, private, and hybrid clouds. This position supports the PeopleSoft HCM user experience team, requiring U.S. citizenship and an active Secret security clearance. The role is hybrid, with on‑site work 2‑3 days per week in Crystal City, Arlington, VA.

Responsibilities

• Plan and conduct user research through interviews, contextual inquiry, observation, usability testing, surveys, and task analysis to understand user needs, behaviors, and pain points.
• Translate research into actionable recommendations, personas/user profiles, journey maps, task flows, usability findings, and prioritized design opportunities.
• Design and improve PeopleSoft HCM experiences using Fluid UI concepts, including homepages, tiles, navigation, responsive pages, search, forms, dashboards, and end‑to‑end workflows.
• Create wireframes, mockups, prototypes, interaction specifications, and other design artifacts that clearly communicate proposed experiences.
• Work closely with PeopleSoft developers, functional analysts, product owners, testers, and business stakeholders to refine requirements and ensure designs are feasible and implemented as intended.
• Evaluate existing PeopleSoft pages and workflows for usability, consistency, efficiency, and accessibility; recommend improvements that reduce user effort and errors.
• Conduct iterative usability testing of concepts, prototypes, and implemented functionality and incorporate findings into subsequent design iterations.
• Develop and maintain UX standards, reusable patterns, design guidance, research repositories, and supporting documentation across PeopleSoft HCM.
• Apply Section 508, WCAG, keyboard navigation, screen‑reader, readability, and other accessibility considerations throughout research and design.
• Use user feedback, analytics, help desk trends, and observed task performance to identify and prioritize high‑value UX improvements.
• Participate in Agile/SAFe activities including backlog refinement, design reviews, demonstrations, acceptance discussions, and coordination with release schedules.
• Partner with training, knowledge management, digital adoption, and help desk teams so recurring user issues and support needs inform UX improvements.
• Other duties as assigned.

Requirements

• Must be a U.S. Citizen with an active Secret security clearance.
• Bachelor's degree in Human‑Computer Interaction, UX Design, Human Factors, Psychology, Information Systems, Computer Science, Design, or a related field; equivalent experience may be considered.
• 3+ years of hands‑on UX design, user research, interaction design, or human‑centered design experience supporting enterprise applications or complex digital products.
• Hands‑on experience with PeopleSoft HCM and PeopleSoft Fluid UI, including enterprise workflows, navigation, pages, transactions, and packaged‑application constraints (preferred).
• Demonstrated experience conducting interviews, observation, usability testing, task analysis, research synthesis, and communicating actionable findings.
• Strong interaction design skills creating personas/user profiles, journey maps, task flows, wireframes, prototypes, mockups, and design specifications.
• Experience with modern UX design and prototyping tools such as Figma, Adobe XD, Sketch, Axure, or comparable tools.
• Strong communication and facilitation skills, with the ability to explain design rationale and collaborate with technical and non‑technical stakeholders.

Skills

• Experience designing or improving PeopleSoft Fluid homepages, tiles, navigation collections, responsive pages, or related PeopleTools user experiences.
• Working knowledge of PeopleTools and technical considerations affecting UX implementation, including page/component structures, configuration, security, and responsive behavior.
• Experience applying human‑centered design methods in large‑scale HCM, ERP, case management, or other complex enterprise environments.
• Knowledge of Section 508 and WCAG standards and experience incorporating accessibility testing and inclusive design practices.
• Experience using analytics, help desk data, or support trends to identify usability problems and measure UX improvements.
• Experience establishing reusable design patterns, UX standards, research repositories, or governance practices across multiple teams.
• Experience working in Agile, SAFe, or similar delivery environments; familiarity with ADO or similar work‑tracking tools is a plus.
• Experience supporting federal or DoD enterprise systems in secured or highly controlled environments is preferred.
• UX, human‑centered design, accessibility, or related professional certification is a plus.

Pay

A reasonable estimate of the current compensation range for this position is $73,400 - $136,300.

Benefits

Full‑time hires are eligible to participate in the DXC benefit program, which includes health, dental, and vision insurance coverage; employee wellness; life and disability insurance; a retirement savings plan; paid holidays; and paid time off.

Schedule

Hybrid work model with on‑site presence 2‑3 days per week in Crystal City, Arlington, VA.

Check for any duplicated content: We have clearance mentioned in About the role and also in Requirements (must be US Citizen with active Secret). That's okay; it's not duplicate exactly but appears twice. Could we remove from About the role? The About the role paragraph includes clearance and work environment; we could keep it there and remove from Requirements? But Requirements must include clearance as it's a requirement. The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we remove clearance from Requirements, we lose that detail. So we need to keep it in Requirements. Having it also in About the role is duplication but maybe acceptable? The instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Duplicated lines refers to exact duplicate lines. Having same sentence in two places is not exactly a duplicated line but similar info. Might be okay. However to be safe, we could keep clearance only in Requirements and not repeat in About the role. But About the role currently includes clearance and work environment; we could move work environment to Schedule section and keep About the role focusing on DXC overview and role purpose without clearance. Let's adjust. About the role: talk about DXC and role purpose (support PeopleSoft HCM UX team). No clearance. Schedule: hybrid on-site 2-3 days, Crystal City, Arlington, VA. Requirements: includes clearance. Thus no duplication. Let's rewrite About the role:

DXC Technology helps global companies run mission‑critical systems while modernizing IT, optimizing data architectures, and ensuring security and scalability across public, private, and hybrid clouds. This position supports the PeopleSoft HCM user experience team, focusing on research, design, and improvement of Fluid UI experiences.

Now Schedule section: hybrid on-site 2-3 days, Crystal City, Arlington, VA. Check Benefits: we have description. Pay: compensation range. Now ensure we didn't miss any substantive info: The "Additional Information" also had "Compensation at DXC is influenced by an array of factors..." but we already have pay range. That's fine. We also had "Full-time hires are eligible to participate in the DXC benefit program. DXC offers a comprehensive, flexible, and competitive benefits program which includes, but is not limited to, health, dental, and vision insurance coverage; employee wellness; life and disability insurance; a retirement savings plan, paid holidays, paid time off." We captured that. We also had "At DXC Technology, we believe strong connections and community are key to our success. Our work model prioritizes in-person collaboration while offering flexibility to support wellbeing, productivity, individual work styles, and life circumstances. We’re committed to fostering an inclusive environment where everyone can thrive." That's somewhat fluff; could be considered boilerplate? It's not EEO but still generic. Might be considered boilerplate; but it's substantive about culture. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those categories; it's a culture statement. Might be okay to keep but could be considered filler. However we already have About the role; we could incorporate a sentence about collaborative environment. But to be safe, we could omit as it's not critical. The instruction says preserve ALL substantive information; does culture statement count as substantive? It's not required for job performance but still part of posting. I'd lean to keep it maybe in About the role. But we already have About the role paragraph; we could add a sentence: "DXC emphasizes in‑person collaboration, flexibility, and an inclusive environment where everyone can thrive." That's not too much. Let's incorporate that. Now check for any other specifics: "Clearance: Must be a US Citizen with an active Secret Security Clearance" appears twice; we have it in Requirements. "Work Environment: Hybrid, on-site 2-3 days, Cristal City, Arlington, VA" appears twice; we have in Schedule. "Compensation at DXC is influenced by an array of factors, including but not limited to the experience, job-related knowledge, skills, competencies, as well as contract-specific affordability and organizational requirements. A reasonable estimate of the current compensation range for this position is $73,400 - $136,300." We have pay range; we could also include the sentence about factors influencing compensation. That's substantive. Let's add to Pay section: a sentence about factors. Thus Pay section: