Sr. DevOps Engineer

Alteva RCM•New York, NY

1d•$160,000 - $200,000

About The Position

Alteva RCM is hiring its first dedicated DevOps engineer to own how code moves from developers’ machines to production safely and repeatably. The role owns development, test, and staging environments; deployment pipelines; and infrastructure standards, while serving as the technical authority directing the managed service provider on production. The engineer will balance developer productivity with security in a HIPAA-regulated environment and will build and maintain systems directly, rather than focusing only on policy. The position covers Azure infrastructure, with a smaller AWS footprint, infrastructure as code, CI/CD for .NET applications and supporting services, release automation, environment isolation, and secure test data. It also includes implementing access controls, secrets management, audit logging, monitoring, alerting, and documentation; coordinating with IT and security; and leading platform incident response and post-incident reviews. The role is not a 24/7 on-call or ticket-taking position. The engineer will establish documentation and monitoring so the managed service provider can handle off-hours support, and will set technical direction as the engineering team grows. During the first 90 days, the engineer will learn the existing environments, pipelines, and pain points; audit data movement between production and non-production; close gaps; and publish a target architecture and initial standards. The role is based in Queens, NY, and is listed as full-time. The stated pay range is $160,000–$200,000 USD.

Requirements

At least 5 years of experience in DevOps, platform engineering, or SRE, including ownership of production environments.
Deep hands-on Azure experience with networking, identity (Entra ID), compute and app hosting, Key Vault, and Azure Monitor.
Infrastructure as code experience with Terraform or Bicep.
CI/CD experience with Azure DevOps or GitHub Actions, ideally for .NET workloads.
Docker experience.
Scripting experience in PowerShell plus Bash or Python.
Experience securing environments that handle sensitive or regulated data.
Experience directing or working closely with an external infrastructure provider.
Clear written documentation habits; runbooks will be used by people who are not present with the engineer.

Nice To Haves

Kubernetes or AKS experience.
HIPAA, SOC 2, or HITRUST experience.
AWS experience.
Salesforce deployment pipelines or other enterprise SaaS release management experience.
Test data masking or synthetic data generation experience.
Supporting AI or LLM-based workloads, and using AI-assisted tooling in professional work.
Background in healthcare, RCM, fintech, or another high-volume operational environment.

Responsibilities

Own development, test, and staging environments, including provisioning, configuration, access, and cost.
Define target production architecture and standards, and direct the managed service provider’s work against them.
Manage infrastructure as code across Azure and a smaller AWS footprint.
Isolate environments to keep production data in production and provide realistic masked or synthetic data for development and testing.
Build and maintain CI/CD pipelines for .NET applications and supporting services.
Own release mechanics, including deployment automation, rollback readiness, and environment promotion.
Serve as the single intake point for infrastructure and environment requests from development teams.
Implement least-privilege access, secrets management, and audit logging that meet HIPAA requirements.
Work with IT and security on endpoint and network controls that enable developers to work effectively without weakening protection.
Maintain infrastructure and access documentation for audits.
Set up monitoring, alerting, and logging so issues are identified early and routed appropriately.
Write runbooks, escalation paths, and setup documentation for the managed service provider’s after-hours, weekend, and holiday support.
Lead incident response and post-incident reviews for platform issues.
In the first 90 days, learn current environments, pipelines, and pain points from developers and the managed service provider; audit data movement between production and non-production and close gaps; and publish a target picture and initial standards.
Set technical direction, decline unsafe approaches, and shape how the team ships as it grows.