Manager, Software Engineering, PharmaApps

What Commercial Technologies Software Engineering contributes to Cardinal Health

Commercial Technologies manages the enterprise's portfolio of commercial technologies to maximize the business value of the technologies and enhance the customer experience. This function creates strategies for the portfolio and innovative solutions based on relationships with business leaders, develops back-end solutions and capabilities, and improves the front-end experience.

Commercial Technologies Software Engineering develops design options, process   improvements   and back-end solutions for commercial technologies to maximize performance and suitability for business needs. This job family manages engineering projects and plans for commercial technologies and interfaces with product managers to develop   objectives . This job family assesses product systems,   identifies   opportunities for process and system improvements, and develops solutions through application of engineering principles.

Responsibilitie s

Solution Ownership & Delivery

-
Own   end ‑ to ‑ end   outcomes for assigned Pharmacy Applications across intake, build/configuration, integration, transition to run, and ongoing support

-
Serve as the single accountable owner for pharmacy system delivery, stability, and outcomes,   eliminating   fragmented ownership across platforms and vendors

-
Translate pharmacy, operations, and business goals into executable delivery and integration plans with clear scope, dependencies, success criteria, and risk awareness

-
Ensure predictable delivery through disciplined planning, estimation, execution, and   follow ‑ through   in an   integration ‑ heavy , operationally sensitive environment

-
Establish and enforce   solution ‑ level   decision rights for Pharmacy Apps, reducing   day ‑ to ‑ day   escalation by driving decisions with clear options, tradeoffs, and recommended paths

-
Serve as the technology owner for assigned pharmacy applications,   establishing   platform strategy, priorities, roadmap, operational   objectives , and investment recommendations

-
Own intake evaluation, prioritization, and sequencing of enhancement requests, operational improvements, technical debt remediation, regulatory requirements, and platform modernization initiatives

-
Accountable for solution-level architecture decisions within assigned pharmacy platforms, including integration patterns, technical tradeoffs, lifecycle planning, scalability, resiliency, and maintainability in partnership with Enterprise Architecture

-
Understand and actively manage the business impact of platform performance on patient onboarding, therapy fulfillment, case processing, reimbursement workflows, pharmacy operations, and client commitments

Strategy, Roadmap & Platform Evolution

-
Develop and   maintain   multi-year application roadmaps that align business priorities, technical debt reduction, platform modernization, regulatory requirements, and operational risk management

-
Balance feature delivery, run stability, remediation work, lifecycle management, and modernization investments across assigned pharmacy platforms

-
Identify   automation, simplification, and platform rationalization opportunities that improve scalability, reliability, cost efficiency, and business usability

-
Provide clear investment recommendations and tradeoffs to business and technology leadership based on business value, operational risk, compliance needs, and platform health

Planning, Financial & Capacity Management

-
Develop and manage delivery plans, schedules, and budgets for Pharmacy Applications and supporting middleware

-
Translate systems and integration LOE (interfaces, data flows, environments, validation) into schedule and cost forecasts

-
Maintain capacity plans across onshore and offshore teams, aligning priorities to skills in systems integration, SQL, API development, and operational support

-
Own   solution ‑ level   resource management across Engineering, Integration, QA, PM, and external partners

-
Understand and manage capital vs. expense treatment aligned to enterprise finance standards for pharmacy systems

-
Protect   Sonexus   revenue and operations by understanding system availability,   financial impact , and risk tied to pharmacy platform decisions

SDLC Governance, Delivery Discipline & Flow of Work

-
Define and   operate   a consistent,   well ‑ understood   flow of work for Pharmacy Applications from intake through deployment,   hypercare , and run

-
Ensure adherence to enterprise SDLC gates, QA standards, structured change control, and operational readiness requirements

-
Ensure platform observability requirements are incorporated into the SDLC flow of work (logging standards,   monitoring   instrumentation, alert hygiene, and   post ‑ incident   follow ‑ ups ) to prevent recurring operational issues.

-
Maintain delivery hygiene through WBS, RAID logs, interface inventories, risk management, decision logs, and issue tracking

-
Apply governance that is disciplined and   right ‑ sized , avoiding   over ‑ engineered   processes while   maintaining   operational rigor

-
Identify   recurring delivery or runtime breakdowns within pharmacy systems and drive targeted process and integration improvements rooted in   root ‑ cause   analysis

-
Adjust planning, governance, and communication practices based on delivery phase, operational risk, and observed system outcomes

-
Define and   maintain   clear accountability boundaries between Product, Architecture, Engineering, Infrastructure, Service Operations, vendors, and business stakeholders to ensure effective execution within the   Sonexus   operating model

-
Maintain application interface inventories, critical data flows, dependency mapping, and integration health across internal and external platforms

Build ‑ to ‑ Run   Transition & Run Stability

-
Ensure   build ‑ to ‑ run   transitions for Pharmacy Applications are clearly defined, documented, and executed, including environment readiness, access controls, and knowledge transfer

-
Be accountable for operational outcomes, service performance, and remediation plans for assigned pharmacy platforms and related integration services

-
Partner with business stakeholders and technical teams to define and   maintain   Service Level Objectives (SLOs) and Service Level Indicators (SLIs) for pharmacy platforms and critical integration flows (e.g., availability, latency, error rates, throughput, processing success).

-
Ensure monitoring, dashboards, and alerting are implemented to support defined SLIs/SLOs, including escalation paths and operational runbooks for   timely   response and recovery.

-
Partner with run support, infrastructure, and vendor teams to triage, prioritize, and resolve issues effectively

-
Own intake and prioritization of break/fix work, technical debt, operational enhancements, and remediation initiatives

-
Drive   root ‑ cause   analysis and preventative actions to reduce repeat incidents and operational risk

-
Own application environment strategy including development, testing, validation, training, and production environments, ensuring availability, refresh processes, access controls, and release readiness

Quality, Compliance &   Evidence ‑ Based   Readiness

-
Enforce consistent requirements, integration validation, and testing practices to strengthen   end ‑ to ‑ end   quality accountability

-
Ensure QA, security, networking, and compliance requirements are met, including required evidence, approvals, and remediation

-
Maintain clean,   validated ,   PHI ‑ safe   operational outputs (data extracts, interfaces, reports) prior to internal or external use

-
Strengthen delivery confidence through   evidence ‑ based   readiness rather than   last ‑ minute   escalation

-
Define   evidence ‑ based   operational readiness for releases by validating SLI/SLO coverage (monitoring + alerting) for critical pharmacy workflows before promoting changes to pr