Engineering Manager, Browser Run

This is a hands-on engineering management role. You will own Browser Run engineering end to end , the people, the roadmap, the reliability, and the story we tell customers about it.

You will report to the Senior Engineering Manager for AI Agents Tooling & Platform and partner closely with Product Management, Developer Relations, and platform teams across Cloudflare.

Browser Run is the primary focus. The team owns other products, and there is scope for some of them to move into your remit as the role and the team grow, but we are hiring someone to make Browser Run excellent first.

You will not be writing most of the code. You will be expected to understand it well enough to review a design document, challenge an architecture, and know when an estimate is wrong.

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.

Requirements

• You have run an engineering team that shipped, and you can point at what it shipped.
• You give your technical legos away. Your measure of success is the team’s output and the growth of the people on it, not your own commit history.
• You are comfortable with ambiguity. Incubation means the requirements move, and you can change direction without drama.
• You are direct. You give feedback early, disagree openly, and admit when you were wrong.
• You write well. You believe a clear design document, roadmap or incident report is as much of a deliverable as the code.
• You care about operational quality and treat a noisy alert as a bug, not as background noise.
• You find browsers genuinely interesting as an engineering problem , how Chrome behaves under load, why automation breaks, and what an AI agent actually needs from a browser it does not own.
• You want to join a team that upholds a culture of support, open and honest communication, and collaborative problem-solving.

Nice to Have

• 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.