CPQ Specialist

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Slalom’s Enterprise Capability" (intro), "What You’ll Do", "What You’ll Bring", "About Us", "Compensation and Benefits". Also maybe "Pay" and "Benefits" sections if present. The posting includes compensation details and benefits. So we should create sections: About the role? Not exactly; we have "About Slalom’s Enterprise Capability" which is about the team. Could be "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings where appropriate. We have: - About Slalom’s Enterprise Capability: could be "About the role" or maybe "About Us"? But we also have separate "About Us". The instruction says use those example headings; we should use them if content matches. We have "What You’ll Do" -> Responsibilities. "What You’ll Bring" -> Requirements/Qualifications/Skills. Could split into Requirements (experience) and Qualifications (certifications) and Skills (communication). But we can combine into one Requirements section if content is substantive. The instruction: prefer a few substantive sections over many thin ones. So we can have sections: About the role (intro), Responsibilities, Requirements, Benefits, Pay. Also maybe About Us? Could be part of About the role? But we have separate "About Us" describing company. Could be included in About the role? Might be redundant. However we should preserve all substantive information. The "About Us" is substantive; we could put it under "About the role" or maybe a separate section like "About the company". But the allowed headings list does not include "About the company". We could put it under "About the role" as it's about the team. Or we could create a section "About Us" but not in allowed list? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning examples, not exhaustive. So we could use other headings if appropriate, but better to stick to those. So we can put "About Us" under "About the role". Or we could have two sections: About the role (intro about Slalom’s Enterprise Capability) and About the company (maybe not needed). But to avoid thin sections, combine. Thus sections: - About the role: combine the introductory paragraph about Slalom’s Enterprise Capability and the "About Us" paragraph. - Responsibilities: the bullet list under "What You’ll Do". Use

• . - Requirements: combine "What You’ll Bring" (experience, skills, certifications). Could also split into Requirements and Qualifications but we can keep as Requirements. - Benefits: the benefits paragraph under "Compensation and Benefits". Use
  • for list of benefits. - Pay: the compensation range paragraph. Use

    . We must not include boilerplate like EEO, Accommodations, application instructions, etc. Remove those. We must preserve all substantive information: ensure we keep details like 3+ years experience, Salesforce ARM, etc. Also keep the list of responsibilities items exactly. We must not repeat job title as heading. Not include Job ID. We must not create sections with filler like "commensurate with experience". Not present. We must output only HTML fragment. 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." Then "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." Combine these into About the role. Responsibilities list: each line after "What You’ll Do". Let's list them: - 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 to keep punctuation. Requirements list: "What You’ll Bring". Items: - 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 split into Requirements and Qualifications but we can keep as Requirements. Benefits list: from "Compensation and Benefits" paragraph: "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." We need to make a

    • list. Items: - 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 Pay section: includes salary ranges and bonus. Text: "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 keep substantive info: the salary ranges, locations, bonus eligibility, contact email. Remove the line about accepting applicants until date? That's maybe considered application instruction? It's about timeline; could be considered boilerplate? The instruction says remove application instructions. The date deadline is an application instruction; we should drop it. Also the contact email for pay questions is maybe okay to keep? It's not exactly application instruction but it's a contact for pay questions. Might be considered part of compensation info. The instruction says remove application instructions; the contact email for pay questions is not exactly application instruction but could be kept. However it's a bit like a contact for pay questions; we could keep it. But to be safe, maybe keep the pay range and bonus, and note that actual compensation depends on factors. The contact email maybe not needed. I'd keep it as part of pay section? It's not a heading but a

      . Could include. We must not include EEO and Accommodations. Thus final HTML:

      About the role

      ...combined intro...

      Responsibilities

      • ...
      ...

      Requirements

      • ...
      ...

      Benefits

      • ...
      ...

      Pay

      ...compensation details...

      Make sure no extra whitespace? It's fine. Now craft the combined intro paragraph: combine both paragraphs into one

      . Ensure we keep all sentences. Let's write:

      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. 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,