Partnership Development Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we should map headings to these standard ones? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings if applicable. But we can also use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they want us to use those exact headings where appropriate. However the posting has sections like "About Balboa", "The Role", "What You'll Do", "First Six Months, Success Looks Like", "Required Experience", "Strong Plus", "What We're Looking For", "Where This Role Goes". We need to map them to the allowed headings. Possibly we can use "About the role" for "About Balboa"? But "About Balboa" is about company, not role. Could use "About the role" for "The Role". "Responsibilities" for "What You'll Do". "Requirements" for "Required Experience". "Qualifications" maybe for "Strong Plus"? Or "Skills". "Benefits" not present. "Pay" not present. "Schedule" not present. We should only include sections when posting has real specific content. So we will include sections for About the role, Responsibilities, Requirements, Qualifications, maybe Skills? The "Strong Plus" could be considered "Preferred Qualifications" or "Skills". We'll map to "Qualifications". Also "What We're Looking For" could be "Skills" or "Qualifications". Might combine.
We need to preserve all substantive information, not invent or summarize away detail. Use - for any list of duties/requirements/benefits, and
for prose.
We need to remove boilerplate etc. There's no explicit boilerplate besides maybe "We're hiring for hunger, polish, and judgment more than for a specific résumé." That's substantive.
We need to output only HTML fragment.
Let's extract content:
About Balboa: paragraph describing Balboa.
The Role: paragraph describing role.
What You'll Do: bullet list of duties.
First Six Months, Success Looks Like: bullet list of success metrics.
Required Experience: bullet list of experience requirements.
Strong Plus: bullet list of pluses.
What We're Looking For: bullet list of non-negotiable traits and hiring criteria.
Where This Role Goes: paragraph about career path.
We need to map to headings.
Let's decide:
About the role
-> combine "About Balboa" + "The Role"? Might be weird. Better to have separate sections: maybe "About the company" not allowed. But we could still use "About the role" for the role description, and maybe include company info in a under that heading? The instruction says use those headings as examples, not strictly limited. It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we could also use other headings? It says use for section headings (e.g. ...). Likely they expect us to use those headings where appropriate, but we can also use other headings if needed? Safer to stick to those headings.
Thus we need to map content to those headings.
We have:
- About the role: could include description of role and maybe company overview.
- Responsibilities: "What You'll Do".
- Requirements: "Required Experience".
- Qualifications: maybe "Strong Plus" (preferred qualifications) and "What We're Looking For" (skills/attributes). Could combine.
- Skills: maybe not needed.
- Benefits: none.
- Pay: none.
- Schedule: none.
We should not create empty sections.
Thus we will output:
About the role
... (Balboa description + role description)
Responsibilities
- ... each duty
Requirements
- ... each required experience
Qualifications
- ... each strong plus
... what we're looking for (non-negotiable traits) maybe as
as well.
But we need to preserve all info. Let's extract each bullet.
From "What You'll Do":
- Own relationships with a territory of Pendo enterprise AEs — become the partner rep they call first
- Source opportunities from Pendo-introduced accounts and from commercial customers we've already worked with
- Partner with our delivery team to identify expansion within active clients — new teams, new use cases, managed services renewals and upgrades
- Prospect into named ICP accounts where there's clear runway to expand the value they're getting from Pendo
- Represent Balboa at conferences, partner events, happy hours, and QBRs
- Run first-call discovery and qualify to a clean handoff
- Keep HubSpot accurate enough that we can forecast off it
- Feed the field back into our GTM — what's landing, what's not, and what Pendo sellers need from us to bring us in more often
From "First Six Months, Success Looks Like":
- Consistent, disciplined activity — the input side is fully in your control
- Named Pendo AE relationships that generate repeat referrals, not one-offs
- Measurable pipeline sourced, from both new logos and existing accounts
- Pipeline that converts — you stay involved through close
From "Required Experience":
- 2–4 years of professional experience, ideally in a client- or customer-facing role at a B2B SaaS or professional services company
- Experience carrying a number, or directly supporting someone who did — you've felt the pressure of a quota cycle
- Track record of building relationships with people you don't manage and can't compel — partners, cross-functional teams, or external stakeholders
- Comfort in the room: you've presented to or run meetings with senior stakeholders (Director level and above)
- Demonstrated ability to learn a technical product well enough to have a credible business conversation about it
- Working fluency with a CRM (HubSpot preferred) and modern sales tooling
- Willingness to travel for events, partner QBRs, and client meetings
From "Strong Plus":
- Pendo experience in any capacity — user, admin, seller, or partner
- Partner or channel sales experience
- Background in product analytics, consulting, or customer success
- You already use AI tools daily and have opinions about them
From "What We're Looking For" (Non-negotiable):
- Comfort operating without a playbook. You're energized, not paralyzed, by ambiguity
- Genuine curiosity — you'll want to understand what Pendo does and how our clients can get more value from it
- Presence. You can hold your own with a VP of Product or a Pendo enterprise AE
- Follow-through. You do what you said you'd do, and it's in the CRM
- We're hiring for hunger, polish, and judgment more than for a specific résumé.
From "Where This Role Goes":
- This is the path to Account Executive at Balboa. You'll be in discovery calls, sitting in on proposals, and staying attached to your deals through close — so you're building AE muscle from day one, not waiting for permission to learn it.
- A rep who consistently sources quality pipeline and shows they can run a deal earns a bag.
- We'd rather promote you than hire around you.
Also "About Balboa" paragraph:
Balboa is an AI-native consulting firm and Pendo Premier Solutions Partner. We help B2B SaaS companies unlock the full strategic value of their Pendo investment — driving adoption, retention, and revenue through a build-operate-transfer delivery model. We're small, growing fast, and we build our own AI infrastructure to do the work: proprietary call intelligence, agent-driven delivery, and a context library that compounds with every engagement. You'll have better tooling here than at companies 50x our size.
"The Role" paragraph:
This is not a dial-500-numbers-a-week job. Our pipeline comes through relationships — primarily with Pendo's enterprise sellers, and with commercial accounts we've supported through Pendo's onboarding motion. Your job is to build and deepen those relationships: earn trust with Pendo AEs, get introduced into their accounts, and turn those introductions into qualified opportunities Balboa can win.You'll also work our existing client base. Some of our best opportunities come from customers already in delivery — new teams, new use cases, new lines of business. You'll be close enough to those accounts to spot them.You'll spend real time in person — at marketing events, partner QBRs, and customer meetings. You'll be the face of Balboa in rooms where Pendo sellers decide who they bring into their deals.There's no playbook for this yet. You'll build it.
We need to combine About Balboa and The Role into About the role section? Probably we should put company description under About the role as well. That seems okay.
Thus About the role section will have two paragraphs: first about Balboa, second about the role.
Now we need to output HTML fragment.
We must not include any markdown code fences. Just raw HTML.
Let's craft:
About the role
Balboa is an AI-native consulting firm and Pendo Premier Solutions Partner. We help B2B SaaS companies unlock the full strategic value of their Pendo investment — driving adoption, retention, and revenue through a build-operate-transfer delivery model. We're small, growing fast, and we build our own AI infrastructure to do the work: proprietary call intelligence, agent-driven delivery, and a context library that compounds with every engagement. You'll have better tooling here than at companies 50x our size.
This is not a dial-500-numbers-a-week job. Our pipeline comes through relationships — primarily with Pendo's enterprise sellers, and with commercial accounts we've supported through Pendo's onboarding motion. Your job is to build and deepen those relationships: earn trust with Pendo AEs, get introduced into their accounts, and turn those introductions into qualified opportunities Balboa can win. You'll also work our existing client base. Some of our best opportunities come from customers already in delivery — new teams, new use cases, new lines of business. You'll be close enough to those accounts to spot them. You'll spend real time in person — at marketing events, partner QBRs, and customer meetings. You'll be the face of Balboa in rooms where Pendo sellers decide who they bring into their deals. There's no playbook for this yet. You'll build it.
Responsibilities
- Own relationships with a territory of Pendo enterprise AEs — become the partner rep they call first
- Source opportunities from Pendo-introduced accounts and from commercial customers we've already worked with
- Partner with our delivery team to identify expansion within active clients — new teams, new use cases, managed services renewals and upgrades
- Prospect into named ICP accounts where there's clear runway to expand the value they're getting from Pendo
- Represent Balboa at conferences, partner events, happy hours, and QBRs
- Run first-call discovery and qualify to a clean handoff
- Keep HubSpot accurate enough that we can
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they want us to use those exact headings where appropriate. However the posting has sections like "About Balboa", "The Role", "What You'll Do", "First Six Months, Success Looks Like", "Required Experience", "Strong Plus", "What We're Looking For", "Where This Role Goes". We need to map them to the allowed headings. Possibly we can use "About the role" for "About Balboa"? But "About Balboa" is about company, not role. Could use "About the role" for "The Role". "Responsibilities" for "What You'll Do". "Requirements" for "Required Experience". "Qualifications" maybe for "Strong Plus"? Or "Skills". "Benefits" not present. "Pay" not present. "Schedule" not present. We should only include sections when posting has real specific content. So we will include sections for About the role, Responsibilities, Requirements, Qualifications, maybe Skills? The "Strong Plus" could be considered "Preferred Qualifications" or "Skills". We'll map to "Qualifications". Also "What We're Looking For" could be "Skills" or "Qualifications". Might combine.
We need to preserve all substantive information, not invent or summarize away detail. Use - for any list of duties/requirements/benefits, and
for prose.
We need to remove boilerplate etc. There's no explicit boilerplate besides maybe "We're hiring for hunger, polish, and judgment more than for a specific résumé." That's substantive.
We need to output only HTML fragment.
Let's extract content:
About Balboa: paragraph describing Balboa.
The Role: paragraph describing role.
What You'll Do: bullet list of duties.
First Six Months, Success Looks Like: bullet list of success metrics.
Required Experience: bullet list of experience requirements.
Strong Plus: bullet list of pluses.
What We're Looking For: bullet list of non-negotiable traits and hiring criteria.
Where This Role Goes: paragraph about career path.
We need to map to headings.
Let's decide:
About the role
-> combine "About Balboa" + "The Role"? Might be weird. Better to have separate sections: maybe "About the company" not allowed. But we could still use "About the role" for the role description, and maybe include company info in a under that heading? The instruction says use those headings as examples, not strictly limited. It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we could also use other headings? It says use for section headings (e.g. ...). Likely they expect us to use those headings where appropriate, but we can also use other headings if needed? Safer to stick to those headings.
Thus we need to map content to those headings.
We have:
- About the role: could include description of role and maybe company overview.
- Responsibilities: "What You'll Do".
- Requirements: "Required Experience".
- Qualifications: maybe "Strong Plus" (preferred qualifications) and "What We're Looking For" (skills/attributes). Could combine.
- Skills: maybe not needed.
- Benefits: none.
- Pay: none.
- Schedule: none.
We should not create empty sections.
Thus we will output:
About the role
... (Balboa description + role description)
Responsibilities
- ... each duty
Requirements
- ... each required experience
Qualifications
- ... each strong plus
... what we're looking for (non-negotiable traits) maybe as
as well.
But we need to preserve all info. Let's extract each bullet.
From "What You'll Do":
- Own relationships with a territory of Pendo enterprise AEs — become the partner rep they call first
- Source opportunities from Pendo-introduced accounts and from commercial customers we've already worked with
- Partner with our delivery team to identify expansion within active clients — new teams, new use cases, managed services renewals and upgrades
- Prospect into named ICP accounts where there's clear runway to expand the value they're getting from Pendo
- Represent Balboa at conferences, partner events, happy hours, and QBRs
- Run first-call discovery and qualify to a clean handoff
- Keep HubSpot accurate enough that we can forecast off it
- Feed the field back into our GTM — what's landing, what's not, and what Pendo sellers need from us to bring us in more often
From "First Six Months, Success Looks Like":
- Consistent, disciplined activity — the input side is fully in your control
- Named Pendo AE relationships that generate repeat referrals, not one-offs
- Measurable pipeline sourced, from both new logos and existing accounts
- Pipeline that converts — you stay involved through close
From "Required Experience":
- 2–4 years of professional experience, ideally in a client- or customer-facing role at a B2B SaaS or professional services company
- Experience carrying a number, or directly supporting someone who did — you've felt the pressure of a quota cycle
- Track record of building relationships with people you don't manage and can't compel — partners, cross-functional teams, or external stakeholders
- Comfort in the room: you've presented to or run meetings with senior stakeholders (Director level and above)
- Demonstrated ability to learn a technical product well enough to have a credible business conversation about it
- Working fluency with a CRM (HubSpot preferred) and modern sales tooling
- Willingness to travel for events, partner QBRs, and client meetings
From "Strong Plus":
- Pendo experience in any capacity — user, admin, seller, or partner
- Partner or channel sales experience
- Background in product analytics, consulting, or customer success
- You already use AI tools daily and have opinions about them
From "What We're Looking For" (Non-negotiable):
- Comfort operating without a playbook. You're energized, not paralyzed, by ambiguity
- Genuine curiosity — you'll want to understand what Pendo does and how our clients can get more value from it
- Presence. You can hold your own with a VP of Product or a Pendo enterprise AE
- Follow-through. You do what you said you'd do, and it's in the CRM
- We're hiring for hunger, polish, and judgment more than for a specific résumé.
From "Where This Role Goes":
- This is the path to Account Executive at Balboa. You'll be in discovery calls, sitting in on proposals, and staying attached to your deals through close — so you're building AE muscle from day one, not waiting for permission to learn it.
- A rep who consistently sources quality pipeline and shows they can run a deal earns a bag.
- We'd rather promote you than hire around you.
Also "About Balboa" paragraph:
Balboa is an AI-native consulting firm and Pendo Premier Solutions Partner. We help B2B SaaS companies unlock the full strategic value of their Pendo investment — driving adoption, retention, and revenue through a build-operate-transfer delivery model. We're small, growing fast, and we build our own AI infrastructure to do the work: proprietary call intelligence, agent-driven delivery, and a context library that compounds with every engagement. You'll have better tooling here than at companies 50x our size.
"The Role" paragraph:
This is not a dial-500-numbers-a-week job. Our pipeline comes through relationships — primarily with Pendo's enterprise sellers, and with commercial accounts we've supported through Pendo's onboarding motion. Your job is to build and deepen those relationships: earn trust with Pendo AEs, get introduced into their accounts, and turn those introductions into qualified opportunities Balboa can win.You'll also work our existing client base. Some of our best opportunities come from customers already in delivery — new teams, new use cases, new lines of business. You'll be close enough to those accounts to spot them.You'll spend real time in person — at marketing events, partner QBRs, and customer meetings. You'll be the face of Balboa in rooms where Pendo sellers decide who they bring into their deals.There's no playbook for this yet. You'll build it.
We need to combine About Balboa and The Role into About the role section? Probably we should put company description under About the role as well. That seems okay.
Thus About the role section will have two paragraphs: first about Balboa, second about the role.
Now we need to output HTML fragment.
We must not include any markdown code fences. Just raw HTML.
Let's craft:
About the role
Balboa is an AI-native consulting firm and Pendo Premier Solutions Partner. We help B2B SaaS companies unlock the full strategic value of their Pendo investment — driving adoption, retention, and revenue through a build-operate-transfer delivery model. We're small, growing fast, and we build our own AI infrastructure to do the work: proprietary call intelligence, agent-driven delivery, and a context library that compounds with every engagement. You'll have better tooling here than at companies 50x our size.
This is not a dial-500-numbers-a-week job. Our pipeline comes through relationships — primarily with Pendo's enterprise sellers, and with commercial accounts we've supported through Pendo's onboarding motion. Your job is to build and deepen those relationships: earn trust with Pendo AEs, get introduced into their accounts, and turn those introductions into qualified opportunities Balboa can win. You'll also work our existing client base. Some of our best opportunities come from customers already in delivery — new teams, new use cases, new lines of business. You'll be close enough to those accounts to spot them. You'll spend real time in person — at marketing events, partner QBRs, and customer meetings. You'll be the face of Balboa in rooms where Pendo sellers decide who they bring into their deals. There's no playbook for this yet. You'll build it.
Responsibilities
- Own relationships with a territory of Pendo enterprise AEs — become the partner rep they call first
- Source opportunities from Pendo-introduced accounts and from commercial customers we've already worked with
- Partner with our delivery team to identify expansion within active clients — new teams, new use cases, managed services renewals and upgrades
- Prospect into named ICP accounts where there's clear runway to expand the value they're getting from Pendo
- Represent Balboa at conferences, partner events, happy hours, and QBRs
- Run first-call discovery and qualify to a clean handoff
- Keep HubSpot accurate enough that we can
for prose. We need to remove boilerplate etc. There's no explicit boilerplate besides maybe "We're hiring for hunger, polish, and judgment more than for a specific résumé." That's substantive. We need to output only HTML fragment. Let's extract content: About Balboa: paragraph describing Balboa. The Role: paragraph describing role. What You'll Do: bullet list of duties. First Six Months, Success Looks Like: bullet list of success metrics. Required Experience: bullet list of experience requirements. Strong Plus: bullet list of pluses. What We're Looking For: bullet list of non-negotiable traits and hiring criteria. Where This Role Goes: paragraph about career path. We need to map to headings. Let's decide:
About the role
-> combine "About Balboa" + "The Role"? Might be weird. Better to have separate sections: maybe "About the company" not allowed. But we could still use "About the role" for the role description, and maybe include company info in aunder that heading? The instruction says use those headings as examples, not strictly limited. It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we could also use other headings? It says use for section headings (e.g. ...). Likely they expect us to use those headings where appropriate, but we can also use other headings if needed? Safer to stick to those headings.
Thus we need to map content to those headings.
We have:
- About the role: could include description of role and maybe company overview.
- Responsibilities: "What You'll Do".
- Requirements: "Required Experience".
- Qualifications: maybe "Strong Plus" (preferred qualifications) and "What We're Looking For" (skills/attributes). Could combine.
- Skills: maybe not needed.
- Benefits: none.
- Pay: none.
- Schedule: none.
We should not create empty sections.
Thus we will output:
About the role
About the role
... (Balboa description + role description)
Responsibilities
- ... each duty
Requirements
- ... each required experience
Qualifications
- ... each strong plus
... what we're looking for (non-negotiable traits) maybe as
- as well.
But we need to preserve all info. Let's extract each bullet.
From "What You'll Do":
- Own relationships with a territory of Pendo enterprise AEs — become the partner rep they call first
- Source opportunities from Pendo-introduced accounts and from commercial customers we've already worked with
- Partner with our delivery team to identify expansion within active clients — new teams, new use cases, managed services renewals and upgrades
- Prospect into named ICP accounts where there's clear runway to expand the value they're getting from Pendo
- Represent Balboa at conferences, partner events, happy hours, and QBRs
- Run first-call discovery and qualify to a clean handoff
- Keep HubSpot accurate enough that we can forecast off it
- Feed the field back into our GTM — what's landing, what's not, and what Pendo sellers need from us to bring us in more often
From "First Six Months, Success Looks Like":
- Consistent, disciplined activity — the input side is fully in your control
- Named Pendo AE relationships that generate repeat referrals, not one-offs
- Measurable pipeline sourced, from both new logos and existing accounts
- Pipeline that converts — you stay involved through close
From "Required Experience":
- 2–4 years of professional experience, ideally in a client- or customer-facing role at a B2B SaaS or professional services company
- Experience carrying a number, or directly supporting someone who did — you've felt the pressure of a quota cycle
- Track record of building relationships with people you don't manage and can't compel — partners, cross-functional teams, or external stakeholders
- Comfort in the room: you've presented to or run meetings with senior stakeholders (Director level and above)
- Demonstrated ability to learn a technical product well enough to have a credible business conversation about it
- Working fluency with a CRM (HubSpot preferred) and modern sales tooling
- Willingness to travel for events, partner QBRs, and client meetings
From "Strong Plus":
- Pendo experience in any capacity — user, admin, seller, or partner
- Partner or channel sales experience
- Background in product analytics, consulting, or customer success
- You already use AI tools daily and have opinions about them
From "What We're Looking For" (Non-negotiable):
- Comfort operating without a playbook. You're energized, not paralyzed, by ambiguity
- Genuine curiosity — you'll want to understand what Pendo does and how our clients can get more value from it
- Presence. You can hold your own with a VP of Product or a Pendo enterprise AE
- Follow-through. You do what you said you'd do, and it's in the CRM
- We're hiring for hunger, polish, and judgment more than for a specific résumé.
From "Where This Role Goes":
- This is the path to Account Executive at Balboa. You'll be in discovery calls, sitting in on proposals, and staying attached to your deals through close — so you're building AE muscle from day one, not waiting for permission to learn it.
- A rep who consistently sources quality pipeline and shows they can run a deal earns a bag.
- We'd rather promote you than hire around you.
Also "About Balboa" paragraph:
Balboa is an AI-native consulting firm and Pendo Premier Solutions Partner. We help B2B SaaS companies unlock the full strategic value of their Pendo investment — driving adoption, retention, and revenue through a build-operate-transfer delivery model. We're small, growing fast, and we build our own AI infrastructure to do the work: proprietary call intelligence, agent-driven delivery, and a context library that compounds with every engagement. You'll have better tooling here than at companies 50x our size.
"The Role" paragraph:
This is not a dial-500-numbers-a-week job. Our pipeline comes through relationships — primarily with Pendo's enterprise sellers, and with commercial accounts we've supported through Pendo's onboarding motion. Your job is to build and deepen those relationships: earn trust with Pendo AEs, get introduced into their accounts, and turn those introductions into qualified opportunities Balboa can win.You'll also work our existing client base. Some of our best opportunities come from customers already in delivery — new teams, new use cases, new lines of business. You'll be close enough to those accounts to spot them.You'll spend real time in person — at marketing events, partner QBRs, and customer meetings. You'll be the face of Balboa in rooms where Pendo sellers decide who they bring into their deals.There's no playbook for this yet. You'll build it.
We need to combine About Balboa and The Role into About the role section? Probably we should put company description under About the role as well. That seems okay.
Thus About the role section will have two paragraphs: first about Balboa, second about the role.
Now we need to output HTML fragment.
We must not include any markdown code fences. Just raw HTML.
Let's craft:
- Own relationships with a territory of Pendo enterprise AEs — become the partner rep they call first
- Source opportunities from Pendo-introduced accounts and from commercial customers we've already worked with
- Partner with our delivery team to identify expansion within active clients — new teams, new use cases, managed services renewals and upgrades
- Prospect into named ICP accounts where there's clear runway to expand the value they're getting from Pendo
- Represent Balboa at conferences, partner events, happy hours, and QBRs
- Run first-call discovery and qualify to a clean handoff
- Keep HubSpot accurate enough that we can
About the role
Balboa is an AI-native consulting firm and Pendo Premier Solutions Partner. We help B2B SaaS companies unlock the full strategic value of their Pendo investment — driving adoption, retention, and revenue through a build-operate-transfer delivery model. We're small, growing fast, and we build our own AI infrastructure to do the work: proprietary call intelligence, agent-driven delivery, and a context library that compounds with every engagement. You'll have better tooling here than at companies 50x our size.
This is not a dial-500-numbers-a-week job. Our pipeline comes through relationships — primarily with Pendo's enterprise sellers, and with commercial accounts we've supported through Pendo's onboarding motion. Your job is to build and deepen those relationships: earn trust with Pendo AEs, get introduced into their accounts, and turn those introductions into qualified opportunities Balboa can win. You'll also work our existing client base. Some of our best opportunities come from customers already in delivery — new teams, new use cases, new lines of business. You'll be close enough to those accounts to spot them. You'll spend real time in person — at marketing events, partner QBRs, and customer meetings. You'll be the face of Balboa in rooms where Pendo sellers decide who they bring into their deals. There's no playbook for this yet. You'll build it.