> Markdown version of [/jobs/ext/1920547-principal-technical-product-manager-ai-integration-organization](https://www.wearedevelopers.com/jobs/ext/1920547-principal-technical-product-manager-ai-integration-organization). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Principal Technical Product Manager - AI Integration Organization - **Company:** CoreLogic, Inc. - **Location:** Dallas, TX, United States - **Experience:** Experienced - **Salary:** $111,900.0 - $175,000.0 - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Application Integration Architecture, Audit Trail, Data Architecture, Programming Tools, Distributed Systems, Metadata Standards, OAuth, Software Product Management, Swagger, Data Streaming, Openapi, Data Logging, Large Language Models, Apigee, AI Platforms, Machine Learning Operations, Virtual Agents, Api Gateway - **Published:** August 4, 2026 - **Apply:** https://www.careerbuilder.com/job-details/principal-technical-product-manager-ai-integration-dallas-tx--99256cee-98ee-405b-a0fc-c0200e84dd74 ## About the Role Required * 8+ years in technical product management or architecture, with at least 3 years owning API platforms, developer tools, data products, or integration infrastructure * Engineering background - you've written code professionally and carry an intuitive understanding of what makes a great developer experience from the consumer side, not just the provider side * Demonstrated experience shipping developer-facing or machine-consumable products with measurable adoption metrics * Strong understanding of API gateway patterns, OAuth/authentication flows, and how distributed systems communicate * Working knowledge of how large language models consume tools - function calling, tool descriptions, context windows, and the failure modes that arise when AI agents interact with external data sources * Experience defining data products for external consumption - what to expose, what to withhold, how to structure responses for different consumer types, and how to manage data quality and trust * Track record of driving delivery through cross-functional teams without direct reporting authority - influencing engineering, product, and business stakeholders to execute against a shared roadmap * Exceptional written communication - you will write tool descriptions that AI agents read, developer documentation that humans read, strategy documents that leadership reads, and contract language that legal reviews * Comfort with ambiguity and speed - this is a new category with no playbook, requiring decisions with incomplete information, shipping MVPs, and iterating rapidly Preferred * Experience with specific API gateway technologies (Apigee, Kong, AWS API Gateway, or equivalent) * Hands-on experience with developer documentation and portal platforms - Mintlify, Swagger/OpenAPI, Redoc, ReadMe, or similar - and a strong opinion on what makes API documentation actually usable * Familiarity with the Model Context Protocol (MCP) or equivalent agent-tool interface standards * Experience in insurance, financial services, or regulated data industries * Understanding of data provenance, audit requirements, and compliance considerations in regulated environments * Experience with pricing and packaging of API/data products (per-query, tiered access, usage-based models) * Background in or exposure to AI/ML workflows, particularly how enterprises are deploying AI agents in production ## Description The Principal Technical Product Manager for AI Integration owns the strategy and delivery of Cotality Insurance's external-facing AI integration layer. This includes the MCP server ecosystem, AI/API gateway, developer experience, and the platform that enables AI agents from clients and third-party partners to discover, authenticate, and consume Cotality's insurance data products autonomously. This is a technical product leadership role with a player-coach model. You set the product direction, make architecture tradeoff decisions alongside Architecture, and drive execution through a dedicated engineering team and cross-functional application team partners who own the underlying product APIs. Core Responsibilities MCP Platform Strategy & Roadmap. Define which Cotality data products get exposed as MCP tools, in what order, and with what capabilities. Align the connector roadmap with business priorities across Claims, Underwriting, Catastrophe Risk, and Contractor Solutions. Own the sequencing decisions - what ships this quarter, what's next, and why. Target cadence: one new MCP connector live per month. Tool Schema & Data Product Definition. Partner with product teams and the Data Architect to define what data gets exposed through each MCP tool - the fields, the boundaries, the descriptions that AI agents read to decide when and how to use a tool. This is the highest-leverage work in the role. The quality of tool schemas directly determines whether an AI agent can use Cotality's data effectively or makes errors that damage client trust. Architecture & Technical Direction. Work with the Architect and engineering team to define gateway configurations, authentication flows, and the aggregation layer. Make tradeoff decisions - when to optimize for speed vs. extensibility, when to wrap an existing API vs. build a composite tool, when to ship and iterate vs. get it right the first time. You don't write the code, but you understand the architecture deeply enough to lead technical decisions. Developer Experience. Own the end-to-end experience for external developers and AI platforms integrating with Cotality's MCP endpoints. This includes the developer portal, API documentation, sandbox environments, authentication guides, SDK examples, and onboarding workflows. You understand what good developer experience feels like because you've been the developer - you've integrated against third-party APIs, read bad documentation, and know the difference between a portal that accelerates adoption and one that generates support tickets. Target: a developer or AI agent goes from zero to working Cotality data in under 60 minutes. Data Provenance & Trust. Own the strategy for ensuring data delivered through MCP tools is verifiable, auditable, and resistant to misattribution or hallucination by consuming AI agents. Define response metadata standards, logging requirements, and the guardrails that protect Cotality's brand when data flows through systems Cotality doesn't control. This includes near-term controls (response signing, audit logs, server instructions) and the longer-term innovation roadmap for data provenance. Go-to-Market Coordination. Work with product marketing, sales engineering, and business development to position the MCP platform for carrier clients and AI platform partners. Support demos, pilot programs, and partner integrations. Cross-Functional Execution. Drive delivery through a dedicated MCP engineering team (MCP Architect, MCP Engineers, Data Architect) and application team partners who own the underlying product APIs. You define what needs to be built, set priorities, and shape tool designs. Application teams contribute significant implementation effort, particularly around exposing their product APIs as MCP-ready services. Keeping multiple workstreams aligned and moving toward shared delivery timelines is a core part of the role. ## Related Videos - [Building Products in the era of GenAI](https://www.wearedevelopers.com/videos/827-building-products-in-the-era-of-genai) - [For the REST of us: API First and Conway’s Law](https://www.wearedevelopers.com/videos/1932-for-the-rest-of-us-api-first-and-conway-s-law) - [Keeping applications secure by evolving OAuth 2.0 and OpenID Connect](https://www.wearedevelopers.com/videos/100152-keeping-applications-secure-by-evolving-oauth-2-0-and-openid-connect) - [Headless by Design: Building Enterprise Systems That Agents Can Actually Use](https://www.wearedevelopers.com/videos/100092-headless-by-design-building-enterprise-systems-that-agents-can-actually-use) - [Contract-First Frontend: Scaling Reliable UIs with OpenAPI and AI](https://www.wearedevelopers.com/videos/1995-contract-first-frontend-scaling-reliable-uis-with-openapi-and-ai) - [Delay the AI Overlords: How OAuth and OpenFGA Can Keep Your AI Agents from Going Rogue](https://www.wearedevelopers.com/videos/1637-delay-the-ai-overlords-how-oauth-and-openfga-can-keep-your-ai-agents-from-going-rogue) ## Related Articles - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [From Prototype to Production: Build AI Agents with This Free 4-Course Learning Path](https://www.wearedevelopers.com/magazine/655-from-prototype-to-production-build-ai-agents-with-this-free-4-course-learning-path) - [Graph and AI Trends 2026: Why Is AI Running but Not Yet Delivering?](https://www.wearedevelopers.com/magazine/680-graph-and-ai-trends-2026-why-is-ai-running-but-not-yet-delivering) - [Everything a Developer Needs to Know About MCP with Neo4j](https://www.wearedevelopers.com/magazine/604-everything-a-developer-needs-to-know-about-mcp-with-neo4j) - [MLOps – What’s the deal behind it?](https://www.wearedevelopers.com/magazine/125-mlops-what-s-the-deal-behind-it) - [What is Agentic Programming and Why Should Developers Care?](https://www.wearedevelopers.com/magazine/625-what-is-agentic-programming-and-why-should-developers-care)