
Forward Deployed Engineer IV, Generative AI, Google Cloud
Posted 21 days ago
The role in short
Embed with customers to architect, code, and deploy production-grade agentic AI solutions and integrations using Google Cloud's AI stack.
Minimum qualifications:
Bachelor’s degree in Engineering, Computer Science, a related field, or equivalent practical experience.
8 years of experience with software development using Python or similar coding languages.
Experience building pipelines for structured and unstructured data using both vector databases and RAG-like architectures to power enterprise AI solutions.
Experience taking production-grade AI-driven solutions from conception to launch for customers.
Experience architecting AI systems on cloud platforms (e.g. Google Cloud Platform (GCP)).
Experience leading technical discovery sessions with customers.
Preferred qualifications:
Master’s degree or PhD in AI, Computer Science, or a related technical field.
Experience implementing multi-agent systems using frameworks (e.g., LangGraph, CrewAI, ADK) and complex patterns (e.g., ReAct, self-reflection, hierarchical delegation).
Knowledge of Large Language Model (LLM) native metrics (e.g., tokens/sec, cost-per-request) and techniques for optimizing state management and granular tracing.
About the job
As a Generative AI (GenAI) Forward Deployed Engineer (FDE) at Google Cloud, you are an embedded builder who bridges the gap between frontier AI products and production-grade reality within customers. Unlike traditional advisory roles, you will function as an innovator-builder, moving beyond high-level architecture to code, debug, and jointly ship bespoke agentic solutions directly within the customer’s environment. This role is designed for high-agency engineers with a founder’s mindset. You will address blockers to production including solving the integration complexities, data readiness issues, and state-management issues that prevent AI from reaching enterprise-grade maturity. By embedding with strategic accounts, you will serve a dual purpose: providing white glove deployment of complex AI systems and acting as a critical feedback loop, transforming real-world field insights into Google Cloud’s future product roadmap.
It's an exciting time to join Google Cloud’s Go-To-Market team, leading the AI revolution for businesses worldwide. You’ll excel by leveraging Google's brand credibility—a legacy built on inventing foundational technologies and proven at scale. We’ll provide you with the world's most advanced AI portfolio, including frontier Gemini models, and the complete Vertex AI platform, helping you to solve business problems. We’re a collaborative culture providing direct access to DeepMind's engineering and research minds, empowering you to solve customer challenges. Join us to be the catalyst for our mission, drive customer success, and define the new cloud era—the market is yours.
Individual pay is determined by factors including job-related skills, experience, and relevant education or training.
US: $207000 - $300000 (USD) + 20% bonus target + equity + benefits
Learn more about benefits at Google.
Responsibilities
Serve as a developer for complex AI applications, transitioning from rapid prototypes to production-grade agentic workflows (e.g., multi-agent systems, MCP servers) that drive measurable Return on Investment (ROI).
Architect and code the connective tissue between Google’s AI products and customer's live infrastructure, including APIs, legacy data silos, and security perimeters as part of an expert team.
Build high-performance evaluation pipelines and observability frameworks to ensure agentic systems meet rigorous requirements for accuracy, safety, and latency.
Identify repeatable field patterns and friction points in Google’s AI stack, converting them into reusable modules or formal product feature requests for the Engineering teams.
Co-build with Customer Engineering teams to instill Google-grade development best practices, ensuring long-term project success and high end-user adoption.
Information collected and processed as part of your Google Careers profile, and any job applications you choose to submit is subject to Google's Applicant and Candidate Privacy Policy.
Google is proud to be an equal opportunity and affirmative action employer. See also Google's EEO Policy.
If you have a need that requires accommodation, please let us know by completing our Accommodations for Applicants form.
Google is a global company and, in order to facilitate efficient collaboration and communication globally, English proficiency is a requirement for all roles unless stated otherwise in the job posting.
To all recruitment agencies: Google does not accept agency resumes. Please do not forward resumes to our jobs alias, Google employees, or any other organization location. Google is not responsible for any fees related to unsolicited resumes.
Equity is granted exclusively and discretionarily by Alphabet Inc. on the basis of an agreement concluded between you and Alphabet Inc. Alphabet Inc. is your sole contractual partner with respect to equity grants. GSU grants are not guaranteed, are discretionary, are subject to approval by the Alphabet Inc. board of directors or its delegate, the terms of the relevant Alphabet Inc. stock plan, and your grant agreement. They have no impact on statutory payments. Current or past grants do not confer an acquired right.
Prep for this interview
4 questions likely to come up at Google, each matched to a line in this posting.
- 1Discovery and scoping
They wrote: “Experience leading technical discovery sessions with customers.”
A customer says “we want AI in our claims process.” What do you ask in the first meeting?
How to answer
Why they ask: Most FDE work starts this vague. They want to hear you find the real problem before you pick a tool.
- Map the current process: who touches a claim, in what order, with which systems
- Find the slowest or most error-prone step and ask what it costs them
- Agree on one measurable goal (for example time per claim, or error rate)
- Ask what data you can access, and who signs off on security
Tip: Ask about the work, not the technology. Who does it today, how long it takes, what a mistake costs, and how they'd know it got better.
- 2Integrations and APIs
They wrote: “Architect and code the connective tissue between Google’s AI products and customer's live infrastructure, including APIs, legacy data silos, and security perimeters as part of an expert team.”
Walk me through connecting our product to a customer's internal system that has no documentation.
How to answer
Why they ask: This happens weekly in the job. They want a calm, step-by-step method.
- Find who owns the system and get read access to a test environment
- Watch real traffic or logs to learn the data shapes
- Build a thin adapter with logging around every call
- Agree on how failures get reported, and who fixes what
Tip: Talk about finding the owner of the system first. The code is the easy part.
- 3LLMs, RAG and agents
They wrote: “Experience building pipelines for structured and unstructured data using both vector databases and RAG-like architectures to power enterprise AI solutions.”
A customer wants a chatbot over their internal documents. How do you build it?
How to answer
Why they ask: RAG is the most common first project. They want the whole path, from messy files to answers people trust.
- Collect and clean the documents; handle permissions per user
- Split them into chunks, embed, and store with source links
- Retrieve, then answer with citations; say “I don't know” when retrieval is weak
- Build a test set of real questions with expected answers before launch
Tip: Spend more time on the data and on testing than on the model.
- 4Cloud, deployment and security
They wrote: “Experience architecting AI systems on cloud platforms (e.g. Google Cloud Platform (GCP)).”
The customer's security team sends a 200-question review. How do you handle it?
How to answer
Why they ask: Security reviews often block deals. FDEs help get through them.
- Start from your company's standard answers (SOC 2 report, past reviews)
- Answer clearly; don't oversell
- Bring in your security team for anything you're unsure of
- Keep the new answers for the next customer
Tip: Reuse past answers, flag honest gaps, and offer a call for the hard questions.
Not the one? Get the next one by email
New roles land here every day. Pick what you want to hear about.
Want the job, not just the posting? Learn how FDEs work.
FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.
Free. One email a week. Unsubscribe in one click.

