Experience Research Senior Associate

We need to output HTML fragment with sections: h3 headings for sections present: About the role? The description includes "Job Description" intro paragraph, then responsibilities, then qualifications, then preferred qualifications, then About Us, then About The Team. Also maybe "Benefits" is mentioned in About Us: "We offer a competitive total rewards package..." includes benefits details. So we should include Benefits section. Pay? Not specific numbers, just "competitive total rewards package including base salary determined based on the role, experience, skill set and location." That's vague; we should not create Pay section unless posting actually states them. It says base salary determined based on role, experience, skill set and location – not a specific number or range. According to rules: 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 Benefits, they do list benefits: comprehensive health care coverage, on-site health and wellness centers, a retirement savings plan, backup childcare, tuition reimbursement, mental health support, financial coaching and more. That's specific enough. So Benefits section is okay. Schedule not mentioned, so omit. Pay: they mention base salary determined based on role, experience, skill set and location – that's vague but maybe considered not specific enough. The rule says never create Pay section unless posting actually states them. It does state base salary determined based on role, experience, skill set and location – that is a statement about pay but not a specific number. Might be considered too vague; safer to omit Pay section. We need to remove boilerplate: EEO, equal opportunity, scam warning, application instructions, cookie/navigation/legal. Also remove duplicated lines. We need to preserve all substantive information. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we should only include sections that have real specific content. We have: About the role (maybe the introductory paragraph). Could be "About the role". Responsibilities (list). Qualifications (maybe combine Required Qualifications and Preferred Qualifications? Could have "Required Qualifications" and "Preferred Qualifications" as separate headings? The instruction says use headings like Qualifications, Skills. But we can use "Required Qualifications" and "Preferred Qualifications" as headings? They said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So they expect those exact headings? It says e.g., meaning examples. We can use those headings. Probably better to map content to those headings: About the role (intro), Responsibilities, Qualifications (maybe combine required and preferred?), Skills (maybe separate?), Benefits. But we have both required and preferred qualifications; we could put them under Qualifications with subpoints? But we need to use

