By FDE Interview Prep, a SourceStrongAI company

In this post13 sections
  1. Customer engineer vs FDE at Google: the short answer
  2. What the customer engineer posting describes
  3. What the FDE postings describe
  4. The two jobs side by side
  5. Same customer, two jobs: a worked example
  6. Pay: the same structure, different jobs
  7. Travel and where the work happens
  8. The loops: what Google publishes and what candidates report
  9. Which one fits you
  10. Start with the role itself
  11. Questions people ask
  12. Keep reading
  13. More from the blog

You have a Google Cloud Customer Engineer posting open in one tab and a posting in the other. Both put you in front of customers, both sound technical, and the one you apply for decides what you spend the next month preparing to prove. In short, the customer engineer helps the customer decide and hands delivery on; the FDE does the delivery, inside the customer’s systems. For the wider comparison across every company, read the FDE vs sales engineer guide.

Customer engineer vs FDE at Google: the short answer

Google’s Platform Customer Engineer posting describes someone who partners with technical sales teams, runs proofs of concept and demos, drives the technical win, and then hands the final delivery plan to implementation teams. Source 1Customer Engineer, Platform, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting Google Cloud’s GenAI FDE postings describe an embedded builder who codes, debugs and jointly ships agentic solutions inside the customer’s environment, as opposed to a traditional advisory role. Source 2Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting

Put plainly: the customer engineer helps the customer decide, and the FDE builds the thing inside the customer’s walls. The first job hands the delivery plan to someone else to build. The second job is the building.

What this comparison rests on

The duties and pay structure below come from Google’s own postings. We compare one Customer Engineer posting, the Platform one. If yours names another specialty, check its duties line by line against the list below. The interview section uses Google’s published hiring page and candidate posts on Blind and Reddit, each labeled with its month, and its level where the poster gave one. We found no published description and no candidate report of the Customer Engineer loop, so we don’t describe one.

What the customer engineer posting describes

The Platform Customer Engineer posting reads like the arc of a sale: Source 1Customer Engineer, Platform, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting

  • Partner with technical sales teams to differentiate Google Cloud to customers.
  • Troubleshoot technical questions and roadblocks.
  • Run proofs of concept and demos, and architect cross-pillar cloud solutions for the customer’s business problems.
  • Drive the technical win.
  • Hand off: support pricing activities and move the final delivery plan to implementation teams.

The last line is the one to underline. The CE hands the final delivery plan to implementation teams; building it is another team’s work. Source 1Customer Engineer, Platform, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting

That shapes the stories a CE interviewer would want to hear, in our reading of the posting: a demo that changed a customer’s mind, a proof of concept scoped small enough to succeed, a technical objection answered before it stalled the deal. Those are real skills. They are not the same skills the FDE postings ask for.

What the FDE postings describe

Google uses the exact title “Forward Deployed Engineer” with numeric levels, such as “Forward Deployed Engineer IV, GenAI, Google Cloud” and “Forward Deployed Engineer III, Generative AI, Google Cloud”. Source 2Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job postingSource 3Forward Deployed Engineer III, Generative AI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting Read the level first: the FDE IV GenAI posting asks for 8 years of software development in Python or similar languages. Source 2Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting

The GenAI postings say you will move beyond high-level architecture to code, debug and jointly ship bespoke agentic solutions directly within the customer’s environment. Source 2Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting They also list building evaluation pipelines and observability frameworks for agentic systems, and turning repeatable field patterns into reusable modules or product feature requests. Source 3Forward Deployed Engineer III, Generative AI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting

Set that beside the CE posting and the difference is where the hand-off sits. The CE posting passes delivery to implementation teams; the FDE postings put the engineer inside the delivery. Source 1Customer Engineer, Platform, Google Cloud — Google CareersPublisherGoogleSource typecompany job postingSource 2Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting

Google Cloud is also hiring more of them. In May 2026, Google Cloud CEO Thomas Kurian posted that Google Cloud had announced a new AI-focused organization within its go-to-market team and was investing in hiring additional FDEs, adding that having FDEs is not new for Google Cloud. Source 4Thomas Kurian LinkedIn postPublisherLinkedIn (Thomas Kurian, CEO Google Cloud)Source typecompany website

“Builder” is the posting’s own word: it calls the FDE an “innovator-builder” who ships inside the customer’s environment. Source 2Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting Your strongest FDE stories are about something you shipped in a system you did not control: the integration that broke on the customer’s network, the eval set that caught a regression before users did, the one-off fix you turned into a module the next customer could use.

The two jobs side by side

This summary is ours, drawn from the postings above. Source 1Customer Engineer, Platform, Google Cloud — Google CareersPublisherGoogleSource typecompany job postingSource 2Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job postingSource 3Forward Deployed Engineer III, Generative AI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting

At GoogleCustomer engineerFDE
Works besideTechnical sales teamsThe customer, in their environment
Main outputDemos, proofs of concept, the technical winShipped agentic solutions, evals, observability
DeliveryHands the final plan to implementationCodes, debugs and ships it
Pay as postedBase, bonus target, equityBase, bonus target, equity

