Senior UI/UX Designer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Our Commitment:" maybe not needed? But we need to keep substantive info like benefits. The posting includes "Our Commitment:" paragraph describing CGS mission, then "We care about our employees. Therefore, we offer a comprehensive benefits package." Then list benefits. Also includes Pay: "#CJ$120,000 - $200,000 a year". That's pay info. Schedule not mentioned. So we should not include Schedule section. Benefits section: list health, dental, vision, life insurance, 401k, FSA, PTO, observance of holidays. Also maybe mention "Contact Government Services (CGS) strives to simplify..." that's about the company; could go under About the role? Actually About the role could be description of role and mission. The posting includes: "CGS is seeking a Senior UI/UX Designer to join our team supporting a wide-ranging technical support initiative for a large Federal agency. CGS brings motivated, highly skilled, and creative people together to solve the government’s most dynamic problems with cutting-edge technology. To carry out our mission, we are seeking candidates who are excited to contribute to government innovation, appreciate collaboration, and can anticipate the needs of others. Here at CGS, we offer an environment in which our employees feel supported, and we encourage professional growth through various learning opportunities." That's about the role/company. So we can put that under About the role. Responsibilities: list of duties from "Skills and attributes for success:" bullet points (starting with "Lead full-scale UX design efforts..." etc). Those are responsibilities. Qualifications: list after "Qualifications:" bullet points. Skills: maybe separate from Qualifications? The posting includes "Skills and attributes for success:" which could be considered Skills. But we already used that for responsibilities? Actually those bullet points are more like responsibilities/skills. The instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. The posting has "Skills and attributes for success:" which is a list of responsibilities/skills. Could treat as Responsibilities. Then "Qualifications:" list is qualifications. There's also "Ideally, you will also have:" list which could be Skills (preferred skills). So we can have Skills section for those preferred skills. Requirements maybe not present; we could omit Requirements if no specific content. The posting does not have a separate "Requirements" heading; but we could combine qualifications as Requirements? However we have both Qualifications and Requirements headings; we need to include only if posting has real specific content. The posting has qualifications list; we could put that under Qualifications. Requirements maybe not present; we could omit Requirements. Skills: we have "Ideally, you will also have:" list; also maybe the "Skills and attributes for success:" could be considered Skills but we used for Responsibilities. Could also split: Responsibilities = lead full-scale UX design efforts etc (action verbs). Skills = expertise in user research methodologies etc. But the list includes both. To be safe, we can treat the first list as Responsibilities, the second list (Ideally, you will also have:) as Skills. Qualifications list as Qualifications. Benefits as Benefits. Pay as Pay. About the role as About the role. No Schedule. No Requirements. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include each bullet point exactly as in posting, preserving wording. Must not omit any bullet. Must not add extra. Must not change wording. We need to output HTML fragment only, no markdown fences. We'll produce:

About the role

CGS is seeking a Senior UI/UX Designer to join our team supporting a wide-ranging technical support initiative for a large Federal agency. CGS brings motivated, highly skilled, and creative people together to solve the government’s most dynamic problems with cutting-edge technology. To carry out our mission, we are seeking candidates who are excited to contribute to government innovation, appreciate collaboration, and can anticipate the needs of others. Here at CGS, we offer an environment in which our employees feel supported, and we encourage professional growth through various learning opportunities.

Responsibilities

• Lead full-scale UX design efforts to include research, blueprinting, and evaluating existing systems.
• Manage the planning, design, and implementation of multiple sites and applications across multiple clients simultaneously in a fast-paced environment.
• Lead all phases of user research and analysis needed to inform the creation of highly usable web pages, application interfaces, and other dynamic solutions.
• Collaborate with federal practice engineers and federal clients to define, design, and implement innovative, beautiful, intuitive solutions for use by our federal customer and their stakeholders.
• Create wireframes, storyboards, and site maps to effectively communicate interaction and design ideas for websites and applications.
• Create scalable design resources to aid in project collaboration and the expansion of ECS creative services.

Qualifications

