Engineering Manager, Integrations

AirOps•San Francisco, CA

About The Position

AirOps is the first end-to-end content engineering platform built for the AI era. In a world where discovery is shifting from traditional search to AI-driven platforms, we help brands get found—and stay found. We are currently in a phase of hyper-growth, having 5x’d our revenue in the last year by helping marketing teams at Ramp, Chime, Carta, and Rippling turn content quality into a durable competitive advantage. Our platform equips marketers to navigate the new discovery landscape, prioritize high-impact opportunities, and create accurate, on-brand content that earns citations from AI and trust from humans. Backed by Greylock, Unusual Ventures, Wing VC, and Founder Collective, we are building the intelligent systems that will empower the next generation of marketing leaders. AirOps is headquartered in San Francisco, New York and Montevideo.

Requirements

2+ years managing a technical or technical-adjacent team, with evidence of leveling up junior members into senior operators
Hands-on with integration craft: REST APIs, webhooks, OAuth, common iPaaS and middleware patterns. You can read code, hold your own in design discussions, and tell a customer config problem from a product bug fast
You have built systems that compound team throughput before — tooling, templates, runbooks — and you can point at the before and after
Comfort in both engineering reviews and partner conversations. You move from a technical escalation with a partner to a feasibility call with Sales without changing register
Capacity-planning instincts: you know what the team can hold, what it should not commit to, and how to say no in a way that keeps the relationship intact
Ownership mentality: scope does not constrain you, outcomes do

Nice To Haves

Familiarity with one or more integration ecosystems: CRM, marketing automation, data warehouse, or vertical SaaS
Partnership or BD experience, or having owned a P&L or budget line
Experience standing up an on-call or rotation model for a growing integration portfolio

Responsibilities

Run the Integration Specialist team: you set the bar, run the 1:1s, build the leveling rubric, and stand behind every commit the team makes. People grow here or you change something
Team throughput as a real metric: you forecast capacity, manage queue depth, and drive integrations-per-specialist-per-quarter up quarter after quarter. The systems that get you there (tooling, templates, SOPs) are yours to build
Integration delivery end to end: scoping, build, QA, handoff. You translate customer and partner needs into clean technical scope and represent integration realities — rate limits, deprecation risk, partner constraints — in every design review
The integration portfolio as an ongoing business asset: usage, error rates, partner SLAs, incident response. You make the maintenance, deprecation, and version-upgrade calls with a clear cost/benefit view, not by default
Partner relationships that matter: top integration partners run through you. Technical escalations, co-build conversations, co-marketing — you are the credible point of contact and you bring opportunities back for the commercial team to act on
Integration-led deals with Sales, CS, and Product: feasibility calls, contract language, rollout, retention. When integrations are the thing standing between us and a deal, you are in the room and you have a point of view