Job Opportunities API

About Pantheon Pantheon WebOps Platform powers the open web, running more than 300,000 sites in the cloud for customers including Google, Princeton, Salesloft and Doctors Without Borders. Every day, thousands of developers and marketers create, iterate, and scale WordPress and Drupal sites to reach billions of people globally. Pantheon’s multitenant, container-based platform enables organizations to manage all of their websites from a single dashboard. Organizations including Clorox and the United Nations drive results through accelerated development and real-time publishing using Pantheon’s collaborative workflows.  The Role This is a foundational role — the first engineer of its kind here, on a product early in its life. There is a large amount of ground to clear and no established playbook. You'll define the discipline as you build it. The people implementing on our new platform — developers at agency partners in most cases, in-house teams at direct customers in others — are building design systems and websites and connecting those sites to third-party services: commerce platforms, identity providers, analytics, search, consent management, industry-specific backends. Your job is to make that work easier. Not by doing it for them — we provide the materials so clients can do it themselves. "Materials" is deliberately broad: documentation and guides, scripts, AI skills, connectors, reference implementations, and example widgets with integrations already built in (which are really just reference implementations in another form). How the work arrives: our sales engineer learns that a client is about to implement against a particular system — say, BigCommerce. You, the SE, and the client then work out the list of materials that would make that implementation easier, and you build them. The one-off then becomes reusable: what you built for one client's BigCommerce integration is the starting kit for the next one. The mix of writing versus coding will shift over time. Early on, it's probably more writing — guides and documentation — with the coding share growing as patterns repeat and reference implementations accumulate. We honestly don't know the long-run split, which is why we need someone genuinely strong at both. What you'll do Scope enablement needs per implementation. Work with the sales engineer and the client to identify what would make an upcoming implementation easier, and turn that into a concrete build list. Write documentation and guides. Clear, tested, step-by-step material that a developer who has never talked to you can follow to a working result. Build reference implementations and example widgets. Working examples with real integrations built in — the fastest way to show a client how something is done is to hand them a version that already does it. Build connectors and adapters. Where a category is a long tail of vendors rather than one dominant player, build the flexible pattern plus worked examples rather than betting on a single vendor. Build scripts and AI skills. Tooling — including agentic AI skills — that automates or accelerates the repetitive parts of implementation work. Generalize from one-off to reusable. When a solution gets built for one client, capture it so the next client with the same need starts from a kit instead of from scratch. Feed product. You'll see, before anyone else, which needs recur often enough to become real platform features. Make that case with evidence. What you'll need Strong full-stack engineering skills with real depth in the modern JavaScript ecosystem — Next.js and React specifically. Experience integrating third-party systems: REST/GraphQL APIs, webhooks, OAuth/SAML authentication flows. Writing ability that matches your engineering ability. Especially early, much of this job's output is written material — and it has to work for a developer you'll never meet. Comfort building with