• Bachelor's Degree.
• Must be able to obtain a Public Trust.
• Strong UX design experience.
• 10+ years combined professional design experience (UCD, UI/UX design).
• Strong online portfolio that showcases the candidate’s ability to make research-driven decisions in the design of responsive web and mobile applications.
• Results-oriented problem solver with high standards for quality, accuracy, attention to detail, and overall excellence.
• Expertise in user research methodologies, user centered design principles and frameworks, and user interface design standards.
• Advanced understanding of user personas, user flows, affinity mapping, and other research tools.
• Strong understanding of the life cycle process of website development (discovery, planning, design, requirements, coding, testing, and user testing and evaluation).
• Experience evaluating existing systems and processes to identify UX issues and develop UX recommendations.
• Experience designing web and mobile applications that are compliant with 508 and US Web Design System (USWDS) standards.
• Experience prioritizing features while accounting for user goals and business requirements.
• Experience carrying designs from start to finish, from wireframes to delivery of final high-fidelity UI mockups.
• Experience establishing and maintaining rapid customer feedback loops to inform design at critical stages.
• Self-starter, motivated, confident and has ability to work independently as well as in a team environment.
• Success on projects designed from scratch as well as redesigns for established platforms or products.
• Experience mentoring/leading junior designers.
• Advanced coding knowledge (HTML, CSS, and JS).
• Advanced proficiency in Adobe xD, InDesign, Illustrator, and Photoshop.

Skills

• Excellent interpersonal and client focused skills— interacts well with all levels of staff and partners with a positive and enthusiastic attitude.
• Experience using Agile methodology to manage projects.
• Experience creating and modifying data visualizations.
• Proficient in Microsoft Office Suite.

Benefits

• Health, Dental, and Vision
• Life Insurance
• 401k
• Flexible Spending Account (Health, Dependent Care, and Commuter)
• Paid Time Off and Observance of State/Federal Holidays

Pay

#CJ$120,000 - $200,000 a year

We must not include Schedule. Also ensure we didn't include any boilerplate like "Contact Government Services (CGS) strives to simplify..." that was in Our Commitment paragraph; we omitted that. Did we lose any substantive info? The "Our Commitment:" paragraph includes description of CGS mission and values; we omitted it. Is that considered substantive? It's about the company, not the role. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Does that include company description? Likely yes, it's substantive info about the employer. However we already included a paragraph about CGS in About the role (the first paragraph). The "Our Commitment:" paragraph is additional info about CGS's mission, values, commitment, benefits statement. We already captured benefits separately. The "Our Commitment:" paragraph includes: "Contact Government Services (CGS) strives to simplify and enhance government bureaucracy through the optimization of human, technical, and financial resources. We combine cutting-edge technology with world-class personnel to deliver customized solutions that fit our client’s specific needs. We are committed to solving the most challenging and dynamic problems. For the past seven years, we’ve been growing our government contracting portfolio, and along the way, we’ve created valuable partnerships by demonstrating a commitment to honesty, professionalism, and quality work. Here at CGS we value honesty through hard work and self-awareness, professionalism in all we do, and to deliver the best quality to our consumers mending those relations for years to come. We care about our employees. Therefore, we offer a comprehensive benefits package." Some of that is covered in About the role paragraph (mission, supportive environment, professional growth). The benefits sentence is covered by Benefits section. The rest about honesty, professionalism, quality work, growing portfolio, partnerships could be considered substantive. Should we include it? The instruction says preserve ALL substantive information. So we should include that info somewhere, perhaps in About the role section expanding it. We can add that paragraph to About the role after the existing description. Ensure we don't repeat. Let's incorporate the "Our Commitment:" paragraph (excluding the benefits sentence which we already have in Benefits). But we need to avoid duplication. We'll include the commitment paragraph as part of About the role. Thus About the role will have two paragraphs: first about seeking candidate, second about CGS commitment. Let's craft:

CGS is seeking a Senior UI/UX Designer to join our team supporting a wide-ranging technical support initiative for a large Federal agency. CGS brings motivated, highly skilled, and creative people together to solve the government’s most dynamic problems with cutting-edge technology. To carry out our mission, we are seeking candidates who are excited to contribute to government innovation, appreciate collaboration, and can anticipate the needs of others. Here at CGS, we offer an environment in which our employees feel supported, and we encourage professional growth through various learning opportunities.

Contact Government Services (CGS) strives to simplify and enhance government bureaucracy through the optimization of human, technical, and financial resources. We combine cutting-edge technology with world-class personnel to deliver customized solutions that fit our client’s specific needs. We are committed to solving the most challenging and dynamic problems. For the past seven years, we’ve been growing our government contracting portfolio, and along the way, we’ve created valuable partnerships by demonstrating a commitment to honesty, professionalism, and quality work. Here at CGS we value honesty through hard work and self-awareness, professionalism in all we do, and to deliver the best quality to our consumers mending those relations for years to come.

Note: we omitted the sentence "We care about our employees. Therefore, we offer a comprehensive benefits package." because we have Benefits section. That sentence is somewhat redundant but we can keep it in Benefits? Actually we already have Benefits list; we could keep that sentence as part of Benefits intro. But we already have Benefits heading with list; we could add