Engineering Manager, Browser Run

Cloudflare•San Francisco, CA

4d•$74,000 - $93,000•Onsite

About The Position

Cloudflare is seeking an Engineering Manager for the Browser Run team, which is part of the Emerging Technologies & Incubation (ETI) department. ETI is responsible for building and releasing new and bold products within Cloudflare. The Browser Run team focuses on building tooling and platform capabilities for AI agents on the Cloudflare Developer Platform, specifically enabling agents to interact with the web securely and efficiently. Browser Run allows developers to run full browser sessions on Cloudflare’s global network, controllable via code or an agent. It offers a Chrome DevTools Protocol endpoint, support for various clients like Puppeteer and Playwright, and a REST API for tasks such as screenshots, PDFs, scraping, and crawling. The product also includes session recording, live debugging, and human-in-the-loop capabilities. It is a growing, billed product used by external developers and internal Cloudflare teams. The role involves managing the engineering team, owning the product roadmap, ensuring operational health, maintaining compatibility with browser automation tools, developing leaders within the team, resolving cross-team dependencies, managing commercial aspects of the service, and representing the product externally.

Requirements

2+ years managing engineering teams, on top of a solid track record as a hands-on engineer.
Experience owning a production service end to end, including on-call rotation, capacity planning and incident review.
Demonstrated experience growing engineers — promotions you supported, and ideally a team lead or first-line manager you developed.
Hands-on familiarity with browser automation — Chrome DevTools Protocol, Puppeteer or Playwright — or with the browser internals underneath them.
Strong technical grounding in distributed systems, web platform fundamentals (HTTP, JavaScript execution models, rendering) or cloud infrastructure — enough to hold a credible design review.
A track record of partnering with Product Management to set and defend a roadmap, including saying no.
Excellent written communication for internal and public-facing technical content.
Experience hiring: writing job descriptions, running interview loops, calibrating a panel and closing candidates.

Nice To Haves

Experience running headless browser infrastructure at scale — browser fleet management, sandboxing and resource isolation.
Experience shipping AI or agent-facing platform primitives, such as MCP servers, tool-calling surfaces or agent orchestration.
Familiarity with the Cloudflare Workers development platform: Workers, Durable Objects, Workflows, R2, D1.
Experience taking an internal tool to a billed external product, including usage metering and pricing.
Experience managing a distributed team across time zones.
Open source maintainership, or a public body of technical writing.

Responsibilities

Manage, coach and grow the team of systems engineers behind Browser Run — 1:1s, career development, performance conversations, and hiring.
Own the Browser Run roadmap and delivery, and give the team and the wider organisation clear visibility into what is being worked on, in what order, and what we are deliberately not doing.
Partner with Product Management to set direction: shape the roadmap, pressure-test scope, and make the trade-off calls that keep an incubation product shipping.
Own Browser Run’s operational health — browser fleet capacity, session reliability, cold-start latency, concurrency limits, on-call rotations, alert quality and incident follow-through.
Keep the automation surface honest: Puppeteer and Playwright compatibility, CDP behaviour that matches what developers expect from a local Chrome, and a credible story for Chrome version upgrades.
Develop leaders. Identify and grow the engineers who will run day-to-day delivery for an area of the product, and hand that work to them.
Resolve cross-team dependencies with the Workers, Developer Platform, Security and Billing teams, and bring contentious technical decisions to closure quickly and calmly.
Own the commercial mechanics of a billed service, including the unglamorous parts: usage metering, quotas, plan limits, abuse protection and pricing input.
Represent Browser Run externally through launch blog posts, developer documentation, conference talks and direct customer conversations.