UI/UX Human Centered Design Specialist

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate. Include only sections with real specific content. We need to extract content: - About the role: The description includes "Seize your opportunity to make a personal impact supporting the Case Management Modernization (CMM) Program..." etc. That's prose. Could be About the role. - Responsibilities: The list under "The UI/UX Human Centered Design Specialist will execute the following responsibilities:" then bullet points. Those are duties. So Responsibilities section with

  • . - Requirements: Possibly the "US Citizenship Required: No" etc. But we need to see if there are specific requirements like clearance etc. The posting says Clearance Level Must Currently Possess: None, Must Be Able To Obtain: None, Public Trust/Other Required: None. Those are not substantive? Might be considered metadata but not required. Could be omitted. Also "Experience: 10 + years of related experience". That's a requirement. Also "US Citizenship Required: No". That's a requirement. Also "Job Family: Software Engineering". Not needed. "Skills: Job Qualifications: User Experience (UX), User Experience (UX) Design, User Interfaces (UI)" maybe duplicates. We'll include Requirements: maybe list of required experience, citizenship, etc. - Qualifications: The block under "QUALIFICATIONS MA/MS degree, or Bachelor's/Master's degree in Human-Computer Interaction (HCI), Design, or a related field, with 10+ years of general experience in information systems and 8+ years of specialized experience in UI/UX design, including 5+ years in a Human-Centered Design (HCD) role supporting enterprise or government applications...." That's qualifications. Also includes experience may be considered in lieu of degree etc. Also expertise in usability testing, proficiency in tools, understanding of Agile/SAFe, familiarity with HTML5/CSS3, experience designing for federal systems, etc. Also communication & organizational skills etc. Also certifications (Preferred). So we can put Qualifications section with bullet list. - Skills: Could be separate but maybe overlapped with qualifications. The posting includes "Skills: Job Qualifications: User Experience (UX), User Experience (UX) Design, User Interfaces (UI)". That's maybe a skill list. Could be separate Skills section. But we can combine into Qualifications. However instruction: Prefer few substantive sections over many thin ones. So we might combine Skills into Qualifications or Responsibilities. But we need to include sections only when posting has real specific content. There is a "Skills:" line but it's vague. Might be better to include Skills section with list: User Experience (UX), User Experience (UX) Design, User Interfaces (UI). That's specific. So we can have Skills section. - Benefits: The "Total Rewards At GDIT:" paragraph describes benefits. That's substantive. So Benefits section with
    • items. - Pay: The posting includes "The likely salary range for this position is $128,039 - $173,229." That's pay info. So Pay section with that sentence. - Schedule: The posting includes "Scheduled Weekly Hours: 40 Travel Required: None Telecommuting Options: Remote Work Location: Any Location / Remote". That's schedule info. So Schedule section with those details. We must not include placeholder like "commensurate with experience". Not present. We must remove boilerplate: EEO, legal, etc. At end there is "Equal Opportunity Employer / Individuals with Disabilities / Protected Veterans". Remove. Also remove "Our Identity Verification Process:" etc. That's boilerplate? Might be considered not needed. It's about hiring process; maybe we can keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Identity verification process could be considered part of hiring process but not boilerplate? Might be considered application instructions? It's about verification. Safer to remove. Also remove "About Our Work:" paragraph? That's company description, maybe not needed but could be considered boilerplate? It's not strictly legal but could be considered fluff. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Our Work:" is not those, but could be considered company overview; maybe we can keep as part of About the role? But we already have About the role describing the role. The company description could be omitted to keep concise. I'd omit. Thus sections:

      About the role

      ... (the paragraph about seizing opportunity, CMM program, GDIT, role description). We'll combine the prose before responsibilities. Then

      Responsibilities

      • ... each bullet. Then

        Requirements

        • ... maybe list: 10+ years of related experience, US Citizenship not required, etc. Also maybe "Clearance Level: None" but that's not a requirement. Could include "No clearance required". But we can include "US Citizenship Required: No". Also maybe "Experience: 10+ years of related experience". Also "Job Family: Software Engineering" not needed. We'll keep only substantive. Then

          Qualifications

          • ... list each qualification bullet. Then

            Skills

            • User Experience (UX)
            • User Experience (UX) Design
            • User Interfaces (UI)
            Then

            Benefits

            • ... list each benefit item from Total Rewards. Then

              Pay

              The likely salary range for this position is $128,039 - $173,229.

              Then

              Schedule

              Scheduled Weekly Hours: 40; Travel Required: None; Telecommuting Options: Remote; Work Location: Any Location / Remote.

              We need to ensure we don't duplicate content. Let's extract exact text. About the role paragraph: "Seize your opportunity to make a personal impact supporting the Case Management Modernization (CMM) Program. The CMM program is an initiative to support the Administrative Office of the US Courts (AO) in developing a modern cloud-based solution to support all 204+ federal courts across the United States. GDIT is your place to make meaningful contributions to challenging projects and grow a rewarding career. The UI/UX Human Centered Design Specialist ensures dashboards, reporting tools, predictive analytics screens, and AI/ML interfaces are intuitive, accessible, and aligned with Judiciary user workflows, supporting the CMM Data Modernization and Governance team in delivering data-driven decision-support tools in alignment with strict federal compliance requirements. This role supports the Reporting, Analytics, and Artificial Intelligence/Machine Learning (AI/ML) deliverables by shaping user-centered visual designs for the Reporting & Analytics Capability and the Measurement Definitions and Decision-Support Package. By applying human-centered design (HCD) best practices to visualizations, navigation patterns, and decision-support experiences, this role enhances adoption and interpretability while ensuring designs meet Section 508, WCAG 2.1 AA, and federal digital service standards for accessibility, performance, and security." That's good. Responsibilities bullet list: after "The UI/UX Human Centered Design Specialist will execute the following responsibilities:" we have: - Reporting & Analytics Design intuitive, accessible dashboards, self-service reporting interfaces, and predictive analytics screens for the CMM Reporting & Analytics Capability, applying Human-Centered Design (HCD) and usability best practices. - Translate UX research, personas, and journey maps into high-fidelity prototypes, wireframes, and interface design specifications for development teams. - Partner with BI Architects, data engineers, product owners, and developers to align visual designs with data models, KPIs, and reporting requirements. - Conduct usability testing, including heuristic evaluations, card sorting, and A/B testing, on dashboards and visualizations, and apply findings to refine designs each sprint. - Define and maintain visualization, navigation, and interaction design standards to ensure reports and dashboards are consistent, interpretable, and support adoption. - Design the user experience for the Measurement Definitions and Decision-Support Package, ensuring metrics and KPIs are presented in a clear, decision-ready format. - Evaluate designs for Section 508 and WCAG 2.1 AA accessibility compliance across all reporting and analytics interfaces. - Support rapid prototyping and iterative validation of dashboard and reporting designs within Agile sprint cycles. - Drive user adoption of dashboards and reporting tools by aligning navigation patterns and visual hierarchy with Judiciary user workflows. - Contribute standardized UI components and templates to the shared CMM design system for reuse across reporting products. - AI/ML Capabilities Design intuitive, explainable interfaces for AI/ML-driven predictive analytics and decision-support features, ensuring model outputs are interpretable to end users. - Apply HCD principles to the presentation of AI/ML model outputs, confidence indicators, and recommendations to support responsible AI adoption. - Collaborate with AI/ML and data science teams to translate model capabilities into user-facing workflows aligned with federal responsible-AI requirements for transparency, fairness, and risk mitigation. - Conduct usability evaluations of AI/ML interfaces and incorporate feedback into iterative design refinements. We need to split into
            • items. Some lines have two sentences combined; we can keep as is. Requirements: Let's extract: - Experience: 10 + years of related experience - US Citizenship Required: No - Clearance Level Must Currently Possess: None (maybe not needed) - Clearance Level Must Be Able To Obtain: None - Public Trust/Other Required: None But these are not really requirements; they are "None". Might be considered not substantive. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. For Requirements, we need real specific content. "US Citizenship Required: No" is specific. "Experience: 10+ years of related experience" is specific. The clearance lines are "None" which is like N/A; maybe we should omit them as filler. So Requirements section will have those two items. Qualifications: We need to parse the block. "QUALIFICATIONS MA/MS degree, or Bachelor's/Master's degree in Human-Computer Interaction (HCI), Design, or a related field, with 10+ years of general experience in information systems and 8+ years of specialized experience in UI/UX design, including 5+ years in a Human-Centered Design (HCD) role supporting enterprise or government applications. Experience may be considered in lieu of degree as follows: HS (16+ years), AA/AS (14+ years), BA/BS (12+ years), Doctorate Degree/Ph.D. (9+ years). Expertise in usability testing methodologies, such as heuristic evaluations, card sorting, and A/B testing, and proficiency in design and prototyping tools (Figma, Sketch, Axure, Storybook, or similar). Strong understanding of Agile/SAFe delivery, iterative design integration, and DesignOps/UX governance practices. Familiarity with HTML5, CSS3, and responsive UI behavior to collaborate effectively with front-end developers. Experience designing for federal systems, with practical knowledge of Section 508 and WCAG 2.1 AA compliance." Then after that there is "COMMUNICATION & ORGANIZATIONAL Excellent presentation and communication (oral and written) skills. Consultant mindset with the ability to work with high level customer