CPQ Specialist

We need to output HTML fragment with sections: About the role? Actually the posting has sections: About Slalom’s Enterprise Capability (intro), What You’ll Do, What You’ll Bring, About Us, Compensation and Benefits, EEO and Accommodations (but we must remove EEO boilerplate). Also we need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we drop EEO and Accommodations section entirely. Also drop "We will accept applicants until December 24th..." maybe considered application instruction? It's a deadline; maybe considered application instruction? The instruction says remove application instructions. The deadline is an application instruction? Probably yes, we should drop that line. Also drop contact email for pay questions? That's also maybe application instruction? It's about compensation questions; could be considered application instruction? Safer to drop it. Also drop "We are committed to pay transparency..." maybe keep? It's about compensation; but it's not boilerplate? It's a statement about pay transparency; could be considered part of Compensation and Benefits? Might be okay to keep as part of that section. However the instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The pay transparency statement is not exactly those; but it's a legal statement. Might be considered legal boilerplate. Safer to remove it. Also "Slalom prides itself on helping team members thrive..." that's benefits description; keep. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. The posting has: About Slalom’s Enterprise Capability (intro) maybe map to About the role? Could be "About the role". Then "What You’ll Do" -> Responsibilities. "What You’ll Bring" -> Requirements/Qualifications/Skills? Could split into Requirements (experience) and Skills (certifications). But we should prefer few substantive sections over many thin ones. Could combine into one section "Requirements". But we have headings list: we can use any of those headings; we need to match content. Let's think: The posting includes: - About Slalom’s Enterprise Capability (intro) -> could be "About the role". - What You’ll Do -> Responsibilities. - What You’ll Bring -> Requirements (includes experience, skills, certifications). - About Us -> maybe "About the company"? Not in list; but we could treat as "About the role"? Already used. Could omit About Us? It's substantive but not in headings list; but we could map to "About the role"? Already used. Could create a section "About Us" but not allowed headings list; we must use only those headings. So we may omit About Us or incorporate into About the role? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we can use other headings? Probably we should stick to those. But we can also use other headings if needed? The examples given are those; but not explicitly forbidden to use others. Safer to use those headings only. So we need to map content to those headings. We have: - About the role: could include the intro about Slalom’s Enterprise Capability and About Us? Might be too much but okay. - Responsibilities: What You’ll Do. - Requirements: What You’ll Bring (experience, etc.) - Benefits: Compensation and Benefits section (benefits description). Pay: salary ranges. - Schedule: not present, so omit. - Qualifications/Skills: maybe split Requirements into Requirements and Skills? But we can keep just Requirements. We must not repeat job title as heading. No job title shown. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from sections we keep. We need to output only HTML fragment, no markdown fences. Let's extract content: About Slalom’s Enterprise Capability paragraph: "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." Note there is a missing space before "Here," but we keep as is. What You’ll Do bullet list (actually sentences each starting with verb). We need to put each as

under

. The 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 What You’ll Bring bullet 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 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." 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. 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 deadline line and contact email line. Also maybe the pay transparency line? It's not exactly application instruction but could be considered legal. Safer to remove it as well. Also remove "We will accept applicants until December 24th, or until the position is filled." and the contact email line. Also maybe the sentence "Slalom is committed to fair and equitable compensation practices." is okay to keep. The pay transparency line is also maybe legal; but we can keep it? The instruction says remove legal boilerplate. That line is legal boilerplate about pay transparency. So remove it. Thus the Benefits section should include the benefits description and the salary ranges (Pay). We need separate sections for Benefits and Pay per headings list. So we can have:

Benefits

• meaningful time off and paid holidays
... etc. But we need to preserve all substantive information; we must not lose details like parental leave, 401(k) with a match, etc. So we need to list each benefit as
• . The benefits paragraph includes a list separated by commas. We need to split into items. 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 exact phrasing. Pay section: salary ranges. We need to present: San Diego, Los Angeles, Orange County, Seattle, Boston, Houston, New Jersey, New York City, Washington DC, Westchester: Senior Consultant: $141,000-$173,000; All other locations: Senior Consultant: $129,000-$158,000. Also mention annual discretionary bonus eligibility. Also note actual compensation depends on skills etc. The salary pay range subject to change may be modified; we might keep that as part of Pay section? It's a note about range; could be considered part of Pay. It's not boilerplate? It's a disclaimer; maybe keep. We should not include the deadline or contact email. Thus Pay section content:

  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,000
  • All other locations: Senior Consultant: $129,000-$158,000