Software Development Engineer - Application Architecture

Position Summary

Our journey calls for senior‑level engineers who can shape the future of pharmacy prior authorization platforms and solutions for CAS (Clinical Authorization System). As a Staff Software Development Engineer - Application Architecture, you serve as a technical authority for CAS architecture and design. You define, evolve, and govern architectural patterns across multiple teams while remaining hands‑on with design, code, and critical technical decisions.

This role is central to CAS modernization as we evolve from a large on‑prem monolith to a cloud‑ready, API‑first, domain‑aligned platform.

• Drive decomposition of legacy monolithic components into cloud‑ready services and modular architectures.
• Balance short‑term delivery needs with long‑term architectural sustainability and modernization goals.
• Define and deliver a clearly articulated CAS North Star Architecture, describing the target‑state platform, core principles, reference patterns, and a phased migration strategy from legacy to future state.
• Architect a cloud‑ready, hybrid‑capable platform supporting coexistence of on‑prem and cloud workloads during migration, with clear service boundaries and integration contracts.
• Drive API‑first design with consistent standards for versioning, backward compatibility, contract testing, and developer experience to enable internal and partner interoperability.
• Establish domain‑aligned services and modular components (DDD‑inspired bounded contexts) to reduce coupling and enable independent delivery by multiple teams.
• Design and promote event‑driven architectures where appropriate, publishing authorization and clinical lifecycle events to enable scalable workflows and downstream integration without point‑to‑point dependencies.
• Define a pragmatic strangler‑fig migration strategy for decomposing the legacy monolith, including incremental cutovers, coexistence patterns, and measurable milestones.

• Own CAS architecture governance, including principles, standards, reference architectures, reference implementations, ADRs, and a lightweight, auditable exception process with time‑bound remediation.
• Produce and maintain executable reference patterns for common concerns such as API design, service templates, security controls, integration patterns, data access, and observability.
• Define and report architecture governance metrics (e.g., standards adoption, exception volume and age, architectural debt remediation, service SLO attainment, and change quality indicators).

• Define architectural patterns spanning presentation, service, integration, data, and platform layers, ensuring alignment between UI experiences, APIs, and backend workflows.
• Establish standards for frontend architectures (componentized UI, accessibility, performance budgets) aligned with shared design systems and backend contracts.
• Design backend services using modern stacks (e.g., .NET, Java, Node.js) with clean architecture, testability, and clear separation of concerns.
• Standardize synchronous and asynchronous integration patterns (REST/JSON, messaging, streaming, gRPC where applicable) with secure partner connectivity.
• Drive platform architecture aligned to Azure and/or GCP, including containerization, environment strategy (dev/test/stage/prod), networking, secrets management, and landing‑zone alignment.
• Partner with Dev Sec Ops  to define CI/CD and Dev Sec Ops  standards, including automation‑first testing, security scanning, policy gates, infrastructure as code, and safe deployment strategies (blue/green, canary).

• Design for reliability and operability by default, defining SLIs/SLOs, graceful degradation, bulkheads, and resilient integration patterns.
• Define and enforce security and compliance architectures for regulated healthcare data, including least‑privilege access, encryption, auditability, identity controls, and data classification standards.
• Establish observability requirements across services (metrics, logs, traces, alerts),…