CPQ Specialist
Pay
with that info. Benefits also present: we can create Benefits section. Schedule? Not mentioned. So we omit Schedule. We must not repeat job title as heading. No Job ID. We must use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However the posting's headings are different: "What You’ll Do", "What You’ll Bring", "About Us", "Compensation and Benefits". We need to map to allowed headings? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems we should use those standard headings, but we can also use other headings if they match content? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect we use those exact headings when appropriate. But we have content that fits: Responsibilities (What You’ll Do), Requirements/Qualifications/Skills (What You’ll Bring), About Us (maybe About the role? Actually About Us is about company). Benefits and Pay we have. So we should output sections: Responsibilities
with list of duties; Requirements
(or Qualifications/Skills) with list; About the company
? Not in list. Could use About the role
for intro? The intro about Slalom’s Enterprise Capability could be under About the role? But they said do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings. The intro is about Slalom’s Enterprise Capability, not the role. Could be under About the role? Might be okay. However they gave example headings; we can also use other headings if they fit content? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we should use those headings when we have content for those categories. If we have other content like About Us, we could still use About the role
or maybe About the company
not in list but maybe acceptable. Safer to stick to given headings: we can put the intro under About the role
. Then Responsibilities, Requirements (or Qualifications/Skills), Benefits, Pay. We could combine Requirements and Qualifications and Skills into one section? They said prefer a few substantive sections over many thin ones. So we could have Requirements that includes experience, skills, certifications. That's fine.
Thus sections:
About the role
-> intro paragraph(s) about Slalom’s Enterprise Capability and maybe the first paragraph "About Slalom’s Enterprise Capability..." plus maybe the "Here, you’ll collaborate..." paragraph.
Then Responsibilities
-> list of duties from "What You’ll Do".
Then Requirements
-> list from "What You’ll Bring".
Then Benefits
-> benefits paragraph from Compensation and Benefits (meaningful time off, parental leave, 401k, health, adoption, disability, $350 reimbursement, discounted insurance).
Then Pay
-> compensation paragraph: salary ranges per location, bonus.
We must remove EEO and Accommodations, application instructions, etc.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the exact details: salary ranges, list of benefits, etc.
We need to format lists with - . For prose, use
.
We must not include markdown code fences.
Let's extract content.
Intro:
"About Slalom’s Enterprise Capability At the heart of Slalom’s Enterprise Capability is a bold ambition: to design and deliver intelligent, human-centered business applications that empower organizations to serve their customers with acceleration, agility, precision, and purpose. We partner with leading platforms—Salesforce, ServiceNow, Adobe, Anaplan, Workday, Contentful, Boomi, Workato and more—to build scalable, end-to-end solutions that unify data, streamline operations, and unlock actionable insights. Our work powers everything from smarter CRM experiences and next-gen commerce sites to resilient case management systems and optimized workforce planning. But we're not just technologists—we’re strategic enablers. Whether helping a client modernize their infrastructure, integrate mission-critical functions, or activate AI-powered innovation, we connect strategy to execution in ways that drive measurable impact.Here, you’ll collaborate with curious, courageous people who believe in growth through experimentation, delivering value through partnerships, and building a future where technology works quietly in service of extraordinary outcomes."
We need to ensure spacing: there is a missing space after impact.We can keep as is.
Now Responsibilities list (What You’ll Do):
- Support Salesforce ARM project implementations through business analysis and delivery activities
- Elicit, document, and validate business requirements for revenue accounting and related commercial processes
- Contribute to solution estimates and communicate scope assumptions, benefits, dependencies, and risks
- Clarify functional requirements, acceptance criteria, and business rules for technical team members
- Stay current on relevant Salesforce platform capabilities, releases, and revenue accounting practices
- Support sales pursuits by contributing discovery inputs, effort assumptions, and functional scope
- Participate in client presentations and provide functional input for demonstrations and proof of concepts
- Participate in integration discussions, requirements sessions, and solution design workshops
- Create and maintain process flows, data mappings, and solution documentation for business and technical audiences
- Analyze and improve revenue processes, data quality, and user experience across commercial workflows
- Support project scope, priorities, and outcomes to ensure alignment with client objectives
Now Requirements list (What You’ll Bring):
- 3+ years of business analysis, revenue accounting, CRM, ERP, or commercial systems implementation experience
- Experience with Salesforce ARM or another configure-price-quote solution; familiarity with quote-to-cash, order-to-cash, billing, or related commercial processes preferred
- Experience working with the Salesforce platform or comparable enterprise business applications
- Understanding of data models, master data management, and data integration concepts
- Strong client-facing written and oral communication skills
- Experience on 2+ projects as a business analyst, consultant, or similar role, with durations of at least 6 months
- Relevant Salesforce, business analysis, or revenue accounting certifications, or ability to achieve relevant certifications upon hire within the first several months
Now About Us paragraph:
"Slalom is a fiercely human business and technology consulting company that leads with outcomes to bring more value, in all ways, always. From strategy through delivery, our agile teams across 52 offices in 12 countries partner with clients to co-create powerful customer experiences, modern ways of working, and meaningful impact. What sets us apart? We believe work should be challenging and fulfilling, not perfect, but possible. That’s why we prioritize purpose, flexibility, connection, and recognition, so our people can thrive and love what they do, most days."
Now Benefits paragraph (from Compensation and Benefits):
"Slalom prides itself on helping team members thrive in their work and life. As a result, Slalom is proud to invest in benefits that include meaningful time off and paid holidays, parental leave, 401(k) with a match, a range of choices for highly subsidized health, dental, & vision coverage, adoption and fertility assistance, and short/long-term disability. We also offer yearly $350 reimbursement account for any well-being-related expenses, as well as discounted home, auto, and pet insurance."
Now Pay paragraph:
"Slalom is committed to fair and equitable compensation practices. For this role, we are hiring at the following levels and targeted base pay salary ranges: San Diego, Los Angeles, Orange County, Seattle, Boston, Houston, New Jersey, New York City, Washington DC, Westchester:Senior Consultant: $141,000-$173,000All other locations:Senior Consultant: $129,000-$158,000 In addition, individuals may be eligible for an annual discretionary bonus. Actual compensation will depend upon an individual’s skills, experience, qualifications, location, and other relevant factors. The salary pay range is subject to change and may be modified at any time. We will accept applicants until December 24th, or until the position is filled.We are committed to pay transparency and compliance with applicable laws. If you have questions or concerns about the pay range or other compensation information in this posting, please contact us at: peopleone@slalom.com. Please note, this recipient is not able to support recruitment inquiries beyond this purpose."
We need to remove application instructions? The last sentences about contacting peopleone@slalom.com is maybe considered application instruction? It's about pay range questions. Might be considered contact for compensation questions, not application instruction. The instruction said remove application instructions. This is not exactly application instruction but could be considered contact for pay questions. Might be okay to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The contact for pay range questions is not exactly application instruction but could be considered part of compensation transparency. I'd keep it as it's substantive about pay transparency. However the sentence "We will accept applicants until December 24th, or until the position is filled." is application instruction (deadline). That should be removed. Also the contact email line maybe also considered application instruction? It's about pay range questions, not application. But to be safe, we could remove the deadline sentence and maybe keep the contact line? The instruction says remove application instructions. The deadline is definitely an application instruction. So remove "We will accept applicants until December 24th, or until the position is filled." Also maybe remove the contact line? It's not exactly an application instruction but could be considered part of pay transparency. I'd keep it.
Thus Pay paragraph becomes:
"Slalom is committed to fair and equitable compensation practices. For this role, we are hiring at the following levels and targeted base pay salary ranges: San Diego, Los Angeles, Orange County, Seattle, Boston, Houston, New Jersey, New York City, Washington DC, Westchester:Senior Consultant: $141,000-$173,000All other locations:Senior Consultant: $129,000-$158,000 In addition, individuals may be eligible for an annual discretionary bonus. Actual compensation will depend upon an individual’s skills, experience, qualifications, location, and other relevant factors. The salary pay range is subject to change and may be modified at any time. We are committed to pay transparency and compliance with applicable laws. If you have questions or concerns about the pay range or other compensation information in this posting, please contact us at: peopleone
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect we use those exact headings when appropriate. But we have content that fits: Responsibilities (What You’ll Do), Requirements/Qualifications/Skills (What You’ll Bring), About Us (maybe About the role? Actually About Us is about company). Benefits and Pay we have. So we should output sections: Responsibilities
with list of duties; Requirements
(or Qualifications/Skills) with list; About the company
? Not in list. Could use About the role
for intro? The intro about Slalom’s Enterprise Capability could be under About the role? But they said do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings. The intro is about Slalom’s Enterprise Capability, not the role. Could be under About the role? Might be okay. However they gave example headings; we can also use other headings if they fit content? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we should use those headings when we have content for those categories. If we have other content like About Us, we could still use About the role
or maybe About the company
not in list but maybe acceptable. Safer to stick to given headings: we can put the intro under About the role
. Then Responsibilities, Requirements (or Qualifications/Skills), Benefits, Pay. We could combine Requirements and Qualifications and Skills into one section? They said prefer a few substantive sections over many thin ones. So we could have Requirements that includes experience, skills, certifications. That's fine.
Thus sections:
About the role
-> intro paragraph(s) about Slalom’s Enterprise Capability and maybe the first paragraph "About Slalom’s Enterprise Capability..." plus maybe the "Here, you’ll collaborate..." paragraph.
Then Responsibilities
-> list of duties from "What You’ll Do".
Then Requirements
-> list from "What You’ll Bring".
Then Benefits
-> benefits paragraph from Compensation and Benefits (meaningful time off, parental leave, 401k, health, adoption, disability, $350 reimbursement, discounted insurance).
Then Pay
-> compensation paragraph: salary ranges per location, bonus.
We must remove EEO and Accommodations, application instructions, etc.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the exact details: salary ranges, list of benefits, etc.
We need to format lists with - . For prose, use
.
We must not include markdown code fences.
Let's extract content.
Intro:
"About Slalom’s Enterprise Capability At the heart of Slalom’s Enterprise Capability is a bold ambition: to design and deliver intelligent, human-centered business applications that empower organizations to serve their customers with acceleration, agility, precision, and purpose. We partner with leading platforms—Salesforce, ServiceNow, Adobe, Anaplan, Workday, Contentful, Boomi, Workato and more—to build scalable, end-to-end solutions that unify data, streamline operations, and unlock actionable insights. Our work powers everything from smarter CRM experiences and next-gen commerce sites to resilient case management systems and optimized workforce planning. But we're not just technologists—we’re strategic enablers. Whether helping a client modernize their infrastructure, integrate mission-critical functions, or activate AI-powered innovation, we connect strategy to execution in ways that drive measurable impact.Here, you’ll collaborate with curious, courageous people who believe in growth through experimentation, delivering value through partnerships, and building a future where technology works quietly in service of extraordinary outcomes."
We need to ensure spacing: there is a missing space after impact.We can keep as is.
Now Responsibilities list (What You’ll Do):
- Support Salesforce ARM project implementations through business analysis and delivery activities
- Elicit, document, and validate business requirements for revenue accounting and related commercial processes
- Contribute to solution estimates and communicate scope assumptions, benefits, dependencies, and risks
- Clarify functional requirements, acceptance criteria, and business rules for technical team members
- Stay current on relevant Salesforce platform capabilities, releases, and revenue accounting practices
- Support sales pursuits by contributing discovery inputs, effort assumptions, and functional scope
- Participate in client presentations and provide functional input for demonstrations and proof of concepts
- Participate in integration discussions, requirements sessions, and solution design workshops
- Create and maintain process flows, data mappings, and solution documentation for business and technical audiences
- Analyze and improve revenue processes, data quality, and user experience across commercial workflows
- Support project scope, priorities, and outcomes to ensure alignment with client objectives
Now Requirements list (What You’ll Bring):
- 3+ years of business analysis, revenue accounting, CRM, ERP, or commercial systems implementation experience
- Experience with Salesforce ARM or another configure-price-quote solution; familiarity with quote-to-cash, order-to-cash, billing, or related commercial processes preferred
- Experience working with the Salesforce platform or comparable enterprise business applications
- Understanding of data models, master data management, and data integration concepts
- Strong client-facing written and oral communication skills
- Experience on 2+ projects as a business analyst, consultant, or similar role, with durations of at least 6 months
- Relevant Salesforce, business analysis, or revenue accounting certifications, or ability to achieve relevant certifications upon hire within the first several months
Now About Us paragraph:
"Slalom is a fiercely human business and technology consulting company that leads with outcomes to bring more value, in all ways, always. From strategy through delivery, our agile teams across 52 offices in 12 countries partner with clients to co-create powerful customer experiences, modern ways of working, and meaningful impact. What sets us apart? We believe work should be challenging and fulfilling, not perfect, but possible. That’s why we prioritize purpose, flexibility, connection, and recognition, so our people can thrive and love what they do, most days."
Now Benefits paragraph (from Compensation and Benefits):
"Slalom prides itself on helping team members thrive in their work and life. As a result, Slalom is proud to invest in benefits that include meaningful time off and paid holidays, parental leave, 401(k) with a match, a range of choices for highly subsidized health, dental, & vision coverage, adoption and fertility assistance, and short/long-term disability. We also offer yearly $350 reimbursement account for any well-being-related expenses, as well as discounted home, auto, and pet insurance."
Now Pay paragraph:
"Slalom is committed to fair and equitable compensation practices. For this role, we are hiring at the following levels and targeted base pay salary ranges: San Diego, Los Angeles, Orange County, Seattle, Boston, Houston, New Jersey, New York City, Washington DC, Westchester:Senior Consultant: $141,000-$173,000All other locations:Senior Consultant: $129,000-$158,000 In addition, individuals may be eligible for an annual discretionary bonus. Actual compensation will depend upon an individual’s skills, experience, qualifications, location, and other relevant factors. The salary pay range is subject to change and may be modified at any time. We will accept applicants until December 24th, or until the position is filled.We are committed to pay transparency and compliance with applicable laws. If you have questions or concerns about the pay range or other compensation information in this posting, please contact us at: peopleone@slalom.com. Please note, this recipient is not able to support recruitment inquiries beyond this purpose."
We need to remove application instructions? The last sentences about contacting peopleone@slalom.com is maybe considered application instruction? It's about pay range questions. Might be considered contact for compensation questions, not application instruction. The instruction said remove application instructions. This is not exactly application instruction but could be considered contact for pay questions. Might be okay to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The contact for pay range questions is not exactly application instruction but could be considered part of compensation transparency. I'd keep it as it's substantive about pay transparency. However the sentence "We will accept applicants until December 24th, or until the position is filled." is application instruction (deadline). That should be removed. Also the contact email line maybe also considered application instruction? It's about pay range questions, not application. But to be safe, we could remove the deadline sentence and maybe keep the contact line? The instruction says remove application instructions. The deadline is definitely an application instruction. So remove "We will accept applicants until December 24th, or until the position is filled." Also maybe remove the contact line? It's not exactly an application instruction but could be considered part of pay transparency. I'd keep it.
Thus Pay paragraph becomes:
"Slalom is committed to fair and equitable compensation practices. For this role, we are hiring at the following levels and targeted base pay salary ranges: San Diego, Los Angeles, Orange County, Seattle, Boston, Houston, New Jersey, New York City, Washington DC, Westchester:Senior Consultant: $141,000-$173,000All other locations:Senior Consultant: $129,000-$158,000 In addition, individuals may be eligible for an annual discretionary bonus. Actual compensation will depend upon an individual’s skills, experience, qualifications, location, and other relevant factors. The salary pay range is subject to change and may be modified at any time. We are committed to pay transparency and compliance with applicable laws. If you have questions or concerns about the pay range or other compensation information in this posting, please contact us at: peopleone
About the role
or maybeAbout the company
not in list but maybe acceptable. Safer to stick to given headings: we can put the intro underAbout the role
. Then Responsibilities, Requirements (or Qualifications/Skills), Benefits, Pay. We could combine Requirements and Qualifications and Skills into one section? They said prefer a few substantive sections over many thin ones. So we could have Requirements that includes experience, skills, certifications. That's fine. Thus sections:About the role
-> intro paragraph(s) about Slalom’s Enterprise Capability and maybe the first paragraph "About Slalom’s Enterprise Capability..." plus maybe the "Here, you’ll collaborate..." paragraph. ThenResponsibilities
-> list of duties from "What You’ll Do". ThenRequirements
-> list from "What You’ll Bring". ThenBenefits
-> benefits paragraph from Compensation and Benefits (meaningful time off, parental leave, 401k, health, adoption, disability, $350 reimbursement, discounted insurance). ThenPay
-> compensation paragraph: salary ranges per location, bonus. We must remove EEO and Accommodations, application instructions, etc. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the exact details: salary ranges, list of benefits, etc. We need to format lists with- . For prose, use
. We must not include markdown code fences. Let's extract content. Intro: "About Slalom’s Enterprise Capability At the heart of Slalom’s Enterprise Capability is a bold ambition: to design and deliver intelligent, human-centered business applications that empower organizations to serve their customers with acceleration, agility, precision, and purpose. We partner with leading platforms—Salesforce, ServiceNow, Adobe, Anaplan, Workday, Contentful, Boomi, Workato and more—to build scalable, end-to-end solutions that unify data, streamline operations, and unlock actionable insights. Our work powers everything from smarter CRM experiences and next-gen commerce sites to resilient case management systems and optimized workforce planning. But we're not just technologists—we’re strategic enablers. Whether helping a client modernize their infrastructure, integrate mission-critical functions, or activate AI-powered innovation, we connect strategy to execution in ways that drive measurable impact.Here, you’ll collaborate with curious, courageous people who believe in growth through experimentation, delivering value through partnerships, and building a future where technology works quietly in service of extraordinary outcomes." We need to ensure spacing: there is a missing space after impact.We can keep as is. Now Responsibilities list (What You’ll Do): - Support Salesforce ARM project implementations through business analysis and delivery activities - Elicit, document, and validate business requirements for revenue accounting and related commercial processes - Contribute to solution estimates and communicate scope assumptions, benefits, dependencies, and risks - Clarify functional requirements, acceptance criteria, and business rules for technical team members - Stay current on relevant Salesforce platform capabilities, releases, and revenue accounting practices - Support sales pursuits by contributing discovery inputs, effort assumptions, and functional scope - Participate in client presentations and provide functional input for demonstrations and proof of concepts - Participate in integration discussions, requirements sessions, and solution design workshops - Create and maintain process flows, data mappings, and solution documentation for business and technical audiences - Analyze and improve revenue processes, data quality, and user experience across commercial workflows - Support project scope, priorities, and outcomes to ensure alignment with client objectives Now Requirements list (What You’ll Bring): - 3+ years of business analysis, revenue accounting, CRM, ERP, or commercial systems implementation experience - Experience with Salesforce ARM or another configure-price-quote solution; familiarity with quote-to-cash, order-to-cash, billing, or related commercial processes preferred - Experience working with the Salesforce platform or comparable enterprise business applications - Understanding of data models, master data management, and data integration concepts - Strong client-facing written and oral communication skills - Experience on 2+ projects as a business analyst, consultant, or similar role, with durations of at least 6 months - Relevant Salesforce, business analysis, or revenue accounting certifications, or ability to achieve relevant certifications upon hire within the first several months Now About Us paragraph: "Slalom is a fiercely human business and technology consulting company that leads with outcomes to bring more value, in all ways, always. From strategy through delivery, our agile teams across 52 offices in 12 countries partner with clients to co-create powerful customer experiences, modern ways of working, and meaningful impact. What sets us apart? We believe work should be challenging and fulfilling, not perfect, but possible. That’s why we prioritize purpose, flexibility, connection, and recognition, so our people can thrive and love what they do, most days." Now Benefits paragraph (from Compensation and Benefits): "Slalom prides itself on helping team members thrive in their work and life. As a result, Slalom is proud to invest in benefits that include meaningful time off and paid holidays, parental leave, 401(k) with a match, a range of choices for highly subsidized health, dental, & vision coverage, adoption and fertility assistance, and short/long-term disability. We also offer yearly $350 reimbursement account for any well-being-related expenses, as well as discounted home, auto, and pet insurance." Now Pay paragraph: "Slalom is committed to fair and equitable compensation practices. For this role, we are hiring at the following levels and targeted base pay salary ranges: San Diego, Los Angeles, Orange County, Seattle, Boston, Houston, New Jersey, New York City, Washington DC, Westchester:Senior Consultant: $141,000-$173,000All other locations:Senior Consultant: $129,000-$158,000 In addition, individuals may be eligible for an annual discretionary bonus. Actual compensation will depend upon an individual’s skills, experience, qualifications, location, and other relevant factors. The salary pay range is subject to change and may be modified at any time. We will accept applicants until December 24th, or until the position is filled.We are committed to pay transparency and compliance with applicable laws. If you have questions or concerns about the pay range or other compensation information in this posting, please contact us at: peopleone@slalom.com. Please note, this recipient is not able to support recruitment inquiries beyond this purpose." We need to remove application instructions? The last sentences about contacting peopleone@slalom.com is maybe considered application instruction? It's about pay range questions. Might be considered contact for compensation questions, not application instruction. The instruction said remove application instructions. This is not exactly application instruction but could be considered contact for pay questions. Might be okay to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The contact for pay range questions is not exactly application instruction but could be considered part of compensation transparency. I'd keep it as it's substantive about pay transparency. However the sentence "We will accept applicants until December 24th, or until the position is filled." is application instruction (deadline). That should be removed. Also the contact email line maybe also considered application instruction? It's about pay range questions, not application. But to be safe, we could remove the deadline sentence and maybe keep the contact line? The instruction says remove application instructions. The deadline is definitely an application instruction. So remove "We will accept applicants until December 24th, or until the position is filled." Also maybe remove the contact line? It's not exactly an application instruction but could be considered part of pay transparency. I'd keep it. Thus Pay paragraph becomes: "Slalom is committed to fair and equitable compensation practices. For this role, we are hiring at the following levels and targeted base pay salary ranges: San Diego, Los Angeles, Orange County, Seattle, Boston, Houston, New Jersey, New York City, Washington DC, Westchester:Senior Consultant: $141,000-$173,000All other locations:Senior Consultant: $129,000-$158,000 In addition, individuals may be eligible for an annual discretionary bonus. Actual compensation will depend upon an individual’s skills, experience, qualifications, location, and other relevant factors. The salary pay range is subject to change and may be modified at any time. We are committed to pay transparency and compliance with applicable laws. If you have questions or concerns about the pay range or other compensation information in this posting, please contact us at: peopleone