Vice President | Research, Insight & Consulting | US
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content. The posting includes: About Us (maybe not needed as heading? It's not listed as a required heading but we could treat as About the role? Actually "About the Role" is present. We need to use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create headings for sections that exist: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly.
Let's parse the posting:
- Title: Vice President (not to repeat as heading)
- Location: open to candidates working East Coast hours from anywhere in the US, or hybrid from New York office.
- About Us: description of company.
- About the Role: description of duties.
- About You: qualifications/requirements.
- Essential: list of requirements.
- And in return, Savanta offers: bullet list of benefits.
- Why Join Us: more description (maybe could be part of About the role or Benefits? but we can include as separate section? Not in list of allowed headings; but we could omit or incorporate into About the role or Benefits. Probably better to not create extra headings not in list; we can incorporate into existing sections.
We need to avoid boilerplate: EEO, visa sponsorship note, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Please click here to view the full job description", "Why Join Us" maybe not boilerplate but could be considered promotional; but we can keep if substantive. However we must only include sections when posting has real specific content. "Why Join Us" has some content about culture, career development, etc. Could be considered as part of About the role or Benefits? Might be okay to include as a separate section but not in allowed headings list. 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 says "Use for section headings (e.g. ...)" implying we should use those headings for sections. It might be okay to add other headings but better to stick to those. We can incorporate "Why Join Us" content into About the role or Benefits.
We need to output only HTML fragment, no /, no markdown fences.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We must preserve ALL substantive information; do NOT invent or summarize away detail.
We need to remove boilerplate: EEO, visa sponsorship note, "All candidates will be considered equally, however, unfortunately we are unable to offer visa sponsorship." Also "We encourage authentic responses..." etc. Also "For information on how Savanta uses your data, please see ..." Remove.
Also remove duplicated lines.
Now let's extract substantive content:
About Us: "Savanta is a leading data, market research and advisory company helping the world's leading brands make better decisions, faster. With over 500 people across offices in multiple countries, we combine deep research expertise, proprietary technology and high-impact consulting to give our clients a complete view of their markets, their customers and their competitors."
About the Role: "As Vice President, you will bring your curiosity and insight storytelling to lead research programs that help answer strategic questions for your clients. You'll own and grow an existing account portfolio, acting as a strategic advisor to clients while identifying new business opportunities that drive sustainable, double-digit year-over-year growth. Running high-level pitches to C-suite audiences, managing a commercial pipeline, and helping to shape the broader growth strategy for the Americas team all sit within your remit. You'll also lead and develop a high-performing team, setting clear progression plans, managing performance, and fostering a culture of innovation and client obsession, while bringing a tech-first mindset that pushes both team and clients toward faster, technology-enabled ways of generating insight."
About You / Requirements: "We're not looking for expertise in a specific sector, though prior experience in financial services research would be a strong advantage. What matters most is strong market research experience across both quantitative and mixed methodologies, paired with the commercial acumen and leadership capability to manage a high-performing team and act as a trusted advisor to senior stakeholders. You'll be a fast-paced, autonomous operator, comfortable delegating to senior and mid-level team members while retaining accountability for revenue, delivery quality, and team performance. The role also works with leads across regions to share best practice and support global client relationships that intersect with Americas accounts."
Essential list:
- 8+ years of experience in market research, insights, or a related consulting field.
- Proven track record of managing and growing client revenue.
- Experience leading and developing a team, including managing performance and career progression.
- A genuine tech-first mindset, comfortable championing new technology and AI-enabled approaches over traditional research methods.
- Strong communication and relationship-building skills, with the ability to operate as a strategic partner to senior client stakeholders.
Benefits (And in return, Savanta offers):
- Salary range: $140,000 +
- Bonus/Commission scheme
- Generous PTO Allowance
- Ongoing Training & Development
- Flexible working practices
- Health package
- Retirement plan
- Team & Company Socials
- Committees for Health & Well Being, Charities & Volunteering and DE&I
Why Join Us content: "This is an opportunity to step into a visible leadership role within our growing US team, with strong client exposure and varied sector experience. You’ll work as part of a collaborative global team, overseeing key research projects, proposals, business development and the future direction of the team. Part of the vibrant Next 15 Communications Group, we have an entrepreneurial and inclusive company culture that actively recognizes and values its people and offers unrivalled scope for career development, including mentoring, coaching as well as extensive training programs. The company was founded on the belief that tech should be integral to its success, and this culture of tech innovation makes us best placed to put Savanta at the heart of our clients’ businesses offering solutions before they even know the problem."
We could incorporate this into About the role or Benefits. Perhaps better to add a section "About the Company" but not in list. Could incorporate into About the role as extra paragraph.
We need to avoid creating Pay/Schedule/Benefits sections unless posting actually states them. We have Pay: Salary range: $140,000 + Bonus/Commission scheme. So we can create a Pay section. Benefits: we have many items. Schedule: not mentioned explicitly; only "Flexible working practices" maybe implies schedule but not explicit. We should not create Schedule section unless posting actually states them. It does not state specific schedule, so we omit Schedule.
We need to include sections only when posting has real specific content. So we will have:
About the role
(maybe also include About Us? Could be separate but not required; we could incorporate About Us into About the role or have a separate About the company but not in list. Safer to include About the role as given, and maybe add a paragraph about About Us inside it? But the About the role section already has content; we could add another about About Us before or after. However the instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings but we should follow that pattern. We could have About the role, Responsibilities (maybe we can split duties into Responsibilities), Requirements, Qualifications, Skills, Benefits, Pay. But we need to avoid thin sections. Let's think.
We have duties described in About the Role paragraph. Could treat that as Responsibilities. We have qualifications/experience in About You and Essential list. Could split into Requirements (essential) and Qualifications (maybe preferred). Skills could be communication, tech-first mindset, etc. Benefits we have. Pay we have.
We need to avoid creating sections with filler like "commensurate with experience". We have concrete data.
Thus we can structure:
About the role
maybe short intro? But we already have About the role content; maybe we treat that as Responsibilities. Actually the posting has "About the Role:" heading. So we should use that as a heading. So About the role
with the paragraph(s) from About the Role.
Then we need Responsibilities? Could be duplicate. But we could treat the About the role as Responsibilities. However the instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we could have both About the role and Responsibilities separate if content exists. But we have only one block describing role; we could split into About the role (brief overview) and Responsibilities (list of duties). But we don't have a separate brief overview; the About the role paragraph already includes duties. To avoid thin sections, we could just have About the role and treat it as the description; we could omit Responsibilities. But the instruction says "Prefer a few substantive sections over many thin ones." So better to have fewer sections.
Thus we could have sections: About the role (includes description), Requirements (includes essential list and maybe About You), Benefits, Pay. Possibly Skills could be included within Requirements.
But we need to follow the instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must use all of them, just that if we use a heading, it should be one of those examples. So we can choose which to include.
Thus we will output:
About the role
... (combined About the Role paragraph plus maybe About Us? Actually About Us is separate; we could include it as a paragraph under About the role or as its own section? Not in list. Safer to include About Us as a paragraph under About the role? But About Us is about company, not role. Could be separate section "About the company" but not allowed. Could incorporate into About the role as context. I'd include a brief paragraph about Savanta (About Us) as part of About the role section, as it's substantive and relevant.
Thus
About the role
Savanta is a leading data, market research and advisory company helping the world's leading brands make better decisions, faster. With over 500 people across offices in multiple countries, we combine deep research expertise, proprietary technology and high-impact consulting to give our clients a complete view of their markets, their customers and their competitors.
As Vice President, you will bring your curiosity and insight storytelling to lead research programs that help answer strategic questions for your clients. You'll own and grow an existing account portfolio, acting as a strategic advisor to clients while identifying new business opportunities that drive sustainable, double-digit year-over-year growth. Running high-level pitches to C-suite audiences, managing a commercial pipeline, and helping to shape the broader growth strategy for the Americas team all sit within your remit. You'll also lead and develop a high-performing team, setting clear progression plans, managing performance, and fostering a culture of innovation and client obsession, while bringing a tech-first mindset that pushes both team and clients toward faster, technology-enabled ways of generating insight.
Then Requirements
We need to include both About You and Essential list. Could combine into a - list. But we also have prose about not looking for specific sector, etc. That could be a
then list.
Thus:
Requirements
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use for section headings (e.g. ...)" implying we should use those headings for sections. It might be okay to add other headings but better to stick to those. We can incorporate "Why Join Us" content into About the role or Benefits.
We need to output only HTML fragment, no /, no markdown fences.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We must preserve ALL substantive information; do NOT invent or summarize away detail.
We need to remove boilerplate: EEO, visa sponsorship note, "All candidates will be considered equally, however, unfortunately we are unable to offer visa sponsorship." Also "We encourage authentic responses..." etc. Also "For information on how Savanta uses your data, please see ..." Remove.
Also remove duplicated lines.
Now let's extract substantive content:
About Us: "Savanta is a leading data, market research and advisory company helping the world's leading brands make better decisions, faster. With over 500 people across offices in multiple countries, we combine deep research expertise, proprietary technology and high-impact consulting to give our clients a complete view of their markets, their customers and their competitors."
About the Role: "As Vice President, you will bring your curiosity and insight storytelling to lead research programs that help answer strategic questions for your clients. You'll own and grow an existing account portfolio, acting as a strategic advisor to clients while identifying new business opportunities that drive sustainable, double-digit year-over-year growth. Running high-level pitches to C-suite audiences, managing a commercial pipeline, and helping to shape the broader growth strategy for the Americas team all sit within your remit. You'll also lead and develop a high-performing team, setting clear progression plans, managing performance, and fostering a culture of innovation and client obsession, while bringing a tech-first mindset that pushes both team and clients toward faster, technology-enabled ways of generating insight."
About You / Requirements: "We're not looking for expertise in a specific sector, though prior experience in financial services research would be a strong advantage. What matters most is strong market research experience across both quantitative and mixed methodologies, paired with the commercial acumen and leadership capability to manage a high-performing team and act as a trusted advisor to senior stakeholders. You'll be a fast-paced, autonomous operator, comfortable delegating to senior and mid-level team members while retaining accountability for revenue, delivery quality, and team performance. The role also works with leads across regions to share best practice and support global client relationships that intersect with Americas accounts."
Essential list:
- 8+ years of experience in market research, insights, or a related consulting field.
- Proven track record of managing and growing client revenue.
- Experience leading and developing a team, including managing performance and career progression.
- A genuine tech-first mindset, comfortable championing new technology and AI-enabled approaches over traditional research methods.
- Strong communication and relationship-building skills, with the ability to operate as a strategic partner to senior client stakeholders.
Benefits (And in return, Savanta offers):
- Salary range: $140,000 +
- Bonus/Commission scheme
- Generous PTO Allowance
- Ongoing Training & Development
- Flexible working practices
- Health package
- Retirement plan
- Team & Company Socials
- Committees for Health & Well Being, Charities & Volunteering and DE&I
Why Join Us content: "This is an opportunity to step into a visible leadership role within our growing US team, with strong client exposure and varied sector experience. You’ll work as part of a collaborative global team, overseeing key research projects, proposals, business development and the future direction of the team. Part of the vibrant Next 15 Communications Group, we have an entrepreneurial and inclusive company culture that actively recognizes and values its people and offers unrivalled scope for career development, including mentoring, coaching as well as extensive training programs. The company was founded on the belief that tech should be integral to its success, and this culture of tech innovation makes us best placed to put Savanta at the heart of our clients’ businesses offering solutions before they even know the problem."
We could incorporate this into About the role or Benefits. Perhaps better to add a section "About the Company" but not in list. Could incorporate into About the role as extra paragraph.
We need to avoid creating Pay/Schedule/Benefits sections unless posting actually states them. We have Pay: Salary range: $140,000 + Bonus/Commission scheme. So we can create a Pay section. Benefits: we have many items. Schedule: not mentioned explicitly; only "Flexible working practices" maybe implies schedule but not explicit. We should not create Schedule section unless posting actually states them. It does not state specific schedule, so we omit Schedule.
We need to include sections only when posting has real specific content. So we will have:
About the role
(maybe also include About Us? Could be separate but not required; we could incorporate About Us into About the role or have a separate About the company but not in list. Safer to include About the role as given, and maybe add a paragraph about About Us inside it? But the About the role section already has content; we could add another about About Us before or after. However the instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings but we should follow that pattern. We could have About the role, Responsibilities (maybe we can split duties into Responsibilities), Requirements, Qualifications, Skills, Benefits, Pay. But we need to avoid thin sections. Let's think.
We have duties described in About the Role paragraph. Could treat that as Responsibilities. We have qualifications/experience in About You and Essential list. Could split into Requirements (essential) and Qualifications (maybe preferred). Skills could be communication, tech-first mindset, etc. Benefits we have. Pay we have.
We need to avoid creating sections with filler like "commensurate with experience". We have concrete data.
Thus we can structure:
About the role
maybe short intro? But we already have About the role content; maybe we treat that as Responsibilities. Actually the posting has "About the Role:" heading. So we should use that as a heading. So About the role
with the paragraph(s) from About the Role.
Then we need Responsibilities? Could be duplicate. But we could treat the About the role as Responsibilities. However the instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we could have both About the role and Responsibilities separate if content exists. But we have only one block describing role; we could split into About the role (brief overview) and Responsibilities (list of duties). But we don't have a separate brief overview; the About the role paragraph already includes duties. To avoid thin sections, we could just have About the role and treat it as the description; we could omit Responsibilities. But the instruction says "Prefer a few substantive sections over many thin ones." So better to have fewer sections.
Thus we could have sections: About the role (includes description), Requirements (includes essential list and maybe About You), Benefits, Pay. Possibly Skills could be included within Requirements.
But we need to follow the instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must use all of them, just that if we use a heading, it should be one of those examples. So we can choose which to include.
Thus we will output:
About the role
... (combined About the Role paragraph plus maybe About Us? Actually About Us is separate; we could include it as a paragraph under About the role or as its own section? Not in list. Safer to include About Us as a paragraph under About the role? But About Us is about company, not role. Could be separate section "About the company" but not allowed. Could incorporate into About the role as context. I'd include a brief paragraph about Savanta (About Us) as part of About the role section, as it's substantive and relevant.
Thus
About the role
Savanta is a leading data, market research and advisory company helping the world's leading brands make better decisions, faster. With over 500 people across offices in multiple countries, we combine deep research expertise, proprietary technology and high-impact consulting to give our clients a complete view of their markets, their customers and their competitors.
As Vice President, you will bring your curiosity and insight storytelling to lead research programs that help answer strategic questions for your clients. You'll own and grow an existing account portfolio, acting as a strategic advisor to clients while identifying new business opportunities that drive sustainable, double-digit year-over-year growth. Running high-level pitches to C-suite audiences, managing a commercial pipeline, and helping to shape the broader growth strategy for the Americas team all sit within your remit. You'll also lead and develop a high-performing team, setting clear progression plans, managing performance, and fostering a culture of innovation and client obsession, while bringing a tech-first mindset that pushes both team and clients toward faster, technology-enabled ways of generating insight.
Then Requirements
We need to include both About You and Essential list. Could combine into a - list. But we also have prose about not looking for specific sector, etc. That could be a
then list.
Thus:
Requirements
- for any list of duties/requirements/benefits, and
for prose. We must preserve ALL substantive information; do NOT invent or summarize away detail. We need to remove boilerplate: EEO, visa sponsorship note, "All candidates will be considered equally, however, unfortunately we are unable to offer visa sponsorship." Also "We encourage authentic responses..." etc. Also "For information on how Savanta uses your data, please see ..." Remove. Also remove duplicated lines. Now let's extract substantive content: About Us: "Savanta is a leading data, market research and advisory company helping the world's leading brands make better decisions, faster. With over 500 people across offices in multiple countries, we combine deep research expertise, proprietary technology and high-impact consulting to give our clients a complete view of their markets, their customers and their competitors." About the Role: "As Vice President, you will bring your curiosity and insight storytelling to lead research programs that help answer strategic questions for your clients. You'll own and grow an existing account portfolio, acting as a strategic advisor to clients while identifying new business opportunities that drive sustainable, double-digit year-over-year growth. Running high-level pitches to C-suite audiences, managing a commercial pipeline, and helping to shape the broader growth strategy for the Americas team all sit within your remit. You'll also lead and develop a high-performing team, setting clear progression plans, managing performance, and fostering a culture of innovation and client obsession, while bringing a tech-first mindset that pushes both team and clients toward faster, technology-enabled ways of generating insight." About You / Requirements: "We're not looking for expertise in a specific sector, though prior experience in financial services research would be a strong advantage. What matters most is strong market research experience across both quantitative and mixed methodologies, paired with the commercial acumen and leadership capability to manage a high-performing team and act as a trusted advisor to senior stakeholders. You'll be a fast-paced, autonomous operator, comfortable delegating to senior and mid-level team members while retaining accountability for revenue, delivery quality, and team performance. The role also works with leads across regions to share best practice and support global client relationships that intersect with Americas accounts." Essential list: - 8+ years of experience in market research, insights, or a related consulting field. - Proven track record of managing and growing client revenue. - Experience leading and developing a team, including managing performance and career progression. - A genuine tech-first mindset, comfortable championing new technology and AI-enabled approaches over traditional research methods. - Strong communication and relationship-building skills, with the ability to operate as a strategic partner to senior client stakeholders. Benefits (And in return, Savanta offers): - Salary range: $140,000 + - Bonus/Commission scheme - Generous PTO Allowance - Ongoing Training & Development - Flexible working practices - Health package - Retirement plan - Team & Company Socials - Committees for Health & Well Being, Charities & Volunteering and DE&I Why Join Us content: "This is an opportunity to step into a visible leadership role within our growing US team, with strong client exposure and varied sector experience. You’ll work as part of a collaborative global team, overseeing key research projects, proposals, business development and the future direction of the team. Part of the vibrant Next 15 Communications Group, we have an entrepreneurial and inclusive company culture that actively recognizes and values its people and offers unrivalled scope for career development, including mentoring, coaching as well as extensive training programs. The company was founded on the belief that tech should be integral to its success, and this culture of tech innovation makes us best placed to put Savanta at the heart of our clients’ businesses offering solutions before they even know the problem." We could incorporate this into About the role or Benefits. Perhaps better to add a section "About the Company" but not in list. Could incorporate into About the role as extra paragraph. We need to avoid creating Pay/Schedule/Benefits sections unless posting actually states them. We have Pay: Salary range: $140,000 + Bonus/Commission scheme. So we can create a Pay section. Benefits: we have many items. Schedule: not mentioned explicitly; only "Flexible working practices" maybe implies schedule but not explicit. We should not create Schedule section unless posting actually states them. It does not state specific schedule, so we omit Schedule. We need to include sections only when posting has real specific content. So we will have:
About the role
(maybe also include About Us? Could be separate but not required; we could incorporate About Us into About the role or have a separate About the company but not in list. Safer to include About the role as given, and maybe add a paragraph about About Us inside it? But the About the role section already has content; we could add anotherabout About Us before or after. However the instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings but we should follow that pattern. We could have About the role, Responsibilities (maybe we can split duties into Responsibilities), Requirements, Qualifications, Skills, Benefits, Pay. But we need to avoid thin sections. Let's think. We have duties described in About the Role paragraph. Could treat that as Responsibilities. We have qualifications/experience in About You and Essential list. Could split into Requirements (essential) and Qualifications (maybe preferred). Skills could be communication, tech-first mindset, etc. Benefits we have. Pay we have. We need to avoid creating sections with filler like "commensurate with experience". We have concrete data. Thus we can structure:
About the role
maybe short intro? But we already have About the role content; maybe we treat that as Responsibilities. Actually the posting has "About the Role:" heading. So we should use that as a heading. SoAbout the role
with the paragraph(s) from About the Role. Then we need Responsibilities? Could be duplicate. But we could treat the About the role as Responsibilities. However the instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we could have both About the role and Responsibilities separate if content exists. But we have only one block describing role; we could split into About the role (brief overview) and Responsibilities (list of duties). But we don't have a separate brief overview; the About the role paragraph already includes duties. To avoid thin sections, we could just have About the role and treat it as the description; we could omit Responsibilities. But the instruction says "Prefer a few substantive sections over many thin ones." So better to have fewer sections. Thus we could have sections: About the role (includes description), Requirements (includes essential list and maybe About You), Benefits, Pay. Possibly Skills could be included within Requirements. But we need to follow the instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must use all of them, just that if we use a heading, it should be one of those examples. So we can choose which to include. Thus we will output:
About the role
... (combined About the Role paragraph plus maybe About Us? Actually About Us is separate; we could include it as a paragraph under About the role or as its own section? Not in list. Safer to include About Us as a paragraph under About the role? But About Us is about company, not role. Could be separate section "About the company" but not allowed. Could incorporate into About the role as context. I'd include a brief paragraph about Savanta (About Us) as part of About the role section, as it's substantive and relevant. Thus
About the role
Savanta is a leading data, market research and advisory company helping the world's leading brands make better decisions, faster. With over 500 people across offices in multiple countries, we combine deep research expertise, proprietary technology and high-impact consulting to give our clients a complete view of their markets, their customers and their competitors.
As Vice President, you will bring your curiosity and insight storytelling to lead research programs that help answer strategic questions for your clients. You'll own and grow an existing account portfolio, acting as a strategic advisor to clients while identifying new business opportunities that drive sustainable, double-digit year-over-year growth. Running high-level pitches to C-suite audiences, managing a commercial pipeline, and helping to shape the broader growth strategy for the Americas team all sit within your remit. You'll also lead and develop a high-performing team, setting clear progression plans, managing performance, and fostering a culture of innovation and client obsession, while bringing a tech-first mindset that pushes both team and clients toward faster, technology-enabled ways of generating insight.
ThenRequirements
We need to include both About You and Essential list. Could combine into a- list. But we also have prose about not looking for specific sector, etc. That could be a
then list. Thus:
Requirements
- list. But we also have prose about not looking for specific sector, etc. That could be a