Engineering Manager

Insight Global; Atlanta (GA); On-site; USD 180,000 - 240,000; Full time

Job summary

Insight Global is seeking a senior Platform Engineering lead to steer a high‑performing team of reliability and quality engineers. You will stay hands‑on, designing infrastructure and pipelines while guiding five engineers through delivery, testing, and on‑call readiness.

You will own cloud infrastructure, cost governance, and end‑to‑end CI/CD, ensuring release readiness with objective criteria and durable postmortem improvements.

Qualifications

• 7+ years in infrastructure/DevOps/platform engineering.
• 2+ years leading a team.
• Hands-on with design and coding in cloud environments.

Responsibilities

• Lead and grow a team of roughly five engineers spanning reliability and infrastructure on one side and quality and verification on the other — hiring, coaching, performance, and the technical direction of both.
• Stay hands‑on. Design and build infrastructure, pipelines and tooling yourself, review your team's work substantively, and take a share of the on‑call rotation.
• Own the cloud infrastructure our services run on — provisioning, networking, identity, secrets, scaling and cost — managed as code and reproducible from scratch.
• Own continuous integration and delivery end to end: build, environment provisioning, deployment, and rollback, with the goal that shipping is routine and reversible rather than an event.
• Own release readiness — define the criteria, make them objective and written, build what measures them, and bring that evidence to the release decision. A failed gate blocks by default; an override is an explicit, recorded decision rather than a quiet one.
• Own observability and incident response — alerting that means something, a humane on‑call rotation, and postmortems that change the system rather than the people.
• Direct the verification strategy for deployed services and applications, and make sure the environments needed to run it can be stood up on demand.
• Partner with engineering leads on testability, deployability and operability early in design, rather than inheriting those properties once the code has shipped.
• Own reliability targets, capacity planning and infrastructure cost for the services your team runs, and make the trade‑offs between them explicit.
• Set the operational and verification standards that later services and teams inherit, and document them well enough to be adopted without you.
• Represent readiness, risk and cost honestly to senior stakeholders, including when the answer is that something is not ready.

Skills

Team leadership

Hands-on design

Cloud infrastructure

Kubernetes

IaC

CI/CD

Incident response

Observability

Python

Communication

Hiring engineers

Tools

Terraform

GitHub Actions

Kubernetes

PostgreSQL

Azure

Job description

You will lead the platform engineering function for our agentic AI products — a small, senior team of reliability and quality engineers responsible

for everything between a merged commit and a customer using the software in production. That spans the cloud infrastructure our services run on,

the pipelines that build and deploy them, the environments they are verified in, the automated testing that establishes whether a release is sound,

and the monitoring and incident response that keeps them healthy. This is a hands-on role: you will lead roughly five engineers while still

designing systems and writing code yourself, and that balance is deliberate — at this size a leader who has stopped building loses the ability to

judge the work. You will own release readiness, by which we mean the criteria and the evidence rather than the authority: you define what sound

looks like, make it objective, build what measures it, and bring that evidence to the decision.

KEY RESPONSIBILITIES

• Lead and grow a team of roughly five engineers spanning reliability and infrastructure on one side and quality and verification on the other — hiring, coaching, performance, and the technical direction of both.
• Stay hands‑on. Design and build infrastructure, pipelines and tooling yourself, review your team's work substantively, and take a share of the on‑call rotation.
• Own the cloud infrastructure our services run on — provisioning, networking, identity, secrets, scaling and cost — managed as code and reproducible from scratch.
• Own continuous integration and delivery end to end: build, environment provisioning, deployment, and rollback, with the goal that shipping is routine and reversible rather than an event.
• Own release readiness — define the criteria, make them objective and written, build what measures them, and bring that evidence to the release decision. A failed gate blocks by default; an override is an explicit, recorded decision rather than a quiet one.
• Own observability and incident response — alerting that means something, a humane on‑call rotation, and postmortems that change the system rather than the people.
• Direct the verification strategy for deployed services and applications, and make sure the environments needed to run it can be stood up on demand.
• Partner with engineering leads on testability, deployability and operability early in design, rather than inheriting those properties once the code has shipped.
• Own reliability targets, capacity planning and infrastructure cost for the services your team runs, and make the trade‑offs between them explicit.
• Set the operational and verification standards that later services and teams inherit, and document them well enough to be adopted without you.
• Represent readiness, risk and cost honestly to senior stakeholders, including when the answer is that something is not ready.

REQUIRED QUALIFICATIONS

• 7+ years in infrastructure, site reliability, DevOps or platform engineering, including 2+ years leading a team — either as a manager or as a technical lead accountable for people outcomes as well as systems.
• Currently hands‑on. You can design and build infrastructure and tooling yourself, and you intend to keep doing so alongside leading.
• Deep cloud infrastructure experience, ideally Azure — compute, networking, identity, secrets management, and cost control.
• Production Kubernetes ownership, including the failure modes you only learn by operating it.
• Infrastructure as code at a professional standard, with Terraform or an equivalent.
• CI/CD pipeline design and ownership — build, deploy, environment provisioning, release gating — ideally with GitHub Actions.
• Incident response leadership: on‑call practice, clear command during an outage, and postmortems that result in durable fixes.
• Has owned or closely managed automated testing, with enough depth to tell a suite that protects the product from one that only looks like it does, and to prioritize that work against operational pressure.
• Strong observability practice — metrics, logs, traces, and alert design that produces signal rather than noise.
• Working proficiency in Python or a comparable language, sufficient to review your team's code and contribute to it.
• Experience building a function at a formative stage — establishing standards, tooling and practice where little existed — rather than only operating a mature one.
• Clear written communication, and the judgment to tell senior stakeholders what is actually true about risk and readiness.
• A track record of hiring and developing strong engineers.

PREFERRED QUALIFICATIONS

• Experience operating LLM-backed or AI‑driven products in production — latency and streaming behavior, provider routing and failover, usage and cost accounting.
• Familiarity with managed model services such as Azure OpenAI, and the operational differences between providers.
• Experience gating releases of shared services or libraries against the downstream teams that consume them.
• Has led a combined reliability and quality function before, or a platform team with verification inside its scope.
• Security and compliance posture work — access control, tenant isolation, secrets handling, and audit requirements such as SOC 2.
• Production experience with Postgres, and with vector or graph databases.
• Ephemeral or on‑demand test environments provisioned per branch or per release.
• Progressive delivery practice — canary releases, blue‑green
• Cloud cost management at scale, including forecasting and accountability by team or service.
• A software engineering background earlier in your career, rather than operations alone.
• Has coached engineers into senior or lead roles.