Senior Solution Architect/Solution Consulting Director (Field Service)
for section headings
- Use - for lists
- Use
for prose
- Do NOT repeat job title as heading (page already shows it)
- Do NOT put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/scam-warning, duplicated lines, application instructions)
- Include section ONLY when posting has real, specific content
- Never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Output ONLY HTML fragment, no /, no markdown code fences
Let me parse the content:
The posting starts with some boilerplate about applying for max 3 roles, job category, etc. That's boilerplate, should be removed.
"About Salesforce" - this is company description, could be part of "About the role" or separate. But the rule says use
for section headings like "About the role". The posting has "About The Roles" which describes two positions. That's substantive.
"About The Roles" describes two individual contributor positions: Senior Solution Architect and Solution Consulting Director. This is the core "About the role" content.
"Your Impact" - this is responsibilities/duties.
"Minimum Requirements" - split by role: Senior Solution Architect (10+ years) and Solution Consulting Director (12+ years), then a list of requirements that apply to both? The list seems to apply to both roles.
"Preferred Requirements" - list.
"Unleash Your Potential" - benefits description, but also marketing fluff. However, there is a specific benefits section later: "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." That's substantive benefits.
"Accommodations" - boilerplate, remove.
"Posting Statement" - EEO, legal boilerplate, remove.
Salary ranges are given: typical base salary range $150,100 - $273,000 annually, and different range for CA, NY, etc. That's Pay section.
Schedule not mentioned.
So sections to include:
1. About the role (from "About The Roles")
2. Responsibilities (from "Your Impact")
3. Requirements (Minimum Requirements and Preferred Requirements)
4. Benefits (from the benefits list)
5. Pay (salary ranges)
I need to structure each with and appropriate content.
For "About the role", I'll include the description of both roles. Since there are two roles, I might need to present both. The posting says "We are currently hiring for two individual contributor positions:" then describes each. I'll keep that as prose and maybe list the two roles.
For Responsibilities, "Your Impact" is a list of bullet points (though in the text they are separated by line breaks). I'll convert to - .
For Requirements, there are minimum requirements (with two sub-parts for each role's years of experience, then a common list) and preferred requirements. I'll combine into one Requirements section with sub-lists? But the rule says use
- for any list. I could have two subsections: Minimum Requirements and Preferred Requirements, but the heading should be
for each? The rule says use for section headings like "Requirements". Could have "Minimum Requirements" and "Preferred Requirements" as ? But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid subsections, but we should prefer a few substantive sections over many thin ones. However, Minimum and Preferred are distinct. I'll make "Requirements" as and then within it, maybe two with labels? But the rule says use - for any list. I could do:
Requirements
Minimum Requirements
- ...
Preferred Requirements
- ...
But the minimum requirements have a split for the two roles. I'll include that as part of the list items.
Let's extract the minimum requirements:
- Senior Solution Architect: 10+ years of experience.
- Solution Consulting Director: 12+ years of experience.
- Must have led multiple large engagements, multi-cloud or multi-workstream, as the lead Architect across all workstreams within Field Service Management and/or Field Service and Operations.
- Understand and be able to speak to challenges of large engagements and what best practices to be used to ensure success
- Advanced industry knowledge and understanding of nuances of delivering Salesforce implementations in that industry
- Extensive experience with configuration and customization on the Salesforce platform
- Expert level experience defining the system architecture landscape, identifying gaps between current and desired end-states, and delivering a comprehensive solution that will enable achievement of the desired business outcomes
- Experience leading discovery sessions, defining business requirements, writing user stories and providing detailed system and functional designs
- Experience in documenting business processes and wire-framing system designs using process flow diagram tools, UML, sequence diagrams, etc. as well as making recommendations for future state improved processes and system designs
- Strong presentation skills; able to effectively present a point of view and clearly articulate the rationale to a variety of stakeholders
- Detail-oriented individual with the ability to rapidly learn and take advantage of new concepts, business models, and technologies
- Strong communication skills, both written and verbal; able to effectively develop materials that are appropriate for the audience
- Must be a team player as demonstrated through a customer qualification of a large scale/enterprise implementation with multiple work streams
- A great listener with the ability to communicate with people in diverse roles
- Resourceful and innovative thinker who can work through and solve problems
- Success as a people leader/people manager
- Experience leading internal initiatives to improve business processes
Preferred Requirements:
- Proven results in delivering high value business outcomes utilizing an agile approach
- Proven results leading customer and/or partner success stories
- Relevant Salesforce certifications and consulting experience are strongly recommended
Benefits list:
- time off programs
- medical, dental, vision
- mental health support
- paid parental leave
- life and disability insurance
- 401(k)
- employee stock purchasing program
Pay:
- Typical base salary range: $150,100 - $273,000 annually
- In California and New York, and select cities in the metropolitan areas of Boston, Chicago, Seattle, and Washington DC: $180,200 - $298,400 per year
- Base salary only, does not include company bonus, incentive for sales roles, equity or benefits
Now, I need to output HTML fragment.
Let's write.
First, About the role: I'll include the "About The Roles" content. It's prose describing two roles. I'll keep as paragraphs.
Second, Responsibilities: "Your Impact" list.
Third, Requirements: Minimum and Preferred.
Fourth, Benefits: list.
Fifth, Pay: salary ranges.
I'll omit the "Unleash Your Potential" marketing paragraph, but keep the benefits list.
Also, the "About Salesforce" paragraph is company boilerplate, but it's part of the posting. The rule says preserve ALL substantive information. However, "About Salesforce" is generic company description. The rule says remove boilerplate. I think it's okay to include as part of "About the role" or separate. But the rule says "use for section headings (e.g. About the role...)". I'll include "About the role" heading and include the "About The Roles" content. The "About Salesforce" could be a brief intro paragraph before the roles description.
I'll structure:
About the role
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.
We are currently hiring for two individual contributor positions:
Senior Solution Architect
The Solution Architect leads one or more workstreams in complex enterprise customer engagements, partnering with key collaborators to drive and achieve the vision while completing key deliverables. They serve as hands-on advisors, using strong interpersonal skills, solution and/or technical knowledge, Salesforce product knowledge, industry experience, consulting experience, and knowledge of their client's business to deliver customer return on investment. Solution Architects are strong presenters and facilitators that are able to co-create the vision and lead the execution with the customer as well as acquire customer acceptance of the delivered solution. They are capable of driving difficult conversations and removing roadblocks to implement the business strategies. They are proficient at analyzing issues and obstacles to settle root cause, and can identify appropriate corrective action. They communicate with technical and business team members from all levels through C-suite. On a day to day basis, they interact with customer product owner, business process owner and technical resources to understand requirements, analyze information, and craft comprehensive solutions. They also show a strong understanding of typical business challenges or common objectives faced by customers within the industry. Solution Architects are stewards of the Professional Services Methodology and use their networks to ensure that standard processes are followed. They engage with Customer Success and Product teams to ensure the solutions are driving the most effective achievement of the value objectives. Solution Architects supply to thought leadership and standard processes by engaging with the cloud-specific practices teams. They will supply both internally in their Community and externally in the marketplace.
Solution Consulting Director
The Solution Consulting Director leads one or more workstreams in complex enterprise customer engagements, partnering with key stakeholders to drive the vision while executing on key deliverables. They serve as hands-on advisors, using strong interpersonal skills, solution and/or technical knowledge, Salesforce product knowledge, industry experience, consulting experience, and knowledge of their client's business to deliver customer ROI. Solution Consulting Directors are strong presenters and facilitators that are able to co-create the vision and lead the execution with the customer as well as obtain customer acceptance of the delivered solution. They are capable of driving difficult conversations and removing roadblocks to execute the business strategies. They are proficient at analyzing issues and obstacles to determine root cause, and can identify appropriate corrective action. They communicate with technical and business stakeholders from all levels through C-suite. On a day to day basis, they interact with customer product owner, business process owner and technical resources to understand requirements, analyze information, and design comprehensive solutions. They also show a strong understanding of typical business challenges or common objectives faced by customers within the industry. Solution Consulting Directors are stewards of the Professional Services Methodology and use their networks to ensure that best practices are followed. They engage with Customer Success and Product teams to ensure the solutions are driving the most effective achievement of the value objectives. Solution Consulting Directors contribute to thought leadership and best practices by engaging with the cloud-specific practices teams. They will contribute both internally in their Community and externally in the marketplace.
But the rule says use for
for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning, duplicated lines, application instructions) - Include section ONLY when posting has real, specific content - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no /, no markdown code fences Let me parse the content: The posting starts with some boilerplate about applying for max 3 roles, job category, etc. That's boilerplate, should be removed. "About Salesforce" - this is company description, could be part of "About the role" or separate. But the rule says use
for section headings like "About the role". The posting has "About The Roles" which describes two positions. That's substantive.
"About The Roles" describes two individual contributor positions: Senior Solution Architect and Solution Consulting Director. This is the core "About the role" content.
"Your Impact" - this is responsibilities/duties.
"Minimum Requirements" - split by role: Senior Solution Architect (10+ years) and Solution Consulting Director (12+ years), then a list of requirements that apply to both? The list seems to apply to both roles.
"Preferred Requirements" - list.
"Unleash Your Potential" - benefits description, but also marketing fluff. However, there is a specific benefits section later: "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." That's substantive benefits.
"Accommodations" - boilerplate, remove.
"Posting Statement" - EEO, legal boilerplate, remove.
Salary ranges are given: typical base salary range $150,100 - $273,000 annually, and different range for CA, NY, etc. That's Pay section.
Schedule not mentioned.
So sections to include:
1. About the role (from "About The Roles")
2. Responsibilities (from "Your Impact")
3. Requirements (Minimum Requirements and Preferred Requirements)
4. Benefits (from the benefits list)
5. Pay (salary ranges)
I need to structure each with and appropriate content.
For "About the role", I'll include the description of both roles. Since there are two roles, I might need to present both. The posting says "We are currently hiring for two individual contributor positions:" then describes each. I'll keep that as prose and maybe list the two roles.
For Responsibilities, "Your Impact" is a list of bullet points (though in the text they are separated by line breaks). I'll convert to - .
For Requirements, there are minimum requirements (with two sub-parts for each role's years of experience, then a common list) and preferred requirements. I'll combine into one Requirements section with sub-lists? But the rule says use
- for any list. I could have two subsections: Minimum Requirements and Preferred Requirements, but the heading should be
for each? The rule says use for section headings like "Requirements". Could have "Minimum Requirements" and "Preferred Requirements" as ? But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid subsections, but we should prefer a few substantive sections over many thin ones. However, Minimum and Preferred are distinct. I'll make "Requirements" as and then within it, maybe two with labels? But the rule says use - for any list. I could do:
Requirements
Minimum Requirements
- ...
Preferred Requirements
- ...
But the minimum requirements have a split for the two roles. I'll include that as part of the list items.
Let's extract the minimum requirements:
- Senior Solution Architect: 10+ years of experience.
- Solution Consulting Director: 12+ years of experience.
- Must have led multiple large engagements, multi-cloud or multi-workstream, as the lead Architect across all workstreams within Field Service Management and/or Field Service and Operations.
- Understand and be able to speak to challenges of large engagements and what best practices to be used to ensure success
- Advanced industry knowledge and understanding of nuances of delivering Salesforce implementations in that industry
- Extensive experience with configuration and customization on the Salesforce platform
- Expert level experience defining the system architecture landscape, identifying gaps between current and desired end-states, and delivering a comprehensive solution that will enable achievement of the desired business outcomes
- Experience leading discovery sessions, defining business requirements, writing user stories and providing detailed system and functional designs
- Experience in documenting business processes and wire-framing system designs using process flow diagram tools, UML, sequence diagrams, etc. as well as making recommendations for future state improved processes and system designs
- Strong presentation skills; able to effectively present a point of view and clearly articulate the rationale to a variety of stakeholders
- Detail-oriented individual with the ability to rapidly learn and take advantage of new concepts, business models, and technologies
- Strong communication skills, both written and verbal; able to effectively develop materials that are appropriate for the audience
- Must be a team player as demonstrated through a customer qualification of a large scale/enterprise implementation with multiple work streams
- A great listener with the ability to communicate with people in diverse roles
- Resourceful and innovative thinker who can work through and solve problems
- Success as a people leader/people manager
- Experience leading internal initiatives to improve business processes
Preferred Requirements:
- Proven results in delivering high value business outcomes utilizing an agile approach
- Proven results leading customer and/or partner success stories
- Relevant Salesforce certifications and consulting experience are strongly recommended
Benefits list:
- time off programs
- medical, dental, vision
- mental health support
- paid parental leave
- life and disability insurance
- 401(k)
- employee stock purchasing program
Pay:
- Typical base salary range: $150,100 - $273,000 annually
- In California and New York, and select cities in the metropolitan areas of Boston, Chicago, Seattle, and Washington DC: $180,200 - $298,400 per year
- Base salary only, does not include company bonus, incentive for sales roles, equity or benefits
Now, I need to output HTML fragment.
Let's write.
First, About the role: I'll include the "About The Roles" content. It's prose describing two roles. I'll keep as paragraphs.
Second, Responsibilities: "Your Impact" list.
Third, Requirements: Minimum and Preferred.
Fourth, Benefits: list.
Fifth, Pay: salary ranges.
I'll omit the "Unleash Your Potential" marketing paragraph, but keep the benefits list.
Also, the "About Salesforce" paragraph is company boilerplate, but it's part of the posting. The rule says preserve ALL substantive information. However, "About Salesforce" is generic company description. The rule says remove boilerplate. I think it's okay to include as part of "About the role" or separate. But the rule says "use for section headings (e.g. About the role...)". I'll include "About the role" heading and include the "About The Roles" content. The "About Salesforce" could be a brief intro paragraph before the roles description.
I'll structure:
About the role
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.
We are currently hiring for two individual contributor positions:
Senior Solution Architect
The Solution Architect leads one or more workstreams in complex enterprise customer engagements, partnering with key collaborators to drive and achieve the vision while completing key deliverables. They serve as hands-on advisors, using strong interpersonal skills, solution and/or technical knowledge, Salesforce product knowledge, industry experience, consulting experience, and knowledge of their client's business to deliver customer return on investment. Solution Architects are strong presenters and facilitators that are able to co-create the vision and lead the execution with the customer as well as acquire customer acceptance of the delivered solution. They are capable of driving difficult conversations and removing roadblocks to implement the business strategies. They are proficient at analyzing issues and obstacles to settle root cause, and can identify appropriate corrective action. They communicate with technical and business team members from all levels through C-suite. On a day to day basis, they interact with customer product owner, business process owner and technical resources to understand requirements, analyze information, and craft comprehensive solutions. They also show a strong understanding of typical business challenges or common objectives faced by customers within the industry. Solution Architects are stewards of the Professional Services Methodology and use their networks to ensure that standard processes are followed. They engage with Customer Success and Product teams to ensure the solutions are driving the most effective achievement of the value objectives. Solution Architects supply to thought leadership and standard processes by engaging with the cloud-specific practices teams. They will supply both internally in their Community and externally in the marketplace.
Solution Consulting Director
The Solution Consulting Director leads one or more workstreams in complex enterprise customer engagements, partnering with key stakeholders to drive the vision while executing on key deliverables. They serve as hands-on advisors, using strong interpersonal skills, solution and/or technical knowledge, Salesforce product knowledge, industry experience, consulting experience, and knowledge of their client's business to deliver customer ROI. Solution Consulting Directors are strong presenters and facilitators that are able to co-create the vision and lead the execution with the customer as well as obtain customer acceptance of the delivered solution. They are capable of driving difficult conversations and removing roadblocks to execute the business strategies. They are proficient at analyzing issues and obstacles to determine root cause, and can identify appropriate corrective action. They communicate with technical and business stakeholders from all levels through C-suite. On a day to day basis, they interact with customer product owner, business process owner and technical resources to understand requirements, analyze information, and design comprehensive solutions. They also show a strong understanding of typical business challenges or common objectives faced by customers within the industry. Solution Consulting Directors are stewards of the Professional Services Methodology and use their networks to ensure that best practices are followed. They engage with Customer Success and Product teams to ensure the solutions are driving the most effective achievement of the value objectives. Solution Consulting Directors contribute to thought leadership and best practices by engaging with the cloud-specific practices teams. They will contribute both internally in their Community and externally in the marketplace.
But the rule says use for
- .
For Requirements, there are minimum requirements (with two sub-parts for each role's years of experience, then a common list) and preferred requirements. I'll combine into one Requirements section with sub-lists? But the rule says use
- for any list. I could have two subsections: Minimum Requirements and Preferred Requirements, but the heading should be
for each? The rule says use
for section headings like "Requirements". Could have "Minimum Requirements" and "Preferred Requirements" as
? But the rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid subsections, but we should prefer a few substantive sections over many thin ones. However, Minimum and Preferred are distinct. I'll make "Requirements" as
and then within it, maybe two
- with labels? But the rule says use
- for any list. I could do:
Requirements
Minimum Requirements
- ...
Preferred Requirements
- ...
for section headings (e.g. About the role...)". I'll include "About the role" heading and include the "About The Roles" content. The "About Salesforce" could be a brief intro paragraph before the roles description. I'll structure:
About the role
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.
We are currently hiring for two individual contributor positions:
Senior Solution Architect
The Solution Architect leads one or more workstreams in complex enterprise customer engagements, partnering with key collaborators to drive and achieve the vision while completing key deliverables. They serve as hands-on advisors, using strong interpersonal skills, solution and/or technical knowledge, Salesforce product knowledge, industry experience, consulting experience, and knowledge of their client's business to deliver customer return on investment. Solution Architects are strong presenters and facilitators that are able to co-create the vision and lead the execution with the customer as well as acquire customer acceptance of the delivered solution. They are capable of driving difficult conversations and removing roadblocks to implement the business strategies. They are proficient at analyzing issues and obstacles to settle root cause, and can identify appropriate corrective action. They communicate with technical and business team members from all levels through C-suite. On a day to day basis, they interact with customer product owner, business process owner and technical resources to understand requirements, analyze information, and craft comprehensive solutions. They also show a strong understanding of typical business challenges or common objectives faced by customers within the industry. Solution Architects are stewards of the Professional Services Methodology and use their networks to ensure that standard processes are followed. They engage with Customer Success and Product teams to ensure the solutions are driving the most effective achievement of the value objectives. Solution Architects supply to thought leadership and standard processes by engaging with the cloud-specific practices teams. They will supply both internally in their Community and externally in the marketplace.
Solution Consulting Director
The Solution Consulting Director leads one or more workstreams in complex enterprise customer engagements, partnering with key stakeholders to drive the vision while executing on key deliverables. They serve as hands-on advisors, using strong interpersonal skills, solution and/or technical knowledge, Salesforce product knowledge, industry experience, consulting experience, and knowledge of their client's business to deliver customer ROI. Solution Consulting Directors are strong presenters and facilitators that are able to co-create the vision and lead the execution with the customer as well as obtain customer acceptance of the delivered solution. They are capable of driving difficult conversations and removing roadblocks to execute the business strategies. They are proficient at analyzing issues and obstacles to determine root cause, and can identify appropriate corrective action. They communicate with technical and business stakeholders from all levels through C-suite. On a day to day basis, they interact with customer product owner, business process owner and technical resources to understand requirements, analyze information, and design comprehensive solutions. They also show a strong understanding of typical business challenges or common objectives faced by customers within the industry. Solution Consulting Directors are stewards of the Professional Services Methodology and use their networks to ensure that best practices are followed. They engage with Customer Success and Product teams to ensure the solutions are driving the most effective achievement of the value objectives. Solution Consulting Directors contribute to thought leadership and best practices by engaging with the cloud-specific practices teams. They will contribute both internally in their Community and externally in the marketplace.
But the rule says usefor
- for any list. I could do:
- for any list. I could have two subsections: Minimum Requirements and Preferred Requirements, but the heading should be