The company provides a customer engagement platform that brands use to run personalised, AI-assisted messaging and journeys, and it is growing rapidly on a global scale.
Salesforce has agreed to acquire the company. The deal has not closed and is subject to customary closing conditions.
The team wants people who take ownership, use their own judgement, and stay open to other views, and who like hard problems and act quickly when things change.
Responsibilities
Partners extend a software company's reach and deepen customer relationships in ways direct sales alone cannot. Technology partners are the platforms, data tools and AI services customers already use, so how well the company works with them shapes what customers can build.
Technology partnerships come in three forms: product partnerships built into the product, strategic partnerships held at senior level with a few platform companies including major cloud and large language model providers, and a long tail of ISVs that integrate and extend what customers can do. The strategy that connects them is still being written.
Reporting to the AVP, Partner Experience, you own the strategy, program and plan across all three forms. You write it with the VP, Technology Partnerships, who leads the strategic relationships. You define what a technology partner is, what each type receives, what is expected in return, and how the forms fit together so partners, Product and the field see one ecosystem.
You work with Product, the Competitive and Monetization Strategy team, Partner Operations and Business Systems, and the Partner Programs Director, whose tiering, benefits, incentives, portal and directory your program runs within. ISV onboarding and evaluation, co-sell and competitive handling need rebuilding. You decide what to keep, change or drop, and set a 24 months plan for what comes next.
Set out the strategy, program and plan for all forms, including partners with and without a commercial motion. Agree it with the VP, Technology Partnerships before it goes wider, and define what good looks like, in what order, and who does what.
Draw the line between an ISV partner, which has an integration with the company, and a technology partner, which has a commercial motion. Define what each receives and what is expected back, within the tiering, benefits and incentives set by the Partner Programs Director.
Align product, ISV and technology partnerships with Product. Map existing product partnerships by category, agree with category leads what counts as a partnership, and give technology partners access to the Product Roadmap and awareness of it.
Rebuild the ISV program: how partners are evaluated and onboarded, and an ideal partner profile (IPP) that shows the team where to invest. Make onboarding completable without chasing, and measure how long a partner takes to become active.
Turn the early co-sell trial into a repeatable program. Define how partners are chosen, how opportunities are shared, how it connects with Sales, and what gets measured. Design a referral program that works both ways between the company and technology partners.
With the Competitive and Monetization Strategy team, define when a technology partner becomes a competitor and the rules of engagement that follow. Build one ongoing competitive process that every partnership decision uses.
Own the company's listings in other companies' directories, such as AI-platform directories like Gemini. Customers cannot buy through these listings, unlike marketplace offerings. With the Lead Partner Program Manager (Channel & Marketplace), keep the line clear: if a customer can buy through it, it belongs to marketplace; if it is only a listing, it sits here.
Assess where technology partners add value, whether through pipeline from a few partners or adoption across the long tail, and where they do not. Recommend what to keep, stop and start over the next 24 months.
With Partner Operations and Business Systems, replace separate reports with single views of partner-influenced pipeline, co-sell opportunities, time to activate and customer adoption of integrations.
Work with Product, Partner Marketing, Partner PMM, Partner Operations and Business Systems so rules, tools and messages agree. Pass what you hear from technology partners into the tiering, benefits and incentives the Partner Programs Director owns.
If the Salesforce acquisition completes, lead the work to bring the technology partner program in line with the broader Salesforce partner program and ecosystem.
Requirements
8+ years in technology partnerships, alliances or partner programs at a B2B SaaS or technology company.
Has owned the strategy for a technology partner program spanning more than one form, such as product, strategic and ISV partnerships, ideally at a larger or more mature company.
Has set a strategy and plan with a senior partnerships leader, and can show what changed: who to partner with, who to decline and where to invest.
Has defined the difference between an integration partner and a partner with a commercial motion, and built the evaluation, onboarding and ideal partner profile that follow.
Has taken a co-sell program from trial to repeatable, and understands how two-way referral programs work.
Has worked with Product to bring partner integrations into the roadmap, and can shape how a product team thinks about partners without owning the roadmap.
Has set rules of engagement for competitive situations with technology partners and made them hold across Sales, Product and Partnerships.
Understands directories and marketplaces, and the difference between a listing and a place a customer can buy through.
Builds reporting that shows where partners create value across pipeline influence and customer adoption.
Has influenced senior stakeholders in Product, Sales and Partnerships without formal authority.
Technically fluent: reads integration documentation, follows conversations with engineers and product managers, and can judge whether an integration is real.
Experience in a MarTech or customer engagement platform business is advantageous.
Familiarity with Salesforce, Crossbeam and Google Workspace is advantageous.
Conditions
Based in AMER, with regular working overlap with a manager based in London.
Hybrid ways of working are supported.
For candidates based in the United States, starting base pay is expected to be $86,400 to $124,000 per year, with expected on-target earnings (OTE, including bonus or commission) of $108,000 to $155,000 per year.
The final offer may vary based on market location, job-related knowledge, skills and experience.
The company treats all applicants equally and encourages people to apply even if they do not meet 100% of the criteria.
Benefits
Benefits differ by country, and full details are shared if you receive an offer.
Pay may include equity, and this role includes restricted stock unit (RSU) grants.
Retirement plan and employee stock purchase plan.
Flexible paid time off.
Medical, dental, vision, life and disability cover.
Fertility benefits and equal paid parental leave.
Formal career pathing, learning platforms and a yearly learning stipend.
A curated in-office experience designed to build community and team connections.
Annual company-wide Volunteer Week and donation matching.