Software Developer I

About the role:

Octagos Health is a cardiac remote-monitoring platform. Our clinical staff monitor pacemakers, defibrillators, and wearable cardiac monitors for patients across the country. When a patient's device stops transmitting, someone has to call them. That outreach runs on NICE CXOne, and it is almost entirely automated.

This is not a contact-center administration role. You will not spend your days configuring skills in a web console. Our phone system is a software product: a nightly data pipeline that qualifies patients out of a multi-tenant clinical database, builds and uploads a dozen or more targeted call campaigns into CXOne, exposes live API endpoints that our IVR scripts call mid-call to make routing decisions, ingests every call attempt and recording back into a reporting warehouse, and surfaces the whole thing through an internal analytics portal. You will help build and extend that code under the guidance of the engineer who owns it today. The majority of your week will be spent writing SQL and application code, not clicking through admin screens.

This position exists because the engineer who built the system is transitioning out, and we are growing the team that will carry it forward. You will get a structured, hands-on knowledge transfer directly from them, and you will not be expected to shoulder the whole system alone. This is not a black box you inherit cold.

What you will work on:

The CXOne platform

• Author and maintain CXOne Studio scripts and IVR call flows, including the runtime logic that decides whether a patient can be dialed and where the call routes.
• Configure and tune skills, campaigns, dispositions, and Personal Connection dialer settings across multiple outreach teams.
• Provision and manage phone numbers (DIDs), including porting and number assignment.
• Produce and maintain recorded prompts and voice messaging.
• Administer agents, teams, roles, and permissions.

The nightly call-list engine

• Help maintain and extend a .NET 8 Azure Function that runs a dozen or more outreach campaigns every night: executing per-campaign qualification stored procedures, fanning out across every clinical tenant database, normalizing phone numbers, chunking and uploading CSVs to the CXOne Admin API, and archiving results.
• Maintain and extend roughly 8,000 lines of T-SQL that decide who gets called: qualification procedures per campaign, shared exclusion logic (do-not-call, patient labels, clinic opt-outs, in-person visits), and helper procedures.
• Support the audit schema that answers the question auditors and clinic partners actually ask: why was, or was not, this patient called on this campaign on this date?
• Help build new campaigns end to end, with senior review, when the outreach team identifies a new patient population worth calling.

The data and reporting pipeline

• Maintain the service that polls the CXOne Reporting API every five minutes and bulk-loads call-attempt data into our SQL Server reporting warehouse.
• Help maintain the nightly job that downloads call recordings from CXOne and transcribes them with speech-to-text, making every patient conversation searchable.

The internal analytics portal

• Contribute to a Python and Flask reporting portal used daily by outreach leadership: campaign performance, live queue status, agent and telephony metrics, per-patient call-history lookup, and recording search and playback.
• Maintain the per-campaign success definitions behind it. Success means something different for every campaign, and keeping those definitions honest is part of the job.
• Extend it as leadership asks new questions.

The runtime API integration layer

• Support the phone-system API endpoints in our main clinical API that CXOne calls live, during an active call: reverse phone-number-to-patient lookup, dial-eligibility checks, patient labeling, call notes, callback scheduling, and status updates.
• Keep the contract between the IVR scripts and the clinical database correct and fast. An agent is waiting on these responses while the patient is on the line.

Required qualifications:

• 1–3 years of T-SQL and SQL Server development. Stored procedures, set-based logic, window functions, and temp tables, with a willingness to grow into query tuning and reading execution plans. This is the single most important skill in the role and the largest share of the codebase.
• Working knowledge of C#/.NET, Python, or both, from coursework, internships, or on the job. Our stack is .NET 8 (Azure Functions, isolated worker model) and Python with Flask. You need to be genuinely comfortable in at least one and willing to learn the other.
• Familiarity with REST API integration. OAuth2 authentication, JSON payloads, paginated endpoints, retry and rate-limit handling, and CSV or file-based data exchange.
• Some exposure to a cloud platform such as Azure (Functions, Key Vault, SQL Database) and/or AWS (EC2). You will work in both.
• Git and a modern source-control workflow: branches, pull requests, code review, and CI/CD.
• An ownership mindset. You want to be the person who investigates when something breaks and learns to debug your way out of it, rather than escalating and moving on.
• Clear written communication. You will document what you build and explain data findings to non-technical clinical and operations leaders.

Preferred qualifications:

• Hands-on NICE CXOne experience: Studio scripting, Admin configuration, the Reporting API, and Personal Connection outbound dialing. Equivalent depth in Genesys Cloud, Five9, Amazon Connect, or Twilio Flex is just as valuable.
• Healthcare experience, particularly working with PHI under HIPAA.
• Flask and Jinja plus front-end JavaScript, including data-grid libraries.
• Speech-to-text or audio-processing pipelines.
• Multi-tenant SQL Server architecture.
• Telecom fundamentals: DIDs, SIP, number porting, and TCPA and do-not-call compliance.
• Power BI or comparable BI tooling.

What you will be trusted with:

• Growth. You will learn a real production telephony platform end to end, with a senior engineer mentoring you and reviewing your work as you take on more responsibility over time.
• Direct access to the people you serve. You will work with outreach and patient-services leadership to decide what gets built, rather than receiving tickets from a queue.
• Real reach. Campaign changes you ship reach thousands of cardiac patients. When this system works, patients whose devices went silent get reconnected, and their clinicians get their data back.