Genesys Cloud Platform Architect

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: Who You’ll Work With (intro), What You’ll Do (responsibilities), What You’ll Bring (requirements/qualifications), Preferred Qualifications, About Us (company description), Compensation and Benefits (pay and benefits). Also maybe "Compensation and Benefits" includes pay ranges and benefits. We must not repeat job title as heading. Use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to map content to appropriate headings. The instructions: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings? Probably we should use those headings where applicable. But we need to include a section only when posting has real, specific content for it. So we need to decide which sections we have content for. We have: - About the role: could be the "Who You’ll Work With" paragraph describing role. That fits About the role. - Responsibilities: "What You’ll Do" bullet list. - Requirements/Qualifications: "What You’ll Bring" (mandatory) and maybe "Preferred Qualifications". Could combine as Requirements and Qualifications? The instruction list includes both Requirements and Qualifications as separate possible headings. We could put mandatory under Requirements, preferred under Qualifications. - Skills: maybe not separate; we could embed skills within Requirements/Qualifications. - Benefits: we have benefits description under Compensation and Benefits. - Pay: we have salary ranges. - Schedule: not mentioned; we should not include Schedule if no content. Also we have About Us (company description). That could be a section but not in the list of headings. The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. But we have About Us content; maybe we can incorporate into About the role? Or we could omit About Us as not required? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep About Us info. If we don't have a heading for it, we could still include it as a

without heading? But they said use

for section headings (e.g. ...). It doesn't say we cannot have other headings, but they gave examples. Safer to include About Us as a heading maybe "About the company" but not in list. Might be okay but risk. Better to follow instruction: only use those headings. Then we need to fit About Us somewhere. Could treat as part of About the role? Not ideal but maybe acceptable. However we could add a heading "About Us" as

though not in examples; but they said "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. So we can use other headings as long as they are

. I think it's fine. Thus we will produce sections:

About the role

with the "Who You’ll Work With" paragraph.

Responsibilities

with list from What You’ll Do.

Requirements

with mandatory "What You’ll Bring" bullet list.

Qualifications

with Preferred Qualifications bullet list.

About Us

with company description.

Benefits

with benefits description (time off, parental leave, 401k, health, etc.)

Pay

with salary ranges. We must not include Schedule. We must remove boilerplate: EEO, accommodations, application instructions, etc. Also remove "We are committed to pay transparency..." etc? That's part of compensation but maybe we keep the pay range and brief statement. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove EEO and accommodations paragraphs. Also remove "We will accept applicants until October 31, 2026 date, or until the position is filled." That's application instruction? Might be considered boilerplate; remove. Also remove contact email for pay questions? That's maybe part of compensation but could be considered boilerplate; but it's about pay range questions. Might be okay to keep? It's not EEO but it's a contact. Might be considered part of compensation transparency; but safe to keep? The instruction says remove application instructions. That email is for questions about pay range; not exactly application instruction. I'd keep it as part of Pay section maybe. Also remove duplicated lines. Now produce HTML fragment: only the sections, no or . Use

for prose,

