Lead Product Manager- Integration & API

Deep enough to make credible technical calls on webhook retry semantics, event driven architecture, API versioning strategies, and encryption at the integration layer. Broad enough to translate framework capabilities into partner value, drive Solutions Exchange as a product led growth surface, and build the business case for API monetization. You'll move between architecture discussions with engineers, roadmap reviews with senior leadership, and go to market conversations with the Global Alliances team, sometimes all in the same week. This role also requires an AI native working style, not as a nice to have, but as a baseline expectation. UKG operates a fully agentic product and development lifecycle: our engineering teams build with AI coding assistants, our PM organization uses AI agents for research, synthesis, and documentation, and the products we ship are themselves AI powered. We're looking for someone who has genuinely internalized this shift, someone who reaches for an AI agent before a spreadsheet, who accelerates their PM work with agentic tools, and who understands how integration infrastructure must evolve to serve agentic consumers, not just human triggered workflows. You will: Own the integration framework strategy and evolution. Define the roadmap for the next generation integration framework: V2 enhancements, event driven architecture, advanced webhooks (editable payloads, retry logic, event filtering, webhook marketplace), batch event processing, and a generic transformation engine that reduces integration build time from months to weeks. Drive Solutions Exchange and partner ecosystem growth. Own the Solutions Exchange roadmap as a product led growth surface: self service partner onboarding, in app integration discovery, activation flows, and the developer experience that enables partners to build and ship integrations independently. Own the Audit Framework capability. Define the roadmap for the Audit Framework infrastructure underlying compliance and audit logging across UKG Ready. (Platform Services PM owns the Audit Trail Report surface; this PM owns the framework itself: audit event capture, data retention, encryption, and the APIs downstream systems consume.) Lead data import/export and encryption strategy. Own the Data Import/Export Framework including SFTP, conversion profiles, and bulk data handling, and own encryption services across the integration layer. Define data security strategy at the integration boundary to meet compliance requirements across all active integrations. Drive the Workflow and Integration Bryte AI Frontdoor. Own the AI powered interface for integration creation and workflow setup, from a partner or admin describing what they want in natural language to a configured, validated integration running in production. Drive integration standards across domain teams to reduce time to market for new partner integrations through reusable components and configuration driven development. Own the developer portal, API reference materials, and SDK guidance. Work as an AI native PM and raise the bar for those around you. Use AI agents daily across PRD drafting, technical research, document synthesis, metrics analysis, and stakeholder communications. Model agentic working practices within the team and bring a practitioner's perspective to the platform you are building for. Communicate strategy and roadmap to senior leadership and partners. Translate integration platform investments into business outcomes for engineering and product leadership. Represent the integration platform story externally to key partner organizations and internally to Global Alliances. Someone who understands that integration infrastructure is not plumbing, it is product. Someone who has shipped developer facing platforms, has the technical credibility to shape architecture decisions, and has the commercial instincts to drive ecosystem growth and monetization. This role requires both worlds: you need to earn the trust of principal engineers in a webhook architecture discussion and then turn around and build the partner GTM case for the same capability. We recognize that background takes many forms. We will consider candidates who meet one of the following experience profiles: Preferred: Technical founder or early engineer turned PM from an integration, API, or developer tools company. You've built something where the integration or the API was the product itself, not a feature appended to something else. You understand webhook delivery semantics, event schema versioning, and OAuth scopes not from a PM brief but from firsthand experience. That depth is exactly what this role demands. Strong: Engineering background with product transition. 4+ years of software engineering in platform, API design, integration infrastructure, or distributed systems, combined with 3+ years of product management in a growth startup or enterprise SaaS environment. You can read a failing integration trace without asking engineering to narrate it, and you bring that fluency into every roadmap conversation. Qualified: Senior PM with deep integration and API platform focus. 7+ years of product management, with at least 3 of those years owning integration platforms, API products, partner ecosystems, or developer tools at enterprise SaaS scale. You've earned technical credibility through proximity and rigor, and you've demonstrated you can hold your own with architects on event driven system design. Regardless of path, you will need to demonstrate the following on day one: Integration architecture depth. Webhooks, event driven architecture, API orchestration, data transformation, retry logic, idempotency, and error handling. You've designed or managed systems where integration reliability was a hard customer commitment, not a best effort feature. REST, OpenAPI, versioning strategies, backward compatibility, rate limiting, and what it takes to build APIs that developers actually adopt. You've written API documentation or led a developer portal initiative and understand why developer experience is a competitive moat. OAuth and authentication fluency for integration patterns. OAuth 2.0, OIDC, API keys, service account lifecycle, and how authentication models change when AI agents are callers rather than humans. This is distinct from core IAM ownership (Identity & Access team) and focused on the integration security boundary. Partner onboarding workflows, integration certification programs, developer SDKs, and the mechanics of a marketplace business. You understand that a partner integration is not done when it ships; it is done when partners adopt it at scale. Bulk data import/export, SFTP workflows, data transformation pipelines, and the compliance constraints that govern data in motion (encryption, retention, audit). Builder's decision making style. You make calls, you defend them, and you update when the data changes. You do not produce requirements documents that hedge every decision back to engineering. The ability to align engineering, domain PMs, partner organizations, Global Alliances, and product leadership across a globally distributed organization without formal reporting authority. Commercial and GTM instincts. You understand the difference between a technically successful integration and a commercially successful one. You've thought about monetization, ecosystem incentives, and what makes partners build on a platform rather than around it. Data driven prioritization. Integration reliability metrics, webhook delivery rates, partner adoption funnels, Solutions Exchange activation data, and API usage analytics drive your roadmap decisions. You actively use AI agents in your daily PM workflow: PRD drafting, technical research, document synthesis, metrics analysis, and stakeholder communications. You've worked in an environment where engineers build with AI coding assistants and you understand how that changes how requirements are written and how teams operate. Candidates who treat AI as an occasional tool rather than a core work practice will not be competitive for this role. Workato, MuleSoft, Boomi, Zapier, Make, or comparable iPaaS platforms, either as a builder or as a PM defining integration patterns that consume them. Designing or operating webhook delivery infrastructure including retry strategies, dead letter queues, payload versioning, and event filtering. Experience with tiered pricing models, usage based billing infrastructure, or platform ecosystem monetization at an API first company (Stripe, Twilio, Salesforce AppExchange patterns are directly relevant). ERP integrations (NetSuite, QuickBooks, Sage Intacct), HRIS or ATS connectivity, or payroll data exchange at enterprise scale. Familiarity with Model Context Protocol, AI agent tool registration, or building API layers that serve as tools for LLM powered agents. Owning or contributing to a developer portal build (README.io, Stoplight, custom), including API reference documentation, sandbox environments, and onboarding flows. Observability and monitoring for integration systems. Grafana, Datadog, or equivalent tools applied to integration pipeline health, webhook delivery SLOs, and partner facing reliability metrics. Advanced degree (MBA, Computer Science, or related field) or equivalent practical experience. What Success Looks Like In the first 90 days: Deliver a clear scope alignment document distinguishing Integration Framework ownership (Audit Framework infrastructure, encryption, data import/export, MCP Server, webhooks) from adjacent team ownership. Establish baseline metrics for Solutions Exchange partner onboarding time, webhook delivery reliability, and integration framework adoption across domain teams. Demonstrate an AI native working rhythm: use agentic tools to drive your own onboarding, synthesize technical documentation, and produce your first roadmap artifacts. In FY27: Technical credibility earned. Engineers and architects bring you into hard conversations before decisions are made, not after. You've made defensible architectural tradeoff calls, navigated competing approaches with data, and earned a genuine seat at the table where integration platform direction gets set. Strategic clarity delivered. Senior leadership has a clear, shared view of the integration platform roadmap and the logic behind it. You've translated technical complexity into business outcomes and can defend prioritization decisions under scrutiny. Partner ecosystem momentum demonstrated. You've moved the partner experience measurably forward: activation is faster, self service motions are live, and the team can point to a funnel with improving conversion. Partners are building and shipping with less manual support from the team. The developer surface is more navigable, better documented, and held to a standard. A new partner can reach their first successful integration without escalating to engineering. You defined what good looks like and held the bar. The integration layer's relationship to agentic consumers is defined and documented, not deferred. You've had the hard interface contract conversations with adjacent teams and the requirements are written down and agreed on. High stakes decision made with data. You've taken a significant ambiguous strategic question, built the validation structure, gathered the evidence, and delivered a recommendation the organization can act on. The path forward is clear. Reliability owned, not monitored. SLOs are established, visible, and trending in the right direction. Partner reported integration incidents are down measurably. The team knows what it owns and is accountable for the numbers.