SVP, Research & Insights - Experience & Design Org
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the posting: It includes "About Salesforce" description, then "SVP, Research & Insights - Experience & Design Org" title (but we should not repeat job title as heading). Then sections: "What You Will Lead" (list of capabilities), "What You Will Do" (list of responsibilities), "What Success Looks Like" (maybe outcomes), "What You Bring" (requirements/qualifications), "Your leadership signature" (maybe skills/attributes), "Why this role matters" (maybe about role), "Unleash Your Potential" (benefits?), "Accommodations" (boilerplate to remove), "Posting Statement" (EEO boilerplate to remove), "Benefits" paragraph about benefits, salary range.
We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove Accommodations, Posting Statement, maybe the "Apply today" etc? The instruction says remove application instructions. So remove "Apply today to not only shape the future — but to redefine what’s possible — for yourself, for AI, and the world." Also remove "Accommodations" etc. Also remove "Please see our Candidate Privacy Statement". Also remove "Posting Statement" etc. Also remove "Salesforce is an equal opportunity employer..." etc.
We need to preserve substantive information: About Salesforce paragraph, the description of role, capabilities list, responsibilities list, success criteria, qualifications, leadership signature, why role matters, benefits and salary.
We need to decide sections: Could have About the role (maybe combine About Salesforce and role description). Responsibilities (What You Will Do). Requirements/Qualifications (What You Bring). Skills (maybe leadership signature). Benefits (benefits paragraph + salary range). Pay (maybe include salary range). Schedule (not present, so omit). We should not create empty sections.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve ALL substantive information; do not invent or summarize away detail.
Let's extract content.
First paragraph: "To get the best candidate experience, please consider applying for a maximum of 3 roles within 12 months to ensure you are not duplicating efforts." This is application instruction? It's a suggestion; maybe considered boilerplate? It's not EEO but it's about applying. Might be considered application instruction; we should remove it? The instruction says remove application instructions. This line is about applying max 3 roles. Likely remove.
Next: "Job Category User Experience" maybe metadata; we can drop minor metadata.
Then "Job Details About Salesforce Salesforce is the #1 AI CRM, where humans with agents drive customer success together. Here, ambition meets action. Tech meets trust. And innovation isn’t a buzzword — it’s a way of life. The world of work as we know it is changing and we're looking for Trailblazers who are passionate about bettering business and the world through AI, driving innovation, and keeping Salesforce's core values at the heart of it all. Ready to level-up your career at the company leading workforce transformation in the agentic era? You’re in the right place! Agentforce is the future of AI, and you are the future of Salesforce."
That's prose about Salesforce.
Then "SVP, Research & Insights - Experience & Design Org" is job title; we should not repeat as heading.
Then paragraph: "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's prose about role.
Then "What You Will Lead - 4 Connected Capabilities" then bullet list:
- 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.
We need to keep each bullet as
- . The heading for this section could be "What You Will Lead" maybe under Responsibilities? But it's more like capabilities led. Could be under Responsibilities or maybe a separate section "Capabilities". Since we have headings limited to predefined list, we could put this under Responsibilities (What You Will Do) but it's actually "What You Will Lead". Might be better to treat as Responsibilities.
Then "What You Will Do" paragraph with bullet list of duties:
- 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.
Then "What Success Looks Like" paragraph with bullet list of outcomes:
- 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.
Then "What You Bring" paragraph with bullet list of qualifications:
- 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.
- 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.
- The 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.
- A record of identifying, recruiting, and developing exceptional research leaders and distinguished practitioners.
Then "Your leadership signature" paragraph (maybe skills):
- 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.
That's more like attributes/skills.
Then "Why this role matters" paragraph:
- The Agentic Enterprise introduces questions of trust, authority, delegation, learning, and organizational change that no existing product metric can answer alone. This role will ensure Salesforce builds from a continuously updated understanding of customers and real work, and that the company learns as its products and agents change. The right leader will make customer truth a durable source of strategic and product advantage.
Then "Unleash Your Potential" paragraph:
- When you join Salesforce, you’ll be limitless in all areas of your life. Our benefits and resources support you to find balance and be your best, and our AI agents accelerate your impact so you can do your best. Together, we’ll bring the power of Agentforce to organizations of all sizes and deliver amazing experiences that customers love.
Then maybe "Apply today..." which we remove.
Then "Accommodations" etc remove.
Then benefits paragraph: "Salesforce offers a variety of benefits to help you live well including: time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program. More details about company benefits can be found at the following link: https://www.salesforcebenefits.com."
Then salary range: "At Salesforce, we believe in equitable compensation practices that reflect the dynamic nature of labor markets across various regions. 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 need to include Benefits and Pay sections if posting actually states them. Benefits: yes. Pay: yes (salary range). Schedule: not present, omit.
We need to avoid duplication: The benefits paragraph appears twice? Actually only once. Good.
We need to ensure we don't include boilerplate like EEO etc. We removed.
Now structure HTML:
We could have sections:
About the role
... (About Salesforce + role description)
Responsibilities
... (What You Will Lead and What You Will Do combined? Might be too many. Could split:
- for any list of duties/requirements/benefits. Use
for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. Let's extract content. First paragraph: "To get the best candidate experience, please consider applying for a maximum of 3 roles within 12 months to ensure you are not duplicating efforts." This is application instruction? It's a suggestion; maybe considered boilerplate? It's not EEO but it's about applying. Might be considered application instruction; we should remove it? The instruction says remove application instructions. This line is about applying max 3 roles. Likely remove. Next: "Job Category User Experience" maybe metadata; we can drop minor metadata. Then "Job Details About Salesforce Salesforce is the #1 AI CRM, where humans with agents drive customer success together. Here, ambition meets action. Tech meets trust. And innovation isn’t a buzzword — it’s a way of life. The world of work as we know it is changing and we're looking for Trailblazers who are passionate about bettering business and the world through AI, driving innovation, and keeping Salesforce's core values at the heart of it all. Ready to level-up your career at the company leading workforce transformation in the agentic era? You’re in the right place! Agentforce is the future of AI, and you are the future of Salesforce." That's prose about Salesforce. Then "SVP, Research & Insights - Experience & Design Org" is job title; we should not repeat as heading. Then paragraph: "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's prose about role. Then "What You Will Lead - 4 Connected Capabilities" then bullet list: - 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. We need to keep each bullet as
- . The heading for this section could be "What You Will Lead" maybe under Responsibilities? But it's more like capabilities led. Could be under Responsibilities or maybe a separate section "Capabilities". Since we have headings limited to predefined list, we could put this under Responsibilities (What You Will Do) but it's actually "What You Will Lead". Might be better to treat as Responsibilities.
Then "What You Will Do" paragraph with bullet list of duties:
- 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.
Then "What Success Looks Like" paragraph with bullet list of outcomes:
- 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.
Then "What You Bring" paragraph with bullet list of qualifications:
- 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.
- 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.
- The 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.
- A record of identifying, recruiting, and developing exceptional research leaders and distinguished practitioners.
Then "Your leadership signature" paragraph (maybe skills):
- 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.
That's more like attributes/skills.
Then "Why this role matters" paragraph:
- The Agentic Enterprise introduces questions of trust, authority, delegation, learning, and organizational change that no existing product metric can answer alone. This role will ensure Salesforce builds from a continuously updated understanding of customers and real work, and that the company learns as its products and agents change. The right leader will make customer truth a durable source of strategic and product advantage.
Then "Unleash Your Potential" paragraph:
- When you join Salesforce, you’ll be limitless in all areas of your life. Our benefits and resources support you to find balance and be your best, and our AI agents accelerate your impact so you can do your best. Together, we’ll bring the power of Agentforce to organizations of all sizes and deliver amazing experiences that customers love.
Then maybe "Apply today..." which we remove.
Then "Accommodations" etc remove.
Then benefits paragraph: "Salesforce offers a variety of benefits to help you live well including: time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program. More details about company benefits can be found at the following link: https://www.salesforcebenefits.com."
Then salary range: "At Salesforce, we believe in equitable compensation practices that reflect the dynamic nature of labor markets across various regions. 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 need to include Benefits and Pay sections if posting actually states them. Benefits: yes. Pay: yes (salary range). Schedule: not present, omit.
We need to avoid duplication: The benefits paragraph appears twice? Actually only once. Good.
We need to ensure we don't include boilerplate like EEO etc. We removed.
Now structure HTML:
We could have sections:
About the role
... (About Salesforce + role description)
Responsibilities
- ... (What You Will Lead and What You Will Do combined? Might be too many. Could split: