AI Engineer, Ecosystem
Job description
About the role
You will serve as the technical owner for Brex's external AI ecosystem, owning the integrations, surfaces, and standards that enable customers to interact with Brex through third-party assistants and platforms. Over the next year, you will transform early integrations into exemplar applications that are stable, secure, and opinionated, becoming the foundation trusted by power users at our most sophisticated customers. You will design how Brex data and actions are safely exposed across boundaries, how permissions and auditability work, and how new capabilities including richer UI surfaces are introduced over time. This role is a product role disguised as infrastructure, where success is measured by real usage, trust, and customer reliance rather than by the number of integrations shipped. You will partner cross-functionally to ensure integrations are safe, valuable, and well-supported, defining and evangelizing the standards and patterns that power AI functionality across the Brex platform and its external ecosystem.
Key facts
What you'll do
- Own Brex's MCP Apps for OpenAI, Claude, Slack, and other embedders, including roadmap decisions across core and long-tail partners.
- Define the technical, UX, and reliability standards for how Brex surfaces and operates within external AI assistant ecosystems.
- Design and maintain secure, auditable integration patterns, including permissions, read/write access, and acting on behalf of users across third-party environments.
- Build and operate production-grade integrations that remain resilient amid evolving platforms, unpredictable clients, and shifting constraints.
- Partner cross-functionally with Security, Platform, Sales, Enablement, and internal agent teams to ensure integrations are safe, valuable, and well-supported.
- Serve as the center of excellence for reusable AI capabilities across Brex, defining and evangelizing standards, patterns, and shared components that power AI functionality both within the Brex platform and across external ecosystem integrations.
- Architect and implement extensible frameworks that abstract complexity for downstream product teams while preserving the flexibility needed for bespoke client workflows.
- Drive the end-to-end lifecycle of integrations from discovery and prototyping through scale-out productionization and ongoing reliability improvements.
- Establish rigorous testing and observability practices tailored to the unique failure modes of AI-driven financial workflows and external API interactions.
- Translate nuanced customer requirements and security constraints into clear product requirements and technical specifications for distributed teams.
- Champion best practices for auditability, traceability, and compliance across all external touchpoints and data exchanges.
- Lead the design of future-state ecosystem experiences, including richer UI surfaces and multimodal interactions, ensuring consistency with Brex's platform principles.
Requirements
- Experience building and owning production software, including systems that integrate with or depend on third-party platforms.
- Demonstrated technical ownership for user-facing products with real external customers in production environments.
- Deep experience with identity, authentication, and secure data access across system boundaries, including OAuth and role-based access control (RBAC) for permissions.
- Proven ability to ship and operate reliable integrations with external APIs and clients outside your control, handling rate limits, version drift, and partial outages.
- Strong understanding of authorization models, data governance, and privacy practices relevant to financial data and regulated workflows.
- Experience designing and implementing secure integration patterns that balance ease of use with strict security and audit requirements.
- Comfort working in fast-moving, ambiguous environments where requirements evolve based on customer and partner feedback.
- Excellent written and verbal communication skills to articulate technical trade-offs to both technical and non-technical stakeholders.
Nice to have
- Experience with AI assistant platforms, plugin ecosystems, and emerging standards for AI-driven workflows.
- Familiarity with financial services data models, transaction semantics, and compliance considerations in regulated environments.
- Background in building and operating SaaS platforms with multi-tenant architecture and strict security expectations.
Practical notes
- Work location is Seattle, Washington, United States.
- Engagement is full-time.
- This role follows a hybrid schedule requiring three coordinated days in the office per week - Monday, Wednesday, and Thursday.
- As a perk, the role includes up to four weeks per year of fully remote work.