Engineering Manager, Partner & Deployment Engineering

Union is taking its platform into deep, long-running partnerships with the largest infrastructure providers in the industry, including AWS, OpenAI, GCP, Azure, NeoClouds, and Apple. Each one is a multi-quarter engineering effort, not a business development handshake. It means porting our product to run natively on the partner's stack, then figuring out how that product gets packaged and installed across the wide range of enterprise environments their customers run.

We're hiring an Engineering Manager to run the two teams that make this possible.

Partner Engineering carries each hyperscaler and OEM relationship (AWS, OpenAI, GCP, Azure, NeoClouds, Apple, and others) through a roughly nine-month integration cycle, porting Union's product onto the partner's infrastructure and control planes.

Deployment Engineering turns what comes out of those integrations into a maintained, repeatable install surface: containers, Helm charts, Terraform modules, marketplace listings, and BYOC or self-managed variants. The goal is that the product installs correctly across enterprise environments without bespoke one-off engineering per customer.

We don't ship an integration and move on. We stay close to what each partnership actually requires in production, and translate real integration and install problems into reusable patterns, automation, and playbooks that make the next partnership smoother than the last.

This role is hybrid, based out of our Seattle office.

Own planning and delivery across partner integrations and deployment formats.

Manage staffing, performance, and career growth across both teams. Identify and develop the project leads who own technical direction for each integration and each deployment work stream.

Own the technical relationship with partner engineering counterparts, including AWS, OpenAI, GCP, Azure, NeoClouds, and Apple, serving as the senior technical point of contact through the full multi-quarter integration cycle.

Set and hold the bar for what production-ready means for a partner integration and a deployment artifact: reliability, security, and operability, not just that it runs.

Set relative priority across active partnerships and deployment work streams when they compete for engineering time, and make that tradeoff visible to leadership rather than absorbing it silently.

Ensure every completed integration produces a corresponding, maintained deployment artifact. Partner Engineering's output should feed Deployment Engineering's roadmap, not create untracked one-off installs.

Track and drive down each team's operational footprint: on-call load, incident recurrence, and the support burden that partner-specific or deployment-specific issues place on the rest of the org.

Partner with project leads and senior engineers on technical direction. Make sure it exists and is sound without setting it yourself.

Work closely with Business Development, Sales, and engineering leadership to align on partnership priorities and technical tradeoffs.

5+ years in software engineering, with meaningful exposure to distributed systems, Kubernetes, or cloud infrastructure.

3+ years managing software engineers or engineering teams, including at least one planning cycle taken from commitment through delivery.

Experience running or closely supporting long-cycle technical partnerships or integrations with external companies, six months or longer. Internal roadmap delivery alone is not the same thing.

Proven experience with AWS, GCP, or Azure, and comfort evaluating tradeoffs across them without writing the code yourself day to day.

Deep familiarity with CI/CD, infrastructure-as-code such as Terraform and Helm, and container orchestration with Kubernetes, enough to hold your own in a design review.

Experience partnering with senior or staff-level engineers on technical direction without personally owning system architecture.

Software packaging and distribution: Helm, Terraform, container or AMI builds, cloud marketplace listings, or equivalent multi-environment install engineering.

Working opposite a hyperscaler or major platform's partner engineering organization, such as AWS, GCP, Azure, OpenAI, or Apple.

Standing up or restructuring a team, such as splitting a single team into multiple project-led teams, or hiring project leads.

Operating in an organization where technical vision is set by ICs or founders rather than by the manager.

Managing at this scope without a management layer beneath you, leading through project or tech leads rather than sub-managers.

Background in Go, Rust, or Python, enough to hold your own in a design review even if you are not shipping production code.

Languages. Go, Rust, Python.

Infrastructure. AWS, GCP, Azure, OCI, Apple platforms, Kubernetes.

Packaging and distribution. Helm, Terraform, Docker and AMI pipelines, cloud marketplace tooling.

CI/CD. Buildkite, ArgoCD.