All interviews
Brex logo

Brex

Mid

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.

Step into this interview

Free · a live voice mock calibrated to this exact role

Practice this 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

View the original posting

Related interviews