Director, Partnerships
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" heading for the job summary? The posting includes "Job Summary:" which we can treat as About the role. Also we have "Responsibilities:" with bullet list. "Qualifications and Job Requirements:" includes qualifications. Also there is "Benefits" mentioned: US benefit offerings. Also "Pay" mentioned: base salary and discretionary bonus, but not specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does mention base salary and discretionary bonus, and benefits. So we can include Pay and Benefits sections. However we must avoid filler like "commensurate with experience". The posting says: "This position receives a base salary and is also eligible to receive a discretionary bonus. For candidates who meet the qualifications and job requirements listed above, individual pay is determined by work location and additional factors, including job-related skills, experience, and relevant education or training." That's not a specific number but it's stating that there is a base salary and discretionary bonus. Is that considered substantive? It says not to create Pay section unless posting actually states them. It does state that there is a base salary and discretionary bonus, but no specifics. Might be okay to include Pay section with that description. Similarly Benefits: they list benefits. So we can include Benefits.
Schedule: not mentioned besides remote position, can be done from anywhere. No explicit schedule (full-time). There's US FLSA Classification: Full-Time/Exempt. That indicates full-time. Could we create Schedule section? The instruction: never create Schedule unless posting actually states them. It does state Full-Time/Exempt, which implies schedule. Might be okay to include Schedule with "Full-Time". But we need to avoid filler like "not specified". It's specified as Full-Time. So we can include Schedule.
We must not include Job ID/requisition numbers. There's "For Toptal Use Only: #us" - drop.
We must remove boilerplate like EEO etc. Not present.
We need to preserve all substantive information. So we need to include the About Toptal paragraph, Job Summary, Responsibilities (list), Qualifications and Job Requirements (list), Essential Job Functions (list?), US FLSA Classification, Pay, Benefits, Schedule.
We need to format as headings and - for lists,
for prose.
We must not repeat job title as heading. So we will not have a heading for "Director of Partnerships". We'll start with maybe
About the role
containing the About Toptal and Job Summary? Actually About the role could combine About Toptal and Job Summary. But we might split: About the role
for Job Summary, and maybe About Toptal
not in list of allowed headings but we could still use About Toptal
as it's a heading. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. Likely we should stick to those examples. So we should not create a heading "About Toptal". Instead we can incorporate that info under About the role or maybe under a generic
without heading. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings when appropriate. So we can use About the role for the job summary and maybe include company description there. Or we could have a separate
about Toptal without heading. Probably better to put company description under About the role heading.
Thus:
About the role
About Toptal Toptal is a global network ...
Job Summary: As Director of Partnerships, you will lead ...
Then Responsibilities heading with list.
Then Qualifications heading with list (maybe combine Requirements and Qualifications). The posting has "Qualifications and Job Requirements:" which we can treat as Qualifications.
Then Essential Job Functions maybe under Requirements? Not in examples. Could treat as Requirements. But we have a separate list of Essential Job Functions. Could put under Requirements heading.
Then Benefits heading with list.
Then Pay heading with paragraph.
Then Schedule heading with paragraph (Full-Time/Exempt).
We must not include fluff like "In the first week..." etc. Those are part of Responsibilities? Actually they are under Responsibilities as expectations. They are substantive, we should keep them. The Responsibilities section includes a paragraph about expectations timeline. We should keep that as part of Responsibilities, maybe as after the list? The responsibilities list includes bullet points; after that there are paragraphs about first week, month, etc. Those are also responsibilities/expectations. We should preserve them. So we can include them as
under Responsibilities after the list.
Similarly Qualifications section includes a paragraph about "You must be a world-class individual contributor..." etc. Keep as
.
Now we need to ensure we don't include boilerplate like "Resumes and communication must be submitted in English." That's application instruction, should be removed. Also "Due to the remote nature of this role, we are unable to provide visa sponsorship." That's also maybe not needed? It's not boilerplate but it's a condition. Might be considered substantive? It's about visa sponsorship. Could be considered a requirement. Might be included under Requirements or Qualifications. But the instruction says remove application instructions. Visa sponsorship is not exactly application instruction but a condition. Might keep? Not sure. Safer to keep as part of Requirements? It's a condition about eligibility. Could be included under Requirements as a note. However the instruction says remove application instructions. This is not exactly application instruction but a limitation. I'd keep it maybe under Requirements as a note.
Also "US FLSA Classification: Full-Time/Exempt" we used for Schedule.
Now produce HTML.
Let's craft.
We need to ensure we only output HTML fragment, no markdown.
Let's write:
About the role
About Toptal Toptal is a global network of top talent in business, design, and technology that enables companies to scale their teams, on-demand. With $200+ million in annual revenue and team members based around the globe, Toptal is the world’s largest fully remote workforce. We take the best elements of virtual teams and combine them with a support structure that encourages innovation, social interaction, and fun. We see no borders, move at a fast pace, and are never afraid to break the mold.
Job Summary: As Director of Partnerships, you will lead the strategy and growth of Toptal’s global partner ecosystem, turning strategic relationships into measurable revenue, differentiated services, and expanded market opportunity across Toptal’s existing and emerging services, products, and new businesses. Reporting to the Chief Customer Officer, AI Services, you will work closely with Sales, Services, Talent, Marketing, and senior leadership to identify, activate, and grow strategic partners. This includes joint go-to-market motions, partner-sourced and influenced pipeline, co-selling, joint solutions, marketplace and reseller opportunities, talent certifications, partnership tiers, executive relationships, and partner-funded programs such as Marketing Development Funds (MDF) and sponsorships. The successful candidate will combine commercial instincts, partnership strategy, operational discipline, and executive relationship management. This is a hands-on leadership role for someone who can develop the strategy, put pen to paper, build the plans and materials, work directly on opportunities, and drive execution through measurable business results. This is a remote position that can be done from anywhere. Due to the remote nature of this role, we are unable to provide visa sponsorship. Resumes and communication must be submitted in English.
But we need to remove application instructions: "Resumes and communication must be submitted in English." That's an application instruction, should be removed. Also maybe "Due to the remote nature of this role, we are unable to provide visa sponsorship." Might stay? It's not an instruction but a condition. I'd keep it.
Thus remove the sentence about resumes.
Now Responsibilities:
Responsibilities
- Drive partnership revenue and pipeline: Build and execute partnership strategies that generate partner-sourced and partner-influenced pipeline, accelerate sales opportunities, and expand revenue across Toptal’s services, products, and new businesses.
- Own strategic partner relationships: Develop joint business plans with priority partners, build executive and field-level relationships, establish shared goals, and lead regular business reviews focused on revenue, pipeline, adoption, and growth.
- Build joint GTM and co-sell motions: Turn partnerships into actionable sales motions through joint solutions, account mapping, co-selling, marketplace opportunities, reseller programs, sales enablement, campaigns, and events.
- Grow Toptal’s position within partner ecosystems: Drive certifications, specializations, partnership tiers, designations, marketplace listings, and other requirements that increase Toptal’s access, credibility, benefits, and commercial opportunity within each ecosystem.
- Secure partner investment: Identify and capture Marketing Development Funds (MDF), sponsorships, enablement funding, event support, sales incentives, and other partner-funded programs that can accelerate growth.
- Manage the partnership lifecycle: Own partnerships from identification and business case through contracting, onboarding, launch, activation, growth, and ongoing performance management.
- Coordinate cross-functional execution: Work closely with Sales, Services, Talent, Marketing, Legal, Finance, Product, and leadership to ensure partnership commitments are translated into clear owners, deliverables, and measurable outcomes.
- Measure portfolio performance: Establish and track KPIs across revenue, pipeline, certifications, tier progression, partner engagement, co-sell activity, and partner investment, while maintaining clear visibility into priorities, blockers, and next steps.
- Build scalable partnership operations: Create the processes, tools, documentation, and operating cadence required to manage a growing partner portfolio efficiently without losing speed or accountability.
- Stay hands-on in execution: Personally develop partner plans, presentations, applications, business cases, enablement materials, and other work required to move partnerships forward and convert strategy into results.
In the first week, expect to: Build context on Toptal’s partnership strategy, priority partners, current pipeline, and active initiatives. Meet key stakeholders across Sales, Services, Talent, Marketing, Legal, Finance, Product, and leadership. Begin transitioning ownership of priority partner relationships, operating cadences, and near-term opportunities.
In the first month, expect to: Develop a clear view of the partner portfolio, including revenue opportunity, tier status, certifications, GTM motions, and key gaps. Take ownership of partnership priorities, partner engagement, pipeline visibility, and cross-functional execution. Identify immediate opportunities to accelerate co-sell activity, partner-funded programs, certifications, and tier progression.
In the first three months, expect to: Establish joint business plans and measurable growth priorities for Toptal’s most strategic partners. Launch or strengthen partner-sourced and partner-influenced GTM motions, including co-selling, account mapping, enablement, marketplace, and joint solution opportunities. Implement scalable processes and metrics for revenue, pipeline, certifications, tier progression, partner investment, and overall portfolio performance.
In the first six months, expect to: Demon
- for lists,
for prose. We must not repeat job title as heading. So we will not have a heading for "Director of Partnerships". We'll start with maybe
About the role
containing the About Toptal and Job Summary? Actually About the role could combine About Toptal and Job Summary. But we might split:About the role
for Job Summary, and maybeAbout Toptal
not in list of allowed headings but we could still useAbout Toptal
as it's a heading. The instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. Likely we should stick to those examples. So we should not create a heading "About Toptal". Instead we can incorporate that info under About the role or maybe under a generic
without heading. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings when appropriate. So we can use About the role for the job summary and maybe include company description there. Or we could have a separate
about Toptal without heading. Probably better to put company description under About the role heading. Thus:
About the role
About Toptal Toptal is a global network ...
Job Summary: As Director of Partnerships, you will lead ...
Then Responsibilities heading with list. Then Qualifications heading with list (maybe combine Requirements and Qualifications). The posting has "Qualifications and Job Requirements:" which we can treat as Qualifications. Then Essential Job Functions maybe under Requirements? Not in examples. Could treat as Requirements. But we have a separate list of Essential Job Functions. Could put under Requirements heading. Then Benefits heading with list. Then Pay heading with paragraph. Then Schedule heading with paragraph (Full-Time/Exempt). We must not include fluff like "In the first week..." etc. Those are part of Responsibilities? Actually they are under Responsibilities as expectations. They are substantive, we should keep them. The Responsibilities section includes a paragraph about expectations timeline. We should keep that as part of Responsibilities, maybe asafter the list? The responsibilities list includes bullet points; after that there are paragraphs about first week, month, etc. Those are also responsibilities/expectations. We should preserve them. So we can include them as
under Responsibilities after the list. Similarly Qualifications section includes a paragraph about "You must be a world-class individual contributor..." etc. Keep as
. Now we need to ensure we don't include boilerplate like "Resumes and communication must be submitted in English." That's application instruction, should be removed. Also "Due to the remote nature of this role, we are unable to provide visa sponsorship." That's also maybe not needed? It's not boilerplate but it's a condition. Might be considered substantive? It's about visa sponsorship. Could be considered a requirement. Might be included under Requirements or Qualifications. But the instruction says remove application instructions. Visa sponsorship is not exactly application instruction but a condition. Might keep? Not sure. Safer to keep as part of Requirements? It's a condition about eligibility. Could be included under Requirements as a note. However the instruction says remove application instructions. This is not exactly application instruction but a limitation. I'd keep it maybe under Requirements as a note. Also "US FLSA Classification: Full-Time/Exempt" we used for Schedule. Now produce HTML. Let's craft. We need to ensure we only output HTML fragment, no markdown. Let's write:
About the role
About Toptal Toptal is a global network of top talent in business, design, and technology that enables companies to scale their teams, on-demand. With $200+ million in annual revenue and team members based around the globe, Toptal is the world’s largest fully remote workforce. We take the best elements of virtual teams and combine them with a support structure that encourages innovation, social interaction, and fun. We see no borders, move at a fast pace, and are never afraid to break the mold.
Job Summary: As Director of Partnerships, you will lead the strategy and growth of Toptal’s global partner ecosystem, turning strategic relationships into measurable revenue, differentiated services, and expanded market opportunity across Toptal’s existing and emerging services, products, and new businesses. Reporting to the Chief Customer Officer, AI Services, you will work closely with Sales, Services, Talent, Marketing, and senior leadership to identify, activate, and grow strategic partners. This includes joint go-to-market motions, partner-sourced and influenced pipeline, co-selling, joint solutions, marketplace and reseller opportunities, talent certifications, partnership tiers, executive relationships, and partner-funded programs such as Marketing Development Funds (MDF) and sponsorships. The successful candidate will combine commercial instincts, partnership strategy, operational discipline, and executive relationship management. This is a hands-on leadership role for someone who can develop the strategy, put pen to paper, build the plans and materials, work directly on opportunities, and drive execution through measurable business results. This is a remote position that can be done from anywhere. Due to the remote nature of this role, we are unable to provide visa sponsorship. Resumes and communication must be submitted in English.
But we need to remove application instructions: "Resumes and communication must be submitted in English." That's an application instruction, should be removed. Also maybe "Due to the remote nature of this role, we are unable to provide visa sponsorship." Might stay? It's not an instruction but a condition. I'd keep it. Thus remove the sentence about resumes. Now Responsibilities:Responsibilities
- Drive partnership revenue and pipeline: Build and execute partnership strategies that generate partner-sourced and partner-influenced pipeline, accelerate sales opportunities, and expand revenue across Toptal’s services, products, and new businesses.
- Own strategic partner relationships: Develop joint business plans with priority partners, build executive and field-level relationships, establish shared goals, and lead regular business reviews focused on revenue, pipeline, adoption, and growth.
- Build joint GTM and co-sell motions: Turn partnerships into actionable sales motions through joint solutions, account mapping, co-selling, marketplace opportunities, reseller programs, sales enablement, campaigns, and events.
- Grow Toptal’s position within partner ecosystems: Drive certifications, specializations, partnership tiers, designations, marketplace listings, and other requirements that increase Toptal’s access, credibility, benefits, and commercial opportunity within each ecosystem.
- Secure partner investment: Identify and capture Marketing Development Funds (MDF), sponsorships, enablement funding, event support, sales incentives, and other partner-funded programs that can accelerate growth.
- Manage the partnership lifecycle: Own partnerships from identification and business case through contracting, onboarding, launch, activation, growth, and ongoing performance management.
- Coordinate cross-functional execution: Work closely with Sales, Services, Talent, Marketing, Legal, Finance, Product, and leadership to ensure partnership commitments are translated into clear owners, deliverables, and measurable outcomes.
- Measure portfolio performance: Establish and track KPIs across revenue, pipeline, certifications, tier progression, partner engagement, co-sell activity, and partner investment, while maintaining clear visibility into priorities, blockers, and next steps.
- Build scalable partnership operations: Create the processes, tools, documentation, and operating cadence required to manage a growing partner portfolio efficiently without losing speed or accountability.
- Stay hands-on in execution: Personally develop partner plans, presentations, applications, business cases, enablement materials, and other work required to move partnerships forward and convert strategy into results.
In the first week, expect to: Build context on Toptal’s partnership strategy, priority partners, current pipeline, and active initiatives. Meet key stakeholders across Sales, Services, Talent, Marketing, Legal, Finance, Product, and leadership. Begin transitioning ownership of priority partner relationships, operating cadences, and near-term opportunities.
In the first month, expect to: Develop a clear view of the partner portfolio, including revenue opportunity, tier status, certifications, GTM motions, and key gaps. Take ownership of partnership priorities, partner engagement, pipeline visibility, and cross-functional execution. Identify immediate opportunities to accelerate co-sell activity, partner-funded programs, certifications, and tier progression.
In the first three months, expect to: Establish joint business plans and measurable growth priorities for Toptal’s most strategic partners. Launch or strengthen partner-sourced and partner-influenced GTM motions, including co-selling, account mapping, enablement, marketplace, and joint solution opportunities. Implement scalable processes and metrics for revenue, pipeline, certifications, tier progression, partner investment, and overall portfolio performance.
In the first six months, expect to: Demon