Usability Researcher [AQ-19981]

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule only if content present. We must not repeat job title. Remove boilerplate: EEO, legal, application instructions, cookie/navigation, duplicated lines. Also remove Aquent Talent description? That's about benefits maybe but we need Benefits section only if posting actually states them. The posting includes "Aquent Talent connects the best talent ... eligible talent get access to amazing benefits like subsidized health, vision, and dental plans, paid sick leave, and retirement plans with a match. We also offer free online training through Aquent Gymnasium." That's benefits info. So we can include Benefits section with that content. Also there is "Why work with AQUENT? Check out our awesome benefits: https://aquent.com/talent/talent-benefits" but that's similar. We need to preserve all substantive information: role description, responsibilities list, qualifications (required and nice-to-have). Also maybe "About Aquent Talent" is not about the role but about the agency; but it's still part of posting. Should we include? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep that info somewhere. Could be placed under a section like "About Aquent Talent" but we only allowed specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The "About Aquent Talent" is not one of those headings; we could fold it into a short

maybe under About the role? But that heading is for role description. The role description currently includes paragraphs about the company and role. We could incorporate Aquent Talent info into a separate paragraph maybe under About the role? But that might mix. However we must not create extra headings not listed. So we need to embed that info within allowed sections or as a

without heading. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should only use those headings when we have content. It doesn't forbid other headings, but says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not add other headings. So we need to place Aquent Talent info maybe under Benefits? But it's about benefits from Aquent, not the client. Could be part of Benefits section. The Benefits section currently we have from Aquent Talent: subsidized health, vision, dental, paid sick leave, retirement plans with match, free online training. That's exactly the benefits. So we can put that under Benefits heading. Good. Now we need to include About the role: the introductory paragraphs about the company and role. That includes: "Aquent is proud to partner with a global technology leader renowned for its groundbreaking innovations... As a Usability Researcher, you will be a passionate advocate..." etc. Also the "What You’ll Do" list. Actually responsibilities are separate. So About the role could be the introductory paragraph before "What You’ll Do". Then Responsibilities heading for the bullet list under "What You’ll Do". Then Requirements heading for required qualifications? Actually we have Required Qualifications and Nice-to-Have Qualifications. Could combine into Requirements and Qualifications? The instruction says we can have Requirements and Qualifications sections. We need to decide what goes where. Typically Requirements = mandatory qualifications; Qualifications = nice-to-have? Or Skills? We have Skills maybe separate. But we have a list of skills in required qualifications: proficiency in qualitative and quantitative research methods, etc. Could be under Skills. However we have many items that could be considered skills. Let's parse: Required Qualifications block includes education/experience requirements plus: "1+ year(s) relevant domain experience within the technology sector." etc. Then a list of competencies: "English language proficiency...", "Proficiency in qualitative and quantitative research methods, quality assurance, user acceptance testing, and user scenario creation and application.", "Strong analytical thinking, data analysis, problem-solving, and translation of insights.", "Experience with collaborative innovation, conflict resolution, distillation of results, industry trends, and stakeholder management.", "Demonstrated decision-making ability, outcome-driven innovation, project management, project visioning, and scope management.", "Creativity, interaction design, user experience, user interface design, and user-centered design principles." These could be considered Skills. Nice-to-Have Qualifications are higher education/experience combos. Thus we could structure: - About the role: intro paragraphs. - Responsibilities: bullet list from "What You’ll Do". - Requirements: education/experience requirements (the degree+years etc) plus domain experience etc? Might be considered requirements. - Qualifications: nice-to-have qualifications. - Skills: the competencies list. - Benefits: Aquent Talent benefits. - Pay: not mentioned -> omit. - Schedule: not mentioned -> omit. We must not create sections with filler like "not specified". So omit Pay and Schedule. Now we need to ensure we don't repeat job title. No mention. We need to remove boilerplate: EEO statements, Aquent equal opportunity, legal, application instructions, duplicated lines. Also remove "Aquent is an equal-opportunity employer." lines. Also remove "More information on our awesome benefits!" maybe but we keep benefits content. Remove "Check out our awesome benefits: https://aquent.com/talent/talent-benefits" maybe but we already have benefits content; we can drop the link. Also remove "Client Description" etc? That's about the client; could be part of About the role? Actually there is a "Client Description" paragraph after Aquent Talent benefits. That describes the global technology leader. That is substantive and could be included in About the role (maybe after intro). We'll incorporate. Also "Why work with AQUENT?" is basically benefits again; we can ignore duplicate. Now produce HTML:

About the role

... paragraphs ...

Responsibilities

• ... each bullet ...

Requirements

... degree/experience requirements ...

Qualifications

... nice-to-have ...

Skills

• ... each skill bullet ...

Benefits

... benefits ...

