Genesys Cloud CX Developer Job – Contact Center Technology and Engineering

Modern contact centers depend on technology that can connect customers with the right people, manage interactions across different channels and keep business processes running reliably. Behind that experience is a considerable amount of technical work involving routing, automation, integrations, application programming interfaces and cloud-based systems. For organizations using Genesys Cloud CX, having a developer who can understand that environment and make practical technical improvements is an important part of maintaining an effective contact-center platform.

This Genesys Cloud CX Developer opportunity is designed for an experienced technical professional who can work directly inside an enterprise contact-center environment. The position is strongly hands-on, with responsibilities ranging from Genesys Cloud configuration and Architect development to API integrations, automation, testing, troubleshooting and deployment.

The ideal candidate is not someone who only understands Genesys Cloud at a theoretical level. The role calls for a developer who can enter an existing environment, understand how its components work together, identify problems, make changes and clearly document the work that has been completed.

Working Inside the Genesys Cloud Environment

At the heart of the position is Genesys Cloud CX. The developer will design, develop, modify and troubleshoot Genesys Cloud Architect flows covering inbound, outbound and common modules.

Architect is central to how contact-center interactions move through the platform, so the successful candidate needs strong practical experience working with different types of flows. This includes tasks, decisions, data actions, error handling and reusable flow designs.

The role also covers the configuration and maintenance of important contact-center components. These include IVR logic, ACD routing, queues, skills, routing methods, wrap-up codes, schedules, callbacks and related functionality.

This means the developer will need to understand how different configuration elements interact rather than treating each component as an isolated feature. Changes made to a flow or routing configuration can affect the way interactions are handled, making careful analysis and testing an important part of the work.

The position also extends beyond traditional voice services. The developer will support voice and digital interactions, including chat, messaging, email and SMS, together with other channels supported by Genesys.

Connecting Genesys to Other Systems

A major technical component of the job involves integrations. The developer will build and maintain connections between Genesys Cloud and external enterprise applications and cloud services.

This work involves Genesys Cloud APIs and REST APIs, as well as OAuth, JSON, webhooks and Genesys Cloud Data Actions. The successful candidate should therefore be comfortable working with application interfaces and understanding how information moves between systems.

Genesys Cloud Data Actions are another important area. The developer will be expected to build and troubleshoot them as part of the integration environment.

The role also calls for development experience using JavaScript, Node.js and Python. These technologies will be used to build supporting services and automation around the contact-center environment.

This combination of platform knowledge and software development experience is important because the position is not limited to configuring an existing interface. The developer may need to create supporting technical solutions when a business requirement cannot be addressed through configuration alone.

Understanding cloud environments is also required. Experience with AWS or Azure and cloud-based application integrations will be useful when connecting Genesys Cloud with wider enterprise technology.

When Something Goes Wrong in Production

One of the defining features of this position is troubleshooting. The developer will investigate complex production issues involving Architect flows, routing, telephony, integrations, API requests, authentication, data actions and application behaviour.

This requires a methodical approach to finding the underlying cause of a problem rather than simply applying temporary fixes.

Production investigation may involve reviewing logs, API traces, interaction details, analytics and Genesys Cloud diagnostic information. The developer will need to use the available technical evidence to understand what happened and determine an appropriate solution.

This responsibility makes practical experience particularly important. The employer is specifically looking for someone who can independently analyze an unfamiliar Genesys environment and work through technical problems.

The ability to communicate technical blockers quickly is also required. When an issue cannot immediately be resolved, the developer should be able to explain the problem clearly and communicate what is preventing progress.

Building a More Automated Way of Working

The position also looks beyond day-to-day configuration and support. The developer will help automate Genesys Cloud configuration management and deployment processes in order to reduce manual changes between environments.

This introduces an engineering and automation dimension to the role. Instead of relying heavily on repetitive manual configuration, the developer will contribute to approaches that make changes easier to manage and deploy consistently.

The position includes participation in CI/CD and Infrastructure-as-Code initiatives for Genesys configuration where technically appropriate. Experience with Git and CI/CD workflows is therefore required.

Terraform or other Infrastructure-as-Code experience is listed as a preferred skill. Candidates with this background may be able to contribute to efforts aimed at making Genesys configuration more structured and repeatable.

Automation also extends to testing. The developer will contribute to automated validation and regression testing for contact-center flows and integrations.

