Lead UX Designer

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. From posting: Company Description (maybe About the role? Actually "Company Description" is about the company, not role. Could map to "About the role"? But they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We have: - About the role: Could be the job description paragraph: "We are seeking a Lead UX Designer for eMMA modernization MITDP project with Department of General Services, Office of Information Technology. The Lead UX Designer will work closely with DGS OIT, business stakeholders, product owners, project managers, developers, DoIT, and implementation partners. The resource will establish and maintain UX standards and provide continuity for UX design decisions as the program evolves." That's about the role. - Responsibilities: The list under "Duties and Responsibilities:" includes many bullet-like sentences. We can put them in

• . - Requirements: There's "Qualifications" section with Bachelor's degree etc. Also "Required Qualifications:" repeated. Also "Background Requirements: Must be able to complete a required fingerprint background investigation successfully." Also "Citizenship Status Required: H 1B". Also "Physical Requirements: None required for this position." Also "Location: 301 E Preston St, Baltimore City, MD." Could be part of Requirements or maybe separate. But we only have allowed headings; we could put location under Requirements or maybe not include if not fitting. Could include as part of Requirements. - Qualifications: There's also "Preferred Qualifications:" list. Could be separate section "Qualifications" (maybe required) and "Preferred Qualifications" could be under Skills? But we have Skills heading. Could treat Skills as preferred qualifications (tools, etc). However we need to avoid filler. We have content for Skills: "Experience with design tools such as Figma, Adobe XD, Sketch, or equivalent." Also "Experience establishing UX standards/design systems for enterprise applications." Also "Experience working with accessibility standards such as WCAG and ADA compliance." Also "Delivery management experience", "Experience with government, ERP, or other enterprise systems.", "Experience with State of Maryland or other public-sector IT projects." Those could be Skills. - Benefits: There's a paragraph about benefits: "Integres offers competitive salaries bolstered by a comprehensive benefits package... Our generous benefits package includes: Healthcare and Insurance: medical, dental, vision, short and long-term disability protection, basic life and AD&D insurance 401(k) Savings Plan Accrued Paid Time Off (PTO) Employee Recognition and Rewards Employee Referral Bonuses". That's benefits content. - Pay: Not specified (no salary). So we should NOT include Pay section. - Schedule: Not specified. So omit. We must not include headings with filler like "commensurate with experience". Not present. We need to preserve all substantive info; do not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID/requisition numbers as headings (none present). Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The posting includes EEO statements at end; we must remove those. Also "Integres is an equal opportunity affirmative-action employer..." etc. Remove. Also "Background Requirements:" includes fingerprint background investigation, citizenship status H1B, physical requirements none, location. Those are substantive; we should keep. We need to decide where to put location and citizenship etc. Could be under Requirements (maybe as part of Requirements). Or we could create a separate section but not allowed headings. So we put them under Requirements. We also have "Core Competencies" list of items the UX Design Lead will be expected to produce and maintain. That seems like responsibilities or maybe skills. Could be under Responsibilities or maybe Skills. But we already have Responsibilities covering duties. Could add those as part of Responsibilities (they are deliverables). Might be better to include them under Responsibilities as they are expected outputs. However we already have a long list of duties; we could incorporate core competencies as part of Responsibilities (maybe as a sublist). But we must not invent headings; we can just add them as
• under Responsibilities. We must ensure we don't duplicate content. The posting includes "Duties and Responsibilities:" list and then later "Core Competencies" list. Both are substantive; we should include both, maybe combine under Responsibilities. We also have "Qualifications" repeated (Required Qualifications). We'll include once. We have "Preferred Qualifications" list; we can put under Skills. We have "Experience leading UX design activities for large-scale enterprise or government applications." etc under Required Qualifications. That's part of qualifications. We have "Strong experience with user research, journey mapping, wireframing, prototyping, and usability testing." etc. We have "Experience working in Agile/product-development environments." We have "Strong understanding of accessibility and user-centered design principles." We have "Experience collaborating with business stakeholders, technical teams, vendors, and senior leadership." We have "Strong communication, facilitation, and presentation skills." We have "Ability to translate complex business processes into simple and intuitive user experiences." These are qualifications/skills. We need to decide structure: maybe sections: About the role (

  About the role

  ), Responsibilities (

  Responsibilities

  ), Requirements (

  Requirements

  ), Skills (

  Skills

  ), Benefits (

  Benefits

  ). Avoid Qualifications heading? The instruction list includes Qualifications as a possible heading. We could use Qualifications for required qualifications, and Skills for preferred qualifications/tools. But we also have Requirements heading. Which is more appropriate? The list includes both Requirements and Qualifications. We need to decide which to use. The posting has "Qualifications" section (Bachelor's degree etc) and "Required Qualifications". Also "Preferred Qualifications". Could map Required Qualifications to Requirements, and Preferred Qualifications to Skills. Or we could use Qualifications for both required and preferred, and Skills for tools. But we have both headings available; we should use them meaningfully. Let's assign: - About the role: intro paragraph. - Responsibilities: duties list + core competencies. - Requirements: required qualifications (degree, years experience, leading UX design for large-scale enterprise/gov, strong experience with user research..., Agile, accessibility understanding, collaborating, communication, ability to translate). Also background requirements (fingerprint, citizenship H1B, physical none, location). Could also include "Must be able to complete a required fingerprint background investigation successfully." etc. - Skills: preferred qualifications (delivery management experience, experience with government/ERP/enterprise systems, experience with State of Maryland or other public-sector IT projects, experience with design tools Figma etc, experience establishing UX standards/design systems, experience with WCAG/ADA). Also maybe "Strong experience with user research..." but that's already in Requirements; we can keep it there. - Benefits: benefits paragraph. We must not include Pay or Schedule. We must ensure we don't include any boilerplate like EEO statements. Now produce HTML fragment: only the sections with appropriate headings and content. We need to wrap each section:

  Heading

  then either

  for prose or

  • for lists. For About the role: we have a paragraph (maybe two sentences). We'll put in

    . For Responsibilities: we have a list of duties (the bullet points under Duties and Responsibilities) plus core competencies list. We'll combine into one

    with many
    • . Ensure we preserve all items exactly as in posting (but we can rephrase? Must not invent or summarize away detail; we can keep the same wording). We'll copy each duty sentence. Let's extract duties from posting: "Lead UX strategy and design activities for the OIT program and related applications." "Support the Launchpad process, including development of user-centered requirements, UX artifacts, workflows, and supporting documentation." "Conduct user research, stakeholder interviews, workshops, and usability assessments to understand user needs and pain points." "Develop user journeys, personas, process flows, information architecture, wireframes, prototypes, and high-fidelity designs." "Translate business and technical requirements into intuitive, accessible, and user-centered experiences." "Facilitate design sessions with business users and technical teams to validate proposed solutions." "Establish UX design standards and patterns that can be consistently applied across DGS applications." "Ensure designs comply with ADA/accessibility requirements and applicable State of Maryland standards." "Collaborate with product owners, business analysts, developers, architects, and project managers throughout the product lifecycle." "Review vendor and implementation-partner deliverables to ensure UX requirements and design standards are met." "Provide UX input into product roadmaps, solution decisions, enhancements, and prioritization." "Identify usability risks and recommend improvements before solutions move into development or production." "Maintain UX documentation and design artifacts as a central source of truth." "Support user acceptance testing and incorporate user feedback into iterative design improvements." "Ensure UX decisions are based on measurable user and business outcomes rather than technology alone." "Provide knowledge transfer and continuity as external UX resources transition off the project." Now core competencies list: "User personas and stakeholder profiles" "Current-state and future-state user journey maps" "User flows and process maps" "Wireframes and prototypes" "High-fidelity UI designs" "Usability testing plans and findings" "UX requirements and acceptance criteria" "Accessibility assessments" "UX/design standards and patterns" "Launchpad UX documentation" "Design decision documentation" "User research and feedback summaries" "UX recommendations for future product enhancements" We'll include these as
    • as well. Now Requirements: list of required qualifications. From posting: "Bachelor's degree in UX Design, Human-Computer Interaction, Interaction Design, Information Architecture, Computer Science, or a related field." "8+ years of experience in UX/UI design, product design, or a related discipline." "Experience leading UX design activities for large-scale enterprise or government applications." "Strong experience with user research, journey mapping, wireframing, prototyping, and usability testing." "Experience working in Agile/product-development environments." "Strong understanding of accessibility and user-centered design principles." "Experience collaborating with business stakeholders, technical teams, vendors, and senior leadership." "Strong communication, facilitation, and presentation skills." "Ability to translate complex business processes into simple and intuitive user experiences." Also background requirements: "Must be able to complete a required fingerprint background investigation successfully." "Citizenship Status Required: H 1B" "Physical Requirements: None required for this position." "Location: 301 E Preston St, Baltimore City, MD." We'll include these as list items. Now Skills: preferred qualifications list: "Delivery management experience" "Experience with government, ERP, or other enterprise systems." "Experience with State of Maryland or other public-sector IT projects." "Experience with design tools such as Figma, Adobe XD, Sketch, or equivalent." "Experience establishing UX standards/design systems for enterprise applications." "Experience working with accessibility standards such as WCAG and ADA compliance." We'll put as list. Now Benefits: paragraph: "Integres offers competitive salaries bolstered by a comprehensive benefits package, which provides safety and security for our employees and their families. Our generous benefits package includes: Healthcare and Insurance: medical, dental, vision, short and long-term disability protection, basic life and AD&D insurance 401(k) Savings Plan Accrued Paid Time Off (PTO) Employee Recognition and Rewards Employee Referral Bonuses" We need to preserve that exactly; maybe split into sentences but keep as

      . Now ensure we didn't