
Sr. Manager, Software Engineering
Most applications go out cold — see where you stand first. No sign-up to start.
Don't just apply. Show up ready.
Olive works from this exact posting — no sign-up to start.
At a glance
Job overview
The Sr. Manager, Software Engineering will lead a small team modernizing a legacy pharmacy automation platform, combining hands‑on coding with player‑coach leadership, driving predictable releases, enforcing engineering practices, and leveraging AI‑native tooling while ensuring backward compatibility for on‑prem customer deployments.
Skills & qualifications
Skills
Qualifications
Benefits
Full job description
The Role:
Lead a small software engineering team modernizing the NEXiA platform — a customer-deployed pharmacy automation system that has evolved through several technology generations. The work is incremental decomposition of a .NET/VB6-era codebase into well-bounded modules, shipped to on-prem customer environments where upgrade safety and backward compatibility are non-negotiable.
The day-one reality: the team is capable but the delivery machinery around it is uneven. Standards vary across repos, test coverage is inconsistent, and release discipline depends more on individual habits than on shared process. The mission is to turn this into a team that ships predictably — clear ownership, reviewed code, tested changes, boring releases.
This is a player-coach role. You will lead the team and you will personally write and review code every week. Candidates whose hands-on work ended when they became managers are not a fit for this role.
The engineering environment here is code-driven end to end: environments are provisioned through Terraform and Ansible, builds and deploys run through GitHub Actions, and the product ships to customers as a versioned VM. You won’t own that substrate — a peer infrastructure team does — but you can’t lead effectively here while treating it as a black box. You need to understand what infrastructure as code is and the role it plays in this ecosystem: why environments are code-driven, what the pipeline does between commit and customer, and how to hold your team accountable for the operability of what they ship. Being able to read the Terraform yourself is a bonus, not the bar.
Finally: this team is pushing boundaries, particularly in agentic tooling, where the state of the art changes monthly. That requires someone who leans in — who learns by trying, breaks things in the process, and treats those mistakes as tuition rather than something to apologize for. Curiosity here is not a personality bonus; it’s how the work gets done.
What you’ll do:
Team Leadership (Player-Coach)
-
Hire, mentor, and lead a small software engineering team while remaining in the code yourself
-
Set technical direction through working examples — the patterns you establish in code review and your own commits are the ones the team follows
-
Create clear ownership and accountability: who owns which modules, who makes which decisions, what “done” means
-
Address performance issues directly and early; a small team can’t carry passengers
-
Represent engineering reality to leadership — honest capacity, honest timelines, honest risk
Delivery Management
-
Own sprint-to-sprint execution: planning, sequencing, and unblocking so the team ships predictably
-
Establish and enforce engineering practices — pull-request review discipline, meaningful test coverage, incremental delivery over big-bang merges
-
Drive releases that are routine, not events: staged rollouts, rollback paths, and validation against the customer configurations that actually exist
-
Prioritize ruthlessly: modernization scope always exceeds capacity, so sequencing (what gets decomposed first, what stays legacy for now) is a core management skill here
Technical Direction
-
Guide the incremental decomposition of legacy NEXiA capabilities into bounded, testable modules without disrupting active customers
-
Make and defend architectural trade-offs between isolation and pragmatism — not every boundary needs a rewrite
-
Design for customer-deployed constraints: long-lived versions, upgrade paths, backward compatibility, customer-specific configurations
-
Partner with Product and Quality so modernization work aligns with customer impact, not just architectural preference
DevOps & Delivery Pipeline Fluency
-
Understand the infrastructure-as-code substrate the team builds on: what Terraform and Ansible manage, which changes affect your team’s environments, and when to pull in the infrastructure team
-
Treat CI/CD as part of the engineering system you manage — hold the team accountable for pipeline health, build times, and flaky tests rather than treating them as someone else’s problem
-
Ensure what the team ships is operable: logging, diagnostics, and upgrade behavior are reviewed as part of the work, not discovered in the field
-
Partner with the infrastructure team on environment needs — self-service test environments, image pipeline requirements, deployment automation — as an informed customer, not a bystander
AI-Native Engineering Practice
-
Work agentically as the default mode: direct coding agents (Claude Code, Codex, opencode) to understand legacy code, draft decompositions, and generate migration scaffolding — then verify everything against real system behavior before it ships
-
Enforce verification discipline on the team: AI will confidently generate a plausible-looking characterization of undocumented code that is subtly wrong; tests, behavior comparison, and staged rollout are the ground truth, not the generated code
-
Extend the agentic tooling itself where it pays off — custom skills, slash commands, agents, and hooks that encode the team’s workflows so the leverage compounds
-
Evolve the team’s workflow as tooling changes — throughput here depends on leverage, not headcount
Who you are:
-
8+ years of software engineering experience, with 2+ years leading engineers while remaining hands-on
-
Strong proficiency in a statically-typed OO language (C#/.NET strongly preferred; Java or similar accepted with willingness to ramp)
-
Experience modernizing or maintaining long-lived production systems — you’ve worked at the boundary between legacy and modern code, not exclusively greenfield
-
Experience shipping customer-deployed or on-prem software: upgrade paths, backward compatibility, long-lived versions
-
DevOps literacy: understands what infrastructure as code is and its role in a modern delivery ecosystem — why environments are provisioned from code, what CI/CD pipelines do between commit and deploy, and what it takes to make software operable in environments you don’t control
-
Track record of raising a team’s engineering discipline — review culture, testing standards, release predictability — with concrete before/after evidence
-
Real agentic development experience: daily-driver use of an agentic coding CLI (Claude Code, Codex, or opencode), with concrete examples and a clear verification discipline — either an experienced power user or a demonstrated rapid adopter
-
Player-coach disposition with evidence: recent commits, recent incidents worked, recent code reviewed — leadership that stayed technical
-
Demonstrated learning agility: a track 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
Even better if you have:
-
Reading fluency in Terraform or Ansible — can follow a plan or a role and spot what it changes (authoring experience even better)
-
Experience with domain-driven design: bounded contexts, anti-corruption layers, strangler-fig migrations
-
Experience shipping software as a virtual appliance or supporting customer-hosted deployments
-
Healthcare, pharmacy, or regulated-environment experience
-
Observability practice: metrics, logging, and alerting as part of the definition of done
-
Experience partnering with (or having owned) a platform/infrastructure team
-
Built agentic tooling, not just used it: custom Claude Code skills/slash commands, plugins, subagent definitions, hooks, or MCP servers — especially ones that encode infrastructure or operations workflows
-
Designed multi-agent or automated agentic workflows (e.g., agents that plan/apply infrastructure changes, review Terraform plans, or run unattended remediation loops with guardrails)
-
Contributions to agentic tooling ecosystems (published plugins, MCP servers, or skills; upstream contributions to agent frameworks)
Applicants must be authorized to work for ANY employer in the U.S. Employer will not sponsor applicants for work visas.
Compensation:
The estimated base annual salary range for this position is $148,750 to $ 201,250, though a candidate’s base annual salary shall be determined on a range of factors, including, but not limited to, qualifications and experience. This position may additionally be eligible for an annual discretionary bonus.
What are the perks?
-
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 growth tech company
-
Competitive benefits, salary, and talent development opportunities
-
Commitment to professional development and working for a company where your voice is heard
More about iA:
iA® (Innovation Associates®) is a pharmacy fulfillment company that provides an integrated platform of capabilities to support Centralized and Community Pharmacy Fulfillment Solutions. With over 30 years of experience in the pharmacy fulfillment business, we have developed and implemented a suite of automation and software solutions that help deliver quick and sustainable business results. Our integrated Pharmacy Fulfillment Platform enables scalable solutions that helps run the prescription fulfillment process from prescription acceptance to delivery, supporting dynamic design flexibility to service pharmacies in a variety of volumes and settings. Our solutions improve workflow, and increase efficiency, while enabling more time for pharmacists to focus on their patients. iA works with pharmacy providers in the Commercial, Health Systems, Government, and Mail Order/eCommerce markets. iA can help customers transform their pharmacy. For more information, visit iARx.com.
Our Mission: We partner with providers to transform pharmacy through our leading-edge software enabled fulfillment technology and partners to deepen the patient-pharmacist relationship, enhancing patient safety and choice while increasing operational efficiency. iA empowers pharmacists to focus on patient care. iA can run the prescription fulfillment process from start to finish, helping pharmacies manage fulfillment and inventory to help lower costs, improve efficiency, increase safety, and provide comprehensive Rx tracking and real-time support.
Our Products:
-
Software
-
Modular Hardware
-
Sophisticated Counting and Collation Devices
Our Core Values:
-
Solutions Driven
-
Customer Centric
-
Championing Diversity
-
Empowering Ownership
-
Trust Daringly
To learn more about iA’s product, people and culture visit us at iARx.com OR check us out on LinkedIn (https://www.linkedin.com/company/iarx/mycompany/) , Facebook (https://www.facebook.com/iA.Pharmacy.Automation/) , or YouTube (https://www.youtube.com/c/InnovationPharmacyAutomation/featured) !
iA provides equal employment opportunities to all employees and applicants for employment and prohibits discrimination and harassment of any type without regard to race, color, religion, age, sex, national origin, disability status, genetics, protected veteran status, sexual orientation, gender identity or expression, or any other characteristic protected by federal, state or local laws.
This policy applies to all terms and conditions of employment, including recruiting, hiring, placement, promotion, termination, layoff, recall, transfer, leaves of absence, compensation and training.
#LI-DNI
You've read the whole posting — now see how you match it.