1

Ivr Developer Jobs in Washington (NOW HIRING)

The Unified Collaborations Engineer serves as a subject matter expert in Cisco Collaboration ... Additionally, a UCCX CSQ or Advanced IVR will be supported per cutover and requires Iron Bow ...

Machine Learning Specialty, Solutions Architect, or DevOps Professional * Experience with TRICARE, DHA, or healthcare insurance domain knowledge * Background in conversational AI design (IVR ...

VoIP Systems Engineer

Mclean, VA · On-site

$165K - $295K/yr

Integrate telephony systems (e.g., IVR, call routing) into web applications using Ruby on Rails ... Proficiency in Ruby programming and the Ruby on Rails framework, along with strong experience in ...

New

Integrate telephony systems (e.g., IVR, call routing) into web applications using Ruby on Rails ... Proficiency in Ruby programming and the Ruby on Rails framework, along with strong experience in ...

NICE CXone Engineer

Columbia, MD · On-site

$100K - $127K/yr

The NICE CXone Engineer is responsible for the configuration, administration, optimization, and ... Troubleshoot IVR logic, call failures, latency, and routing issues Analytics & Reporting Support

next page

Showing results 1-20

Ivr Developer information

What are the key skills and qualifications needed to thrive in the Ivr Developer position, and why are they important?

To thrive as an IVR Developer, you need a solid background in software development, strong knowledge of telephony systems, and experience with scripting or programming languages such as VXML, Java, or Python—often supported by a degree in computer science or a related field. Familiarity with IVR platforms like Genesys, Avaya, or Cisco, as well as an understanding of APIs and speech recognition technologies, are frequently required; relevant certifications in these platforms can be advantageous. Strong problem-solving abilities, effective communication, and attention to detail are essential soft skills for this role. These competencies ensure the development of reliable, user-friendly IVR systems and enable effective collaboration with cross-functional teams to meet business needs.

What is an IVR Developer job?

An IVR Developer is responsible for designing, developing, and maintaining Interactive Voice Response (IVR) systems that automate customer interactions over the phone. They work with telephony technologies, scripting languages, and APIs to create voice-driven applications that handle tasks like call routing, authentication, and self-service options. IVR Developers collaborate with business teams to gather requirements and ensure the system meets customer needs while integrating with backend databases or CRM systems. Strong knowledge of VoIP, SIP protocols, and IVR tools like Genesys, Avaya, or Twilio is often required.

What are the typical daily responsibilities of an IVR Developer?

IVR Developers typically spend their days designing, coding, and testing interactive voice response applications tailored to meet specific business requirements. They collaborate closely with business analysts, QA testers, and system administrators to ensure seamless integration with existing infrastructure and optimal user experience. Daily tasks often include troubleshooting issues, optimizing call flows, maintaining documentation, and implementing updates based on user feedback or new features. This role frequently involves analyzing call data and user interactions to identify areas for improvement and deliver high-quality voice solutions.

What are popular job titles related to Ivr Developer jobs in Washington? For Ivr Developer jobs in Washington, the most frequently searched job titles are:
What job categories do people searching Ivr Developer jobs in Washington look for? The top searched job categories for Ivr Developer jobs in Washington are:
What cities in Washington are hiring for Ivr Developer jobs? Cities in Washington with the most Ivr Developer job openings:
What are popular job titles related to Ivr Developer jobs in WA? For Ivr Developer jobs in WA, the most frequently searched job titles are:
Infographic showing various Ivr Developer job openings in Washington as of July 2026, with employment types broken down into 82% Full Time, 8% Part Time, 1% Temporary, and 9% Contract. Highlights an 80% Physical, 5% Hybrid, and 15% Remote job distribution.
UC Engineer

Full-time

Re-posted 13 days ago


Job description

The Unified Collaborations Engineer serves as a subject matter expert in Cisco Collaboration technologies to include Cisco Unified Communications Manager, Unity, Contact Center Express, Emergency Responder.
WHAT YOU'LL BE DOING
· Provide technical expertise to customers and partner engineering teams.
· Work as a trusted advisor to customers in knowledge of Cisco collaboration technologies.
· Support complex migrations as part of a team.
· Support customers regarding cloud, collaboration, security, networking, mobility, end user devices, managed services, and workforce experience.
· Support technical strategies that satisfy customer requirements based on Iron Bows capabilities.
· Traveling to local customer sites in the DC Metro area.
LOCATION
· Georgetown University Hospital located at 3800 Reservoir Rd NW, Washington, DC 20007
TRAVEL REQUIREMENTS
· This position requires candidates to be based in the greater Washington, D.C. metropolitan area and be able to travel to customer sites within the Washington DC area.
IMPLEMENTATION TASKS
· Iron Bow Engineers will perform the following tasks:
· Oversee deployment of Cisco IP Phones and associated Key Expansion Modules (KEM)
· Oversee deployment of Analog Gateways
· Add mailboxes to Unity Connection
· Oversee rack, install, and configure of Analog Gateways
· Configure workbooks
· Support Migration and Cutover
· Perform Test and Acceptance
Workbook Planning
· Workflows / Device Programming / Workbooks
o Capture end-user requirements and define the test plan.
o Detail required Workflows / functional user groups / operational units
o Each Workflow is based on one functional user group / community that shares the same call flow, main numbers, etc. as to not break the mainline / call flow dependency per workbook.
o Review and updated documents (Floor Plans, BAT)
o Functional Workgroup Design
o capture end-user requirements and define the test plan.
o Work with our clients to align existing capabilities to MedStar standard capabilities for example:
§ Line Appearances
§ DID vs non-DID
§ Main Line / Back Line
§ Required Device
§ Voicemail
§ IVR
§ Port List
§ E911 ELINs
§ E911 Emergency Contact Information
§ E911 RedSky User data
o Document call flow(s) and provide meeting notes to update workbook with data captured and provide to the Iron Bow PM within 3 business days
o Under the Iron Bow Lead Engineer direction facilitate technical discussions during workbook reviews with functional user groups.
o Within each workbook, a Test Plan will be created that details how the solution will be tested and what results are expected. The test plan will include items such as:
§ validating build
§ validating call flows
§ validating IVRs
§ desk set features/functions
§ failover testing
§ and integration testing (SME, UCCX, Unity Connection, etc.)
o
Device Programming
· Program devices based on the final approved workbooks
o Voicemail Mailbox Creation
o Configure analog ports
o VoIP Phones
o KEM (only works with 8851, new or exsiting)
Cutover/Post-Cutover Support
On customer site supporting Cutover tasks
· Execute and documents Tests with MedStar (Based on the Workbooks)
· The installation anticipates a phased approach to minimize impact to staff and patients, and to fit into the MedStar Maintenance Windows.
· Iron Bow plans for six (6) cutovers for telephones and analog ports, which will include migrating from 4 to 5 digits prior to or during the first cut-over.
· Phased cutovers will cover the Unify multi-button IP Telephones.
· A cutover for the analog station ports to take place with each phased phone station cutover. The hospital cutovers will be coordinated with MedStar and will involve configurations to both the CUCM and the Unify phone system, and to the PSTN connectivity from the PSTN providers. Additionally, a UCCX CSQ or Advanced IVR will be supported per cutover and requires Iron Bow support during cutover and support post cutover.
· At a high level the cutover will include:
o Legacy PBX configuration to support Inter-system calling, meaning re-route of internal and PSTN calling to phones that have been migrated to CUCM via SIP trunks
o CUCM configuration to ensure inter-system calling to the legacy PBX and to the PSTN
o Porting DID extensions from the facilities in the legacy PBX to SIP trunking to the ISR4451 and the ASR1002X CUBE gateways
o Migration from 4 to 5 digit dialing prior to or during first cutover
o UCCX Basic and Advanced IVR updates and end-user support
o Telephone replacement as outlined in the sections above
o Test and Acceptance per design documentation
· On customer site supporting Post Cutover tasks for 8 hours per day for three consecutive days following each cutover.
e911
· Travel to site and test each ELIN (108) added to an ERL using the ?Test ERL? via VPN or Local test phone. The reason to test an ELIN is to ensure it will be displayed at the PSAP correctly. The ERLs and Discovery via IP Subnet have already been established. Once testing has been completed successfully, the ELINs will be added to their ERL as appropriate prior to phone go-live and documented for transition.