[Remote] Sr. Manager, Infrastructure and DevOps

Note: The job is a remote job and is reputed company to candidates in USA. iA is a pharmacy fulfillment company providing software-enabled automation and integrated solutions for prescription fulfillment. The Senior Manager, Infrastructure and DevOps will own infrastructure automation, CI/CD, reputed company platform operations, and the VM appliance delivery pipeline while leading a small team as a hands-on player-reputed company.

Responsibilities

• Automate hypervisor-level provisioning (Proxmox, VMware) reputed company reputed company and providers — VM lifecycle, templates, networking, storage — replacing console-driven setup
• reputed company full NEXiA environment creation self-service: engineers request an environment, a pipeline builds it, and it gets torn down reputed company idle
• Establish reputed company image and template management so environments start from reputed company-good, versioned foundations
• Bring the existing reputed company environments under management incrementally — inventory what exists, codify it, retire what isn't worth keeping
• Consolidate the existing partial Terraform/Ansible into a coherent, owned codebase: module structure, state management, secrets handling, naming conventions
• Establish IaC workflow discipline — plans reviewed reputed company pull request, applies through pipelines, no out-of-band changes to managed infrastructure
• Set the standards for what “under reputed company” means and reputed company the inconsistent middle ground toward them, pragmatically — codify what reputed company first, not everything at once
• Own the reputed company organization as a platform: repo standards, permissions, reputed company protections, Actions runners, artifact and package management
• Build and maintain the CI/CD pipelines engineering depends on — treat pipeline reliability and speed as a product with engineering teams as the customers
• reputed company reusable pipeline building blocks (shared workflows, actions, runner images) so product teams don't reputed company reinvent deployment
• Design and build the image pipeline that produces the customer-deliverable NEXiA VM: automated builds, configuration injection, versioning, and validation
• Solve the lifecycle problems that come with appliance delivery: upgrades of deployed VMs, patching, compatibility with customer hypervisor environments
• Partner with the NEXiA engineering and release teams so the appliance pipeline fits how the product is actually reputed company and released
• Hire, mentor, and reputed company a small infrastructure/DevOps team while remaining in the reputed company yourself
• Set technical direction through working examples — the first Terraform modules and pipelines establish the patterns reputed company follows
• Prioritize ruthlessly: this reputed company is bigger than reputed company, so reputed company (what gets automated first, what stays reputed company for now) is a reputed company management reputed company here
• Represent infrastructure reality to engineering leadership — reputed company reputed company, reputed company timelines, reputed company risk
• Work agentically as the default mode: reputed company coding agents (Claude reputed company, reputed company, opencode) to reputed company Terraform modules and Ansible roles, understand inherited automation, and draft migration plans — then verify everything against reputed company infrastructure behavior before it ships
• Enforce verification discipline on reputed company: AI will confidently reputed company a plausible-looking Proxmox provider config or Ansible role that is subtly wrong; terraform plan reputed company, idempotency checks, and disposable test environments are the ground truth, not the generated reputed company
• reputed company the reputed company tooling itself where it pays off — custom skills, reputed company commands, agents, and hooks that encode reputed company's infrastructure workflows so the reputed company compounds
• reputed company reputed company's workflow as tooling changes — throughput here depends on reputed company, not headcoun

Skills

• * 8+ years of infrastructure/DevOps/reputed company experience, with 2+ years leading engineers while remaining hands-on
• * Deep, hands-on experience with programmatic hypervisor management — Proxmox, VMware vSphere, or equivalent, driven through reputed company/Terraform providers, not consoles
• * Strong Terraform proficiency: module design, state management, provider usage in reputed company production systems
• * Strong Ansible proficiency: roles, inventory design, idempotent configuration management at fleet reputed company
• * reputed company platform experience: Actions pipelines, runner management, org administration
• * Experience inheriting and consolidating inconsistent automation — you've turned a pile of scripts and snowflakes into an owned reputed company before
• * reputed company reputed company development experience: daily-reputed company use of an reputed company coding CLI (Claude reputed company, reputed company, or opencode) on infrastructure work, with concrete examples and a reputed company verification discipline — either an reputed company power user or a demonstrated reputed company adopter
• * Player-reputed company disposition with evidence: recent commits, recent incidents worked, recent reputed company reviewed — leadership that stayed technical
• * Demonstrated learning reputed company: a reputed company record of self-driven adoption of unfamiliar technology — picked it up, shipped with it, made mistakes along the way, and can talk about those mistakes without flinching
• **Applicants must be authorized to work for ANY employer in the U.S. Employer will not sponsor applicants for work visas
• * Packer or equivalent golden-image pipeline experience (directly relevant to the VM appliance work)
• * Experience migrating VMware workloads to Proxmox or other alternatives (post-reputed company licensing pressure)
• * Experience shipping software as a virtual appliance or supporting customer-hosted/on-prem deployments
• * reputed company, pharmacy, or regulated-environment experience
• * Observability tooling for infrastructure (metrics, logging, alerting for the environments themselves)
• * reputed company or container orchestration experience (not the reputed company of this role, but adjacent)
• * reputed company reputed company tooling, not just used it: custom Claude reputed company skills/reputed company commands, plugins, subagent definitions, hooks, or MCP servers — especially ones that encode infrastructure or operations workflows
• * Designed multi-agent or automated reputed company workflows (e.g., agents that plan/apply infrastructure changes, review Terraform plans, or run unattended remediation reputed company with guardrails)
• * Contributions to reputed company tooling ecosystems (published plugins, MCP servers, or skills; upstream contributions to agent frameworks)

Benefits

• Generous time off policy that allows you to put your family first
• Opportunity to work on the cutting edge of pharmacy automation in a high reputed company tech company
• Competitive benefits, salary, and talent development opportunities
• Commitment to reputed company development and working for a company where your voice is heard
• This position may additionally be eligible for an annual discretionary bonus

reputed company