Senior, Specialist SE
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide headings: About the role (or Overview), Responsibilities, Required Qualifications, Preferred Qualifications, How We Work, Benefits, Pay, Schedule. Possibly also "Location" but location can be part of Schedule or maybe separate? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use About the role for overview, Responsibilities, Required Qualifications, Preferred Qualifications (maybe combine as Qualifications? but they said Qualifications heading acceptable). We'll separate Required and Preferred as subheadings? Could use "Required Qualifications" and "Preferred Qualifications" as h3 each. That's okay.
How We Work maybe under "Skills"? But they said Skills heading possible. However we have "How We Work" which is more about culture. Could treat as "Skills" but better to follow instruction: use headings from list; we can use "Skills" for How We Work? Might be okay but we risk misrepresenting. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not strict list; we can use other headings if appropriate? It says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings. So we should map content to those headings. Let's map:
- About the role: overview description.
- Responsibilities: responsibilities list.
- Qualifications: could combine required and preferred? But they have separate headings Requirements and Qualifications. Could use Requirements for required qualifications, Qualifications for preferred? Or we could have both Required Qualifications and Preferred Qualifications under Qualifications? Might be better to have two sections: Requirements (required) and Qualifications (preferred). We'll do that.
- Skills: maybe "How We Work" or "Builder mentality" etc. Could treat as Skills.
- Benefits: benefits list.
- Pay: salary info.
- Schedule: hybrid, location, time zone.
We must not create sections with filler. All have content.
Now we need to extract content.
Overview: "Overview Do you want to be part of an outstanding team selling into the world's top organizations? Come join the Salesforce Solution Engineering team! Through collaboration with the customer, the Sales team, the Product team, and Professional Services, our Solution Engineers (SEs) drive the technical sale of our products and help customers realize real business value. This unique perspective creates an opportunity for the SE to interact with the entire customer lifecycle. As a Solution Engineer at Salesforce, you must have a strong desire to demonstrate technical and sales skills, including the ability to drive discovery, solicit business requirements, develop a technical sales strategy, and configure and successfully demonstrate solutions that address those requirements and deliver business value."
We'll put that in
.
Responsibilities: list of bullet points after "Responsibilities". Let's extract them:
- Play a pivotal role in aligning innovative solutions to technology challenges within complex CBS accounts, partnering with clients and collaborating with internal team members to drive consensus on multi-product technology solutions across Salesforce's product lines, with a primary focus on the Analytics portfolio
- Handle business development, operations strategy, and product demonstrations as a trusted advisor for innovative solutions
- Business Problem Solving: Define ambiguous business problems through research and assessment, drive innovative ideas, and recommend practical next steps
- Innovation Management: Focus client decision-making by evaluating solutions and driving stakeholder consensus; help build decision frameworks that deliver ongoing value
- Connect Experiences: Demonstrate connected, data-driven experiences through software demos and rapid prototyping with Salesforce and Tableau, bringing genuine energy and enthusiasm to every customer presentation
- Build customized solutions and demonstrations for multiple personas, showing how platforms accelerate strategy and deliver value
- Understand and advise on customer data and analytics architecture as it relates to Salesforce and Tableau solutions, including modern data warehouse/lakehouse environments (e.g., Snowflake, Databricks)
- Participate in all appropriate product, sales, and procedural training and certifications to maintain the knowledge needed to be effective in the role
We'll put each as
- .
Required Qualifications: list after "Required Qualifications":
- B.S. in Computer Science, Software Engineering, MIS, Data Science, or equivalent relevant experience (experience evaluated on core competencies — extracurricular leadership, military experience, volunteer roles, work experience, etc.)
- Approximately 3–5 years of relevant SE, consulting, or analytics/BI experience
- Hands-on experience across multiple Tableau products (not just Tableau Desktop), or equivalent breadth with a comparable BI platform (e.g., Power BI); familiarity with data visualization, dash boarding, and self-service analytics best practices
- Experience with modern cloud data platforms such as Snowflake or Databricks
- Solid oral, written, presentation, collaboration, and interpersonal communication skills — and the charisma and passion to bring genuine excitement to customer-facing presentations
- Ability to work as part of a team to solve technical problems in varied organizational and political environments
- Strategic and creative problem solver comfortable engaging technical, business, and executive audiences
- Willingness and ability to travel occasionally for customer engagements and team events
Preferred Qualifications: list after "Preferred Qualifications":
- Previous experience as a solution/sales engineer/consultant for a CRM, analytics, or BI company, or in a similar customer-facing technical role
- Experience building with AI tools (Claude, Cursor, ChatGPT, etc.) as these are an expanding portion of our demo toolkit
- Salesforce Certifications (including Tableau Certifications)
- Familiarity with AI/ML fundamentals and how analytics platforms surface AI-driven insights (e.g., Einstein, agentic AI, predictive analytics)
- Experience with SQL and data modelling across structured and semi-structured data
- Basic programming/scripting experience (Python, HTML, JavaScript, or similar)
- Experience with design thinking, persona-based discovery, or workshop facilitation techniques
How We Work: bullet points after "How We Work":
- Builder mentality: we show up with working demos and real solutions — not just slides
- Customer obsession: we go deep on customer problems before prescribing solutions
- Peer teaching: we share what we learn — internally, with customers, and at industry events
- Flexibility: hybrid, based near an East Coast office, with a preference for Central/Eastern time zone coverage
Unleash Your Potential: paragraph after "Unleash Your Potential":
"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. Apply today to not only shape the future — but to redefine what’s possible — for yourself, for AI, and the world."
But we should not include application instructions. The sentence "Apply today to not only shape the future — but to redefine what’s possible — for yourself, for AI, and the world." is an application instruction? It's a call to apply. According to instruction: remove application instructions. So we should remove that sentence. Also earlier "Apply today to not only shape the future — but to redefine what’s possible — for yourself, for AI, and the world." is definitely an application instruction. So we should omit that sentence. Keep the rest: "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." That's okay.
Benefits: list after "Salesforce offers a variety of benefits to help you live well including:" then list: time off programs, medical, dental, vision, mental health support, paid parental leave, life and disability insurance, 401(k), and an employee stock purchasing program. Also link to benefits page but we can keep as prose maybe. We'll make a
list.
Pay: The typical base salary range for this position is $113,260 - $151,550 annually There is a different range applicable to specific work locations. In California and New York, and select cities in the metropolitan areas of Boston, Chicago, Seattle, and Washington DC, the base pay range for this role in those locations is $124,670 - $166,810 per year. Your recruiter can share more about the specific salary range for the job location during the hiring process. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable.
We'll put that in maybe.
Schedule: location and hybrid info: "Location: Hybrid, based near a Salesforce office on the East Coast — Atlanta, DC, Boston, Austin, Chicago, or New York. Preference for Central and Eastern time zones." Also from How We Work flexibility bullet: "Flexibility: hybrid, based near an East Coast office, with a preference for Central/Eastern time zone coverage". We'll combine.
We'll create Schedule section with
containing that info.
Now ensure we don't include any boilerplate like EEO, accommodations, privacy statement, posting statement, etc. Also remove the initial "To get the best candidate experience..." line.
Now produce HTML fragment.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
...
Qualifications
...
Skills
...
(for How We Work)
Benefits
...
Pay
...
Schedule
...
Check that we didn't repeat job title. Good.
Now ensure we preserve all substantive info. Did we miss any? The overview also includes "Agentforce is the future of AI, and you are the future of Salesforce." That's in the earlier part before Overview? Actually after "Ready to level-up your career at the company leading workforce transformation in the agentic
for prose. We need to decide headings: About the role (or Overview), Responsibilities, Required Qualifications, Preferred Qualifications, How We Work, Benefits, Pay, Schedule. Possibly also "Location" but location can be part of Schedule or maybe separate? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use About the role for overview, Responsibilities, Required Qualifications, Preferred Qualifications (maybe combine as Qualifications? but they said Qualifications heading acceptable). We'll separate Required and Preferred as subheadings? Could use "Required Qualifications" and "Preferred Qualifications" as h3 each. That's okay. How We Work maybe under "Skills"? But they said Skills heading possible. However we have "How We Work" which is more about culture. Could treat as "Skills" but better to follow instruction: use headings from list; we can use "Skills" for How We Work? Might be okay but we risk misrepresenting. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not strict list; we can use other headings if appropriate? It says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings. So we should map content to those headings. Let's map: - About the role: overview description. - Responsibilities: responsibilities list. - Qualifications: could combine required and preferred? But they have separate headings Requirements and Qualifications. Could use Requirements for required qualifications, Qualifications for preferred? Or we could have both Required Qualifications and Preferred Qualifications under Qualifications? Might be better to have two sections: Requirements (required) and Qualifications (preferred). We'll do that. - Skills: maybe "How We Work" or "Builder mentality" etc. Could treat as Skills. - Benefits: benefits list. - Pay: salary info. - Schedule: hybrid, location, time zone. We must not create sections with filler. All have content. Now we need to extract content. Overview: "Overview Do you want to be part of an outstanding team selling into the world's top organizations? Come join the Salesforce Solution Engineering team! Through collaboration with the customer, the Sales team, the Product team, and Professional Services, our Solution Engineers (SEs) drive the technical sale of our products and help customers realize real business value. This unique perspective creates an opportunity for the SE to interact with the entire customer lifecycle. As a Solution Engineer at Salesforce, you must have a strong desire to demonstrate technical and sales skills, including the ability to drive discovery, solicit business requirements, develop a technical sales strategy, and configure and successfully demonstrate solutions that address those requirements and deliver business value." We'll put that in
. Responsibilities: list of bullet points after "Responsibilities". Let's extract them: - Play a pivotal role in aligning innovative solutions to technology challenges within complex CBS accounts, partnering with clients and collaborating with internal team members to drive consensus on multi-product technology solutions across Salesforce's product lines, with a primary focus on the Analytics portfolio - Handle business development, operations strategy, and product demonstrations as a trusted advisor for innovative solutions - Business Problem Solving: Define ambiguous business problems through research and assessment, drive innovative ideas, and recommend practical next steps - Innovation Management: Focus client decision-making by evaluating solutions and driving stakeholder consensus; help build decision frameworks that deliver ongoing value - Connect Experiences: Demonstrate connected, data-driven experiences through software demos and rapid prototyping with Salesforce and Tableau, bringing genuine energy and enthusiasm to every customer presentation - Build customized solutions and demonstrations for multiple personas, showing how platforms accelerate strategy and deliver value - Understand and advise on customer data and analytics architecture as it relates to Salesforce and Tableau solutions, including modern data warehouse/lakehouse environments (e.g., Snowflake, Databricks) - Participate in all appropriate product, sales, and procedural training and certifications to maintain the knowledge needed to be effective in the role We'll put each as
- list.
Pay: The typical base salary range for this position is $113,260 - $151,550 annually There is a different range applicable to specific work locations. In California and New York, and select cities in the metropolitan areas of Boston, Chicago, Seattle, and Washington DC, the base pay range for this role in those locations is $124,670 - $166,810 per year. Your recruiter can share more about the specific salary range for the job location during the hiring process. The range represents base salary only, and does not include company bonus, incentive for sales roles, equity or benefits, as applicable.
We'll put that in
- ... ...
maybe. Schedule: location and hybrid info: "Location: Hybrid, based near a Salesforce office on the East Coast — Atlanta, DC, Boston, Austin, Chicago, or New York. Preference for Central and Eastern time zones." Also from How We Work flexibility bullet: "Flexibility: hybrid, based near an East Coast office, with a preference for Central/Eastern time zone coverage". We'll combine. We'll create Schedule section with
containing that info. Now ensure we don't include any boilerplate like EEO, accommodations, privacy statement, posting statement, etc. Also remove the initial "To get the best candidate experience..." line. Now produce HTML fragment. Structure:
About the role
...
Responsibilities
Requirements
- ...
Qualifications
- ...
Skills
- ...
Benefits
- ...
Pay
...
Schedule
...
Check that we didn't repeat job title. Good. Now ensure we preserve all substantive info. Did we miss any? The overview also includes "Agentforce is the future of AI, and you are the future of Salesforce." That's in the earlier part before Overview? Actually after "Ready to level-up your career at the company leading workforce transformation in the agentic