Build internal developer platforms and agentic tooling (MCP servers, AI agents) for Cloudflare's engineering org

Cloudflare's Engineering Platform and Productivity team builds the self-service platform and internal tools hundreds of engineers rely on to deploy and operate services safely. This role has a specific focus on Agentic Engineering — building MCP servers, agentic IDEs, autonomous agents, and evals to bring AI-native improvements to Cloudflare's internal SDLC. Based in Bengaluru, India, working across Bash, TypeScript, and Go, with both software engineering and DevOps/on-call responsibilities.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Agentic engineering: building MCP servers, agents, evals for internal tooling
Developer productivity platform design (self-service, GitOps, migration safety)
Incident response and hardening shared platform infrastructure
Working across Bash, TypeScript, and Go codebases
Breaking down ambiguous platform problems and discussing tradeoffs

Common question themes

Describe an MCP server, agent, or AI-native tool you built and how you evaluated it

How would you design a GitOps improvement or automated migration-safety check

Tell me about an incident on a shared platform and what you changed afterward

How do you decide what to build as a reusable platform vs. leave to product teams

Walk through your approach to a messy source-control situation (rebase/merge conflict)

How do you harden a platform against security or resource-contention issues

How candidates describe it

Real Software Engineer - Platforms & Productivity interview stories — retold from candidates' public write-ups, with sources.

Google · L3 Software EngineerOffer

Google L3 software engineer interview: phone screen, four coding rounds, and the Googleyness round

A candidate with two years of experience went from recruiter outreach to offer over about four months. The onsite was four 45-minute coding rounds — three of them featuring binary trees — and one round turned into a 25-minute chain of follow-ups about approximating an optimal solution at scale.

Interviewed June 2020 · Bangalore, IN

Google · L4 Software EngineerNo offer

Google L4 Software Engineer Interview: Eight Rounds, No Offer

An L4 Software Engineer candidate went through two phone screens, three onsite rounds, a culture conversation, and a team-matching call with a Google hiring manager, then watched the process stall for about a month and a half over a tightened experience requirement before an added extended round ended without an offer.

Interviewed February 2024 · Not specified

Google · L5 Software EngineerNo offer

Google L5 software engineer interview: phone screening, three onsite rounds, system design, and a late rejection

A candidate interviewing for an L5 role went through a phone screening, three onsite coding rounds, a mobile system design round, and a Googleyness and Leadership round. Two of the four technical rounds went poorly by the candidate's own assessment, and after roughly two months of silence the recruiter reported that the role had been closed.

Interviewed January 2023 · Not specified

View the original posting

All Cloudflare Software Engineer interviews

All Cloudflare interviews