SVP, Research & Insights - Experience & Design Org
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. The page already shows it, so we don't add a heading for SVP, Research & Insights.
We must not put Job ID/requisition numbers as headings.
We must output only HTML fragment.
Let's craft.
Structure:
About the role
...
Then Responsibilities:
Responsibilities
- ...
...
We need to extract responsibilities from "What You Will Lead" and "What You Will Do". Could combine.
What You Will Lead bullet points: list of 4 capabilities with sub-bullets. We'll flatten into li items.
What You Will Do list: many items.
We'll combine.
Then Requirements/Qualifications: maybe separate Requirements and Qualifications? The instruction says use headings for Requirements, Qualifications, Skills. We could put Requirements as "What You Bring" (experience). Qualifications maybe "Your leadership signature". Skills maybe list of specific skills.
But we must only include sections when posting has real specific content. All three have content.
Let's define:
Requirements
A record of leading Research across a complex, multi-product enterprise, platform, or ecosystem at significant scale. Evidence that research you personally led changed product strategy, architecture, investment, operating decisions, or shipped experiences, not merely stakeholder understanding.
Qualifications
You are a truth-teller with product consequence. You combine deep curiosity and methodological rigor with exceptional product judgment. You can hold contradiction, identify the non-obvious implication, and make complex evidence clear without manufacturing certainty. You are independent without becoming distant from the work, and influential without allowing stakeholder preference to rewrite what is true.
Skills
- Deep expertise across qualitative research, behavioral science, mixed methods, experimentation, measurement, and interpretation of product and production data.
- Meaningful experience with AI, automation, human factors, intelligent systems, trust, or human-machine collaboration.
- Ability to reconstruct how complex domains and people actually work across roles, systems, incentives, constraints, implementations, and time.
- Demonstrated strength in foundational research, generative product influence, continuous evaluation, and enterprise synthesis.
- Experience integrating qualitative, quantitative, behavioral, commercial, implementation, and service evidence without overstating certainty or confusing correlation with customer understanding.
- Executive presence and organizational courage sufficient to challenge powerful stakeholders, protect difficult findings, and redirect consequential decisions.
- Experience leading a centrally connected research organization with senior portfolio leaders and deeply embedded teams.
- Record of identifying, recruiting, and developing exceptional research leaders and distinguished practitioners.
Benefits:
Benefits
- Time off programs
- Medical, dental, vision
- Mental health support
- Paid parental leave
- Life and disability insurance
- 401(k)
- Employee stock purchasing program
Pay:
Pay
The typical base salary range for this position is $399,000 - $453,000 annually. In select cities within the San Francisco and New York City metropolitan area, the base salary range for this role is $399,000 - $453,000 annually. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable.
We should also include maybe a short paragraph about the role under About the role.
About the role: combine the intro paragraphs about Salesforce and the role description.
We need to avoid boilerplate like "To get the best candidate experience..." etc. Also avoid "Accommodations", "Apply today", "Unleash Your Potential" (maybe part of benefits but we already have benefits). We'll keep About the role as:
SVP, Research & Insights - Experience & Design Org. The next Salesforce will be shaped by how well people and agents can understand one another, share context, delegate authority, recover from failure, and accomplish meaningful outcomes together. These behaviors unfold across roles, products, implementations, data, policies, channels, and time. They cannot be understood through episodic studies or a single adoption metric. The SVP, Research + Insights will lead Research across Salesforce Experience Design and build a continuous intelligence capability spanning Customer 360, Platform, Data 360, Agentforce, Slack, and emerging surfaces. Reporting to the EVP, Chief Experience Officer, this executive will move Research further upstream into enterprise and product strategy while extending evaluation through implementation, production, and longitudinal use.
That seems good.
Now responsibilities: combine What You Will Lead and What You Will Do.
Let's extract What You Will Lead bullet points:
- Enterprise Experience Intelligence + Foresight. Foundational domain research, longitudinal customer programs, strategic opportunity intelligence, ecosystem and competitive synthesis, failed-adoption and win/loss evidence, foresight, and executive synthesis.
- Portfolio Research + Insights. Deeply embedded research leadership and teams serving Salesforce's major product portfolios while operating within one enterprise agenda, talent system, evidence standard, and knowledge environment.
- Human-Agent Research, Evaluation + Measurement. Human factors, behavioral science, trust and delegation, agent-behavior evaluation, scenario and rubric development, production-evidence interpretation, and experience-outcome measurement.
- Research Operations + Knowledge. Participant systems, customer access, governance and ethics, methods and standards, knowledge infrastructure, evidence taxonomy, tooling, vendors, and research program operations.
What You Will Do list:
- Establish one enterprise Research + Insights agenda tied to Salesforce's most consequential customer, product, platform, architecture, and business decisions.
- Build Experience Intelligence as a live, cumulative understanding of how customers, industries, organizations, roles, and work actually operate and how they change over time.
- Ensure foundational, generative, and evaluative research shape product strategy before solution direction and roadmap commitments harden.
- Create a continuous evaluation system spanning early concepts, working prototypes, implementations, shipped products, production behavior, and longitudinal customer outcomes.
- Define the research and measurement models Salesforce needs for human-agent collaboration, including trust, delegation, autonomy, authority, observability, intervention, correction, escalation, learning, and recovery.
- Integrate relevant evidence across Product Analytics, Marketing, Sales, Customer Success, Support, Services, Trust, implementation, and market intelligence without duplicating those organizations or collapsing distinct evidence into one score.
- Build a durable knowledge system that makes customer and product evidence searchable, reusable, appropriately contextualized, and available at the moment consequential decisions are made.
- Protect the independence and integrity of customer evidence, including confidence, limitations, contradictions, and unresolved questions, even when the findings challenge a committed direction.
- Recruit and develop an exceptional bench of research leaders, distinguished researchers, behavioral scientists, measurement experts, research technologists, knowledge architects, and Research Operations talent.
We'll make each bullet an - .
Now Requirements: we used "What You Bring" paragraph. Also maybe include "What Success Looks Like" could be part of responsibilities? But we already have responsibilities. Could also add a separate section for "What Success Looks Like" but not required headings. We'll keep as responsibilities maybe.
But we have not included "What Success Looks Like". Could be part of responsibilities or maybe a separate section like "Success Metrics". Not in allowed headings. We'll incorporate into responsibilities as additional items.
Let's add those success items as li under Responsibilities as well.
Success Looks Like bullet points:
- Within the first year, Research should operate as an enterprise decision system: close enough to change the work and independent enough to challenge it.
- A single enterprise research agenda is actively shaping priority product, portfolio, architecture, and business decisions.
- Live domain and work models are in place for the highest-priority areas and are changing what teams choose to build or stop.
- A continuous evaluation model connects prototypes, production behavior, implementation evidence, customer outcomes, and longitudinal learning.
- Human-agent research and measurement are informing Agentforce, Slack, Experience Architecture, and selected portfolio experiences.
- Evidence from implementation, support, service, win/loss, telemetry, and direct research is entering decisions with clear provenance and interpretation.
- The research knowledge environment is reducing duplicated discovery and making prior evidence available without stripping it of context.
- Salesforce has one strong Research leadership and talent system, with deep portfolio proximity and a credible distinguished-practitioner bench.
- Unsupported directions are redirected or stopped before major investment because the evidence is timely, credible, and consequential.
We'll add these.
Now we need to ensure we don't duplicate content. We'll combine all responsibilities into one list.
Now check for any prohibited boilerplate: we removed "Accommodations", "Apply today", "Unleash Your Potential", "Posting Statement", "Know your rights", etc.
We kept benefits list
for prose. We must not repeat job title as heading. The page already shows it, so we don't add a heading for SVP, Research & Insights. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment. Let's craft. Structure:
About the role
...
Then Responsibilities:Responsibilities
- ... ... We need to extract responsibilities from "What You Will Lead" and "What You Will Do". Could combine. What You Will Lead bullet points: list of 4 capabilities with sub-bullets. We'll flatten into li items. What You Will Do list: many items. We'll combine. Then Requirements/Qualifications: maybe separate Requirements and Qualifications? The instruction says use headings for Requirements, Qualifications, Skills. We could put Requirements as "What You Bring" (experience). Qualifications maybe "Your leadership signature". Skills maybe list of specific skills. But we must only include sections when posting has real specific content. All three have content. Let's define:
- Deep expertise across qualitative research, behavioral science, mixed methods, experimentation, measurement, and interpretation of product and production data.
- Meaningful experience with AI, automation, human factors, intelligent systems, trust, or human-machine collaboration.
- Ability to reconstruct how complex domains and people actually work across roles, systems, incentives, constraints, implementations, and time.
- Demonstrated strength in foundational research, generative product influence, continuous evaluation, and enterprise synthesis.
- Experience integrating qualitative, quantitative, behavioral, commercial, implementation, and service evidence without overstating certainty or confusing correlation with customer understanding.
- Executive presence and organizational courage sufficient to challenge powerful stakeholders, protect difficult findings, and redirect consequential decisions.
- Experience leading a centrally connected research organization with senior portfolio leaders and deeply embedded teams.
- Record of identifying, recruiting, and developing exceptional research leaders and distinguished practitioners.
- Time off programs
- Medical, dental, vision
- Mental health support
- Paid parental leave
- Life and disability insurance
- 401(k)
- Employee stock purchasing program
- . Now Requirements: we used "What You Bring" paragraph. Also maybe include "What Success Looks Like" could be part of responsibilities? But we already have responsibilities. Could also add a separate section for "What Success Looks Like" but not required headings. We'll keep as responsibilities maybe. But we have not included "What Success Looks Like". Could be part of responsibilities or maybe a separate section like "Success Metrics". Not in allowed headings. We'll incorporate into responsibilities as additional items. Let's add those success items as li under Responsibilities as well. Success Looks Like bullet points: - Within the first year, Research should operate as an enterprise decision system: close enough to change the work and independent enough to challenge it. - A single enterprise research agenda is actively shaping priority product, portfolio, architecture, and business decisions. - Live domain and work models are in place for the highest-priority areas and are changing what teams choose to build or stop. - A continuous evaluation model connects prototypes, production behavior, implementation evidence, customer outcomes, and longitudinal learning. - Human-agent research and measurement are informing Agentforce, Slack, Experience Architecture, and selected portfolio experiences. - Evidence from implementation, support, service, win/loss, telemetry, and direct research is entering decisions with clear provenance and interpretation. - The research knowledge environment is reducing duplicated discovery and making prior evidence available without stripping it of context. - Salesforce has one strong Research leadership and talent system, with deep portfolio proximity and a credible distinguished-practitioner bench. - Unsupported directions are redirected or stopped before major investment because the evidence is timely, credible, and consequential. We'll add these. Now we need to ensure we don't duplicate content. We'll combine all responsibilities into one list. Now check for any prohibited boilerplate: we removed "Accommodations", "Apply today", "Unleash Your Potential", "Posting Statement", "Know your rights", etc. We kept benefits list
Requirements
A record of leading Research across a complex, multi-product enterprise, platform, or ecosystem at significant scale. Evidence that research you personally led changed product strategy, architecture, investment, operating decisions, or shipped experiences, not merely stakeholder understanding.
Qualifications
You are a truth-teller with product consequence. You combine deep curiosity and methodological rigor with exceptional product judgment. You can hold contradiction, identify the non-obvious implication, and make complex evidence clear without manufacturing certainty. You are independent without becoming distant from the work, and influential without allowing stakeholder preference to rewrite what is true.
Skills
Benefits
Pay
The typical base salary range for this position is $399,000 - $453,000 annually. In select cities within the San Francisco and New York City metropolitan area, the base salary range for this role is $399,000 - $453,000 annually. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable.
We should also include maybe a short paragraph about the role under About the role. About the role: combine the intro paragraphs about Salesforce and the role description. We need to avoid boilerplate like "To get the best candidate experience..." etc. Also avoid "Accommodations", "Apply today", "Unleash Your Potential" (maybe part of benefits but we already have benefits). We'll keep About the role as:SVP, Research & Insights - Experience & Design Org. The next Salesforce will be shaped by how well people and agents can understand one another, share context, delegate authority, recover from failure, and accomplish meaningful outcomes together. These behaviors unfold across roles, products, implementations, data, policies, channels, and time. They cannot be understood through episodic studies or a single adoption metric. The SVP, Research + Insights will lead Research across Salesforce Experience Design and build a continuous intelligence capability spanning Customer 360, Platform, Data 360, Agentforce, Slack, and emerging surfaces. Reporting to the EVP, Chief Experience Officer, this executive will move Research further upstream into enterprise and product strategy while extending evaluation through implementation, production, and longitudinal use.
That seems good. Now responsibilities: combine What You Will Lead and What You Will Do. Let's extract What You Will Lead bullet points: - Enterprise Experience Intelligence + Foresight. Foundational domain research, longitudinal customer programs, strategic opportunity intelligence, ecosystem and competitive synthesis, failed-adoption and win/loss evidence, foresight, and executive synthesis. - Portfolio Research + Insights. Deeply embedded research leadership and teams serving Salesforce's major product portfolios while operating within one enterprise agenda, talent system, evidence standard, and knowledge environment. - Human-Agent Research, Evaluation + Measurement. Human factors, behavioral science, trust and delegation, agent-behavior evaluation, scenario and rubric development, production-evidence interpretation, and experience-outcome measurement. - Research Operations + Knowledge. Participant systems, customer access, governance and ethics, methods and standards, knowledge infrastructure, evidence taxonomy, tooling, vendors, and research program operations. What You Will Do list: - Establish one enterprise Research + Insights agenda tied to Salesforce's most consequential customer, product, platform, architecture, and business decisions. - Build Experience Intelligence as a live, cumulative understanding of how customers, industries, organizations, roles, and work actually operate and how they change over time. - Ensure foundational, generative, and evaluative research shape product strategy before solution direction and roadmap commitments harden. - Create a continuous evaluation system spanning early concepts, working prototypes, implementations, shipped products, production behavior, and longitudinal customer outcomes. - Define the research and measurement models Salesforce needs for human-agent collaboration, including trust, delegation, autonomy, authority, observability, intervention, correction, escalation, learning, and recovery. - Integrate relevant evidence across Product Analytics, Marketing, Sales, Customer Success, Support, Services, Trust, implementation, and market intelligence without duplicating those organizations or collapsing distinct evidence into one score. - Build a durable knowledge system that makes customer and product evidence searchable, reusable, appropriately contextualized, and available at the moment consequential decisions are made. - Protect the independence and integrity of customer evidence, including confidence, limitations, contradictions, and unresolved questions, even when the findings challenge a committed direction. - Recruit and develop an exceptional bench of research leaders, distinguished researchers, behavioral scientists, measurement experts, research technologists, knowledge architects, and Research Operations talent. We'll make each bullet an