YouTube
YouTube

Forward Deployed Engineer, GenAI, YouTube Go-To-Market Technology and Insights

$128–184kSan Bruno, CA, USA; Mountain View, CA, USA; New York, NY, USA; San Bruno, CA; New York, NYOn-siteMidFull-time

Posted 7 days ago

The role in short

Build and deploy internal GenAI tools and multi-agent systems to optimize YouTube's Go-To-Market business operations.

Minimum qualifications:

  • Bachelor's degree in Computer Science, Electrical Engineering, Math or related quantitative field, or equivalent practical experience in software development.
  • 4 years of experience in full-stack software development and system design.
  • Experience with front end languages (e.g., JavaScript or TypeScript).
  • Experience with backend languages (e.g., Java, Python, or C++).
  • Experience working with database technologies (e.g., SQL, NoSQL).
  • Experience with full-stack development, API design, and systems engineering.

Preferred qualifications:

  • 4 years of experience with cloud/microservice architectures, building LLM applications, multi-agent systems, or GenAI frameworks (e.g., MCP).
  • 4 years of experience optimizing databases, alongside vector databases, embedding generation, search architectures, and AI data-readiness issues.
  • 2 years of experience collaborating on requirements, bringing domain knowledge of GTM operations, enterprise sales workflows, or CRM/CMS integrations.
  • 2 years of experience in SRE, InfoSec, or DevOps, plus background in LLM evals, observability frameworks, and AI guardrails.
  • Experience in tech consulting or entrepreneurial environments, delivering zero-to-one initiatives and building scalable products from the ground up.

About the job

It's an exciting time to join the AI Accelerator team, a newly formed task force dedicated to driving AI transformation for YouTube Business Go-To-Market (GTM) operations. Our mission is to operate as a high-velocity, horizontal transformation engine at the intersection of consulting, product strategy, applied AI, and systems engineering—redesigning legacy workflows from scratch to drive direct business impact for YouTube.

At YouTube, we believe that everyone deserves to have a voice, and that the world is a better place when we listen, share, and build community through our stories. We work together to give everyone the power to share their story, explore what they love, and connect with one another in the process. Working at the intersection of cutting-edge technology and boundless creativity, we move at the speed of culture with a shared goal to show people the world. We explore new ideas, solve real problems, and have fun — and we do it all together.

Individual pay is determined by factors including job-related skills, experience, and relevant education or training.

US: $128000 - $184000 (USD) + 15% bonus target + equity + benefits

Learn more about benefits at Google.

Responsibilities

  • Partner with stakeholders to co-create tool roadmaps, translating ambiguous business problems into tangible software solutions that enable YouTube's operations.
  • Iterate GenAI proof-of-concepts (LLMs, RAG, agentic frameworks) into production-grade AI applications (multi-agent systems, MCP servers) that drive measurable ROI.
  • Execute the full software development lifecycle: author technical design documents, ship maintainable code, build intuitive frontend surfaces, and manage deployment.
  • Build high-performance evaluation (eval) pipelines and observability frameworks to ensure agentic systems meet accuracy, safety, compliance, and latency requirements.
  • Resolve technical hurdles preventing AI maturity, including data readiness gaps, system integration complexities, edge-case managing, and state-management issues.

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. We are committed to building a workforce that is representative of the users we serve, creating a culture of belonging, and providing an equal employment opportunity regardless of race, creed, color, religion, gender, sexual orientation, gender identity/expression, national origin, disability, age, genetic information, veteran status, marital status, pregnancy or related condition (including breastfeeding), expecting or parents-to-be, criminal histories consistent with legal requirements, or any other basis protected by law. See also Google's EEO Policy, Know your rights: workplace discrimination is illegal, Belonging at Google, and How we hire.

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

5 questions likely to come up at YouTube, each matched to a line in this posting.

  1. 1LLMs, RAG and agents
    They wrote: “Iterate GenAI proof-of-concepts (LLMs, RAG, agentic frameworks) into production-grade AI applications (multi-agent systems, MCP servers) that drive measurable ROI.”

    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.

    1. Collect and clean the documents; handle permissions per user
    2. Split them into chunks, embed, and store with source links
    3. Retrieve, then answer with citations; say “I don't know” when retrieval is weak
    4. 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.

  2. 2Discovery and scoping
    They wrote: “Partner with stakeholders to co-create tool roadmaps, translating ambiguous business problems into tangible software solutions that enable YouTube's operations.”

    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.

    1. Map the current process: who touches a claim, in what order, with which systems
    2. Find the slowest or most error-prone step and ask what it costs them
    3. Agree on one measurable goal (for example time per claim, or error rate)
    4. 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.

  3. 3Coding
    They wrote: “Experience with backend languages (e.g., Java, Python, or C++).”

    Here's a CSV export from a customer. Write a script that cleans it and loads it into our API.

    How to answer

    Why they ask: Very close to real FDE work. They watch how you handle bad rows and failures.

    1. Read with a proper CSV parser; check the header first
    2. Validate each row and collect errors, not crash on the first one
    3. Send in batches with retries and a clear report at the end
    4. Write one or two quick tests for the parsing

    Tip: Talk through edge cases out loud: encodings, missing fields, duplicates, rate limits.

  4. 4Integrations and APIs
    They wrote: “Experience with full-stack development, API design, and systems engineering.”

    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.

    1. Find who owns the system and get read access to a test environment
    2. Watch real traffic or logs to learn the data shapes
    3. Build a thin adapter with logging around every call
    4. 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.

  5. 5Data and SQL
    They wrote: “Experience working with database technologies (e.g., SQL, NoSQL).”

    Write a query that finds each customer's first and most recent order.

    How to answer

    Why they ask: A quick check that you're comfortable with grouping, joins and window functions.

    1. Clarify the tables and what counts as an order (cancelled ones?)
    2. Use MIN/MAX with GROUP BY, or ROW_NUMBER() if you need the whole row
    3. Handle ties on the same timestamp, and customers with no orders
    4. Explain how you'd test it on a few known customers

    Tip: Say what you'd check in the data before writing the query: duplicates, time zones, nulls.

Not the one? Get the next one by email

New roles land here every day. Pick what you want to hear about.

FDE Info

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.

Similar roles at other companies

YouTube

$128–184k · On-site

Apply