Staff Product Manager, Integrations
- .
Requirements: "What You’ll Bring" bullet list (10+ years PM experience etc). Also "How You’ll Grow" sections maybe not requirements but could be considered growth expectations; but we can treat them as part of Requirements? Probably not; they are growth expectations, but we can include as part of Requirements or maybe as separate? The instruction: include a section only when posting has real specific content for it. We have content for Responsibilities, Requirements (experience), Qualifications (maybe same as Requirements?), Skills (maybe technical fluency). Benefits: there is a Benefits Program section with details. Pay: salary ranges given. Schedule: remote work info maybe schedule? There's mention of remote workforce, flexible PTO, work from home support. Not explicit schedule like full-time, but we could infer schedule is full-time? Not given explicitly. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated. Pay is stated (salary ranges). Schedule: not explicitly stated; there is mention of remote work, flexible PTO, but not schedule like "Full-time" or "Hybrid". Might be considered not specific enough. Safer to omit Schedule section.
We also need to avoid boilerplate like EEO, legal, etc. Remove those.
We need to preserve all substantive info; not invent or summarize away detail. Must not omit details like specific benefits numbers, etc.
We need to format: Use
for section headings. Use
- for any list of duties/requirements/benefits, and
for prose. We need to decide what goes into each section. About the role: could include the initial description and maybe the "Why join Sprout’s Product team?" paragraph (mission). That's prose. Responsibilities: list from "What You’ll Do". We'll extract each sentence as a bullet. Requirements: maybe include "What You’ll Bring" bullet list (experience). Also maybe "How You’ll Grow" could be considered growth expectations but not requirements. We'll keep Requirements as the bullet list of experience and skills. Qualifications: maybe we could separate technical fluency etc. But we have overlapping. Could treat Qualifications as the technical fluency and commercial judgment mentioned earlier. However we already have that in About the role. Might be redundant. Safer to have Requirements include experience, and Qualifications include technical fluency and commercial judgment? But we need to avoid duplication? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep all info; duplication is okay if it's in the original? But we should not repeat same info unnecessarily? It didn't forbid duplication, but better to organize logically. We could have: - About the role: description of role and mission. - Responsibilities: bullet list of duties. - Requirements: bullet list of experience (10+ years PM experience etc). - Qualifications: bullet list of technical fluency (APIs, managed packages, platform events, OAuth/permission models) and commercial judgment. - Skills: maybe bullet list of soft skills: cross-functional collaboration, over communication, etc. - Benefits: list of benefits. - Pay: salary ranges and geographic zones. We must not include Schedule. Now we need to ensure we don't include boilerplate like "This list is for informational purposes only." That's part of benefits but maybe we should keep? It's substantive? It's a disclaimer; maybe we should keep as it's part of benefits description. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits disclaimer "This list is for informational purposes only. Benefit offerings are discretionary and subject to change and do not constitute a contract or guarantee of benefits." Might be considered legal boilerplate. Might be removed? It's not exactly EEO but it's a disclaimer. Safer to keep? The instruction says remove legal boilerplate. This is a legal disclaimer about benefits. I'd remove it to be safe. However we need to preserve substantive benefit details; the disclaimer is not substantive. So we can omit that sentence. Also remove the EEO statement at the end. Also remove the "We share both our current hiring range..." etc? That's part of Pay; we keep. Also remove the "We have two geographic pay zones..." we keep as part of Pay. Also remove the "We also evaluate compensation bi-annually..." maybe keep as part of Pay? It's substantive about compensation philosophy. Could keep. But we need to avoid duplication. Now craft HTML. We'll start with
About the role
then...
. Combine the initial description and the "Why join Sprout’s Product team?" paragraph into one prose. Let's extract: Description: "Sprout Social is seeking an experienced Product Manager to own the strategy, delivery, and scaling of our partner and platform integration ecosystem. This role sits at the center of a critical shift for Sprout: moving from bespoke, one-off partner integrations toward a scalable, platform-based integration model that reduces engineering lift per partner while expanding the ecosystem of systems that connect to Sprout. This is an individual contributor role requiring deep technical fluency in integration architecture (APIs, managed packages, platform events, OAuth/permission models) paired with strong commercial judgment on what's worth building, for whom, and when." Why join Sprout’s Product team? paragraph: "Sprout empowers businesses worldwide to harness the immense power and opportunity of social media in today’s digital-first world. Processing over one billion social messages daily, our platform serves up essential insights and actionable information to over 30,000 brands, informing strategic decisions that drive business growth and innovation, and fostering deeper, authentic connections to their end customers. Our full suite of social media management solutions includes comprehensive publishing and engagement functionality, customer care solutions, influencer marketing, connected workflows, and business intelligence. This is an exciting opportunity for a leader to come in and have full ownership of our integrations strategy. Our Product team operates at the intersection of strategy, innovation, customer value, and go-to-market collaboration. We are focused on delivering unified, data-driven solutions across our multi-product portfolio. As part of the broader R&D organization, our team collaborates closely with Engineering, Product Design, and Go-to-Market (GTM) teams to create impactful experiences for customers while driving measurable business outcomes. This cross-functional partnership ensures that our products not only meet technical excellence but are also positioned effectively in the market, aligning with customer needs and business growth objectives. You won't just help set the vision for our integration platform, you'll also play a key role in shaping our overall approach to partner and platform strategy and own both strategy, execution, and outcomes." We'll combine. Now Responsibilities: list from "What You’ll Do". Let's extract each sentence: - Own individual integrations strategy end-to-end from pricing and packaging to distribution strategy to GA readiness, including ongoing relationship management with cross-functional teams - Partner closely with Engineering to sequence integration investments, balancing near-term customer/revenue commitments against longer-term platform scalability - Define and execute platform-based integration strategies (e.g., generalized APIs or connectors) that let customers self-integrate, reducing the need for bespoke builds per vendor - Serve as the key driver of integration lifecycle management, from alpha and beta through GA and post-launch scaling, aligning with strategic partners and key customers on roadmap, timeline, and requirements at each stage - Own permissioning, security, and licensing model decisions for packaged integrations (managed packages, namespace strategy, license management) - Build the business case and prioritization framework for new integration bets, including clear kill criteria and proof points before scaling investment - Act as connective tissue between GTM, Partnerships, and Engineering to ensure integration work is commercially viable, not just technically sound - Drive the execution of "best-in-class" product delivery, balancing the urgency of immediate customer needs with the long-term scalability and innovation of our core We'll put each as - . Now Requirements: from "What You’ll Bring" bullet list: - 10+ years of PM experience in ecosystem or integration roles in a B2B product-driven SaaS environment. - Proven success leading initiatives in a multi-product portfolio company. - Experience collaborating closely with product, design, engineering, and GTM leaders to deliver cohesive solutions. - Experience partnering with distributed engineering teams across different time zones - A default toward over communication: written specs, recorded walkthroughs, decision logs, and proactive status instead of waiting to be asked. We'll list. Now Qualifications: maybe technical fluency and commercial judgment from earlier: "deep technical fluency in integration architecture (APIs, managed packages, platform events, OAuth/permission models) paired with strong commercial judgment on what's worth building, for whom, and when." Also maybe "How You’ll Grow" sections? But those are growth expectations, not qualifications. We'll keep Qualifications as that technical fluency and commercial judgment. Now Skills: maybe soft skills: cross-functional collaboration, over communication, etc. But we already have over communication in Requirements. Could separate: Skills: ability to work cross-functionally, ability to partner with distributed teams, etc. But to avoid duplication, we could put cross-functional collaboration and partnering with distributed teams as Skills. However the instruction: preserve ALL substantive information; duplication is okay but we might want to avoid redundancy. I'd rather keep Requirements as experience, Qualifications as technical fluency/commercial judgment, Skills as cross-functional collaboration and over communication (maybe also ability to partner with distributed teams). But we already have over communication in Requirements; we could move it to Skills. Let's decide: Requirements: years of experience, proven success, experience collaborating, experience partnering with distributed teams. Skills: default toward over communication (written specs, etc). That seems reasonable. Now Benefits: list from Benefits Program. We'll extract each benefit item as
- . Need to keep details. Benefits list: - Comprehensive Health & Wellness: Premium BCBSIL medical, dental (high/low plans), and vision (Eyemed) insurance for you and your eligible dependents. - Premium Mental Health Support: Full, free access to Modern Health for you and your dependents, including coaching, therapy sessions, and digital wellness resources. - Retirement Savings: 401(k) plan with a 50% company match on your first 6% of contributions (a 3% total match). - Financial Security: 100% employer-paid Life and Disability insurance for your peace of mind. - Flexible Paid Time Off: A flexible PTO policy, supplemented with additional company-wide Rest & Recharge days throughout the year. - Paid Parental Leave: Up to 16 weeks of paid leave for new parents to support you in expanding your family. - Annual Lifestyle Stipend: A $1
- for any list of duties/requirements/benefits, and