Azure Software Engineer

Azure Software Engineer
Department: Technology
Location: Remote
FLSA Status: Exempt
People Leader: No
Travel: Less than 10%
Summary
Company Summary
Accuity partners with hospitals and health systems through a technology-enabled, physician-led model that improves clinical documentation integrity, coding accuracy, reimbursement optimization, and quality outcomes.
Job Summary
The Azure Software Engineer owns the engineering, operation, and reliability of Accuity’s Azure application and data services, including the functions, integrations, health data services, and database platforms that Accuity’s products depend on. Reporting to the Vice President, Data Architecture, this is a deep, hands-on engineering role at the center of Accuity’s cloud environment.
The role is accountable for how those services behave in production, including availability, resilience, performance, and cost. It leads root cause analysis and durable remediation for Azure platform incidents, maintains and tests disaster recovery and failover procedures, and keeps provisioned capacity matched to actual workload as systems change.
The Azure Software Engineer is the primary technical contributor to Accuity’s Azure engineering standards, which are owned by Data Architecture leadership and applied consistently across the environment. The role also leads Accuity’s move toward repeatable, code-defined provisioning as the company modernizes how cloud resources are deployed, and builds the documentation and automation that allow the environment to be operated, supported, and extended by more than one engineer.
Responsibilities
Azure Application and Data Services Engineering
• Design, build, and maintain Accuity’s Azure application and data services, including Azure Functions, APIs, integration and messaging services, and supporting components.
• Own the engineering of Accuity’s health data and FHIR services, including ingestion, transformation, and integration with clinical and revenue cycle applications.
• Build and maintain integrations with third-party clinical data platforms and interface partners.
• Develop automation and tooling that reduces manual operation of the Azure environment.
• Support application and data teams with Azure service design, implementation patterns, and troubleshooting.
Reliability, Performance, and Resilience
• Own availability, performance, and resilience for the Azure services in scope, and be accountable for how they behave in production.
• Lead root cause analysis and durable remediation for Azure platform incidents affecting production applications, rather than repeated manual recovery of the same failure.
• Maintain, document, and test disaster recovery and failover procedures for owned services, including participation in scheduled tabletop and recovery exercises.
• Design and tune for real load characteristics, including concurrency, contention, throughput, and latency under peak conditions.
• Implement monitoring, alerting, and observability so service health is visible and issues are detected before users report them.
• Define and maintain availability, recovery, and performance targets for owned services in partnership with Data Architecture leadership.
Cost, Capacity, and Resource Management
• Own cost visibility for the Azure services in scope, and identify and execute optimization opportunities.
• Right-size provisioned capacity as workloads change, including after migrations, cutovers, and service retirements, so the environment reflects actual demand rather than historical allocation.
• Explain cost movement in owned services, including the drivers behind month-over-month variance.
• Recommend service tier, SKU, and architecture changes that reduce cost without compromising reliability or compliance.
• Support Azure consumption planning and forecasting in partnership with Data Architecture and Finance.
Standards, Provisioning, and Deployment Modernization
• Serve as the primary technical contributor to Accuity’s Azure engineering standards, which are owned by Data Architecture leadership, covering resource provisioning, naming, tagging, environment separation, and lifecycle management.
• Apply those standards consistently across the Azure estate, and bring existing resources into alignment over time.
• Lead Accuity’s move toward repeatable, code-defined provisioning, evaluating infrastructure as code approaches and recommending how Accuity should deploy and manage cloud resources going forward.
• Follow change management for production Azure resources, including documented approval, testing, and rollback planning.
• Partner with Platform Management on shared deployment pipelines and environment capability rather than building parallel tooling.
Security and Compliance