Staff+ Software Engineer, Enterprise Connectivity

The shape of it

In the posting’s own words

You'll be a technical leader who owns activation end to end, from the moment someone sees a connector to their first successful use of it. You'll also help to shape the foundations that help the connector ecosystem grow, and the governance controls that make it safe at enterprise scale. You'll partner closely with product, design and data science, and carry real ownership over what we ship next.

What it asks for · 7

• Have shipped growth or activation work: onboarding flows, funnels, experimentation, and measuring what actually moves usage
• Are comfortable with authorization and identity (OAuth 2.0, OIDC, SSO), enough to make setup flows simple without cutting corners
• Have built on large platform APIs (Microsoft Graph, Google Workspace or similar) and can debug failures on both sides of the boundary
• Have built platform or ecosystem surfaces that other teams or developers rely on, and care about durable, well-designed APIs
• Understand what enterprise admins and security teams need from policy, permissions and governance at scale
• Use data and user research to decide what to build, and can explain the tradeoffs to product and design partners
• Drive cross-team and cross-company alignment to ship, with influence over authority

Also a plus

• Have 8+ years of software engineering experience, ideally with 2+ years at a Staff or equivalent technical leadership level
• Contributed to or implemented emerging auth standards (IETF OAuth drafts, MCP authorization)
• Experience with data governance or information protection (sensitivity labels, DLP)
• Built admin consoles or policy engines for multi-tenant SaaS
• Run growth experiments on activation funnels
• Built AI products or agent tool integrations (MCP)
• Helped grow a developer or partner ecosystem around a platform

What the job covers

• Own connector activation end to end: measure the funnel from discovery to first use to habit, find the biggest drop-offs, and fix them
• Build and run experiments on default connectors, in-product suggestions, connector requests and onboarding flows
• Make setup close to zero-touch, building on open standards like Cross App Access (XAA) and the MCP authorization spec so one approval can turn a connector on for everyone
• Improve the connectors people reach for most, like Microsoft 365 and Google Workspace, so the first experience works and keeps working
• Lay platform foundations for the connector ecosystem: reusable building blocks that make every new connector easier to launch, discover and activate
• Build out the enterprise control plane: admin controls and governance (domain restrictions, labels, permissions) that help security teams say yes faster instead of blocking rollout
• Partner with product, design, data science and sales to turn usage data and customer feedback into priorities
• Set technical direction and standards for the team, mentor other engineers, and lead with influence rather than authority

Tools and skills named

Words the posting leans on

• connector13×
• activation5×
• data5×
• enterprise5×
• admin4×
• built4×
• control4×
• end4×
• governance4×
• partner4×
• platform4×
• product4×
• setup4×
• build3×
• building3×
• connector ecosystem3×

Counted from the posting after the mission statement and the legal notices are set aside. The ones near the top are the ones a screener is looking for.

More open at Anthropic

• 3P Revenue Accounting & ReportingSan Francisco, CA | Seattle, WA
• Account Executive, AI NativeNew York City, NY; San Francisco, CA | New York City, NY
• Account Executive - DNBSingapore
• Account Executive, NonprofitSan Francisco, CA | New York City, NY
• Account Executive - Public Sector (ASEAN)Singapore
• Account Executive, StartupsDublin, IE