Insights Director
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content. No job title heading. No Job ID etc. Remove boilerplate like EEO, legal, etc. Must preserve all substantive info.
We need to parse the posting.
Key sections:
- Key Responsibilities (list)
- JOB DESCRIPTION (some prose)
- The Ideal Candidate has the following Skills, Experience, and Attributes (list)
- In order to comply... US Citizen requirement (maybe part of Requirements)
- If you don’t meet 100%... (maybe not needed)
- We may consider... (maybe not needed)
- In accordance with NY/CO/CA/WA law, the estimated base salary range for this role is $125,000 to $135,000. (Pay)
- Your final base salary will be determined... (maybe part of Pay)
- What’s In It For You At Ipsos you’ll experience opportunities for Career Development, an exceptional benefits package (including generous PTO, healthcare plans, wellness benefits), a flexible workplace policy, and a strong collaborative culture. (Benefits)
- Benefits To find out more... (maybe link but we can drop as boilerplate? It's a link to benefits page; but it's still benefits info. Might keep as prose.)
- Commitment to Diversity (maybe not needed as boilerplate? It's EEO/diversity statement; we should remove as per instruction: remove EEO/equal-opportunity boilerplate. So drop.
- About Us (maybe not needed? It's about company; could be considered boilerplate? Not explicitly listed to remove, but it's generic. Might keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Us is not necessarily boilerplate but could be considered generic. However we need to preserve ALL substantive information; not invent or summarize away detail. About Us is substantive about company. Might keep as a section? But we only have headings list; we could use About the role
etc. There's no explicit "About Us" heading in allowed list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit content into those headings. About Us could go under About the role? Probably not. Maybe we can omit About Us as it's not required heading; but we must preserve ALL substantive information. However we can't create new headings beyond allowed list. 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, not exclusive? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we must map content to those sections.
Thus we need to decide which sections to include based on content.
- About the role: could contain overview of role, maybe from JOB DESCRIPTION paragraph.
- Responsibilities: list of duties.
- Requirements: maybe citizenship, experience, education.
- Qualifications: maybe degree, experience.
- Skills: list of skills.
- Benefits: benefits description.
- Pay: salary range.
- Schedule: not mentioned; we should not include if no content.
We must not include sections with filler like "commensurate with experience". We have salary range, so Pay section is valid.
We need to preserve all substantive info: responsibilities list, ideal candidate skills/experience/attributes, US Citizen requirement, benefits, salary range, maybe also note about flexible workplace policy, career development, etc.
We must remove duplicated lines, boilerplate like EEO, legal, etc. Also remove application instructions (like "If you don’t meet 100%..." maybe that's encouraging to apply; could be considered application instruction? It's not exactly instruction to apply but encourages. Might be considered boilerplate; but it's substantive? It's more about encouraging to apply; could be removed as application instruction. Safer to remove.
Also remove "We may consider a variety of backgrounds..." maybe also application instruction.
We must keep US Citizen requirement as it's a requirement.
Now craft HTML.
Structure:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we must map content to those sections.
Thus we need to decide which sections to include based on content.
- About the role: could contain overview of role, maybe from JOB DESCRIPTION paragraph.
- Responsibilities: list of duties.
- Requirements: maybe citizenship, experience, education.
- Qualifications: maybe degree, experience.
- Skills: list of skills.
- Benefits: benefits description.
- Pay: salary range.
- Schedule: not mentioned; we should not include if no content.
We must not include sections with filler like "commensurate with experience". We have salary range, so Pay section is valid.
We need to preserve all substantive info: responsibilities list, ideal candidate skills/experience/attributes, US Citizen requirement, benefits, salary range, maybe also note about flexible workplace policy, career development, etc.
We must remove duplicated lines, boilerplate like EEO, legal, etc. Also remove application instructions (like "If you don’t meet 100%..." maybe that's encouraging to apply; could be considered application instruction? It's not exactly instruction to apply but encourages. Might be considered boilerplate; but it's substantive? It's more about encouraging to apply; could be removed as application instruction. Safer to remove.
Also remove "We may consider a variety of backgrounds..." maybe also application instruction.
We must keep US Citizen requirement as it's a requirement.
Now craft HTML.
Structure:
About the role
... overview from JOB DESCRIPTION: To understand the background and intent of client requests (participating in kick-off calls, reviewing proposals and market research briefs) Includes taking the time to develop a deeper understanding of the clients’ categories and key competitors Lead the development of research plans and proposals (adhering to PRS IN VIVO best practices, services, and visual guidelines) Willingness to get their ‘hands dirty’ with nitty-gritty of research process, if necessary, including screeners, questionnaire design, scripting surveys, etc. Managing / directing projects from start to finish including close collaboration with PM/fieldwork department Writing and presenting strategic reports of findings in PowerPoint Assisting with (and eventually leading) debrief presentations Develop (or learn how to develop) client relationships outside of individual studies to grow revenue
But that's basically responsibilities; maybe better to put overview in About the role short paragraph, then Responsibilities list. Let's extract overview: "To understand the background and intent of client requests (participating in kick-off calls, reviewing proposals and market research briefs) Includes taking the time to develop a deeper understanding of the clients’ categories and key competitors Lead the development of research plans and proposals (adhering to PRS IN VIVO best practices, services, and visual guidelines) Willingness to get their ‘hands dirty’ with nitty-gritty of research process, if necessary, including screeners, questionnaire design, scripting surveys, etc. Managing / directing projects from start to finish including close collaboration with PM/fieldwork department Writing and presenting strategic reports of findings in PowerPoint Assisting with (and eventually leading) debrief presentations Develop (or learn how to develop) client relationships outside of individual studies to grow revenue" That's essentially responsibilities. So maybe About the role can be a brief summary: "The role involves understanding client briefs, leading research plan development, managing projects end-to-end, delivering strategic reports, and growing client relationships." We must not invent; we need to preserve info, not summarize away detail. Summarizing may be considered summarizing away detail? The instruction: "Do NOT invent or summarize away detail." So we should not summarize; we should keep the detail. But we can keep the same sentences as prose in About the role. However that duplicates responsibilities. Maybe we can put the whole block as About the role prose, and then Responsibilities as a list of bullet points derived from same sentences? That would be duplicating. Better to have About the role as a short paragraph that captures the essence but not lose detail? The instruction says not to summarize away detail, meaning we shouldn't omit details. If we write a short paragraph that omits some details, that's summarizing away detail. So we should keep the detail in the appropriate section. Perhaps we can treat About the role as a short intro that is not required to be exhaustive; but we risk violating. Safer: we can omit About the role section entirely if we don't have specific content beyond responsibilities. But we need to include sections only when posting has real, specific content for it. The posting does have a "JOB DESCRIPTION" block which is essentially responsibilities. So we could put that under Responsibilities as a list, and not have About the role. The instruction: "Prefer a few substantive sections over many thin ones." So we can have Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. That's enough. Thus we will not include About the role. Now Responsibilities: we need to convert the responsibilities into- . The responsibilities are described in sentences; we can break them into bullet points. List: - Understand the background and intent of client requests (participating in kick-off calls, reviewing proposals and market research briefs) - Develop a deeper understanding of the clients’ categories and key competitors - Lead the development of research plans and proposals (adhering to PRS IN VIVO best practices, services, and visual guidelines) - Get hands‑dirty with the nitty‑gritty of the research process when needed, including screeners, questionnaire design, scripting surveys, etc. - Manage/direct projects from start to finish, collaborating closely with PM/fieldwork department - Write and present strategic reports of findings in PowerPoint - Assist with and eventually lead debrief presentations - Develop (or learn how to develop) client relationships outside of individual studies to grow revenue That seems comprehensive. Now Requirements: include US Citizen requirement, maybe also "8+ years of experience in a top research consultancy, or as a brand strategist in an ad agency, consultancy or market research environment, ideally with CPG/FMCG clients and/or shopper/packaging/ NPD/ retail research". Also "BA/BS in related field". Also maybe "Experience with quantitative and qualitative analysis". Also "Proven ability to take responsibility, think analytically, and communicate clearly". Also "Understanding of questionnaire design and creation". Also "Knowledge and interest in new-tech and digital research solutions essential". Also "Strong writing and analytical ability – knowing how to convert data and analysis into stories". Also "Written and oral communication – used to correspond clearly and concisely with clients, outside vendors, and internal departments". Also "Creating instruction materials for our internal and external field partners". Also "Attending client briefings and debriefs". Also "Good understanding of quantitative metrics and experience in combined qual-quant projects execution and analysis preferred". Also "Strong experience in qualitative consumer research". Also "IT skills focusing on Word, Excel and PowerPoint, video editing is a plus". Also "Must be able to work independently, yet be comfortable asking questions". Also US Citizen. But many of these overlap with Skills. We need to separate Requirements vs Qualifications vs Skills. The posting lumps them under "The Ideal Candidate has the following Skills, Experience, and Attributes". So we could treat that as Skills section. Requirements could be things like US Citizen, 8+ years experience, BA/BS. Qualifications maybe degree? But we have limited headings. We could put experience and education under Requirements, and skills under Skills. Qualifications maybe not needed. Let's decide: - Requirements: US Citizen, 8+ years experience in top research consultancy or brand strategist, BA/BS in related field. - Qualifications: maybe not needed; we could omit. - Skills: list of skills: quantitative and qualitative analysis, analytical thinking, communication, questionnaire design, new-tech/digital research, writing/storytelling, oral/written communication, creating instruction materials, attending briefings/debriefs, quantitative metrics, combined qual-quant, qualitative consumer research, IT skills (Word, Excel, PowerPoint, video editing plus), independent work, asking questions. We need to avoid duplication. Some items appear in both lists; we need to ensure we keep all substantive info but not duplicate exactly same phrase. We can merge similar items. Let's extract from the "Ideal Candidate" paragraph: "8+ years of experience in a top research consultancy, or as a brand strategist in an ad agency, consultancy or market research environment, ideally with CPG/FMCG clients and/or shopper/packaging/ NPD/ retail research" "BA/BS in related field" "Experience with quantitative and qualitative analysis" "Proven ability to take responsibility, think analytically, and communicate clearly" "Understanding of questionnaire design and creation" "Knowledge and interest in new-tech and digital research solutions essential" "Strong writing and analytical ability – knowing how to convert data and analysis into stories" "Written and oral communication – used to correspond clearly and concisely with clients, outside vendors, and internal departments" "Creating instruction materials for our internal and external field partners" "Attending client briefings and debriefs" "Good understanding of quantitative metrics and experience in combined qual-quant projects execution