Senior Engineering Manager, Platform Engineering (Remote)

ezCater is the #1 food tech platform for workplaces in the US. The company makes it easy for any organization to manage its food needs and order from over 125,000 restaurants nationwide. For workplaces, ezCater provides flexible and scalable solutions for everything from employee meal programs to one-off meetings, all backed by beyond helpful 24/7 service and business-grade reliability.

For restaurant partners, ezCater helps grow their business by bringing them new high-value customers and large orders. ezCater is investing in a next-generation, composable platform that powers future product experiences across the organization. This platform is API-first, headless, and designed to enable teams to build and evolve product capabilities quickly, safely, and at scale.

As Senior Engineering Manager, Platform Engineering, you will lead the teams responsible for the foundation that every engineering team builds on: infrastructure, developer experience, shared libraries, CI/CD, observability, and governance. You will own delivery across developer experience, core platform tooling, and platform infrastructure -- ensuring that domain teams building on the platform have an opinionated, supported path that lets them focus on their domain instead of infrastructure decisions. This is a hands-on engineering management role.

You are close to the work -- reviewing technical designs, pairing with engineers on hard problems, and making informed tradeoff calls across infrastructure, tooling, and developer experience. You came up through engineering, you understand distributed systems and cloud-native infrastructure, and you bring that judgment to every decision about what to build, how to build it, and in what order. What You’ll Own: Delivery across platform engineering: developer experience, core platform tooling (shared libraries, event streaming clients, auth middleware), and platform infrastructure (compute clusters, networking, infrastructure-as-code, observability) The opinionated path for building and operating services: language, frameworks, CI/CD, deployment, observability, and governance -- the defaults that come with support out of the box Milestone delivery for the platform foundation on a timeline that unblocks domain teams building search, identity, payments, and other capabilities Day-to-day engineering management: hiring, developing, and retaining strong engineers across the platform teams Cross-team coordination: when domain teams need something from the platform, you own prioritization and delivery What Your Teams Will Build: A fresh compute cluster for new platform services, with namespace isolation, modern autoscaling, and clean networking CI/CD pipelines (build, test, contract validation, GitOps deployment) that are the single supported path for all new services A service template that gives domain teams a working, observable, deployable service in minutes Shared libraries and building blocks: event streaming clients, HTTP clients, auth middleware, instrumentation Infrastructure modules: reusable, versioned modules for databases, event streaming topics, caching, secrets -- provisioned via infrastructure-as-code An observability stack (APM, logging, tracing, alerting) that ships by default with every service.

What Success Looks Like (12-18 Months): Domain teams can scaffold, build, deploy, and observe a new service using the platform path without making infrastructure decisions or filing tickets The platform foundation is delivered on the milestone timeline, unblocking the first wave of domain services Every new service is deployed through the same CI/CD pipeline with consistent observability and operational standards Infrastructure provisioning is self-service via versioned modules -- no manual work or ad-hoc configuration The platform teams are well-staffed, well-organized, and operating with clear ownership Engineering teams view the platform path as the easiest way to ship -- not a constraint to work around.