• for lists. We need to preserve all substantive information. Let's extract details. Who You’ll Work With paragraph: "As a Genesys Consultant or Senior Consultant on Slalom's Contact Center Modernization team, you will design, configure, and deliver Genesys Cloud CX solutions for enterprise clients. You will be a hands-on technologist who can take a solution from requirements through build, testing, and go-live, working with architects, business analysts, and client technical teams." That's the prose. What You’ll Do bullet points (each starts with a bold phrase? Actually they are separated by · and line breaks). We need to convert each bullet to
• . Let's list them: - Design, configure, and deploy Genesys Cloud CX solutions, including Architect call flows, in-queue flows, routing strategies (skills-based, bullseye, and predictive routing), queues, users, roles, and permissions - Build and support digital channels in Genesys Cloud, including web messaging, chat, email, SMS (Short Message Service), and social channels - Configure Genesys Cloud telephony, including Bring Your Own Carrier (Cloud and Premises), SIP (Session Initiation Protocol) trunks, number porting, sites, and Edge configuration - Build integrations using Genesys Cloud Data Actions, the Platform API (Application Programming Interface), AppFoundry applications, and webhooks to connect to client CRM (Customer Relationship Management), ticketing, and back-office systems - Implement and support CRM integrations, including Salesforce (CX Cloud from Genesys and Salesforce, or Genesys Cloud for Salesforce), Microsoft Dynamics, and ServiceNow - Configure Workforce Engagement Management (WEM) capabilities, including workforce management, quality management, recording policies, speech and text analytics, and evaluation forms - Implement Genesys AI capabilities, including bot flows, digital bot flows, Agent Copilot, and integrations with third-party intelligent virtual agent platforms - Support migrations from legacy and on-premises platforms (e.g., Genesys PureConnect, Genesys Engage, Avaya, Cisco) to Genesys Cloud, including flow conversion and cutover planning - Participate in client sessions to gather technical requirements, and translate them into solution designs, configuration workbooks, and user stories - Create and maintain technical documentation, including solution design documents, call flow diagrams, integration specifications, and runbooks - Develop and execute test plans and scripts for System Integration Testing (SIT) and User Acceptance Testing (UAT); troubleshoot and resolve defects - Support go-live cutover activities and hypercare, and transition solutions to client support teams - Contribute to effort estimates, statements of work, and solution demonstrations as part of business development pursuits - Perform impact analysis on scope change requests as they relate to configuration, integrations, and timeline - Contribute to practice development through reusable assets, accelerators, and knowledge-sharing sessions for Slalom teams Now What You’ll Bring (mandatory): - 3+ years of hands-on experience implementing, configuring, or administering Genesys Cloud CX (5+ years for Senior Consultant) - 5+ years of overall contact center technology experience across cloud or on-premises platforms - Strong working knowledge of Genesys Architect, routing, queues, and Genesys Cloud administration - Experience with contact center telephony concepts, including SIP, carriers, number management, and call recording - Experience building integrations using REST (Representational State Transfer) APIs, JSON (JavaScript Object Notation), and Genesys Data Actions - Understanding of contact center operations and common service metrics (e.g., average handle time, service level, first contact resolution), and how technology decisions affect them - Experience working through the full project lifecycle on enterprise implementations with multiple workstreams - Familiarity with agile delivery methodologies and tools such as Scrum, Jira, and Azure DevOps - Strong written and verbal communication skills, with the ability to explain technical concepts to business and technical audiences - Ability to lead or support client working sessions, virtually or in person - Active Genesys Cloud CX certifications (e.g., Professional, Developer, or Workforce Engagement Management), or ability to achieve them within 90 days of hire Preferred Qualifications: - Consulting or professional services experience delivering Genesys implementations for enterprise clients - Experience with CX Cloud from Genesys and Salesforce, or Salesforce Service Cloud - Experience migrating clients from Genesys PureConnect or Genesys Engage to Genesys Cloud - Scripting or development experience (e.g., JavaScript, Python, Node.js) for integrations, custom agent interfaces, or automation - Experience with Genesys Cloud AI, bots, or third-party conversational AI platforms (e.g., Google Dialogflow, Amazon Lex) - Experience with Genesys Cloud CX as Code, Terraform, or Archy for configuration management across environments - Familiarity with other CCaaS (Contact Center as a Service) platforms, such as Amazon Connect, NICE CXone, or Five9 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." Compensation and Benefits section: we need to split into Benefits and Pay. Benefits prose: "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." Pay prose: "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: The targeted base salary pay range for a Senior Consultant is: * East Bay, San Francisco, Silicon Valley: * Senior Consultant: $167,000-$203,000 * San Diego, Los Angeles, Orange County, Seattle, Boston, Houston, New Jersey, New York City, Washington DC, Westchester: * Senior Consultant: $153,000-$186,000 * All other locations: * Senior Consultant: $140,000-$171,000 In addition, individuals may be eligible for an annual discretion