Remote Senior Java Developer - with IVR (Avaya OD)

Hi,

Hope you are doing well,

Please find the job description given below and let me know your interest.

Position: 100% Remote Senior Java Developer with IVR (Avaya OD)

Location: Remote

Duration: 12 month project ( high chance of C2H)

Job Description

Core Qualifications

10+ years of Java development experience, with a strong foundation in traditional Java and Spring Framework.

Avaya Orchestration Designer (OD) IVR experience is mandatory must have worked on IVR systems in at least 3 recent projects.

Deep understanding of RESTful API integration, including consuming and creating endpoints.

Experience with SOAP APIs, with the ability to migrate away from legacy SOAP to REST.

Familiarity with MS SQL Server and relational databases (PostgreSQL, Oracle); exposure to NoSQL (e.g., MongoDB) is a plus.

Exposure to Salesforce integrations, especially screen pops and backend data flows.

Comfortable working with GitHub and GitHub Actions; able to contribute to maturing CI/CD pipelines.

Strong communication skills able to collaborate across teams, explain architecture, and advocate for technical decisions.

Work Style & Expectations

Must be able to work independently with minimal supervision.

Expected to own the replatforming effort and lead the rebuild of the IVR application.

Will collaborate with one junior FTE engineer and provide ongoing knowledge transfer.

Will receive onboarding and architectural guidance from Rick Groshek, a manager with deep IVR experience.

Must be proactive, resourceful, and capable of navigating complex environments with minimal hand-holding.

Project Overview

Current System

IVR system built using Avaya OD and Java, hosted on WebSphere.

Integrates with Nuance for speech recognition.

Uses SOAP-based legacy APIs for client data, authentication, and product lookups.

Caller data is written to an MS SQL database, supporting Salesforce screen pops.

Migration Goals

Lift-and-shift the application from WebSphere to Tomcat (TC Server).

Replace SOAP integrations with RESTful APIs from Enterprise Integration Services (EIS).

Maintain existing routing logic and Nuance integration no major functional changes.

Ensure compatibility with new API endpoints and database interactions.

Tech Stack

Java (Spring Framework)

REST APIs

GitHub & GitHub Actions

MS SQL Server

Salesforce

No containerization (not using Docker or OpenShift)

Work Environment

Remote role