Senior Product Marketing Manager, Fund Administration
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to decide which sections to include based on content.
We have:
- About Juniper Square (company description). Could be "About the role"? Actually "About Juniper Square" is company description, not role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map content accordingly.
We have sections:
- About Juniper Square (company overview). Could be placed under "About the role"? Not exactly. But we could treat as "About the role" maybe includes role description? However there is also "About Your Role" later. The instruction says do NOT repeat the job title as a heading. So we can have headings like "About the role" (maybe summarizing role). But we have "About Your Role" which is a heading in the posting. We could keep that as a heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Probably we should map content to those standard headings.
Thus we can have:
- About the role
containing the "About Juniper Square" and "About Your Role" combined? Or maybe we split: "About Juniper Square" as a paragraph under About the role? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can have a heading "About the role" and then include description of role and company.
But we also have "What You'll Do" which is responsibilities. So we can have Responsibilities
with list items.
We have "Qualifications" heading already. So we can have Qualifications
with list.
We have "Compensation" with base salary ranges. That's Pay. So we can have Pay
with paragraph describing salary ranges.
We have "Benefits Include ..." list. So we can have Benefits
with list.
We have "Your recruiter can provide additional details about compensation and benefits." That's minor metadata; we can fold into a short
maybe under Benefits or Pay.
We have also "Juniper Square offers employees a variety of ways to work..." That's about work arrangement; could be under Schedule? Not exactly schedule but maybe remote/hybrid. The instruction says only create Schedule section if posting actually states them. It does mention remote/flexible work, offices locations. That could be considered Schedule? Might be better to include under Benefits? But we can create a Schedule section if we have specifics: "Juniper Square offers employees a variety of ways to work, ranging from a fully remote experience to working full-time in one of our physical offices. We invest heavily in digital-first operations, allowing our teams to collaborate effectively across 27 U.S. states, 2 Canadian Provinces, India, Luxembourg, and England. We also have physical offices in San Francisco, New York City, Mumbai and Bangalore for employees who prefer to work in an office some or all of the time." That's about work location/arrangement, not schedule (hours). Could be considered Schedule? The instruction says only create Schedule section if posting actually states them. It does state ways to work, but not schedule like hours. Might be better to incorporate into Benefits or a separate section like "Work Arrangement". But we are limited to given headings; we could put under Benefits? Not ideal. Perhaps we can create a Schedule section with that content, as it's about work arrangement (though not strictly schedule). The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state ways to work, which could be considered schedule? I'd lean to include a Schedule section with that content.
We also have "About Juniper Square" which is company overview; could be under About the role or maybe we could have a separate section like "About the company". But not in list. Could fold into About the role paragraph.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can reformat.
Let's extract substantive content:
Company description:
"About Juniper Square Private markets are one of the largest, most complex, and most underserved corners of global finance. Our mission at Juniper Square is to unlock their full potential. We’re the Operations Partner trusted by 2,300+ GPs, unifying technology, data, and fund administration services into a single platform that helps GPs move faster, make better decisions, and scale with precision. With $300B+ under administration and 700,000+ LPs on platform, we’ve built the scale to match our ambition. And with JunieAI, our purpose-built AI platform, we’re reimagining how private markets operate, embedding intelligence across every workflow. Founder-led since 2014, backed by $350M+ in funding, and now 1,000+ employees strong, we’re building a company designed to shape the future of private markets for decades to come. Our culture is built for people who want to do ambitious, meaningful work alongside exceptionally talented teammates. We think like owners, move with urgency, and take pride in solving hard problems that truly matter to our customers and the future of private markets. We believe the best ideas come from open debate, deep collaboration, and diverse perspectives, which is why we believe transparency is the default and feedback makes us stronger. If you’re energized by high standards, rapid growth, and the opportunity to help define a category at a pivotal moment, come join us!"
Then "Juniper Square offers employees a variety of ways to work, ranging from a fully remote experience to working full-time in one of our physical offices. We invest heavily in digital-first operations, allowing our teams to collaborate effectively across 27 U.S. states, 2 Canadian Provinces, India, Luxembourg, and England. We also have physical offices in San Francisco, New York City, Mumbai and Bangalore for employees who prefer to work in an office some or all of the time."
Then "About Your Role Fund administration is one of the most important and fastest-growing areas of the Juniper Square business, and how we win there depends on product marketing expertise that sits shoulder-to-shoulder with Sales. We're seeking a Senior Product Marketing Manager, Fund Administration to own GTM strategy, as well as the messaging, positioning, and enablement that move fund administration deals forward. What sets this role apart: fund administration is a service, so understanding the offering means understanding the people who deliver it. You'll know our fund administration leaders and experts cold, including where each one is strongest, and you'll know our reference clients and how they differ across size, asset class, and profile. Keeping that picture current as the team scales fast is one of the most important parts of the job. This role reports to the Head of Product Marketing and partners closely with Sales leadership and Pipeline."
Then "What You'll Do" with bullet points (actually paragraphs). Let's extract each bullet:
- Fund Administration strategy, positioning & messaging
- Own Juniper Square's go-to-market strategy, positioning and messaging for the fund administration business unit, articulating a differentiated value proposition for each stakeholder in the buying group; CFOs, fund controllers, Heads of Finance and Fund Operations, leaders across investor services, accounting, treasury, compliance, and loan operations, and technical evaluators.
- Position Juniper Square's fund administration service so buyers understand not just what it delivers but how it changes the way their teams work, and prepare Sales and Customer Success to have credible, informed conversations about it.
- Build the fund administration persona and industry playbooks: buyer and influencer roles, priorities, objections, and content needs at every stage of the sales journey.
- Fund administration expertise & references
- Build and maintain a living map of Juniper Square's fund administration leaders and experts: who presents well, where each one is strongest, and who to bring into a given deal or moment.
- Keep that picture current through constant data-gathering as the fund administration team grows fast, so sales always knows who to pull in and when.
- Maintain deep knowledge of our fund administration reference clients and how they vary by customer size, asset class, and profile, so sellers can match the right proof to the right prospect.
- Fund administration launches
- Own every fund administration product and feature launch end to end with repeatable frameworks that scale from major product announcements to quarterly release moments.
- Define what launch readiness looks like and drive the cross-functional plan that gets there, so each release lands with Sales, Customer Success, and the market ready.
- Close the loop after launch, feeding adoption signal and customer feedback back to Product to shape what ships next.
- Sales enablement & deal support
- Work directly with Sales leadership and top sellers to co-create the collateral that wins fund administration deals: executive briefs, ROI narratives, competitive battlecards, demo narratives, and stakeholder-specific decks for each stage of the buying process.
- Drive pipeline, upsell, and cross-sell velocity across the GP experience and fund administration suite, maintaining a cohesive release narrative that keeps prospects and customers engaged across the lifecycle.
- Act as the internal expert on fund administration deal dynamics, playing an active role in shaping messaging and strategy on high-stakes opportunities.
- Voice of customer & competitive intelligence
- Conduct deep voice-of-customer research through customer interviews, win/loss analysis, and Sales feedback to continuously enrich our understanding of fund administration personas and use cases across investor services, accounting, treasury, compliance, and loan operations.
- Create the fund administration customer stories that validate our messaging with real-world proof.
- Own competitive intelligence for the fund administration segment and disseminate actionable insights to Sales, Growth Marketing, and Product so the whole go-to-market motion stays aligned around how these teams actually buy.
- Build AI-native
- Use AI agents and tooling as core infrastructure to research accounts, synthesize customer and competitive inputs, which measurably accelerates the production of messaging and enablement assets.
- Apply judgment to what AI produces: know where automation accelerates the work and where human judgment is critical.
Then "Qualifications" bullet list:
- 3+ years of experience in or adjacent to fund administration is required (at a fund administrator, on a fund CFO, controller, or finance operations team, or at a company selling fund administration technology or services); you understand how these teams operate, who the buyers are, and what they care about.
- Experience in B2B product marketing or GTM strategy roles is advantageous but not required, with a strong bias toward supporting Sales and influencing deal outcomes.
- AI Fluency: experience using LLMs, agents, and AI automation tools to measurably accelerate your work, and understanding where human judgment
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. We have: - About Juniper Square (company description). Could be "About the role"? Actually "About Juniper Square" is company description, not role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map content accordingly. We have sections: - About Juniper Square (company overview). Could be placed under "About the role"? Not exactly. But we could treat as "About the role" maybe includes role description? However there is also "About Your Role" later. The instruction says do NOT repeat the job title as a heading. So we can have headings like "About the role" (maybe summarizing role). But we have "About Your Role" which is a heading in the posting. We could keep that as a heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Probably we should map content to those standard headings.
Thus we can have:
- About the role
containing the "About Juniper Square" and "About Your Role" combined? Or maybe we split: "About Juniper Square" as a paragraph under About the role? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can have a heading "About the role" and then include description of role and company.
But we also have "What You'll Do" which is responsibilities. So we can have Responsibilities
with list items.
We have "Qualifications" heading already. So we can have Qualifications
with list.
We have "Compensation" with base salary ranges. That's Pay. So we can have Pay
with paragraph describing salary ranges.
We have "Benefits Include ..." list. So we can have Benefits
with list.
We have "Your recruiter can provide additional details about compensation and benefits." That's minor metadata; we can fold into a short
maybe under Benefits or Pay. We have also "Juniper Square offers employees a variety of ways to work..." That's about work arrangement; could be under Schedule? Not exactly schedule but maybe remote/hybrid. The instruction says only create Schedule section if posting actually states them. It does mention remote/flexible work, offices locations. That could be considered Schedule? Might be better to include under Benefits? But we can create a Schedule section if we have specifics: "Juniper Square offers employees a variety of ways to work, ranging from a fully remote experience to working full-time in one of our physical offices. We invest heavily in digital-first operations, allowing our teams to collaborate effectively across 27 U.S. states, 2 Canadian Provinces, India, Luxembourg, and England. We also have physical offices in San Francisco, New York City, Mumbai and Bangalore for employees who prefer to work in an office some or all of the time." That's about work location/arrangement, not schedule (hours). Could be considered Schedule? The instruction says only create Schedule section if posting actually states them. It does state ways to work, but not schedule like hours. Might be better to incorporate into Benefits or a separate section like "Work Arrangement". But we are limited to given headings; we could put under Benefits? Not ideal. Perhaps we can create a Schedule section with that content, as it's about work arrangement (though not strictly schedule). The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state ways to work, which could be considered schedule? I'd lean to include a Schedule section with that content. We also have "About Juniper Square" which is company overview; could be under About the role or maybe we could have a separate section like "About the company". But not in list. Could fold into About the role paragraph. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can reformat. Let's extract substantive content: Company description: "About Juniper Square Private markets are one of the largest, most complex, and most underserved corners of global finance. Our mission at Juniper Square is to unlock their full potential. We’re the Operations Partner trusted by 2,300+ GPs, unifying technology, data, and fund administration services into a single platform that helps GPs move faster, make better decisions, and scale with precision. With $300B+ under administration and 700,000+ LPs on platform, we’ve built the scale to match our ambition. And with JunieAI, our purpose-built AI platform, we’re reimagining how private markets operate, embedding intelligence across every workflow. Founder-led since 2014, backed by $350M+ in funding, and now 1,000+ employees strong, we’re building a company designed to shape the future of private markets for decades to come. Our culture is built for people who want to do ambitious, meaningful work alongside exceptionally talented teammates. We think like owners, move with urgency, and take pride in solving hard problems that truly matter to our customers and the future of private markets. We believe the best ideas come from open debate, deep collaboration, and diverse perspectives, which is why we believe transparency is the default and feedback makes us stronger. If you’re energized by high standards, rapid growth, and the opportunity to help define a category at a pivotal moment, come join us!" Then "Juniper Square offers employees a variety of ways to work, ranging from a fully remote experience to working full-time in one of our physical offices. We invest heavily in digital-first operations, allowing our teams to collaborate effectively across 27 U.S. states, 2 Canadian Provinces, India, Luxembourg, and England. We also have physical offices in San Francisco, New York City, Mumbai and Bangalore for employees who prefer to work in an office some or all of the time." Then "About Your Role Fund administration is one of the most important and fastest-growing areas of the Juniper Square business, and how we win there depends on product marketing expertise that sits shoulder-to-shoulder with Sales. We're seeking a Senior Product Marketing Manager, Fund Administration to own GTM strategy, as well as the messaging, positioning, and enablement that move fund administration deals forward. What sets this role apart: fund administration is a service, so understanding the offering means understanding the people who deliver it. You'll know our fund administration leaders and experts cold, including where each one is strongest, and you'll know our reference clients and how they differ across size, asset class, and profile. Keeping that picture current as the team scales fast is one of the most important parts of the job. This role reports to the Head of Product Marketing and partners closely with Sales leadership and Pipeline." Then "What You'll Do" with bullet points (actually paragraphs). Let's extract each bullet: - Fund Administration strategy, positioning & messaging - Own Juniper Square's go-to-market strategy, positioning and messaging for the fund administration business unit, articulating a differentiated value proposition for each stakeholder in the buying group; CFOs, fund controllers, Heads of Finance and Fund Operations, leaders across investor services, accounting, treasury, compliance, and loan operations, and technical evaluators. - Position Juniper Square's fund administration service so buyers understand not just what it delivers but how it changes the way their teams work, and prepare Sales and Customer Success to have credible, informed conversations about it. - Build the fund administration persona and industry playbooks: buyer and influencer roles, priorities, objections, and content needs at every stage of the sales journey. - Fund administration expertise & references - Build and maintain a living map of Juniper Square's fund administration leaders and experts: who presents well, where each one is strongest, and who to bring into a given deal or moment. - Keep that picture current through constant data-gathering as the fund administration team grows fast, so sales always knows who to pull in and when. - Maintain deep knowledge of our fund administration reference clients and how they vary by customer size, asset class, and profile, so sellers can match the right proof to the right prospect. - Fund administration launches - Own every fund administration product and feature launch end to end with repeatable frameworks that scale from major product announcements to quarterly release moments. - Define what launch readiness looks like and drive the cross-functional plan that gets there, so each release lands with Sales, Customer Success, and the market ready. - Close the loop after launch, feeding adoption signal and customer feedback back to Product to shape what ships next. - Sales enablement & deal support - Work directly with Sales leadership and top sellers to co-create the collateral that wins fund administration deals: executive briefs, ROI narratives, competitive battlecards, demo narratives, and stakeholder-specific decks for each stage of the buying process. - Drive pipeline, upsell, and cross-sell velocity across the GP experience and fund administration suite, maintaining a cohesive release narrative that keeps prospects and customers engaged across the lifecycle. - Act as the internal expert on fund administration deal dynamics, playing an active role in shaping messaging and strategy on high-stakes opportunities. - Voice of customer & competitive intelligence - Conduct deep voice-of-customer research through customer interviews, win/loss analysis, and Sales feedback to continuously enrich our understanding of fund administration personas and use cases across investor services, accounting, treasury, compliance, and loan operations. - Create the fund administration customer stories that validate our messaging with real-world proof. - Own competitive intelligence for the fund administration segment and disseminate actionable insights to Sales, Growth Marketing, and Product so the whole go-to-market motion stays aligned around how these teams actually buy. - Build AI-native - Use AI agents and tooling as core infrastructure to research accounts, synthesize customer and competitive inputs, which measurably accelerates the production of messaging and enablement assets. - Apply judgment to what AI produces: know where automation accelerates the work and where human judgment is critical. Then "Qualifications" bullet list: - 3+ years of experience in or adjacent to fund administration is required (at a fund administrator, on a fund CFO, controller, or finance operations team, or at a company selling fund administration technology or services); you understand how these teams operate, who the buyers are, and what they care about. - Experience in B2B product marketing or GTM strategy roles is advantageous but not required, with a strong bias toward supporting Sales and influencing deal outcomes. - AI Fluency: experience using LLMs, agents, and AI automation tools to measurably accelerate your work, and understanding where human judgment