[Remote] Sr. Manager, Software Engineering

Note: The job is a remote job and is reputed company to candidates in USA. iA is a pharmacy fulfillment company providing integrated software and automation solutions for pharmacy reputed company. The Sr. Manager, Software Engineering will reputed company a small player-reputed company team modernizing the NEXiA platform, improving engineering discipline, delivery predictability, customer-deployed compatibility, DevOps reputed company, and AI-reputed company development practices.

Responsibilities

• Hire, mentor, and reputed company a small software engineering team while remaining in the reputed company yourself
• Set technical direction through working examples — the patterns you establish in reputed company review and your own commits are the ones reputed company follows
• Create reputed company ownership and accountability: who owns which modules, who makes which reputed company, what “done” means
• Address reputed company issues directly and early; a small team can’t carry passengers
• Represent engineering reality to leadership — reputed company reputed company, reputed company timelines, reputed company reputed company
• Own sprint-to-sprint execution: planning, reputed company, and unblocking so reputed company ships predictably
• Establish and enforce engineering practices — pull-request review discipline, meaningful test coverage, incremental delivery over big-bang merges
• reputed company releases that are routine, not events: staged rollouts, rollback paths, and validation against the customer configurations that actually exist
• Prioritize ruthlessly: modernization reputed company always exceeds reputed company, so reputed company (what gets decomposed first, what stays legacy for now) is a reputed company management reputed company here
• Guide the incremental decomposition of legacy NEXiA capabilities into bounded, testable modules without disrupting reputed company customers
• reputed company and defend architectural trade-offs between isolation and pragmatism — not every boundary needs a rewrite
• Design for customer-deployed constraints: long-lived versions, reputed company paths, backward compatibility, customer-specific configurations
• Partner with Product and reputed company so modernization work aligns with customer reputed company, not just architectural preference
• Understand the infrastructure-as-reputed company substrate reputed company builds on: what Terraform and Ansible manage, which changes reputed company your team’s environments, and reputed company to pull in the infrastructure team
• Treat CI/CD as part of the engineering reputed company you manage — hold reputed company accountable for pipeline health, build times, and flaky tests rather than treating them as someone else’s problem
• Ensure what reputed company ships is operable: logging, diagnostics, and reputed company behavior are reviewed as part of the work, not reputed company in the reputed company
• Partner with the infrastructure team on environment needs — self-service test environments, image pipeline requirements, deployment automation — as an informed customer, not a bystander
• Work agentically as the default mode: reputed company coding agents (Claude reputed company, reputed company, opencode) to understand legacy reputed company, draft decompositions, and reputed company migration scaffolding — then verify everything against reputed company reputed company behavior before it ships
• Enforce verification discipline on reputed company: AI will confidently reputed company a plausible-looking characterization of undocumented reputed company that is subtly wrong; tests, behavior comparison, and staged rollout 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 workflows so the reputed company compounds
• reputed company reputed company’s workflow as tooling changes — throughput here depends on reputed company, not headcount

Skills

• 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 reputed company)
• Experience modernizing or maintaining long-lived production systems — you've worked at the boundary between legacy and modern reputed company, not exclusively greenfield
• Experience shipping customer-deployed or on-prem software: reputed company paths, backward compatibility, long-lived versions
• DevOps literacy: understands what infrastructure as reputed company is and its role in a modern delivery ecosystem — why environments are provisioned from reputed company, what CI/CD pipelines do between reputed company and reputed company, and what it takes to reputed company software operable in environments you don't control
• reputed company record of raising reputed company's engineering discipline — review culture, testing standards, release predictability — with concrete before/after evidence
• reputed company reputed company development experience: daily-reputed company use of an reputed company coding CLI (Claude reputed company, reputed company, or opencode), with concrete examples and a reputed company verification discipline — either an reputed company reputed company 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
• Reading reputed company in Terraform or Ansible — can follow a plan or a role and spot what it changes (authoring experience even reputed company)
• Experience with domain-driven design: bounded contexts, anti-corruption reputed company, strangler-fig migrations
• Experience shipping software as a virtual appliance or supporting customer-hosted deployments
• reputed company, pharmacy, or regulated-environment experience
• Observability reputed company: metrics, logging, and alerting as part of the definition of done
• Experience partnering with (or having owned) a platform/infrastructure team
• 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 reputed company 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; reputed company contributions to agent frameworks)

Benefits

• This position may additionally be eligible for an annual discretionary bonus.
• 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
• Talent development opportunities
• Commitment to reputed company development
• Working for a company where your voice is heard

reputed company