• for any list of duties/requirements/benefits. So we can have a

  Qualifications

  then
  with required and preferred items? Might be okay. Skills: we could list skills from qualifications: advanced proficiency in research methods, etc. But maybe we can skip Skills section if covered. Better to follow the example headings: About the role, Responsibilities, Qualifications, Benefits. Also maybe "About Us" and "About The Team" could be merged into About the role? But they are separate sections. The instruction didn't list About Us or About Team as example headings, but we could still use

  for those if they have content. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings. However we need to preserve all substantive information, including About Us and About The Team. We could incorporate that info into About the role section? Might lose nuance. But we could create additional headings like About Us and About The Team as

  as well; the instruction didn't forbid, just gave examples. I think it's okay to add those headings. We must not repeat the job title as a heading. The job title is "Experience Research Senior Associate in Connected Commerce – Banking Payments". Not to be used as heading. We must not put Job ID/requisition numbers as headings. We must remove boilerplate: EEO, equal opportunity, etc. We need to output only HTML fragment. Let's extract content: Intro paragraph: "Bring your industry trends and knowledge to our team and shape exceptional user experiences through cutting-edge research, influencing product design and functionality. As an Experience Research Senior Associate in Connected Commerce – Banking Payments, you will play a pivotal role in shaping user experiences across our products and services. Leveraging advanced proficiency in research methods, analysis, and both quantitative and qualitative techniques, identify customer needs and translate them into actionable insights and recommendations. You will act as a core contributor to aid in developing research studies that answer user needs. Your work will directly impact the design, architecture, and functionality of our offerings, collaborating with cross-functional teams to contribute to discussions on design and research, and leading the decision on which methods best suit key design questions." That's the About the role. Responsibilities list: - Conduct and execute research studies using advanced research methods, such as surveys, interviews, ethnography, and quantitative and qualitative techniques, to gather customer insights - Analyze and interpret data, identify patterns and trends, and provide actionable recommendations to inform user experience design decisions and facilitate improvements in customer satisfaction and engagement - Collaborate with cross-functional teams to ensure the integration of user insights into product development processes based on research findings - Contribute to the creation and refinement of experience research strategies and connect craft work to business goals and success metrics, taking into consideration downstream implications - Stay current with industry trends and incorporate knowledge into team insights Required Qualifications: - 3+ years of experience or equivalent expertise in generative and evaluative user experience research, employing advanced research methods and techniques - Demonstrated proficiency in both quantitative and qualitative research methods, including survey and interview design, ethnography, and data analysis - Advanced knowledge of user experience design principles and practices, with a focus on how ethnographic principles influence effective user experiences - Advanced understanding of current research methodologies, with the ability to review and understand how to apply current research practices to better inform experience designs Preferred Qualifications: - Experience applying research in finance or fintech - Mixed methods skillset, with a knack for leading teams through ambiguous problem spaces - Master's or PhD in a field with advanced research training About Us: - Chase is a leading financial services firm, helping nearly half of America's households and small businesses achieve their financial goals through a broad range of financial products. - Our mission is to create engaged, lifelong relationships and put our customers at the heart of everything we do. - We also help small businesses, nonprofits and cities grow, delivering solutions to solve all their financial needs. - We offer a competitive total rewards package including base salary determined based on the role, experience, skill set and location. Those in eligible roles may receive commission-based pay and/or discretionary incentive compensation, paid in the form of cash and/or forfeitable equity, awarded in recognition of individual achievements and contributions. - We also offer a range of benefits and programs to meet employee needs, based on eligibility. These benefits include comprehensive health care coverage, on-site health and wellness centers, a retirement savings plan, backup childcare, tuition reimbursement, mental health support, financial coaching and more. - Additional details about total compensation and benefits will be provided during the hiring process. - We recognize that our people are our strength and the diverse talents they bring to our global workforce are directly linked to our success. - We are an equal opportunity employer and place a high value on diversity and inclusion at our company. We do not discriminate on the basis of any protected attribute, including race, religion, color, national origin, gender, sexual orientation, gender identity, gender expression, age, marital or veteran status, pregnancy or disability, or any other basis protected under applicable law. - We also make reasonable accommodations for applicants' and employees' religious practices and beliefs, as well as mental health or physical disability needs. - Visit our FAQs for more information about requesting an accommodation. - Equal Opportunity Employer/Disability/Veterans We need to remove EEO/equal-opportunity boilerplate. So remove paragraphs about equal opportunity, disability, veterans, accommodations, FAQs, etc. Also remove "Equal Opportunity Employer/Disability/Veterans". Also remove "We also make reasonable accommodations..." etc. Also remove "Visit our FAQs...". Also remove "We are an equal opportunity employer..." etc. Also remove "Additional details about total compensation and benefits will be provided during the hiring process." maybe keep? It's about benefits but it's generic; could be considered filler? It's not specific benefit; but it's about benefits. Might keep as part of Benefits section? It's vague; but we already have specific benefits list. The line "Additional details about total compensation and benefits will be provided during the hiring process." is generic; could be considered filler. Might drop. Also remove "We recognize that our people are our strength..." maybe keep as part of About Us? It's substantive about company values. Keep. Now About The Team: - Our Consumer & Community Banking division serves our Chase customers through a range of financial services, including personal banking, credit cards, mortgages, auto financing, investment advice, small business loans and payment processing. - We're proud to lead the U.S. in credit card sales and deposit growth and have the most-used digital solutions – all while ranking first in customer satisfaction. - The Digital team is dedicated to creating innovative, industry-leading products and experiences that help customers access, share and control their financial data so they can make smart decisions with their money. - Teams enable innovation while adhering to the firm's data sharing principles of security, customer control and convenience, and privacy. We can keep that. Now we need to format. We'll have sections:

  About the role

  Intro paragraph.

  Responsibilities

  • ... each.

  Qualifications

  We could split into Required and Preferred as subheadings? But we only have h3 allowed; we could use

  Required Qualifications

  and

  Preferred Qualifications

  as they are still h3 headings. The instruction didn't forbid using other h3 headings. So we can do that. Thus:

  Required Qualifications

  ...

  Preferred Qualifications

  ...

  Benefits

  list benefits: comprehensive health care coverage, on-site health and wellness centers, a retirement savings plan, backup childcare, tuition reimbursement, mental health support, financial coaching and more.
  We might also include About Us and About The Team as sections.

  About Us

  Chase is a leading financial services firm... mission... also help small businesses... We recognize that our people are our strength...

  About The Team

  Our Consumer & Community Banking division... The Digital team is dedicated... Teams enable innovation...

  We need to ensure we didn't include any boilerplate like EEO. Check About Us paragraph: we kept mission, helping households, also help small businesses, we recognize that our people are our strength. We removed equal opportunity lines. Now check for any leftover boilerplate: The phrase "We also offer a range of benefits and programs to meet employee needs, based on eligibility." is part of Benefits? We moved benefits to list; we could keep that sentence as intro to benefits but it's generic. Might keep as

  before list. But it's not specific; maybe we can keep as part of Benefits section intro. It's not