Grokking the Google Forward Deployed Engineer Interview
Vote

0% completed

​

Levels from FDE I to Staff

The Levels in the Postings

How FDE Levels Compare with Software Engineer Levels

What Each Level Owns

Other FDE Roles for Comparison

How the Level Is Decided

Using This in an Interview

Key Takeaways

Practice Questions

Title image: the Google FDE levels from FDE I to Staff, with the years of experience each posting asks for.
Title image: the Google FDE levels from FDE I to Staff, with the years of experience each posting asks for.

Near the end of a first recruiter call, the recruiter asks how many years you have worked with Python and how many systems you have taken to production. The answer decides which level the recruiter proposes, and the level decides which questions the interviewers expect you to handle and what the offer can be.

Google posts forward deployed engineer roles at four numbered levels and at Staff. The postings state the experience each level requires, and the US postings state a base pay range.

The Levels in the Postings

Each FDE level has a minimum number of years in its posting, and the US postings add a base pay range and a bonus target. The table uses current Google Cloud postings. No US posting at FDE I or FDE II was open when this lesson was written, so those two rows use ranges collected from earlier postings by fde.directory, a site that tracks FDE roles.

LevelMinimum experienceUS base pay rangeBonus target
FDE IAbout 2 years102,000 to 145,000 US dollars (earlier postings)Not confirmed
FDE II2 years127,000 to 183,000 US dollars (earlier postings)Not confirmed
FDE III5 years174,000 to 252,000 US dollars15 percent
FDE IV8 years207,000 to 300,000 US dollars20 percent
Staff8 yearsNot listed in current US postingsNot listed

Several FDE III postings in New York, San Francisco, Pittsburgh, and Chicago list the same range, and so do FDE IV postings in San Francisco, Seattle, and Pittsburgh. These Google Cloud postings add equity and benefits to the base and bonus. Postings outside the US state no range, and pay there follows the local market.

The FDE ladder: minimum years and US base pay ranges for FDE III and FDE IV from current postings, FDE I and FDE II from earlier postings, and Staff with no listed range.
The FDE ladder: minimum years and US base pay ranges for FDE III and FDE IV from current postings, FDE I and FDE II from earlier postings, and Staff with no listed range.

How FDE Levels Compare with Software Engineer Levels

Third-party trackers map FDE I to FDE IV roughly onto Google's software engineer levels L3 to L6, but Google does not publish this mapping. Under that estimate, FDE III sits near L5, the level at which Google expects an engineer to work with little supervision. The Design Gurus answer What is L5 level in Google? describes those expectations.

The mapping helps when you compare an FDE offer with a software engineer offer. Treat it as an estimate, and ask the recruiter if the comparison matters to your decision.

What Each Level Owns

The years rise with each level, and the scope the postings describe rises with them: from building parts of a system, to leading one customer's build, to setting direction across several customers.

  • FDE I and FDE II. The postings ask for about 2 years of Python and experience designing AI systems on a cloud platform. They do not describe how work is split between levels. On most teams, an engineer at this level builds parts of a system that a more senior FDE designs.
  • FDE III. The postings ask for 5 years of Python and experience taking AI systems from idea to launch. The GenAI postings describe the FDE as the lead developer who moves prototypes to production. At the freight carrier, the 12-week exceptions engagement fits this level.
  • FDE IV. The postings ask for 8 years. The Applied AI posting adds Terraform, full-stack applications that work with enterprise systems, and troubleshooting live systems with heavy traffic. It also asks the FDE to "co-build" with the customer's engineers and teach them Google's development practices.
  • Staff. The postings ask for 8 years of shipping production AI systems and experience with executive stakeholders. The GenAI Staff posting adds mentoring other engineers, co-building with customer teams, and influencing strategy across a region.

FDE IV and Staff ask for the same minimum years. The difference is scope: an FDE IV leads a large customer's delivery, while a Staff FDE is expected to improve how many engagements are run.

Other FDE Roles for Comparison

FDE roles outside the main Cloud teams use their own ranges. These help when you compare offers across Google:

  • Kaggle and DeepMind, fixed-term contract: 174,000 to 232,000 US dollars, plus a 15 percent bonus target.
  • YouTube GenAI FDE, 4 years of experience: 128,000 to 184,000 US dollars, plus 15 percent.
  • Lead GenAI FDE, YouTube: 186,000 to 269,000 US dollars, plus 20 percent.

How the Level Is Decided

The recruiter proposes a target level from your experience, and the hiring committee sets the final level from the interview notes. A hiring committee is a group of senior Googlers who did not interview you and who decide from the written feedback alone. Strong evidence of scope in the design and behavioral rounds can support a higher level. A weak coding round can lower it, even when the other rounds are strong.

Two habits protect your level. First, ask the recruiter which level the loop is calibrated for, so you know what the interviewers expect. Second, describe past work by its scope: how many customers, how many engineers, and which decisions were yours. The Hiring Committee and Your Written Packet covers how that evidence reaches the committee.

Using This in an Interview

Recruiters often ask, "What level are you targeting?" Name the level, and support it with the scope you have already owned, not with years alone.

"I am targeting FDE IV. I have 9 years of experience, and for the last three I led delivery for two enterprise customers at once, each with its own engineering team that I trained. I owned the integration design, the evaluation plan, and the decision to keep every write behind an approval step."

Expect two follow-up questions:

  • "Would you consider FDE III?" Say what would change your mind: ask which round the recruiter expects to be weakest, and offer extra evidence for it.
  • "Why not Staff?" Be honest about scope. Staff postings describe work across a region, so name the cross-customer work you have done or say you have not done it yet.

Key Takeaways

  • Google posts FDE roles at FDE I to FDE IV and Staff, with minimums of about 2, 2, 5, 8, and 8 years.
  • Current US postings list 174,000 to 252,000 US dollars for FDE III and 207,000 to 300,000 for FDE IV, plus bonus, equity, and benefits.
  • FDE levels map roughly to software engineer levels L3 to L6, but only as a third-party estimate.
  • The hiring committee sets the final level from written evidence, so describe your work by its scope.

The next lesson, The Google FDE Loop, Round by Round, describes each interview in the loop and what it scores.

Practice Questions

1. FDE IV and Staff postings both ask for 8 years. What separates them?

<details><summary>Show answer</summary>

Scope. An FDE IV leads a large customer's delivery, while a Staff FDE mentors other engineers and influences how engagements run across a region.

</details>

2. An engineer with 9 years of experience, whom the recruiter proposed for FDE IV, is offered FDE III after strong design rounds and a weak coding round. What is the most likely reason?

<details><summary>Show answer</summary>

The coding feedback limited the level. The hiring committee reads every round, and a weak coding round can hold the level down even when other rounds support a higher one.

</details>

3. Why should you avoid quoting the FDE to L3 through L6 mapping as a fact?

<details><summary>Show answer</summary>

Because Google does not publish it. It comes from third-party trackers, so confirm any comparison that matters with the recruiter.

</details>

Reading Progress

0%


Vote for new content

On This Page

The Levels in the Postings

How FDE Levels Compare with Software Engineer Levels

What Each Level Owns

Other FDE Roles for Comparison

How the Level Is Decided

Using This in an Interview

Key Takeaways

Practice Questions