1

Genesys Developer Jobs in New York (NOW HIRING)

Showing results 41-60

Genesys Developer information

See New York salary details

$21

$62

$83

How much do genesys developer jobs pay per hour?

As of Aug 22, 2026, the average hourly pay for genesys developer in New York is $62.63, according to ZipRecruiter salary data. Most workers in this role earn between $56.01 and $72.07 per hour, depending on experience, location, and employer.

What is a Genesys developer?

A Genesys Developer is responsible for designing, developing, and maintaining customer experience solutions using the Genesys platform. They work with various Genesys technologies, such as Genesys Cloud, PureEngage, or PureConnect, to configure IVR, routing strategies, and integrations with backend systems. Their role often includes scripting, API development, troubleshooting, and optimizing contact center workflows. They collaborate with business teams to enhance customer support experiences through automation and personalization. Strong programming skills, knowledge of telephony systems, and familiarity with cloud-based contact center solutions are essential for this role.

What are the key skills and qualifications needed to thrive as a Genesys developer?

To thrive as a Genesys Developer, you need expertise in computer programming, call center technologies, and knowledge of the Genesys telecommunications platform, often backed by a degree in computer science or a related field. Familiarity with Genesys Composer, Genesys Engage/Cloud, APIs, and certification like Genesys Certified Professional is highly valued. Strong problem-solving abilities, teamwork, and excellent communication skills help developers collaborate with both technical teams and business stakeholders. These competencies are essential for designing effective solutions and ensuring seamless customer experiences in complex contact center environments.

What are some common challenges faced by Genesys developers, and how can they be addressed?

Genesys Developers often encounter challenges related to integrating Genesys with multiple third-party systems, customizing solutions to meet specific business requirements, and maintaining high system reliability. Addressing these challenges typically involves staying updated with platform changes, following best practices for documentation and version control, and working closely with cross-functional teams such as QA, network engineers, and business analysts. Proactive communication and a willingness to learn new features or modules are essential for effectively troubleshooting and delivering robust, scalable solutions. Many organizations support professional development and encourage collaboration, helping developers continuously improve their skills and overcome technical hurdles.

What are the most commonly searched types of Genesys Developer jobs in New York?

The most popular types of Genesys Developer jobs in New York are:

What are popular job titles related to Genesys Developer jobs in New York?

For Genesys Developer jobs in New York, the most frequently searched job titles are:

What job categories do people searching Genesys Developer jobs in New York look for?

The top searched job categories for Genesys Developer jobs in New York are:

Infographic showing various Genesys Developer job openings in New York as of August 2026, with employment types broken down into 81% Full Time, 6% Part Time, and 13% Contract. Highlights an 83% Physical, 5% Hybrid, and 12% Remote job distribution, with an average salary of $130,278 per year, or $62.6 per hour.

Network Voice Support Engineer

Long Finch Technologies

Staten Island, NY • Hybrid

Full-time

This job post has expired 1 day ago. Applications are no longer accepted.


Job description

Provides day‑to‑day operational support and deep telecom expertise across SBC‑centric voice environments. Responsible for monitoring, incident triage, SBC troubleshooting, and carrier coordination in support of a hybrid contact center stack (Genesys today, Amazon Connect migration underway). Works from established runbooks, participates in incident bridges, and escalates issues appropriately

Why this role exists

To provide the day‑to‑day operational backbone for a combined telecom security and incident response program - ensuring stable operations across SBC‑centric voice environments while the contact center runs in a hybrid state (Genesys now, Amazon Connect migration underway), with disciplined incident response and change execution.

Key Responsibilities:

·       Monitor and triage telecom incidents impacting public‑facing voice platforms, including SBC health and call routing behavior

·       Investigate issues using CDRs, SBC logs, SIP traces, and vendor/carrier feedback

·       Support STIR/SHAKEN operational behaviors, including signing success/failure, exceptions, unsigned calls, and carrier rejections

·       Execute approved operational changes using defined runbooks and change windows (no ad‑hoc architecture changes)

·       Coordinate with carriers, vendors, and internal engineering/SRE teams during incidents

·       Participate in incident bridges and support escalation workflows

·       Maintain runbooks/SOPs and operational documentation/audit artifacts; contribute to post‑incident RCA documentation

Required Qualifications:

·       5–7+ years of VoIP/telecom operations experience in enterprise environments

·       Strong experience supporting SBC‑based voice services, including SIP call flows, routing, and log analysis (CDR/SBC/SIP/session logs)

·       Experience with incident management processes (ITSM/ticketing, escalations, documentation)

·       Working familiarity with contact center call flows and platforms (Genesys and/or Amazon Connect

Preferred Qualifications:

·       Experience in BFS or regulated industries with strict change/audit requirements

·       Ribbon SBC familiarity (preferred) and/or exposure to PSX‑style routing/policy constructs

·       Familiarity with STIR/SHAKEN failure modes and operational monitoring patterns

·       Experience supporting hybrid contact center environments during migrations (on‑prem to cloud)

·       Experience acting as a telecom architect or L3 support

·       Exposure to enterprise monitoring and observability tools

  • Experience working in BFS Sector