AI Engineer owning Brex's MCP Apps across OpenAI, Claude, and Slack — a product role disguised as infrastructure

Brex is hiring an AI Engineer to be the technical owner of its external AI ecosystem — MCP Apps and integrations that let customers interact with Brex through third-party assistants like OpenAI, Claude, and Slack. The JD explicitly frames this as 'a product role disguised as infrastructure,' measured by real usage and customer trust rather than integrations shipped, with heavy emphasis on secure cross-boundary identity (OAuth, RBAC) and resilience against unpredictable third-party platforms.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Secure, auditable cross-boundary integration design (OAuth, RBAC)
Building resilient integrations against unpredictable third-party platforms
Product ownership of external AI ecosystem surfaces (MCP Apps)
Prioritizing roadmap across core vs. long-tail embedder partners
Measuring success via real usage/trust, not integration count
Evaluations for AI feature quality, reliability, and safety

Common question themes

How would you design OAuth-based permissioning so a third-party AI assistant can act on a customer's behalf without overreaching

Tell me about operating an integration with an external API that kept changing outside your control

How do you decide which platform partners or features to prioritize when you can't do everything

What does 'success' look like for an ecosystem integration beyond just shipping it

Describe building evaluations to measure quality, reliability, or safety of an AI-powered feature

Have you published or maintained an app in a third-party marketplace — what did that process look like

How candidates describe it

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

Google · L3 Software EngineerOffer

Google L3 software engineer interview: phone screen, four coding rounds, and the Googleyness round

A candidate with two years of experience went from recruiter outreach to offer over about four months. The onsite was four 45-minute coding rounds — three of them featuring binary trees — and one round turned into a 25-minute chain of follow-ups about approximating an optimal solution at scale.

Interviewed June 2020 · Bangalore, IN

Google · L4 Software EngineerNo offer

Google L4 Software Engineer Interview: Eight Rounds, No Offer

An L4 Software Engineer candidate went through two phone screens, three onsite rounds, a culture conversation, and a team-matching call with a Google hiring manager, then watched the process stall for about a month and a half over a tightened experience requirement before an added extended round ended without an offer.

Interviewed February 2024 · Not specified

Google · L5 Software EngineerNo offer

Google L5 software engineer interview: phone screening, three onsite rounds, system design, and a late rejection

A candidate interviewing for an L5 role went through a phone screening, three onsite coding rounds, a mobile system design round, and a Googleyness and Leadership round. Two of the four technical rounds went poorly by the candidate's own assessment, and after roughly two months of silence the recruiter reported that the role had been closed.

Interviewed January 2023 · Not specified

View the original posting

All Brex AI Engineer interviews

All Brex interviews