Principal Product Manager - Customer Zero
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information; not invent or summarize away detail. So we need to keep the details: responsibilities list items, skills list, education/experience list, benefits list, pay range.
We need to avoid creating placeholder text like "commensurate with experience". Not present.
Now let's extract content.
First, About the role: combine the introductory paragraphs up to "Celigo is looking for a Principal Product Manager - Customer Zero to own the highest-leverage program..." plus maybe the mission description. Let's capture:
"Integration meets InnovationAt Celigo, we believe integration should empower — not exhaust — innovation. As a modern Integration and Automation Platform (iPaaS), we’re on a mission to simplify how companies integrate, automate, and optimize processes. Powered by game-changing technology like runtime AI and prebuilt, mission-critical integrations, Celigo is redefining how businesses connect their world.Celigo is looking for a Principal Product Manager - Customer Zero to own the highest-leverage program in the company: running Celigo on Celigo. When GTO operates on our own platform across GTM, CX, and G&A systems, we become our own best customer. We discover what's hard before customers find it, feed it directly into Product, and give Sales a credible, live reference in every deal. This role is the dedicated owner of that program, end-to-end."
We need to ensure spacing; but we can just put as paragraph.
Now Responsibilities: the "What would you do if hired?" section includes multiple paragraphs each starting with a bolded phrase? Actually the text:
"What would you do if hired?Own the Customer Zero program as a funded initiative with a real roadmap, clear outcomes, and an operating rhythm that holds across competing priorities. You set the pace, define what done looks like, and keep the work alive without needing someone to push it. You measure yourself by business value delivered, not by meetings held.Drive adoption of Celigo's own products (agents, MCP, Ora/CLI, integrations) inside GTO's GTM, CX, and G&A systems. When you run into friction, you dig into it before being asked. Surface what's genuinely hard, prioritize it, and shepherd it into Product's roadmap in partnership with the CPO's org.Use Celigo's AI-powered platform as part of how you work every day. You will be one of the first people inside the company to push on new agentic capabilities, give Product honest feedback on where they deliver and where they fall short, and help define what "AI-first" actually looks like inside an enterprise workflow. Your daily use is part of the feedback loop.Bring product discipline to every workstream: defined requirements, clear success criteria, and prioritization grounded in adoption and business value. Committed dates should hold because you've done the thinking up front, shipping the smallest version that delivers real value and iterating from there rather than waiting for a perfect build.Operate in both hats simultaneously: design the underlying business processes and own the solution as a product manager. You're the person who figures out how the process should work and the person accountable for whether what ships delivers an outstanding experience.Weigh user needs against security, privacy, and governance considerations (RBAC, permissions, service accounts), making trade-offs deliberately rather than after the fact. Build the prescriptive playbook Product and Sales need: governance patterns, reference architectures, and proof points that hold up in enterprise conversations.Be the external face of how Celigo runs on Celigo. Present at flagship events, join key customer and prospect conversations, and package our internal use into references Sales can put in front of prospects and existing customers. Enable Product Marketing and Sales to scale the story beyond you."
We need to turn each sentence into list items? The instruction: Use
- for any list of duties/requirements/benefits. So we should treat each distinct duty as a list item. Could split by the sentences after each bolded phrase? But we can just make each sentence a list item. However we need to preserve all substantive information; we can keep the sentences as list items.
Better to group: each paragraph after the bold heading is a duty. Let's split by the periods that start a new capitalized phrase after a period? Might be messy. Simpler: make each sentence a list item. That will preserve all info.
Now Requirements: Education & Experience section:
"Education & Experience 8+ years in product management, comfortable operating hands-on as a Principal individual contributor while owning a program end-to-end.Deep functional experience in GTM and/or CX operations and the systems that run them (Salesforce, HubSpot, Gainsight, or similar), sufficient to design the processes, not just manage the backlog.Track record of running an internal-as-first-customer, dogfooding, or Customer Zero program, or standing up a Product function where one didn't exist.Experience building and packaging reference stories or proof points that Sales and Marketing can use externally.Preferred: background with SaaS, iPaaS, integration, or automation platforms, and comfort with AI-first or agentic products.Preferred: hands-on experience using the product you support internally.Preferred: close partnership with a CPO or Product org to influence a public roadmap."
We need to split into list items. Each sentence separated by period. We'll make each as
- .
Now Skills: Skills & Abilities section:
"Skills & AbilitiesYou're energized by building something that doesn't fully exist yet. You ask the questions others skip past, including the uncomfortable ones about what's actually broken, and you treat ambiguity as the job, not an obstacle to it.You connect your work to the bigger picture. You understand why Customer Zero matters to the company, and you make decisions that serve that outcome, including the trade-offs nobody told you to make. You ask "why" before "how."You ship the smallest version that delivers real value and iterate on real feedback. A 10-slide internal use case that lands in one deal is better than a perfect playbook no one has read. You recover quickly when something doesn't land, without drama.You treat the program's problems as your own. You move on things before being asked, you measure yourself by outcomes rather than activity, and you find the faster path and take it.You drive results through influence, not authority. You create alignment with engineering teams, Sales, and the CPO's org by understanding what each team needs and making it easy for them to say yes.You're comfortable applying AI to your own work: drafting, research, analysis, and wherever else it frees you for the judgment calls that matter. Genuine curiosity about what AI can and cannot do is part of what makes someone thrive here, especially in a role that's also responsible for making AI credible to customers.You translate clearly between business stakeholders (GTM, CX, G&A) and technical teams. You know enough about the systems to design processes, not just manage a backlog.You're credible on stage and in a boardroom. Executive presence is real for this role: you will represent Celigo externally and need customers and prospects to trust what you say.You use data (adoption, usage, outcomes) to prioritize, to influence colleagues and executives, and to know early when something isn't working."
Again split into list items.
Now Benefits: The paragraph after "Here you'll experienceRemote-first culture, built on trust, collaboration, and transparencyA high-growth, inclusive work environment where innovation thrives and ideas are implementedLightspeed learning opportunities to keep you at the leading edge of your fieldExceptional coworkers who challenge and inspire you dailyCompetitive compensation and benefits, including:Three weeks of vacation (starting year one)Wellness days and holidays to rechargeParental leave and a generous benefits packageMonthly tech stipendRecognition and career development
for prose. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep the details: responsibilities list items, skills list, education/experience list, benefits list, pay range. We need to avoid creating placeholder text like "commensurate with experience". Not present. Now let's extract content. First, About the role: combine the introductory paragraphs up to "Celigo is looking for a Principal Product Manager - Customer Zero to own the highest-leverage program..." plus maybe the mission description. Let's capture: "Integration meets InnovationAt Celigo, we believe integration should empower — not exhaust — innovation. As a modern Integration and Automation Platform (iPaaS), we’re on a mission to simplify how companies integrate, automate, and optimize processes. Powered by game-changing technology like runtime AI and prebuilt, mission-critical integrations, Celigo is redefining how businesses connect their world.Celigo is looking for a Principal Product Manager - Customer Zero to own the highest-leverage program in the company: running Celigo on Celigo. When GTO operates on our own platform across GTM, CX, and G&A systems, we become our own best customer. We discover what's hard before customers find it, feed it directly into Product, and give Sales a credible, live reference in every deal. This role is the dedicated owner of that program, end-to-end." We need to ensure spacing; but we can just put as paragraph. Now Responsibilities: the "What would you do if hired?" section includes multiple paragraphs each starting with a bolded phrase? Actually the text: "What would you do if hired?Own the Customer Zero program as a funded initiative with a real roadmap, clear outcomes, and an operating rhythm that holds across competing priorities. You set the pace, define what done looks like, and keep the work alive without needing someone to push it. You measure yourself by business value delivered, not by meetings held.Drive adoption of Celigo's own products (agents, MCP, Ora/CLI, integrations) inside GTO's GTM, CX, and G&A systems. When you run into friction, you dig into it before being asked. Surface what's genuinely hard, prioritize it, and shepherd it into Product's roadmap in partnership with the CPO's org.Use Celigo's AI-powered platform as part of how you work every day. You will be one of the first people inside the company to push on new agentic capabilities, give Product honest feedback on where they deliver and where they fall short, and help define what "AI-first" actually looks like inside an enterprise workflow. Your daily use is part of the feedback loop.Bring product discipline to every workstream: defined requirements, clear success criteria, and prioritization grounded in adoption and business value. Committed dates should hold because you've done the thinking up front, shipping the smallest version that delivers real value and iterating from there rather than waiting for a perfect build.Operate in both hats simultaneously: design the underlying business processes and own the solution as a product manager. You're the person who figures out how the process should work and the person accountable for whether what ships delivers an outstanding experience.Weigh user needs against security, privacy, and governance considerations (RBAC, permissions, service accounts), making trade-offs deliberately rather than after the fact. Build the prescriptive playbook Product and Sales need: governance patterns, reference architectures, and proof points that hold up in enterprise conversations.Be the external face of how Celigo runs on Celigo. Present at flagship events, join key customer and prospect conversations, and package our internal use into references Sales can put in front of prospects and existing customers. Enable Product Marketing and Sales to scale the story beyond you." We need to turn each sentence into list items? The instruction: Use
- for any list of duties/requirements/benefits. So we should treat each distinct duty as a list item. Could split by the sentences after each bolded phrase? But we can just make each sentence a list item. However we need to preserve all substantive information; we can keep the sentences as list items. Better to group: each paragraph after the bold heading is a duty. Let's split by the periods that start a new capitalized phrase after a period? Might be messy. Simpler: make each sentence a list item. That will preserve all info. Now Requirements: Education & Experience section: "Education & Experience 8+ years in product management, comfortable operating hands-on as a Principal individual contributor while owning a program end-to-end.Deep functional experience in GTM and/or CX operations and the systems that run them (Salesforce, HubSpot, Gainsight, or similar), sufficient to design the processes, not just manage the backlog.Track record of running an internal-as-first-customer, dogfooding, or Customer Zero program, or standing up a Product function where one didn't exist.Experience building and packaging reference stories or proof points that Sales and Marketing can use externally.Preferred: background with SaaS, iPaaS, integration, or automation platforms, and comfort with AI-first or agentic products.Preferred: hands-on experience using the product you support internally.Preferred: close partnership with a CPO or Product org to influence a public roadmap." We need to split into list items. Each sentence separated by period. We'll make each as
- . Now Skills: Skills & Abilities section: "Skills & AbilitiesYou're energized by building something that doesn't fully exist yet. You ask the questions others skip past, including the uncomfortable ones about what's actually broken, and you treat ambiguity as the job, not an obstacle to it.You connect your work to the bigger picture. You understand why Customer Zero matters to the company, and you make decisions that serve that outcome, including the trade-offs nobody told you to make. You ask "why" before "how."You ship the smallest version that delivers real value and iterate on real feedback. A 10-slide internal use case that lands in one deal is better than a perfect playbook no one has read. You recover quickly when something doesn't land, without drama.You treat the program's problems as your own. You move on things before being asked, you measure yourself by outcomes rather than activity, and you find the faster path and take it.You drive results through influence, not authority. You create alignment with engineering teams, Sales, and the CPO's org by understanding what each team needs and making it easy for them to say yes.You're comfortable applying AI to your own work: drafting, research, analysis, and wherever else it frees you for the judgment calls that matter. Genuine curiosity about what AI can and cannot do is part of what makes someone thrive here, especially in a role that's also responsible for making AI credible to customers.You translate clearly between business stakeholders (GTM, CX, G&A) and technical teams. You know enough about the systems to design processes, not just manage a backlog.You're credible on stage and in a boardroom. Executive presence is real for this role: you will represent Celigo externally and need customers and prospects to trust what you say.You use data (adoption, usage, outcomes) to prioritize, to influence colleagues and executives, and to know early when something isn't working." Again split into list items. Now Benefits: The paragraph after "Here you'll experienceRemote-first culture, built on trust, collaboration, and transparencyA high-growth, inclusive work environment where innovation thrives and ideas are implementedLightspeed learning opportunities to keep you at the leading edge of your fieldExceptional coworkers who challenge and inspire you dailyCompetitive compensation and benefits, including:Three weeks of vacation (starting year one)Wellness days and holidays to rechargeParental leave and a generous benefits packageMonthly tech stipendRecognition and career development