0% completed
The Google FDE Loop, Round by Round
On This Page
Two Reported Loop Shapes
The Rounds
The Recruiter Screen
DSA Coding
Vibe Coding
Agentic and ML System Design
Googleyness and Leadership
After the Interviews
Using This in an Interview
Key Takeaways
Practice Questions
One candidate's report of a Google forward deployed engineer (FDE) loop describes a coding round in a shared document with no run button. The first question was a meeting-rooms problem. After a quick answer, the interviewer asked for the maximum number of squares that overlap at a single point. Halfway through, the interviewer asked the candidate to switch to a different approach.
Another candidate reports a much shorter process: two interviews over two days. Google does not publish an FDE loop, so every round in this lesson comes from candidate reports and prep guides. Google's careers page does state one fact for all roles: the process typically takes roughly 6 to 8 weeks once interviews begin.
Two Reported Loop Shapes
Candidates report two shapes of the Google FDE loop: a full loop of five rounds, and a compressed loop of as few as two interviews. Both end with a hiring committee, the group of senior Googlers who decide from written feedback alone.
- The full loop. A recruiter screen comes first. Then come four interviews: data structures and algorithms (DSA) coding, vibe coding, agentic and ML system design, and Googleyness and Leadership.
- The compressed loop. As few as two interviews over two days, for example one agent design discussion and one coding round.
The arithmetic matters for preparation. In the full loop, the four interviews after the screen add up to about 3 hours and 45 minutes, if DSA coding takes a standard hour. In the compressed loop, two interviews must produce the same decision. Each one is therefore about half of the evidence, so a weak round is harder to balance with a strong one. Ask the recruiter which shape your loop uses.
The Rounds
| Round | Reported length | What reports say it scores | One reported example |
|---|---|---|---|
| Recruiter screen | 30 to 45 minutes | Motivation, past deployments, clear description of your work | "Why forward-deployed engineering at Google Cloud, and why this team?" |
| DSA coding | Not consistently reported | Correct code at the Google software engineer bar, complexity, edge cases | Meeting rooms, then maximum overlapping squares, with a forced change of approach |
| Vibe coding | About 60 minutes | Building from a loose specification that changes midway | "Parse this messy export and reconcile it against a second source, then handle a burst" |
| Agentic and ML system design | About 60 minutes | An agent or retrieval design for an enterprise customer | How to scale an agent, keep it safe, and handle agent infinite loops |
| Googleyness and Leadership | About 45 minutes | Ambiguity, ownership, collaboration | A project with no clear owner; a disagreement with a teammate |
The Recruiter Screen
The recruiter screen checks that you understand the job and can describe your work in deployment terms. Candidates report questions on motivation and past deployments. One prep guide suggests preparing two systems: one agentic or ML system and one classic engineering project. Describe each by what the user received, not by the tools you used. Ask which team the role belongs to, because the team decides the focus of the design round.
DSA Coding
The DSA round uses the standard Google software engineer bar, and reports say it often runs in a shared document with no run button. The reported problems are classic interval and grid problems. The meeting-rooms report shows the pattern to expect. A fast first answer brings a harder follow-up, and the interviewer may ask for a different method in the middle. How Google Runs the Coding Round covers this round in full.
Vibe Coding
The vibe coding round is a build of about 60 minutes from a loose, production-style specification. The interviewer leaves parts of the task undefined and, according to reports, changes a requirement midway. The reported example has three parts: parse a messy export, reconcile it against a second source, and handle a burst of records. The round scores how you ask questions, build a small working version, and adapt it to the change.
Agentic and ML System Design
The design round asks for an end-to-end system for an enterprise customer, usually an agent or retrieval over private data. Reported questions include how to scale an agent, keep it safe, and stop an agent that repeats steps forever. Others are "design an agentic system that handles a specific enterprise workflow" and retrieval-augmented generation over a customer's private data. The focus changes with the team, so a Data Cloud loop is likely to include more data design.
One report from an L4 loop describes a different format. The interviewer played the customer's chief technology officer (CTO), and the candidate ran the conversation from discovery to an end-to-end design. Role-Play: The Interviewer as the Customer's CTO gives a full transcript of that format.
Googleyness and Leadership
The behavioral round, about 45 minutes, asks how you work when the problem has no clear owner. Reported questions include a project with no clear owner and a disagreement with a teammate. For an FDE, the answers matter more than usual, because the FDE represents Google inside another company.
After the Interviews
Three steps follow the last interview. Each one has its own lesson.
- The hiring committee reads the written feedback and decides. The Hiring Committee and Your Written Packet explains what it reads.
- Team match pairs an approved candidate with a team that has open headcount. Team Match, Timelines, and Bilingual Roles covers it.
- AI tool rules differ by round and by pilot. Rules for AI Tools and Shared Documents explains what to ask.
Google's careers page also says that some roles again hold in-person interviews, usually after initial interviews by video. The Design Gurus answer What is the Google FDE interview process like? gives a shorter summary of the same rounds.
Using This in an Interview
At the end of the recruiter screen, the recruiter usually asks whether you have questions. Use that time to learn the shape of your loop, because the reports differ.
"I have three questions about the process. First, is my loop the full set of rounds, or a shorter set of two interviews? Second, which team is the role on, so I know what the design round will focus on? Third, is the coding round in a shared document or in an editor that runs code?"
Expect two follow-up questions:
- "Why does the loop shape matter to you?" In a two-interview loop, each round is about half of the evidence, so I would spend more time on the two rounds I will actually take.
- "Which round worries you most?" Name one honestly, and name the practice you are doing for it, such as solving problems in a plain document.
Key Takeaways
- Candidates report a full loop (recruiter screen, DSA, vibe coding, agentic design, Googleyness) and a compressed loop of as few as two interviews.
- Every round fact is a third-party report, because Google publishes no FDE loop.
- Google's careers page states roughly 6 to 8 weeks once interviews begin.
- Ask the recruiter for your loop's shape, team, and coding format before you plan your preparation.
The next lesson, The Hiring Committee and Your Written Packet, explains how your answers become the written evidence the committee reads.
Practice Questions
1. A candidate's loop has only two interviews. Why should the preparation change?
<details><summary>Show answer</summary>Because each interview is about half of the evidence. A weak round is harder to balance, so the candidate should prepare the two rounds deeply instead of spreading time across five.
</details>2. Which reported round is closest to real FDE work at a customer, and why?
<details><summary>Show answer</summary>The vibe coding round. It gives a loose specification and changes a requirement midway, which is how customer requests arrive during an engagement.
</details>3. Why should you describe a round's length as "reported" when you discuss the Google FDE loop?
<details><summary>Show answer</summary>Because Google does not publish the FDE loop. The lengths come from candidate reports and prep guides, and they differ by team and by loop shape.
</details>Reading Progress
0%
On This Page
Two Reported Loop Shapes
The Rounds
The Recruiter Screen
DSA Coding
Vibe Coding
Agentic and ML System Design
Googleyness and Leadership
After the Interviews
Using This in an Interview
Key Takeaways
Practice Questions