CPQ Specialist

We need to output HTML fragment with sections: About the role? The posting includes "About Slalom’s Enterprise Capability" then "What You’ll Do", "What You’ll Bring", "About Us", "Compensation and Benefits". Also maybe "About Slalom’s Enterprise Capability" is like intro. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to map content to appropriate headings. We have sections: - About Slalom’s Enterprise Capability (intro) maybe "About the role" or "About Us"? Actually "About Us" later. The intro is about the capability; could be "About the role". But we have also "About Us" later describing company. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which headings to include based on content. We have: - Responsibilities: "What You’ll Do" list. - Requirements/Qualifications/Skills: "What You’ll Bring" includes experience, certifications etc. Could be split into Requirements and Qualifications and Skills. But we can combine into one section maybe "Requirements". However instruction: Prefer a few substantive sections over many thin ones. So we could have sections: About the role (intro), Responsibilities, Requirements, About Us (maybe as "About the company"? Not in list but could be "About Us" not in allowed headings? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It does not include About Us. But we could put company description under "About the role"? Or maybe we can omit About Us as not required? But we must preserve ALL substantive information; we cannot drop it. So we need to include it somewhere. Perhaps we can treat "About Us" as part of "About the role" or as a separate section but we need to use allowed heading names. Could we use "About the role" for the intro about Slalom’s Enterprise Capability and then later "About Us" could be merged into same section? Or we could create a section "About the company" but not allowed. However instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests these are examples, not exclusive list? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. But we can also include other headings if needed? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those are typical. Safer to stick to those. We have content that maps: - About the role: could include the intro about Slalom’s Enterprise Capability and maybe also About Us? But About Us is separate description of company; could be included under About the role as well. - Responsibilities: What You’ll Do. - Requirements: What You’ll Bring (experience, certifications). Could also split into Qualifications and Skills but we can keep as Requirements. - Benefits: Compensation and Benefits section includes benefits description and pay ranges. Pay: we have salary ranges. So we need separate Pay and Benefits sections? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states compensation and benefits, including pay ranges and benefits. So we should have both Pay and Benefits sections. - Schedule: not mentioned, so omit. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. We need to ensure we don't include filler like "commensurate with experience". Not present. We need to preserve all substantive information: include bullet lists for duties/requirements/benefits. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we must cut out EEO and Accommodations paragraph, also the "We will accept applicants until December 24th..." maybe considered application instruction? It's a deadline; could be considered application instruction. The instruction says remove application instructions. So we should remove that line. Also remove "Please note, this recipient is not able to support recruitment inquiries beyond this purpose." That's also application instruction. Remove EEO and Accommodations paragraph. Also remove "Slalom is committed to fair and equitable compensation practices." maybe part of compensation? It's okay to keep? It's not boilerplate? It's generic but maybe keep as part of compensation? Might be considered boilerplate but it's about compensation practices. Safer to keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That line is not EEO but it's about compensation practices; not sure. Might keep. We also need to remove duplicated lines: none. Now craft HTML. Structure:

About the role

... intro about Slalom’s Enterprise Capability and About Us combined? We'll include both paragraphs. We need to preserve the intro text: "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." Then About Us: "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." We can combine into one

or two

s. Use

for prose. Then Responsibilities:

Responsibilities

• ... each bullet from What You’ll Do list. List items: - 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 Make sure each is
• . Then Requirements:

  Requirements

  • ... from What You’ll Bring. List: - 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 We could also split into Qualifications and Skills but not needed. Then Benefits:

    Benefits

    • ... list benefits from Compensation and Benefits paragraph. Benefits list: - 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 - short/long-term disability - yearly $350 reimbursement account for any well-being-related expenses - discounted home, auto, and pet insurance We should keep the sentence about Slalom prides itself etc maybe as prose before list. Could include a

      then

      . Then Pay:

      Pay

      ... include salary ranges and note about discretionary bonus, location-based ranges, etc. We need to preserve: "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 ..." That's benefits. Then "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 lines about deadline and contact email maybe considered application instruction? The instruction says remove application instructions. The deadline and contact email are likely application instructions. So we should remove those lines. Also the line about contacting for pay range maybe also instruction? It's about pay range inquiry; could be considered application instruction as well. Safer to remove that too. Also the line about EEO we already removed. Thus for Pay section we keep: "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