← Search all jobs

Technical Program Manager - Pharmacy Care

Accolade

Chicago, IL · Posted October 23, 2026

Just laid off? Start here: a plan for the first weeks

More in Illinois job market · All Technical Program Manager jobs (488) · Technology & Software · Engineering jobs

More roles at Accolade

Similar jobs

Where Chicago, IL ranks

Where Chicago, IL placed in our monthly rankings, month by month. Each month stays online at its own address.

Pay compared with the market

This listing does not state pay. Across 150 open technical program manager listings that state pay, the middle half runs $150,000 to $194,500 and the median is $167,500.

Listed pay is what employers advertise, not what people are paid.

Technical Program Manager salaries by state · Check your own pay

How AI is used in this kind of work

AI use among pharmacy aides is little observed so far. Measured exposure for pharmacy aides: 2% (little observed).

Share of this job’s tasks that AI is already used for at work, from real usage. It is not a forecast of job loss, and a low number means no use seen yet. Source: Anthropic Economic Index.

Check how this applies to your own job

Skills this job asks for

Say which you have and which you want to build. We use it to match you to jobs like this one.

  • Reconciliation
  • HIPAA
  • Sso
  • Xml

About the job

The Technical Program Manager, Pharmacy Care owns the delivery of our largest and most complex pharmacy platform programs. This is a hands-on technical delivery role for someone who can hold a multi-party, multi-phase implementation together: integration dependencies across organizations, contractual milestones with defined acceptance criteria, regulated launch requirements, and a phased rollout that moves from a controlled pilot all the way through government-program populations.

You will be the connective tissue between Product, Engineering, Design, Solutions, Data, Security, Compliance, Client Services, Service Delivery, and external partners. The work is equal parts technical fluency and program discipline . Y ou need to be able to read an API specification, run the integration conversation on your own, and then convert what you heard into a plan, a dependency, or an escalation. If a date is going to move, you know first and you say so early.

This program delivers a pharmacy-first digital member experience: medic ine cabinet , claims and prior-authorization visibility, real-time price transparency, benefit and accumulator presentment, digital ID cards, document access, member notifications, an AI care assistant, and the partner integrations that power all of it.

What you'll do

Own the program end to end

Own delivery of a multi-phase, enterprise-scale platform implementation from mobilization and discovery through pilot, staged client rollout, and transition to ongoing operations.

Structure the program into workstreams with clear owners, milestones, and exit criteria.

Build and maintain the integrated program plan: scope, milestones, critical path, dependencies, acceptance criteria, and readiness gates across every workstream.

Sequence phased rollout waves : internal pilot, shared pilot clients, standard commercial rollout, strategic accounts, and regulated and government-program populations

Drive milestone attainment where milestones carry contractual acceptance criteria and commercial consequence . Know exactly what must be true for each gate to close.

Drive the technical integration

Coordinate delivery across the full integration surface: eligibility, identity and authentication, claims history, accumulators, formulary and medication data, real-time pricing, prior-authorization status and intake, document retrieval, event and webhook interfaces, notifications, and federated SSO connections.

Work with Engineering and Architecture on integration design, data mapping, identifier reconciliation across systems, environment strategy, and interface specifications covering authentication, schemas, idempotency, error handling, monitoring, and reconciliation.

Hold the line on data quality and interface readiness , real-time versus batch trade-offs, validation rigor, and what happens when bad data moves downstream fast.

Manage partner-side technical dependencies rigorously: API documentation and sandbox access, file specifications and cadence, test data and credentials, environment provisioning, technical SMEs, and approvals. Track them, age them, and escalate with evidence before they become schedule impacts.

Run governance and quality

Establish and run program governance: meeting cadence, status reporting, RAID log, decision records, RASCI ownership across organizations, and executive-level reporting that tells the truth concisely.

Own scope discipline. Distinguish clarification from expansion, route genuine change through a documented change-control process and protect the committed timeline.

Partner with QA and Engineering to maintain a live quality and release-readiness view : test coverage and execution, defect counts by severity and trend, automation and regression status, environment and test-data blockers, and an honest Green/Yellow/Red call.

Produce release readiness summaries ahead of each major milestone: included and deferred scope, test and UAT completion, open defects and mitigations, security, privacy, performance and accessibility results, residual risk, and a clear Go / Go-with-conditions / No-Go recommendation.

Run post-production validation after each go-live — smoke checks, incident and defect capture, corrective actions, and follow-through.

Carry the regulated-delivery load

Coordinate security and privacy readiness: penetration testing and vulnerability assessment evidence, HIPAA security and privacy review, remediation plans for critical and high findings, compensating controls, and formal sign-off gates.

Drive accessibility conformance, including testing evidence, remediation, and an exceptions process.

<span xml:lang