This means the role is concerned not only with making a change work once, but also with helping establish ways to check that important functionality continues to work after future changes are introduced.

Supporting Contact Center Migration

Another responsibility is supporting the migration of contact-center functionality from legacy platforms into Genesys Cloud CX.

Candidates with previous Genesys Cloud migration experience will therefore have an advantage, particularly those who have worked with platforms such as Avaya, Cisco, NICE or other legacy contact-center systems.

Migration work requires an understanding of how existing contact-center functionality can be moved into a new environment while preserving the necessary business behaviour. The developer's knowledge of Architect, routing, integrations and APIs becomes particularly relevant when supporting this type of work.

The preferred skills also include knowledge of Genesys Cloud outbound campaigns and dialer functionality. Experience with conversational AI, bots, NLU, intelligent routing or Genesys AI capabilities would provide additional value.

These areas are not presented as mandatory requirements, but they can distinguish candidates who have broader exposure to the Genesys Cloud ecosystem.

Documentation Is Part of the Engineering Work

Technical changes need to be understandable after they have been completed. The developer will therefore create clear documentation covering configurations, Architect flows, APIs, integrations, deployment procedures and troubleshooting.

Good documentation is particularly important in an enterprise environment where technical systems may be maintained or changed by more than one person.

The role also involves participating in technical discussions and providing practical recommendations for solutions that are scalable and maintainable. This means the developer should be able to explain technical decisions rather than simply implement instructions.

Strong written and verbal English communication skills are required, along with the ability to work independently.

The Experience That Matters Most

The most important requirement for this position is strong hands-on experience with Genesys Cloud CX.

Candidates should have significant practical knowledge of Genesys Architect, including inbound call flows, common modules, tasks, decisions, data actions, error handling and reusable flow design. They should also understand ACD routing, queues, skills, routing methods, IVR, callbacks, schedules and broader contact-center concepts.

Technical integration experience is equally important. Applicants should have hands-on experience with Genesys Cloud REST APIs and the Platform API, together with experience developing and troubleshooting Genesys Cloud Data Actions.

A working understanding of OAuth 2.0, REST APIs, JSON, webhooks and API authentication is required.

On the development side, candidates should have experience with JavaScript or Node.js and Python, as well as experience with AWS or Azure and cloud-based integrations.

Knowledge of microservices and event-driven architectures is also required. These skills support the wider engineering responsibilities associated with integrating Genesys Cloud with other systems.

More Than Platform Administration

This opportunity is specifically aimed at a developer rather than someone whose Genesys experience is primarily administrative.

The successful person should be comfortable opening an unfamiliar Genesys Cloud environment, studying existing Architect flows and routing configurations, investigating how systems are connected and identifying the cause of technical problems.

They should also be able to modify configurations, work with APIs, build supporting automation and explain precisely what was changed and the reason behind the change.

That hands-on expectation is one of the clearest characteristics of the role. The position combines development, configuration, troubleshooting and engineering practices, meaning candidates need to be comfortable moving between these areas.

Experience with automated testing, Terraform, CI/CD pipelines, reporting and analytics, operational monitoring, outbound campaigns, AI capabilities or regulated enterprise environments can strengthen an application, although these are listed as preferred rather than core requirements.

Genesys Cloud certifications are also preferred but are not mandatory.

An Engineering Role Within the Contact Center

The Genesys Cloud CX Developer role brings together several technical disciplines within one position. It involves contact-center configuration, software development, cloud integration, API engineering, automation, troubleshooting and deployment.

The successful candidate will work on Architect flows and routing while also supporting digital channels and integrations. They will investigate production issues, contribute to migration projects, improve configuration management and help develop automated testing and deployment processes.

Just as importantly, the developer will need to document technical work and participate in discussions about practical, scalable solutions.

For an experienced Genesys Cloud professional who prefers hands-on engineering over purely administrative work, the position offers an opportunity to work across the technical components that make an enterprise contact-center environment function.

Applicants should make their practical Genesys Cloud experience especially clear when preparing their applications. Experience with Architect, ACD routing, APIs, Data Actions, JavaScript or Node.js, Python, cloud services, troubleshooting and CI/CD should be easy to identify.

Ultimately, the role calls for a developer who can take ownership of technical problems, understand an existing Genesys environment, build and modify solutions, and remain involved from development and testing through to deployment and production support. That combination of platform expertise and engineering ability is at the centre of what this opportunity requires.

Application

CLICK HERE