Job description
About Runlayer
AI is transforming how every company operates, but most enterprises are stuck. They want to move fast with AI Agents, tools, and workflows, but they can't do it safely. We're fixing that.
Our team built AI Actions for OpenAI, shipped Zapier Agents to millions of users, and launched the first remote MCP server with Anthropic. We helped establish the protocol, and now we're building the platform enterprises need to actually put AI to work.
Runlayer is one platform for MCPs, Skills, and Agents: purpose-built security, fine-grained governance, and complete observability so organizations can go all-in on AI across the entire company without the risk. We just raised a $30M Series A led by Felicis, with participation from Khosla Ventures, bringing our total raised to $42M. Already trusted by Gusto, Instacart, Opendoor, dbt Labs, and Decagon.
About the RoleAs an Integrations Engineer, you'll own Runlayer's coverage surface: making every AI client, agent framework, and MCP server work first-class through the control plane. Coverage is the product, so you'll own integrations end to end, from design and launch through monitoring and debugging, and catch breaks before customers do. This is a hands-on, high-ownership role, and you'll help shape how the integrations function works as it grows.
Why You'll Thrive HereImpact: Coverage is the product; you'll make every AI client, agent framework, and MCP server work first-class through Runlayer.
Excellence: Work alongside engineers who helped establish MCP and ship fast.
Ownership: Own integrations end to end, from design and launch to monitoring, on-call, and incident response.
What You'll DoOwn the full lifecycle of integrations: design, build, launch, monitor, and debug connectors across clients, agent frameworks, and MCP servers.
Make every major AI client (Claude Code, Claude Desktop, Cursor, Codex, Copilot, and the long tail) work first-class through Runlayer, from auth to policy enforcement, hooks, and session extraction.
Give agents built on any ADK (Claude Agent SDK, OpenAI Agents SDK, LangGraph, Google ADK, and whatever ships next) identity, governance, and observability, including agent accounts and attributing MCP calls to the agents that made them.
Keep 50+ third-party MCP connectors reliable: catch upstream breaks and auth regressions before customers hit them, and guide admins safely through migrations (URL changes, stdio-to-deploy, forced re-auth, scope changes).
Own reliability end to end: coverage smoke-tests on every release, monitoring, and fast debugging under real-time customer pressure.
Build the OAuth broker (the TypeScript/Express service managing OAuth 2.1 flows for third-party servers) and the tooling that scaffolds, validates, and publishes new integrations with little manual work.
Work cross-functionally with product, partnerships, and customers, and help shape how the integrations function grows.
What We're Looking For5+ years building integrations, SDKs, or developer-platform connectors, with strong opinions on partner API design.
Expert-level OAuth 2.1: you've implemented authorization servers, token brokers, or complex multi-provider OAuth flows.
Agent-ecosystem fluency: you've built or operated MCP servers and shipped on at least one agent framework, and can explain transports, tool schemas, and session lifecycle from experience.
Strong TypeScript and Python.
You've built integration test suites that run against real third-party APIs with auth.
An operational mindset: you own systems in production, treat reliability as first-class, and can trace an issue from a customer report through logs and API responses to root cause.
You've maintained a catalog or marketplace of third-party integrations, with versioning, deprecation, and migration patterns.
AI-native workflow: you delegate real work to agents daily
Bonus QualificationsContributions to the MCP spec or to an agent framework.
Experience running or scaling a partner / integrations engineering function.
Familiarity with enterprise identity (SSO, SCIM) and policy enforcement.
What We OfferWe provide a competitive package designed to attract and retain top talent who can work effectively with enterprise customers.
Competitive salary and equity — compensation that reflects your expertise and customer-facing responsibilities.
Paid time off — paid vacation, paid sick leave, and paid parental leave.
Professional development — budget for conferences, courses, and certifications in AI, enterprise software, and customer success.
Top-tier equipment — your choice of laptop and accessories to create your ideal work environment.
Health benefits — comprehensive health, dental, and vision coverage.
Customer interaction opportunities — work directly with innovative companies and see the immediate impact of your work.
Not quite the right fit? Reach out to careers@runlayer.com with details about your experience and interests.
Prepare your application
Use the description above to assess your fit for Runlayer. This checklist is guidance from Resumize, rather than additional requirements from the employer. Imported listings can be shortened or change after collection, so confirm the complete description and current availability before sending an application.
Match requirements to evidence
Identify the responsibilities and skills the employer explicitly names. For each important requirement, choose one example from your work, education, training, or projects. Explain what you did, how you did it, and what changed as a result. Include a measurable outcome when you can support it. If you lack a requirement, describe related experience accurately instead of adding an unfamiliar skill to your resume.
Put the most relevant examples near the top of your resume. Keep job titles, dates, qualifications, and contact details consistent across your application materials. Use the employer’s terminology when it describes your experience accurately; a copied list of keywords does not explain your contribution. A short, specific bullet is easier to review than a paragraph that mixes several unrelated duties.
Check the working arrangement
Confirm the location, schedule, employment type, and any eligibility requirements on the employer’s site. A remote label does not establish worldwide eligibility or flexible hours. If compensation, benefits, equipment, travel, or contract duration are missing from this listing, write down your questions for the recruiter. Do not assume details from another opening at the same company apply to this role.
Review before submitting
Follow the employer’s requested file format and application instructions. Open your exported resume and check that its text is selectable, its sections read in order, and its links work. Proofread names, dates, and contact information. Share confidential work samples only when you have permission, and use an anonymized example when necessary.
Submit through a trusted employer or recruiting destination. If the original listing has disappeared, search the employer’s careers page for the title rather than assuming the vacancy remains open. Save the application date, job reference, and the version of your resume you sent. Those details help you prepare for a later conversation and avoid submitting conflicting information through several job boards.
Review your resume for writing and readability feedback, or browse other openings if this opportunity is unavailable.