Same customer, two jobs: a worked example

Here is one fictional deal, seen from both seats. A regional grocery chain wants an AI that answers store managers’ questions about stock and orders, using its inventory system.

The customer engineer’s week. You join the account executive in a meeting with the chain’s head of IT. The objection comes fast: “Our inventory data lives in an on-prem database and it isn’t moving.” You build a proof of concept on a sample export, showing the agent answering the questions managers really ask. You sketch how the pieces would connect, answer the security team’s questions, and the chain agrees to the technical case. You write the delivery plan and hand it to implementation.

The FDE’s week. You are embedded with the chain’s engineers. You find that the managers’ most common question depends on a nightly batch job that runs hours late on Mondays, so the agent gives confident, stale answers. You build the connector the plan assumed already existed. You write an evaluation set from real manager questions and catch the agent confusing “on order” with “in stock”. You ship to a few pilot stores, watch the traces, and turn the connector into a reusable module for the next retailer.

Same customer, same product. Ask yourself which of those two weeks you already have evidence for, because that is the evidence each posting asks for.

Pay: the same structure, different jobs

As of September 2026, the Platform Customer Engineer posting states US pay as a base range plus a bonus target plus equity plus benefits, without the word “quota”, and Google’s FDE IV, GenAI posting states US pay in the same shape. Source 1Customer Engineer, Platform, Google Cloud — Google CareersPublisherGoogleSource typecompany job postingSource 2Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting

Both list the same parts, but the bonus target is a larger share of base pay in the CE posting than in the FDE IV posting, and the FDE salary guide has the figures. Source 1Customer Engineer, Platform, Google Cloud — Google CareersPublisherGoogleSource typecompany job postingSource 2Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting What the bonus is tied to matters more than its name, so ask the recruiter:

  • “What is the bonus target tied to: company performance, team results or my own targets?”
  • “Does any part of it depend on deals closing?”
  • “Which level is this offer at, and what would the next level expect of me?”

A bonus tied to deals closing makes a role more sales-shaped, whatever the title says. The posting won’t tell you; the recruiter can.

Travel and where the work happens

As of September 2026, Google’s Applied AI FDE postings at levels III and IV list “Ability to travel up to 50% of the time” under preferred qualifications, call the role “high-travel”, and place delivery at the largest customers’ sites. Source 5Forward Deployed Engineer III, Google Cloud, Applied AI — Google CareersPublisherGoogleSource typecompany job postingSource 6Forward Deployed Engineer IV, Applied AI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting

Read that carefully. It is a preferred qualification in one group of FDE postings, not a promise about every FDE role. We have no travel line from the Customer Engineer posting, so don’t assume it is lighter or heavier.

Ask both recruiters the same thing: “In a normal month, how many days would I spend at customer sites, and how long does one engagement last?” The lesson on travel, location and on-site time has the follow-up questions.

The loops: what Google publishes and what candidates report

What Google publishes, for every role

Google’s hiring page says that before the in-depth interviews you will typically have one or two shorter conversations with a recruiter, then a panel of interviews over video or in person, and that every candidate is assessed using clear rubrics. Source 7Our hiring process - Google CareersPublisherGoogleSource typecompany hiring page That page covers hiring at Google in general, not the FDE loop or the CE loop.

Google’s published policy says AI tools are not permitted during interviews. Source 7Our hiring process - Google CareersPublisherGoogleSource typecompany hiring page Many of Google’s FDE postings add that, in most instances, the position requires in-person interviews. Source 2Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting

The customer engineer loop

We found no published description and no candidate report of it, so we won’t guess. Ask your recruiter for the round list for your role and level, in writing if you can.

The FDE loop, from Blind

Posters on Blind describe a two-interview FDE loop. One candidate, at L4, wrote in July 2026 that there were only two interviews, a system architecture round and a coding round, and three others wrote before interviewing that they had been told of, or had scheduled, two. Source 8FDE Interview Experience at Google (L4) - BlindPublisherBlindSource typecandidate report on BlindSource 9URGENT!! GOOGLE FDE 4 (L6) - BlindPublisherBlindSource typecandidate report on BlindSource 10Google Cloud GenAI FDE Interview - BlindPublisherBlindSource typecandidate report on BlindSource 11Can anyone share insights into Google FDE interviews? - BlindPublisherBlindSource typecandidate report on Blind One of those posters, interviewing for FDE 4 (L6) in July 2026, wrote that the recruiter said “one LC medium/hard and one RRK Agentic system design”. Source 8FDE Interview Experience at Google (L4) - BlindPublisherBlindSource typecandidate report on BlindSource 9URGENT!! GOOGLE FDE 4 (L6) - BlindPublisherBlindSource typecandidate report on BlindSource 10Google Cloud GenAI FDE Interview - BlindPublisherBlindSource typecandidate report on BlindSource 11Can anyone share insights into Google FDE interviews? - BlindPublisherBlindSource typecandidate report on Blind (LC is LeetCode; RRK is what these posters call the design round, and our post on what candidates describe in the Google FDE loop unpacks it.)

