Senior API Platform Engineer | Digital Transformation | API Platform & Agentic Ecosystem

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions. Must preserve all substantive info. We need to parse the posting. Job title: Senior API Platform Engineer Sections present: - About YPO (company description) maybe "About the role"? The posting includes "ABOUT YPO". Could map to "About the role"? Actually "About the role" is typical heading for description of role. The posting includes "ABOUT YPO" which is about company. Could treat as "About the role"? Might be better to use "About the role" for description of role and responsibilities? But we have separate sections for Responsibilities etc. The "ABOUT YPO" is company overview, not strictly role. Could we include it under "About the role"? Probably yes, as it's about the role context. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role heading with content from ABOUT YPO and maybe THE OPPORTUNITY? Actually THE OPPORTUNITY describes the role. Could combine. We need to decide what goes where. We have sections: - About the role: could include ABOYPO and THE OPPORTUNITY summary. - Responsibilities: from "WHAT YOU’LL DO" bullet list. - Requirements: from "WHAT WE’RE LOOKING FOR" bullet list. - Qualifications: maybe overlapping with Requirements; but we could treat Requirements as qualifications. However we need to decide if we have separate Qualifications section. The posting does not have separate qualifications beyond requirements. Could we omit Qualifications section if no distinct content? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So if we don't have distinct qualifications, we should not include Qualifications heading. - Skills: maybe we could extract skills from requirements (like experience with AWS API Gateway, etc). But that might be duplicative. Better to have Skills section if we can list specific skills. The posting includes many specific skills: REST/GraphQL design, AWS API Gateway, Lambda, Step Functions, Kafka, EventBridge, CDC, Terraform/CDK, OAuth2, Auth0/Okta, DDD, GDPR/CCPA, AI dev tools. Could create Skills section. - Benefits: posting mentions "Compensation at YPO is one part of a broader Total Rewards philosophy... performance-based bonus opportunities, remote work flexibility and a comprehensive rewards package". Also mentions remote work flexibility. So we have some benefits info: performance-based bonus, remote work flexibility, comprehensive rewards package. Also maybe "Flexible hours to support global teams" under ADDITIONAL INFORMATION. So we can include Benefits section with those. - Pay: posting includes compensation range: USD $119,200–$155,000 annually. Also mentions performance-based bonus opportunities. So we can include Pay section with that range. - Schedule: posting includes "Schedule: Flexible hours to support global teams" under ADDITIONAL INFORMATION. Also travel 10-15%. So we can include Schedule section with flexible hours. We must not include boilerplate like EEO, etc. We must not include duplicated lines. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like bullet points. We need to format using

for headings,

• for lists,

  for prose. We must output only HTML fragment, no /, no markdown fences. Let's craft. First, About the role: combine ABOYPO and THE OPPORTUNITY. ABOUT YPO paragraph: "YPO is a global leadership community of 35,000+ chief executives across 142 countries, built on peer learning, shared experiences and trusted relationships. Our digital transformation is building a platform where members can discover relevant peers and experiences, understand why they see what they see, control their data and trust every interaction. At the center of that transformation is a modern data and intelligence platform - with APIs serving as the connective tissue across YPO’s digital ecosystem." THE OPPORTUNITY: "We’re looking for a Senior API Platform Engineer with deep backend and API engineering experience to help build the platform powering YPO’s member ecosystem, chapter operations and emerging Agentic AI capabilities. This is more than an API implementation role. You’ll work through complex questions around API architecture, highly connected data, scalability, caching, consistency, performance, security and governance - and turn those decisions into production-quality solutions. You’ll own technical implementation end-to-end, make thoughtful architectural tradeoffs and partner across Product, Data, IT and Security to build systems that are scalable, secure, observable and maintainable." We can combine into a couple paragraphs. Now Responsibilities: from WHAT YOU’LL DO bullet list. Need to capture each bullet as

