Genesys Cloud Platform Architect

We need to output HTML fragment with sections: About the role? Actually the posting includes "Who You’ll Work With", "What You’ll Do", "What You’ll Bring", "Preferred Qualifications", "About Us", "Compensation and Benefits". We need to map headings: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should use appropriate headings: maybe "About the role" corresponds to "Who You’ll Work With"? Or "What You’ll Do" is Responsibilities. "What You’ll Bring" is Requirements/Qualifications. "Preferred Qualifications" could be Skills or additional 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. So we can include About Us as maybe not a standard heading but we could put under "About the role"? But they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. - About the role: could be "Who You’ll Work With" description. - Responsibilities: "What You’ll Do". - Requirements: "What You’ll Bring" (mandatory). - Qualifications: maybe "Preferred Qualifications". - Skills: maybe not separate; could combine with Qualifications. - Benefits: from "Compensation and Benefits" section includes benefits description. - Pay: salary ranges. - Schedule: not mentioned; we should not include Schedule if not present. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: EEO, accommodations, application instructions, etc. Also remove "We will accept applicants until October 31, 2026 date, or until the position is filled." That's application instruction? It's a deadline; maybe considered application instruction; we should remove. Also contact email for pay range questions? That's maybe part of compensation; but it's a contact for questions; could be considered boilerplate? Might keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The contact email for pay range questions is not exactly application instruction but could be considered part of compensation transparency; but it's a contact for questions; might be okay to keep? Safer to remove? It's not EEO; it's about pay range questions. Might be considered part of compensation info; but it's a contact. I'd keep it as part of Compensation and Benefits? However they said "include a section ONLY when the posting has real, specific content for it". The contact email is specific content; but it's not a standard heading. Could be placed in a

under Benefits or Pay. I'd include it as a

under Pay maybe. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from sections. Let's extract content: 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 (Responsibilities): List bullet points starting with "·". Need to convert to

• . Keep all bullet points. What You’ll Bring (Requirements): Bullet points. Preferred Qualifications: Bullet points. About Us: Paragraph about Slalom. Compensation and Benefits: Paragraph about benefits, then salary ranges with bullet-like asterisks. We need to format salary ranges: maybe as
  • etc. The text includes: "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 remove the application deadline line and maybe the contact email? The contact email is part of compensation transparency; but it's a contact for questions; might be considered not boilerplate. However it's a line that says "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." This is somewhat like a contact for compensation questions; could be kept. But it's not a standard heading; we can put as a

    under Pay or Benefits. We must not include EEO etc. So remove the EEO and Accommodations section entirely. Now produce HTML:

    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
    • 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

    Requirements

    • 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

    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 the company

    maybe not needed but we have About Us content. The instruction headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About Us". But we could put under "About the role"? Already used. Could we add a section "About the company"? Not in list; better to omit? But we must preserve ALL substantive information; omitting About Us would lose