Lead a team of engineers focused on AI tools and engineering standards at Cloudflare in a hybrid work environment.
Posted by employer 9 hours ago
First seen on Joblaze 50 minutes ago
Last verified on the company career page 50 minutes ago
Skills & Technologies
What you'll build
Must have
Nice to have
Role intensity
10% coding — mostly leadership/strategy
AI in the day-to-day
We're responsible for AI-assisted development across all of Cloudflare engineering.
Requirements
Not disclosed in this posting: compensation, visa sponsorship.
Joblaze summary
The Engineering Manager at Cloudflare leads a team focused on developing AI tools and enforcing engineering standards, ensuring that internal platforms enhance the productivity of software engineers. Key skills include hands-on experience with AI in engineering contexts and a strong background in developer tools and CI/CD systems. This role is suited for someone with significant management experience and a track record of product ownership, particularly in fast-paced environments. The team operates with a high degree of autonomy, emphasizing rapid iteration and user feedback.
Joblaze insights
Quick facts
From the original posting
About the department
Cloudflare's Engineering team builds and runs the software that handles a large share of the Internet's requests. We also build the internal tools and platforms that software depends on. Teams own large areas with real impact and work autonomously within them, whether their customers are external or other Cloudflare engineers.
About the team
Developer Productivity builds the internal tools and platforms Cloudflare engineers use to take code from commit to production. We own developer infrastructure (CI/CD, build systems), developer insights and ADLC metrics, AI-assisted development, and Cloudflare-on-Cloudflare dogfooding.
We're responsible for AI-assisted development across all of Cloudflare engineering, and adoption has grown 4 to 6 times over in the last year. We also own the tooling behind Cloudflare's Engineering Codex, the standards every engineering team is expected to meet.
About the role
This is a front-line engineering manager role leading a team of 6+ engineers in Bengaluru. The team's initial focus will be on two areas:
AI tools for engineers. Agents, agentic systems, MCP servers, evals, and context engineering that change how Cloudflare engineers write, review, and ship code.
Engineering standards and the tooling that enforces them. Continuing to transform our Engineering standards into automated guardrails, paved paths, and feedback engineers can act on, instead of checklists and manual review.
You'll own the product direction for both areas. There are no dedicated product managers on the team. Our users are Cloudflare engineers, and our engineers work as product engineers who talk to users, watch how tools get used, and help decide what to build next. You'll lead that work, deciding what to build and why, and making sure it gets adopted and solves real problems.
You don't need to write code every day, but you should be able to review a design, debug a broken pipeline, or prototype an agent when the team needs it.
We move fast. AI tooling changes month to month, so a six-month plan is stale in six weeks. We ship small, put it in front of engineers early, and change course based on what we hear. We'd rather ship a rough version this week and improve it next week than spend a month polishing a design doc. We add process only when it solves a real problem.
You'll partner closely with engineering managers and principal engineers in the US, UK, and Europe, and work with teams across Cloudflare's global organization. The team starts in Bengaluru. As it grows, it may include engineers in other regions.
What you'll do
Hire, onboard, and grow your team. Coach engineers to think like product engineers, run career conversations, give direct feedback, and handle performance.
Own the product roadmap. Spend time with the engineers who use your tools, decide which problems matter most, and say no to the rest.
Keep the team shipping. Release in small increments, get feedback from users quickly, and cut process that slows the team down without adding value.
Deliver in both focus areas: agents, MCP servers, and evals the rest of engineering relies on, and Codex standards turned into CI/CD checks, templates, and policy-as-code, with remediation and exception workflows to match.
Measure whether the work is landing: tool adoption, Codex compliance, and what engineers actually think of the experience.
Own operations for the platforms your team runs, including on-call and incident response.
What we're looking for
3+ years managing software engineers, including hiring, onboarding, and developing people.
8+ years of total software engineering experience, with enough recent hands-on work to hold your own in code and design reviews.
Hands-on experience with AI in engineering organizations, such as building agents, running agentic systems in production, or governing how a company uses AI. This is not a model-training or ML research role.
Experience building or running developer tools, internal platforms, or CI/CD systems.
Product and user thinking. You've owned a roadmap, with or without a PM, and you can point to decisions you made because of what users told you or how they actually used what you built.
A bias to action. You've led teams that shipped often and changed direction when the evidence called for it, while still delivering on commitments.
Clear judgment and clear writing. You make sound trade-offs and explain the "why" as well as the "how". Much of your work with partners will happen asynchronously across time zones.
Bonus points
You've built MCP servers or LLM evals, or worked on context engineering for agents.
Experience with policy-as-code or compliance automation.
Experience measuring developer productivity, using frameworks such as DORA or SPACE, or developer surveys.
You've built a team from scratch or started an engineering presence in a new location.
Familiarity with TypeScript, Go, or Kubernetes-based systems.
Standard company text repeated across Cloudflare's postings is omitted here.