AI Engineer, Ecosystem

EngineersOfAI; Seattle (WA); Hybrid; USD 130,000 - 160,000; Full time

Benefits offered by this job

Hybrid work model

Up to four weeks fully remote work per year

Job summary

EngineersOfAI in Seattle is seeking a Technical Owner for their AI ecosystem. This role involves integrating Brex with third-party platforms, focusing on robust implementations and user trust. You will collaborate across functions to create seamless AI interactions while ensuring security and reliability.

The ideal candidate has experience with production software and API integrations. The position promotes a hybrid work environment with flexibility around remote work days.

Qualifications

• Experience building and owning production software with third-party platforms.
• Demonstrated technical ownership of user-facing products.
• Deep understanding of identity and authentication across systems.

Responsibilities

• Own Brex's MCP Apps for integrations including roadmap decisions.
• Define UX and reliability standards for Brex in external ecosystems.
• Build secure, auditable integration patterns.

Skills

Production software ownership

API integration

Secure data access

OAuth

Cross-functional collaboration

Job description

AI at Brex

AI Engineering at Brex is redefining how businesses run their finances by building intelligent, autonomous systems directly into the Brex platform. Our teams develop AI agents that don’t just surface insights—they take action, optimizing spend, managing workflows, and making real-time decisions on behalf of our customers. By deeply integrating proprietary financial data with product and platform infrastructure, we’re turning complex financial operations into simple, automated experiences and setting a new standard for how modern finance works.

What you’ll do

You’ll be a technical owner for Brex’s external AI ecosystem: the integrations, surfaces, and standards that allow customers to interact with Brex through third‑party assistants and platforms.

Over the next year, you’ll turn early integrations into first‑class, exemplar applications—stable, secure, and opinionated—that are showcased by platform partners and relied on by power users at Brex’s most sophisticated customers. You’ll design how Brex data and actions are safely exposed, how permissions and auditability work across boundaries, and how new capabilities (including richer UI surfaces) are introduced over time.

This is a product role disguised as infrastructure. Success is measured by real usage, trust, and customer reliance—not by the number of integrations shipped.

Where you’ll work

This role will be based in our Seattle office. We are a hybrid environment that combines the energy and connections of being in the office with the benefits and flexibility of working from home. We require three coordinated days in the office per week — Monday, Wednesday, and Thursday. As a perk, we also have up to four weeks per year of fully remote work!

Responsibilities

• 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.

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.
• 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 cont