Architect the orchestration layer that fuses vendor AI and internal multi-agent chat at Coinbase

This is an IC5 ML engineering interview for Coinbase's CX Intelligence team, centered on designing the unified orchestration layer that routes state, context, and intent across vendor chatbots, internal multi-agent systems, and human agents. Expect deep technical design questions on LLM orchestration architecture, production Python services, and cross-team technical leadership rather than pure ML modeling trivia.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Multi-agent/LLM orchestration architecture (state, context, intent routing)
Hybrid vendor + internal system integration and hand-off design
Production-grade Python service design and testing discipline
Generative AI frameworks (LangGraph, LangSmith, Vertex AI, AWS Bedrock, Google ADK)
Technical leadership: design docs, trade-offs, mentoring, design reviews
Responsible/human-in-the-loop use of generative AI tools

Common question themes

Design an orchestration layer that hands off a conversation between a vendor chatbot and an internal agent mid-session — how do you preserve context and detect failure?

Walk through a production ML/AI service you shipped end-to-end — what broke in production and how did you catch it?

How would you structure intent routing across multiple LLM frameworks with different latency/reliability profiles?

Describe a time you had to make a technical trade-off under cross-functional pressure and how you communicated it to non-technical stakeholders

How do you apply human-in-the-loop practices when using generative AI copilots in your daily workflow?

What does your specialized depth (NLP / IR / CV / stats) bring to a conversational AI system like this one?

How candidates describe it

Real Senior Machine Learning Engineer interview stories — retold from candidates' public write-ups, with sources.

Google · L5 Machine Learning EngineerOffer

Google L5 machine learning engineer interview: phone screen skipped, four technical rounds, and an offer

A candidate applying for an L5 machine learning engineer role at Google had the phone screen skipped due to a referral and prior tenure at the company, then went through four technical and design rounds plus a behavioral round before receiving an L5 offer. The loop was one leg of a broader search that produced offers from several companies in the same cycle.

Interviewed April 2022 · Remote

Amazon · Applied Scientist (L4)Offer

Amazon Applied Scientist Interview Experience: Alexa Speech Team, 2021

A redirected recruiter call turned into an Amazon Applied Scientist loop with the Alexa Speech team: a phone screen, a split five-round virtual onsite across two teams, a bar raiser, and an added ML-breadth round, ending in an offer with a downlevel from L5 to L4.

Interviewed July 2021 · Boston, MA (Remote)

View the original posting

All Coinbase interviews