Equinix is the world’s digital infrastructure company®, shortening the path to connectivity to enable the innovations that enrich our work, life and planet. 

Job Summary

Analyzes business requirements to determine feasibility of design within time and cost constraints. Designs software systems.

Builds and operates internal and external tooling that enables a robust, usable API ecosystem—API governance, specifications (e.g., OpenAPI, OAuth2/OIDC, MCP), SDK and documentation generation workflows, and docs and developer platform engineering (e.g., Docusaurus, Backstage, Confluence) including plugins, upgrades, theming, and CI/CD. Applies automation (including AI agents/skills) to reduce toil and improve quality, safety, and operational reliability.

Responsibilities

Requirements Analysis

• Converts developer/customer integration feedback into API governance requirements (consistency, usability, versioning, deprecation, backward compatibility).

• Performs change‑impact analysis from specification and platform changes to downstream artifacts (SDKs, IaC integrations, docs generation, examples) and defines mitigation plans.

• Defines measurable outcomes for ecosystem improvements (adoption friction, validation coverage, pipeline reliability, support deflection).

Software Architecture

• Leads architecture and technical decision‑making for API ecosystem tooling: spec validation, SDK/IaC generation pipelines, docs generation, and release governance.

• Establishes standards and reference patterns for API lifecycle management (linting rules, breaking‑change policy, compatibility strategy) adopted across teams.

• Partners with gateway/edge stakeholders to align API designs with routing, policy enforcement, and onboarding constraints (e.g., Apigee, ALB, Kubernetes Ingress, Envoy).

• Defines secure‑by‑default architecture patterns in collaboration with identity and security teams (authentication flows, authorization models, policy boundaries).

Software Design

• Designs reusable, low‑friction interfaces and workflows enabling product teams to adopt governance and generation tooling with minimal coupling.

• Designs maintainable extension patterns for docs and developer platforms (e.g., Docusaurus, Backstage, Confluence): plugins, themes, UI extensions, and build integrations.

• Establishes contribution guidelines and engineering patterns (templates, scaffolding, conventions) that improve cross‑repo consistency and long‑term maintainability.

Development/Coding

• Understands and analyzes API Specifications (e.g., OpenAPI, OAuth2/OIDC, MCP).

• Builds and maintains automation and services that generate SDKs and documentation from API specifications.

• Builds and maintains IaC ecosystem components (e.g., Terraform Providers and Modules) and associated tooling to ensure high‑quality integrations.

• Develops and operates core ecosystem tooling in Go and Python (generators, validators, release tooling, CI helpers).

• Integrates gateway/edge and identity requirements into tooling and reference implementations (e.g., auth flows, policy hooks, onboarding paths).

• Uses AI agents/skills to reduce engineering toil (e.g., automated PR checks, impact summaries, suggested remediations) with deterministic verification and human review gates.

Testing

• Implements automated quality gates for ecosystem artifacts (SDKs, IaC providers/modules, docs outputs) using contract tests, golden tests, and spec compliance checks.

• Builds breaking‑change detection and compatibility testing across versions, including automated rollback and remediation guidance when validation fails.

DevOps

• Owns CI/CD for ecosystem tooling and docs/developer platforms: build/test/release, preview environments, artifact publishing, promotion/rollback workflows.

• Applies infrastructure‑as‑code practices to make environments repeatable and auditable; operates relevant services in Kubernetes‑based environments where applicable.

• Establishes release governance for generated artifacts (versioning policy, changelogs, signing/provenance where applicable) to improve trust and reproducibility.

Software Reliability & Support Engineering

• Defines and owns SLOs/SLAs for ecosystem pipelines and developer platforms; improves availability through observability, alerting, and runbooks.

• Serves as escalation point for incidents affecting spec validation, generation pipelines, portal builds, and gateway/identity integrations; drives post‑incident improvements.

• Implements change control practices that reduce risk during platform upgrades, plugin changes, generator updates, and pipeline refactors (canary, feature flags, staged rollouts).

Customer/Stakeholder Engagement

• Acts as internal advocate for developer experience and API usability; aligns product, platform, and security stakeholders on standards and adoption strategies.

• Provides technical guidance and high‑leverage reviews to teams contributing API changes, generators, providers/modules, and platform extensions.

Technical Project Management

• Plans and executes multi‑repo, cross‑team initiatives spanning specs, generators, IaC releases, and docs/developer platform deployments, including dependency and risk management.

• Communicates progress through outcome‑focused metrics (adoption, pipeline health, defect leakage, time‑to‑release), not status‑only reporting.

• Drives prioritization and scope tradeoffs to meet roadmap objectives while protecting ecosystem stability and compatibility commitments.

R&D/Innovation

• Evaluates and prototypes new approaches in API governance, specification tooling, and automation, with a focus on correctness and maintainability.

• Explores MCP‑based tooling and agentic workflows to improve developer experiences (e.g., agent‑driven validation and guided remediation), ensuring outputs remain verifiable and governed.

• Identifies opportunities to standardize and templatize ecosystem onboarding (reference repos, scaffolds, best‑practice docs/dev platform plugins).

Qualifications

Required

• Formal education in Computer Science, Computer Engineering, or a related field —or— equivalent practical experience.

• Experience building and operating production services and/or developer tooling with strong ownership and an operational mindset.

• Demonstrated experience with API lifecycle practices and governance: specifications (e.g., OpenAPI, OAuth2/OIDC, MCP), versioning, backward compatibility, breaking‑change management, and deprecation strategy.

• Proficiency in Go and/or Python, including building maintainable libraries/services and automation tools.

• Experience building internal platforms/tooling for developers (validators, generators, CI/CD automation, release tooling, developer workflows).

• Experience with infrastructure‑as‑code and automation‑first engineering practices, including building or maintaining IaC integrations (e.g., Terraform Providers and Modules).

• Working knowledge of Kubernetes concepts (deployments, config, networking, observability) and operating CI/CD‑driven delivery workflows in Linux environments.

• Knowledge of gateway/edge concepts and integration patterns (e.g., Apigee, ALB, Kubernetes Ingress, Envoy).

• Demonstrated effective use of AI agents/skills in engineering workflows with emphasis on verification, governance, and safe operation.

• Ability to lead through influence: setting technical direction, driving standards, mentoring, and aligning cross‑team stakeholders.

Preferred

• Strength in MCP development and applying MCP‑based tools to improve engineering workflows and developer experiences.

• Experience with docs and developer platforms (e.g., Docusaurus, Backstage, Confluence) including plugins, theming, build systems, and platform upgrades.

• Experience integrating or developing identity and authorization backends (e.g., OAuth/OIDC implementations, token services, policy enforcement, RBAC/ABAC).

• Experience with SDK generation and ecosystem stewardship (multi‑language clients, release/versioning strategies, compatibility testing).