Genesys Cloud Platform Architect

We need to output HTML fragment with sections: About the role? Actually we have "Who You’ll Work With" and "What You’ll Do" and "What You’ll Bring" and "Preferred Qualifications" and "About Us" and "Compensation and Benefits". According to rules: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map content to these headings. The posting includes: Who You’ll Work With (maybe About the role?), What You’ll Do (Responsibilities), What You’ll Bring (Requirements/Qualifications/Skills), Preferred Qualifications (maybe Skills or Qualifications), About Us (maybe not needed? It's company description; could be omitted? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. About Us is specific content about company; we could include as a section maybe "About the company"? But not in list of allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map to those. "About Us" could be considered "About the role"? Not exactly. Might be better to omit About Us as not required headings. However we could include it under "About the role"? 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. So we should map content accordingly. We have: - Who You’ll Work With: could be part of About the role (description of team). We'll put under

About the role

. - What You’ll Do: Responsibilities. - What You’ll Bring: Requirements/Qualifications/Skills. Could split: Requirements (years experience), Qualifications (certifications), Skills (technical). But we can combine into one section maybe "Requirements". However we have also Preferred Qualifications separate. Could treat as "Qualifications" (required) and "Preferred Qualifications" maybe as "Skills"? But better to have separate sections: Requirements (mandatory), Preferred Qualifications (preferred). The allowed headings include Qualifications and Skills. We could put mandatory experience under Qualifications, and skills under Skills. Preferred Qualifications could be under Skills as well? Might be confusing. Simplify: Use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We'll omit Schedule as not present. We need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, accommodations, application instructions, etc. Also remove duplicated lines. We need to extract content: From posting: Who You’ll Work With: "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." What You’ll Do (list): - 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 What You’ll Bring: - 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: Paragraph about 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. 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 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 October 31, 2026 date, 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 exclude application instructions, EEO, accommodations, etc. The compensation paragraph includes contact email for pay questions; that's not application instruction? It's still contact for pay questions; maybe we keep it? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The email for pay questions is not exactly application instruction; it's about pay transparency. Might be okay to keep? But it's still a contact. Safer to keep only substantive compensation and benefits info, not the contact email. The instruction says remove application instructions; the email is not exactly application instruction but could be considered contact for pay questions; I'd keep it maybe but it's borderline. I'd remove the contact line to be safe. Also need to remove duplicated lines: none. Now produce HTML. Structure:

About the role

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.

Responsibilities

• 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