Make sure to not include any extra whitespace? It's fine. Now craft the content. About the role paragraph(s): We need to combine: "Aquent is proud to partner with a global technology leader renowned for its groundbreaking innovations that shape how millions worldwide connect, work, and live. This company is at the forefront of developing cutting-edge products and services that define the digital landscape. Joining this team means contributing to a legacy of excellence and driving the next generation of user experiences. As a Usability Researcher, you will be a passionate advocate for the user, eager to dive deep into understanding human behavior and translate those insights into impactful product decisions. This dynamic and pivotal role allows you to shape the future of products and services, ensuring offerings are intuitive, secure, and delightful for users on a global scale, making a tangible impact on how people interact with technology every day." Then maybe add the Client Description: "Join a global technology leader driving innovation and empowering people and organizations worldwide to achieve more. Here, you’ll collaborate with passionate, diverse teams to create impactful solutions that shape the future. The culture prioritizes growth, inclusion, and purpose—where your ideas are valued, and your work drives real change. Wherever your passion lies and wherever your career is headed—you’ll play a role in projects that touch billions of lives. With flexible work options and a supportive environment, you’ll have the tools to thrive both personally and professionally. Be part of something that truly matters." We can combine into one or two paragraphs. Now Responsibilities bullet list from "What You’ll Do": - Create and drive research plans and roadmaps for various product areas, defining problems and success criteria aligned with business needs. - Apply diverse research methods to execute studies effectively, guiding multi-person research efforts for strong product outcomes. - Synthesize and distill data into actionable insights, communicating findings to activate design and engineering processes. - Conduct research to clarify customer identities, contexts, needs (e.g., Jobs To Be Done), and journeys to inform product strategy. - Assess user insights across the entire user journey—from awareness through adoption and retention—leveraging both quantitative and qualitative data. - Contribute to solution formation by partnering with product management, design, and engineering, integrating security as a fundamental aspect of development. - Produce research-driven insights on industry and vertical trends to reduce uncertainty for future initiatives. - Collaborate with cross-disciplinary teams, educating and mentoring on research value, rigor, and methodology. - Develop recruitment screeners and review data collection instruments, ensuring privacy and security compliance. - Provide effective tools and templates for product makers to capture assumptions and express them as testable hypotheses. - Collaborate with the team to create well-formed user experience goals, signals, metrics, and criteria, integrating security UX KPIs. - Apply experience checkpoints and iterative research processes to ensure product quality and drive continuous improvement. Now Requirements: The degree/experience requirements: "Master’s Degree in Human-Computer Interaction, Human Factors Engineering, Computer Science, Technical Communications, Information Science, Information Architecture, User Experience Design, Behavioral Science, Social Sciences, or a related field AND 1+ year(s) User Experience Research experience; OR Bachelor’s Degree in Human-Computer Interaction, Human Factors Engineering, Computer Science, Technical Communications, Information Science, Information Architecture, User Experience Design, Behavioral Science, Social Sciences, or a related field AND 2+ years User Experience Research experience; OR equivalent experience. 1+ year(s) relevant domain experience within the technology sector. 1+ year(s) experience in research methods impacting both product direction and detailed experience design." We could keep as a paragraph. Now Qualifications (nice-to-have): "Doctorate in Human-Computer Interaction, Human Factors Engineering, Computer Science, Technical Communications, Information Science, Information Architecture, User Experience Design, Behavioral Science, Social Sciences, or a related field AND 2+ years user experience research experience; OR Master’s Degree in Human-Computer Interaction, Human Factors Engineering, Computer Science, Technical Communications, Information Science, Information Architecture, User Experience Design, Behavioral Science, Social Sciences, or a related field AND 3+ years user experience research experience; OR Bachelor’s Degree in Human-Computer Interaction, Human Factors Engineering, Computer Science, Technical Communications, Information Science, Information Architecture, User Experience Design, Behavioral Science, Social Sciences, or a related field AND 5+ years user experience research experience; OR equivalent experience." Now Skills bullet list: - English language proficiency, with clear, accurate, and understandable oral and written communication, presentations, and research writing skills. - Proficiency in qualitative and quantitative research methods, quality assurance, user acceptance testing, and user scenario creation and application. - Strong analytical thinking, data analysis, problem-solving, and translation of insights. - Experience with collaborative innovation, conflict resolution, distillation of results, industry trends, and stakeholder management. - Demonstrated decision-making ability, outcome-driven innovation, project management, project visioning, and scope management. - Creativity, interaction design, user experience, user interface design, and user-centered design principles. Now Benefits paragraph: "Subsidized health, vision, and dental plans; paid sick leave; retirement plans with a match; free online training through Aquent Gymnasium." We could also mention "Aquent Talent connects the best talent in marketing, creative, and design with the world’s biggest brands." but that's more about Aquent; maybe we can incorporate into benefits? But it's not a benefit per se. However we need to preserve substantive information. Could add a short paragraph under Benefits? Or maybe under About the role? But it's about Aquent Talent, not the role. The instruction says preserve ALL substantive information. So we need to include that somewhere. Could add a