• . The bullet list includes many items grouped under headings: API Architecture & Engineering, Event-Driven & Distributed Systems, Agentic Ecosystem Engineering, API Lifecycle & Governance. We should preserve all bullet points. Let's extract bullet points: Under API Architecture & Engineering: - Design and build production-scale REST and GraphQL APIs using AWS API Gateway - Create stable API contracts that remain decoupled from underlying data and backend schemas - Design APIs over complex, highly connected and relationship-driven data - Solve architectural challenges involving caching, data consistency, concurrency, latency and performance - Define clear API and service boundaries using Domain-Driven Design principles - Design for scalability, reliability, resilience, security and observability - Implement versioning, backward compatibility and breaking-change strategies - Build within a serverless-first architecture using AWS Lambda and Step Functions Under Event-Driven & Distributed Systems: - Apply event-driven patterns using technologies such as Kafka, EventBridge and CDC - Design idempotent and resilient distributed workflows - Address data consistency, failure recovery and system behavior across interconnected services - Implement performance controls including caching, pagination and rate limiting Under Agentic Ecosystem Engineering: - Build governed API boundaries for AI agents using technologies including OpenAI, RAG and Gemini - Ensure agents interact through approved APIs rather than unrestricted raw data access - Support structured retrieval, provenance and deterministic fallback patterns - Build security, governance and observability into agent interactions Under API Lifecycle & Governance: - Own the API lifecycle from design and development through testing, documentation, versioning and deprecation - Maintain backward compatibility and clear breaking-change policies - Support CI/CD pipelines, observability and uptime requirements - Manage infrastructure through Infrastructure as Code using Terraform and/or AWS CDK - Partner with Security and Data teams on identity, authorization, privacy and consent requirements We'll list all as
• under a single
  maybe grouped but okay. Now Requirements/Qualifications: from WHAT WE’RE LOOKING FOR bullet list. Extract bullet points: - 6–8+ years of backend/API engineering experience, with deep hands-on experience designing and building API layers for complex, production-scale systems - Strong REST and/or GraphQL API design experience, including contracts, versioning and lifecycle management - Experience designing APIs over complex or highly connected data models, including graph-based or relationship-driven data - Strong understanding of non-functional requirements at the API layer, including scalability, reliability, resilience, latency, security and observability - Experience solving caching, data consistency, concurrency and performance challenges in distributed systems - Ability to evaluate architectural tradeoffs and translate business and product requirements into maintainable technical solutions - Experience with AWS API Gateway and serverless architecture, including Lambda and Step Functions - Experience with event-driven systems such as Kafka, EventBridge and CDC patterns - Infrastructure as Code experience using Terraform and/or AWS CDK - Experience with OAuth2 and identity platforms such as Auth0 or Okta - Understanding of Domain-Driven Design and clear service/API boundaries - Experience building privacy- and consent-aware systems, including GDPR/CCPA considerations - Strong cross-functional communication skills and the ability to explain complex technical decisions clearly - Active use of AI development tools such as Copilot or Cursor We could put these under Requirements heading. Could also split into Requirements and Skills but we have Skills separate. We need to decide: maybe Requirements = experience/years, Qualifications = education? Not present. So we could omit Qualifications. Skills: we could list specific technical skills: REST, GraphQL, AWS API Gateway, Lambda, Step Functions, Kafka, EventBridge, CDC, Terraform, AWS CDK, OAuth2, Auth0, Okta, DDD, GDPR/CCPA, AI dev tools (Copilot, Cursor). Also maybe GraphQL, etc. But we already have many of those in Requirements. To avoid duplication, we could put Skills as a concise list of technologies/methodologies. However instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If we put skills separately, we might be duplicating content but that's okay as long as we preserve. However we risk repeating same info. Might be better to not have Skills section if it would just repeat. But we could still have Skills section with a list of specific skills extracted from Requirements, but that would be summarizing (maybe okay). However we risk losing some nuance if we omit some details from Requirements. Better to keep Requirements as the detailed list and omit Skills unless there are additional skills not captured. The posting does not have a separate "Skills" section besides the requirements list. So we can omit Skills heading. Benefits: from "Compensation at YPO is one part of a broader Total Rewards philosophy..." and ADDITIONAL INFORMATION: travel 10-15%, flexible hours. Also "performance-based bonus opportunities, remote work flexibility and a comprehensive rewards package". Also maybe "remote work flexibility". So we can list benefits: performance-based bonus opportunities, remote work flexibility, comprehensive rewards package, travel 10-15% domestic and international, flexible hours to support global teams. We should preserve details: "performance-based bonus opportunities", "remote work flexibility", "comprehensive rewards package built around their wellbeing and growth". Also travel percentage. Pay: compensation range: USD $119,200–$155,000 annually. Also mention performance-based bonus opportunities (but that's also benefit). We'll include range. Schedule: "Schedule: Flexible hours to support global teams". Also travel 10-15% maybe under schedule? Travel is separate but we can include in Schedule or Benefits. The instruction: include Schedule section only if posting actually states them. It does state schedule: flexible hours. So we include Schedule with that line. Travel could be part of Schedule or Benefits; but we already have travel in Benefits maybe. We'll keep travel under Benefits. Now we need to ensure we don't include boilerplate like EEO, etc. Remove that. Now construct HTML. We'll have:

  About the role

  YPO is a global leadership community of 35,000+ chief executives across 142 countries, built on peer learning, shared experiences and trusted relationships. Our digital transformation is building a platform where members can discover relevant peers and experiences, understand why they see what they see, control their data and trust every interaction. At the center of that transformation is a modern data and intelligence platform - with APIs serving as the connective tissue across YPO’s digital ecosystem.

  We’re looking for a Senior API Platform Engineer with deep backend and API engineering experience to help build the platform powering YPO’s member ecosystem, chapter operations and emerging Agentic AI capabilities. This is more than an API implementation role. You’ll work through complex questions around API architecture, highly connected data, scalability, caching, consistency, performance, security and governance - and turn those decisions into production-quality solutions. You’ll own technical implementation end-to-end, make thoughtful architectural tradeoffs