Treat these as a handful of dated accounts, not a map of every loop. The loop post linked above has each report in full and a worked answer to the design role-play.

Notice what that design round asks for. A CTO describes a business problem, and you discover, scope and design an agent system, then defend it under follow-up questions. One candidate, the L4 poster, wrote that the discussion ran through deployment, security and evaluation Source 8FDE Interview Experience at Google (L4) - BlindPublisherBlindSource typecandidate report on BlindSource 12Is Google FDE interview same as SWE? - BlindPublisherBlindSource typecandidate report on Blind, so plan to explain how you would test the agent, not only how you would demo it. Practice designing an eval harness for a support agent, and read the agentic system design interview walk-through for tools, permissions and stuck agents. To rehearse that CTO conversation out loud, the free practice case puts you in front of an AI customer; it needs a sign-in.

Which one fits you

These are our heuristics, not Google’s criteria.

The customer engineer is likely the better fit if

  • You like being in the room when the customer decides, then moving to the next account.
  • Your best stories are demos, proofs of concept and objections answered.
  • You would rather design across many products than own one codebase in production.

The FDE is likely the better fit if

  • You want to own the code that runs in the customer’s environment.
  • You have stories about debugging a system you did not control.
  • You can explain how you would measure whether an agent works, not only how it is built.

Exact words for “why FDE and not customer engineer?”

If you are moving from a pre-sales seat, expect this question in some form. A strong answer names the part of the work you want, with evidence you have done some of it:

“I’ve spent the last few years on the side of the work that wins the technical decision, and I’ve watched a lot of delivery plans go to implementation. The part I keep reaching for is after that: writing the code inside the customer’s environment and being the one who knows why it breaks. On my last proof of concept I stayed on through the first production release. That’s the job the FDE posting describes, so that’s the one I applied for.”

Swap the last two sentences for your own evidence, then back it up. Prepare the customer-facing experience question with a shipping story, not a deal story.

Common mistakes, and the fix

  • Telling a deal story in an FDE interview. Fix: end on what shipped, who used it and how you knew it worked.
  • Calling a proof of concept “production”. Fix: say what it took to go from the proof of concept to the version people used, or say plainly that you handed it off.
  • Assuming the CE and FDE loops are alike. Fix: we have no evidence either way for the CE loop, so ask your recruiter for both round lists.
  • Practicing with an assistant open. Fix: rehearse the way you will interview, because Google’s published policy says AI tools are not permitted during interviews. Source 7Our hiring process - Google CareersPublisherGoogleSource typecompany hiring page

One candidate reported, in August 2026, clearing the Google FDE onsite and then waiting on a team match. Source 15Google FDE (GenAI) — team match before HC? Curious about others' timelines (post by u/No_Minimum415)PublisherReddit r/leetcodeSource typecandidate report on Reddit What candidates report about Google FDE team matching covers what to ask your recruiter while you wait.

Start with the role itself

Before you prepare for either loop, get sharp on what separates these jobs, because you will be asked. Our curriculum starts with The FDE role, decoded, a free module that covers what FDEs do, how the role differs from its neighbors, what travel involves and how to read a posting. Begin with telling the FDE, solutions architect and sales engineer apart, then read the Google posting you are applying to alongside how to read an FDE job posting line by line.

GlossaryForward deployed engineerA software engineer who builds and ships production systems inside a customer’s problem and environment, accountable to that customer’s outcome.More on Forward deployed engineerGlossaryAgentA system in which a model chooses steps and tool calls to complete a task, within limits the design sets.More on Agent

Questions people ask

What is the difference between a Google Cloud customer engineer and an FDE?

Google’s Platform Customer Engineer posting has the CE partner with sales, run proofs of concept and demos, drive the technical win and hand the delivery plan to implementation teams. Its GenAI FDE postings describe an embedded builder who codes, debugs and ships agentic solutions inside the customer’s environment.Source 1Customer Engineer, Platform, Google Cloud — Google CareersPublisherGoogleSource typecompany job postingSource 2Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting

Is Google’s customer engineer a quota-carrying role?

The Platform Customer Engineer posting states pay as a base range plus a bonus target plus equity, and does not use the word quota. Its bonus target is a larger share of base pay than in Google’s FDE IV GenAI posting. Ask the recruiter what the bonus is tied to.Source 1Customer Engineer, Platform, Google Cloud — Google CareersPublisherGoogleSource typecompany job postingSource 2Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting

Can you use AI tools in a Google FDE interview?

Google’s published policy says AI tools are not permitted during interviews.Source 7Our hiring process - Google CareersPublisherGoogleSource typecompany hiring page

Keep reading

Guides

Company guides

Lessons

Questions

More in Company loops