partnerships-career

{
  "skill_name": "partnerships-career",
  "evals": [
    {
      "id": 1,
      "prompt": "I'm a Senior Affiliate Manager at a DTC skincare brand called Havstrand, five years in, base $96k. A recruiter just reached out about a Director of Partnerships role at a Series B fintech called Pellworth and asked what number I'm looking for. I need to give her a figure by Thursday. What's the going rate for Director of Partnerships right now, and what should I say back?",
      "expected_output": "A refusal to hand over a single market rate, an explanation of the 2-3x spread between published partnerships salary sources and why it exists, a pointer to the field's own specialist benchmark for live verification, and the structural questions (reporting line, attribution model, three-part affiliate comp shape) that have to be answered before any number means anything.",
      "files": [],
      "expectations": [
        "States that published salary sources disagree by roughly 2-3x on the same partnerships title",
        "Names Salary.com's roughly $206-215k median for Director of Partnerships against PayScale's roughly $74k average as the concrete example of that disagreement",
        "Attributes the gap to differing sample populations and methodology rather than to one source being wrong",
        "Attaches a source, population and date to every compensation figure it states, or marks the figure as needing live verification",
        "Names Partnership Leaders' compensation database as the field's own specialist benchmark to check live rather than relying on generic aggregators",
        "Declines to produce a single 'going rate' number presented as the market rate",
        "Notes that crowdsourced total-comp figures such as Levels.fyi's roughly $226k Partner Manager median come from a different population (large tech employers, equity included) and must not be quoted against base-salary aggregator figures",
        "Explains that Affiliate Manager compensation is commonly three-part: base salary, a performance bonus, and commission tied to revenue managed through the program",
        "Advises asking which attribution model (sourced, influenced, attached, or delivered) triggers any variable component",
        "Puts establishing the reporting line and the metric that department buys ahead of settling on a number",
        "Names the sub-discipline the target role actually sits in rather than treating 'partnerships' as one job"
      ]
    },
    {
      "id": 2,
      "prompt": "Two offers landed the same week and I have to answer by Monday. Offer A: 'Head of Strategic Partnerships' at Trelloway, a 400-person HR-tech company, $165k base plus 20% variable, reports into the CRO. Offer B: 'Partner Manager' at Kosmen, a 90-person dev-tools company, $148k base plus 15% variable, reports to the CEO with partnerships standing as its own function. Offer A has the better title and more money. Am I overthinking this?",
      "expected_output": "A scoring order that puts the reporting line and its metric first, the attribution model behind each variable component second, and the package last, with the explicit statement that the two variable components are not comparable until each offer's attribution model is known, plus the diligence questions to ask before Monday.",
      "files": [],
      "expectations": [
        "Scores the reporting line and the metric that department buys before the compensation package",
        "Puts the attribution model behind the variable pay ahead of the package in the scoring order",
        "Asks which attribution model (sourced, influenced, attached, or delivered) triggers each offer's variable component",
        "States explicitly that the two variable components cannot be compared until each offer's attribution model is known",
        "States that a senior-sounding title reporting into the wrong function is a worse offer than a lower title with a clean reporting line",
        "Declines to treat Offer A's higher base and more senior title as decisive on their own",
        "Treats 'reports into its own function' as a materially different measurement regime from reporting into sales or into marketing, not a cosmetic difference",
        "Advises asking each employer whether a written career matrix or ladder exists",
        "Notes that a role reporting into sales risks program work being crowded out by deal-sized work, while one reporting into marketing risks over-rotation onto campaign and asset work",
        "Does not assert a published partnerships salary band for either title without naming source, population and date",
        "Sets a dated review or decision point for the comparison"
      ]
    },
    {
      "id": 3,
      "prompt": "I run partner marketing at Brenholm, a 250-person logistics SaaS company. My manager asked me to write up my own three-year progression plan with the levels above me spelled out, because HR wants it in the review doc. Can you lay out the standard partnerships career ladder - titles, levels, typical years at each - so I can drop it straight in?",
      "expected_output": "A plain statement that partnerships publishes no cross-company career ladder, a refusal to invent rungs and year counts, the two markers the field does publish (the CPO/VP Partner Ecosystem tier, the VP-versus-C-level split), and the mandate/decides table offered as the closest available level differentiator once the employer confirms no written matrix exists.",
      "files": [],
      "expectations": [
        "States plainly that no published cross-company career ladder exists for partnerships",
        "Contrasts this with a field that does publish one, naming sales (Bridge Group benchmarks) or DevRel's documented ladder",
        "Refuses to produce an invented rung-by-rung ladder presented as the standard one",
        "Attributes the absence to extreme title proliferation with no standardization across companies",
        "Names Chief Partner Officer / VP Partner Ecosystem as the one formally recognized senior tier and describes it as a single top-of-ladder marker, not a rung-by-rung framework",
        "Distinguishes a VP as an execution role measured on program delivery from a CPO/C-level role that sets company strategy",
        "Tells the user to ask their employer for a written career matrix first",
        "Offers the mandate and decision-rights distinction across roles (Partner/Channel Manager, Alliance Lead, Head of Partnerships, Partner Marketing, Partner Operations, Partner Enablement) as the closest available level differentiator when no matrix exists",
        "Does not attach year counts to invented rungs as though they were published benchmarks",
        "Names the sub-discipline the user actually sits in rather than treating 'partnerships' as one job",
        "Sets a dated review point for the progression plan"
      ]
    },
    {
      "id": 4,
      "prompt": "I have a first round next Tuesday for an Affiliate Manager role at Norvell & Co, a mid-size outdoor gear retailer. I've never interviewed for an affiliate job before. Walk me through the interview loop stage by stage so I know exactly what's coming - how many rounds, what each one tests, and the questions they'll ask at each stage.",
      "expected_output": "An explicit statement that no documented public loop pattern exists for Affiliate Manager roles, a refusal to fabricate one, a redirect to preparing from the role's own outcome metrics, and the activity-versus-outcome reporting distinction that determines how senior the candidate reads.",
      "files": [],
      "expectations": [
        "States that no comparably documented public interview-loop pattern exists for Affiliate Manager roles",
        "Refuses to invent a stage-by-stage affiliate loop presented as what to expect",
        "States that the well-documented loop pattern belongs to Channel/Partner Manager roles specifically",
        "Offers the channel-manager pattern only as a loose directional analogue, explicitly labelled as such rather than as what to expect verbatim",
        "Directs the user to confirm the actual format with the recruiter before preparing",
        "Redirects preparation to the role's own outcome metrics: program performance numbers owned, commission-economics literacy, and affiliate-network and tooling fluency",
        "Labels each recommendation with the sub-discipline it applies to",
        "States that the level-defining shift in affiliate roles is reporting scope, not tenure",
        "Explains that coordinators report activity (clicks, conversions, commissions paid) while directors report outcomes (revenue contribution, CAC efficiency, incrementality, channel ROI against paid media)",
        "Warns that a candidate who can only speak in click and conversion terms reads as capped below director level regardless of years in seat",
        "Sets a dated preparation checkpoint ahead of the interview date"
      ]
    },
    {
      "id": 5,
      "prompt": "Final panel on the 14th for a Senior Channel Manager job at Ivarsen Cloud - about 1,200 people, they sell through resellers and two hyperscalers. The recruiter said it's 'a panel with a few department leads plus an exercise' and left it at that. I've done plenty of sales interviews so I'm mostly not worried. What should I actually drill this week?",
      "expected_output": "Prep for the senior-level panel exercise (30/60/90 channel plan or mock partner business review), the two named judgment questions with the reasoning behind the rewarded answers, the negotiation role-play and what it is actually scored on, the channel-conflict scenario's process-discipline answer, and the enterprise-specific certification tracking load.",
      "files": [],
      "expectations": [
        "Predicts a multi-department panel with a mock 30/60/90-day channel plan or a mock partner business review as the senior-level exercise",
        "Describes that stage as evaluated like a general-manager interview, on cross-functional leadership rather than deal execution alone",
        "Prepares the user for the judgment question about closing a deal in January the same way it was closed in December to hit the quarter",
        "States that the rewarded answer to that question is no",
        "Explains the reasoning: the relationship, not the quarter, is the unit a partner manager optimizes, in contrast to a quota-carrying rep for whom the quarter is the unit",
        "Prepares the de-prioritization follow-up: walking through the last partner the candidate de-prioritized and how that conversation went",
        "Explains that the de-prioritization question tests whether the candidate has actually said no to a partner, not just built relationships",
        "Prepares a two-sided negotiation role-play with hidden constraints the candidate must surface through questioning rather than being told upfront",
        "States that the role-play is judged on structuring win-win terms and defending or finding a rational walk-away point, never on whether the candidate 'won'",
        "Covers the channel-conflict scenario with process discipline as the evaluated move - pulling the deal-registration timeline and CRM activity and bringing both reps into one conversation - rather than arbitrating by loyalty or gut feel",
        "Advises confirming the exact stage set with the recruiter because no standard loop length or stage set exists",
        "Notes that at an enterprise selling through named hyperscalers, certification and compliance tracking against each partner's own program is an explicit job responsibility"
      ]
    },
    {
      "id": 6,
      "prompt": "Found a posting I like: 'Partnerships & Growth Ninja' at Sundqvist Labs - 300 employees, Series C, closed a $40M round last year. The posting says 'you'll wear many hats,' lists deal sourcing, affiliate program ops, community building and content marketing, and ends with 'competitive salary, DOE.' No range anywhere. A friend told me 'many hats' is just normal startup stuff and I should apply. Should I?",
      "expected_output": "A company-type check that rejects the startup-normal framing for a 300-person Series C, the breadth-plus-stated-path distinguishing test, the hybrid-title and vague-comp flags with the partnerships-specific reason each lands harder here, the three questions the posting must answer, and an honest statement that the field has no named red-flag taxonomy.",
      "files": [],
      "expectations": [
        "Checks the company-type row before judging the 'many hats' phrase rather than accepting the startup-normal framing",
        "States that 'many hats' is not disqualifying at a genuine early-stage startup but that a 300-person Series C company is not that stage",
        "Applies the distinguishing test: breadth plus a stated ownership boundary and a stated path forward is a startup generalist role, breadth with no stated path is the trap",
        "Flags the buzzword/hybrid title as signalling the company has not decided what it needs",
        "Identifies the collapse of partnerships, growth marketing and community into one title with no stated primary metric as the specific problem, not the word 'ninja' on its own",
        "Flags 'competitive salary' with no published range as a stronger warning signal in partnerships than in most fields",
        "Ties that specifically to published partnerships comp benchmarks already disagreeing by 2-3x, leaving the candidate with no anchor at all",
        "Tells the user to ask for a numeric time-split across the role's stated components",
        "Tells the user to ask for the reporting line - sales, marketing, or its own function",
        "Tells the user to ask whether a written career matrix or ladder exists at all",
        "States that no named field-specific posting red-flag taxonomy exists for partnerships rather than presenting an invented one"
      ]
    },
    {
      "id": 7,
      "prompt": "I'm an AE at Hallenbeck Systems, 180 people. We have a two-person partnerships team. I'm at 71% of quota this year (rough territory, long story), but I've been informally handling three reseller relationships that came in inbound, maybe four hours a week, for about eight months now. I've got a 1:1 with the VP of Partnerships on Friday and I'm going to ask her to move me over. What should I say?",
      "expected_output": "A flag that 71% of quota conflicts with the top-performer precondition for an internal transfer, recognition that the informal reseller work means the transfer sequence is already underway rather than starting, a redirect of Friday's meeting toward diligence and business-case building instead of the cold ask, and the efficiency-versus-ceiling framing of the internal route.",
      "files": [],
      "expectations": [
        "Flags that asking while below quota conflicts with the field's repeated precondition that an internal-transfer candidate be a top performer in their current seat",
        "States that the ask should come from a position of standing, not from enthusiasm alone",
        "Recognizes that the user is already doing partnerships work informally and treats the internal-transfer sequence as already underway rather than as a plan to start",
        "Skips the sequence steps the user has already completed instead of restating them as next actions",
        "Directs the user to build the business case with real numbers: pipeline or revenue attributable to the three reseller relationships",
        "Recommends networking with the existing partnerships team - shadowing a partner meeting, asking what they look for in a candidate",
        "Recommends repurposing Friday's meeting toward that diligence rather than making the ask cold",
        "States that internal transfer is more efficient than external entry and costs near zero because the work happens on company time in a role already held",
        "Notes that internal transfer wins on speed rather than on ceiling, since external entry into a sub-discipline-specific seat lands the same title",
        "Names the sub-discipline the reseller work maps to (channel/alliance) rather than calling it 'partnerships'",
        "Sets a dated review point for when to make the actual ask"
      ]
    },
    {
      "id": 8,
      "prompt": "I've been in B2B content marketing for three years. My company is a 40-person agency with no partnerships function at all, so there's nobody internally to shadow. I found impact.com's PXA certification and ASAP's CA-AM. My plan is to spend the next four months getting both before I start applying, then go straight for an Affiliate Manager or an Influencer Partnerships Manager role. Sound right?",
      "expected_output": "A correction of the certification-first plan on the grounds that postings list these as preferred and never required, the promotion of external entry to the only available route given no internal function to transfer into, the adjacent feeder roles to target, and a warning that influencer/creator partnerships is almost never a direct point of entry.",
      "files": [],
      "expectations": [
        "States that job postings consistently list PXA and CA-AM as 'preferred', never as 'required'",
        "Advises against spending the four-month budget on certifications ahead of building a track record",
        "States that practical experience and industry-network reputation outweigh any credential in this field",
        "Notes that PXA is free and tiered, and that its expert-tier content targets creators and publishers rather than brand-side partner managers",
        "Notes that ASAP's CA-AM sits on the alliance-management side specifically and costs money",
        "Recognizes that with no internal partnerships function there is nothing to transfer into, and promotes external entry from the default second-place route to the only available option",
        "States that no fixed entry path exists in this field and that marketing is one of several legitimate feeders alongside sales, business development and account management",
        "Points the user at entry-level business development, account management or sales roles as the transferable-skill feeder",
        "States that no SDR/BDR-equivalent dedicated junior partnerships title exists to apply for directly",
        "Warns that Influencer/Creator Partnerships Manager is almost never a direct point of entry and is a specialist track built on broader marketing or social-media experience",
        "Sets a dated review point for the plan"
      ]
    },
    {
      "id": 9,
      "prompt": "Two postings I'm shortlisting. One is 'Referral Program Manager' at Grindelwald Health, 600 people. The other is 'Partnerships Manager' at Ottavia, which is very product-led - self-serve signup, no sales team until you hit enterprise. I have five years in lifecycle marketing. Which is the better fit, and how do I tailor for each?",
      "expected_output": "Disambiguation of the Referral Program Manager title between customer/growth and employee-referral recruiting before anything else, a read of the PLG posting as most likely integrations/marketplace/affiliate/agency work rather than channel sales, and an honest account of where the referral seat leads next.",
      "files": [],
      "expectations": [
        "States that two unrelated occupations share the 'Referral Program Manager' title and that the posting must be disambiguated before anything else applies",
        "Describes the customer/growth referral track: refer-a-friend program design, incentive structure, tracking, and CRM-side coordination with marketing",
        "Describes the employee-referral recruiting track as an HR or talent-acquisition function tracking referral-to-hire conversion",
        "Tells the user how to determine which of the two the Grindelwald posting means before applying",
        "States that a PLG-labelled partnerships req is more likely to mean integrations, marketplace, affiliate and agency programs than channel-sales deal registration or co-sell process design",
        "Tells the user to read the PLG posting for which half of the hybrid it actually needs rather than assuming the title predicts the work",
        "Notes that PLG-motion companies invest disproportionately more in communities, integrations, affiliates, agencies and referral partnerships than in traditional reseller or channel partnerships",
        "Notes that no published multi-rung ladder exists for the Referral Program Manager title and that it usually sits as one IC role inside a growth or lifecycle-marketing team",
        "States that the honest next move from a referral seat is usually lateral - into a broader referral, affiliate and loyalty remit, or into Partner Marketing - rather than a same-title promotion",
        "Names each posting's sub-discipline explicitly rather than treating both as 'partnerships'",
        "Sets a dated review point for the shortlist decision"
      ]
    }
  ],
  "trigger_queries": [
    { "query": "How do I break into partnerships?", "should_trigger": true },
    { "query": "I want to become a partner manager - where do I start?", "should_trigger": true },
    { "query": "What's the career path for an affiliate manager?", "should_trigger": true },
    { "query": "I have a channel manager interview next week, how should I prep?", "should_trigger": true },
    { "query": "Is this partnerships job posting a red flag?", "should_trigger": true },
    { "query": "Got two offers for partner manager roles, which one should I take?", "should_trigger": true },
    { "query": "What do partnerships people actually get paid?", "should_trigger": true },
    { "query": "Should I get the PXA certification before applying to partnership jobs?", "should_trigger": true },
    { "query": "I'm an AE and I want to move to the alliances team internally. How do I pitch it?", "should_trigger": true },
    { "query": "Help me prepare for a negotiation role-play in a partner manager interview", "should_trigger": true },
    { "query": "What's the difference between a channel manager job and an alliance manager job?", "should_trigger": true },
    { "query": "I've been doing partner work on the side of my sales role for a year. Is that enough to get hired into it full time?", "should_trigger": true },
    { "query": "Is there a career ladder for partnerships?", "should_trigger": true },
    { "query": "What separates a junior partner manager from a senior one?", "should_trigger": true },
    { "query": "How do I evaluate a Head of Partnerships offer?", "should_trigger": true },
    { "query": "Should I take an influencer partnerships job or an affiliate manager job?", "should_trigger": true },
    { "query": "What questions should I ask the hiring manager in a partnerships interview?", "should_trigger": true },
    { "query": "This req says 'partnerships ninja' and lists five different jobs in one. Thoughts?", "should_trigger": true },
    { "query": "I want to leave sales. What's a realistic next move that actually uses my relationships?", "should_trigger": true },
    { "query": "My title is Partnerships Associate and I have no idea what the next rung is supposed to be.", "should_trigger": true },
    { "query": "How many years until I can realistically be a Director of Partnerships?", "should_trigger": true },
    { "query": "A recruiter asked for my salary expectations for a VP Partnerships role and I have no idea what to say.", "should_trigger": true },
    { "query": "What's the going rate for a partner manager in tech?", "should_trigger": true },
    { "query": "I keep seeing 'Referral Program Manager' roles - is that an HR job or a marketing job?", "should_trigger": true },
    { "query": "Do I need a marketing degree to get hired running an affiliate program?", "should_trigger": true },
    { "query": "Breaking into alliances from customer success - possible?", "should_trigger": true },
    { "query": "What track record do I need to show to get hired as a partner manager?", "should_trigger": true },
    { "query": "First partnerships hire at a seed startup - is that a good move for me or a trap?", "should_trigger": true },
    { "query": "How does an enterprise alliance role differ day to day from a startup partnerships role?", "should_trigger": true },
    { "query": "They asked me in an interview whether I'd close a deal in January the same way I closed it in December. What were they testing?", "should_trigger": true },
    { "query": "Is partnerships a good career to be in?", "should_trigger": true },
    { "query": "I run the affiliate program at a DTC brand and I'm bored. What's next for me?", "should_trigger": true },
    { "query": "prep me for a mock partner business review exercise in a final round", "should_trigger": true },
    { "query": "They want me to present a 30/60/90 channel plan at the final panel next week.", "should_trigger": true },
    { "query": "Which pays better over a career, affiliate management or channel sales?", "should_trigger": true },
    { "query": "How do I switch from influencer marketing into B2B channel partnerships?", "should_trigger": true },
    { "query": "The listing says competitive salary with no range anywhere. Should that worry me as a candidate?", "should_trigger": true },
    { "query": "What does a Chief Partner Officer actually do that a VP doesn't?", "should_trigger": true },
    { "query": "I'm interviewing at a product-led company for a partnerships role. What will the job actually be?", "should_trigger": true },
    { "query": "Should I take a lateral move or even a step down in title to get into partnerships?", "should_trigger": true },
    { "query": "how do i get my company to create a partnerships role for me", "should_trigger": true },
    { "query": "What's the bar for being the first dedicated partnerships hire at a startup?", "should_trigger": true },
    { "query": "Give me a story bank to bring into a partner manager loop.", "should_trigger": true },
    { "query": "I'm comparing a Partner Manager title reporting to the CRO against a Head of Partnerships reporting to the CEO.", "should_trigger": true },
    { "query": "no idea what to expect from an alliances interview loop, help", "should_trigger": true },
    { "query": "I'm hiring our first partner manager - what should the scorecard look like?", "should_trigger": false },
    { "query": "Design the interview loop for the channel manager role we're opening.", "should_trigger": false },
    { "query": "Write the job description for the Affiliate Manager we want to hire.", "should_trigger": false },
    { "query": "Where should we source candidates for an alliances role?", "should_trigger": false },
    { "query": "What should we budget to pay our new partner manager?", "should_trigger": false },
    { "query": "Set the commission rate for our new affiliate program.", "should_trigger": false },
    { "query": "How long should our affiliate cookie attribution window be?", "should_trigger": false },
    { "query": "Draft the terms and conditions affiliates accept when they join our program.", "should_trigger": false },
    { "query": "Our affiliate traffic looks fake - how do I detect cookie stuffing?", "should_trigger": false },
    { "query": "Audit this month's affiliate payout run before we disburse it.", "should_trigger": false },
    { "query": "Build the metric set and layout for our affiliate performance dashboard.", "should_trigger": false },
    { "query": "Write the welcome sequence for newly approved affiliates.", "should_trigger": false },
    { "query": "Draft a recruitment email to bring new affiliates into our program.", "should_trigger": false },
    { "query": "Does this creator's caption meet FTC disclosure rules?", "should_trigger": false },
    { "query": "Rank these five candidate strategic alliances by expected value.", "should_trigger": false },
    { "query": "Write our deal registration policy for partner-sourced deals.", "should_trigger": false },
    { "query": "Draft the campaign brief for the creator we just signed.", "should_trigger": false },
    { "query": "Define the criteria we'll use to shortlist influencers for this campaign.", "should_trigger": false },
    { "query": "What KPIs should we set before this creator campaign launches?", "should_trigger": false },
    { "query": "Prepare my opening positions for negotiating usage rights with a creator.", "should_trigger": false },
    { "query": "Write a first-touch pitch to this YouTuber proposing a partnership.", "should_trigger": false },
    { "query": "Plan the joint go-to-market motion with our new ISV partner.", "should_trigger": false },
    { "query": "Two partners registered the same deal. Write the rules of engagement.", "should_trigger": false },
    { "query": "Design our partner program from scratch - tiers, benefits, which motions to run.", "should_trigger": false },
    { "query": "Model whether this reseller partner is actually profitable for us.", "should_trigger": false },
    { "query": "Map our whole partner ecosystem and find the channel coverage gaps.", "should_trigger": false },
    { "query": "Which partner category should we add to the ecosystem next?", "should_trigger": false },
    { "query": "Sequence the training and certification our partners need to sell on their own.", "should_trigger": false },
    { "query": "Which cloud marketplaces should we list our product on?", "should_trigger": false },
    { "query": "Build the per-partner scorecard and QBR structure for our program.", "should_trigger": false },
    { "query": "Redesign our silver/gold/platinum partner tiers and the promotion rules.", "should_trigger": false },
    { "query": "Cap the rewards on our refer-a-friend program so customers stop gaming it.", "should_trigger": false },
    { "query": "How much should we pay out for each customer referral?", "should_trigger": false },
    { "query": "Route this partnerships task to whichever skill in the collection fits.", "should_trigger": false },
    { "query": "Reformat my resume so it gets through ATS screening.", "should_trigger": false },
    { "query": "Rewrite my resume bullets with stronger quantified numbers.", "should_trigger": false },
    { "query": "Tailor my resume to this specific job description.", "should_trigger": false },
    { "query": "Help me negotiate my salary offer for a senior software engineer role.", "should_trigger": false },
    { "query": "Generate behavioral interview questions for a product manager loop.", "should_trigger": false },
    { "query": "Parse this job posting into a structured list of required versus preferred qualifications.", "should_trigger": false },
    { "query": "I'm switching careers from teaching into tech - translate my experience across.", "should_trigger": false },
    { "query": "Write an executive resume for a CMO search.", "should_trigger": false },
    { "query": "Run a mock discovery interview with me for user research.", "should_trigger": false },
    { "query": "Help me build a portfolio site as a freelance designer.", "should_trigger": false },
    { "query": "Prep me for negotiating a vendor contract renewal with a SaaS supplier.", "should_trigger": false }
  ]
}

# Company-type bar

Contents: pre-hire signals · the four company-type rows · the two named startup-hire failure modes.

## Pre-hire stage: founder-led, no dedicated seat yet

Partnerships work is almost always founder- or CEO-led before any dedicated hire exists, and stays that way until it consumes real founder time. Two named timing signals for when a company formalizes the role:

- **Founding-team fit** - if founders already have partnerships/domain expertise, hiring can wait until post-Series A or B; if the founding team lacks it and partnerships are core to growth strategy, a BD/partnerships leader comes on shortly after founding instead.
- **Revenue signal** - dedicate a hire once founder-led partnerships are already driving meaningful revenue (the figure cited is $500k+), rather than hiring speculatively ahead of proof.

## Startup, first dedicated hire: generalist, not specialist

The first partnerships/BD hire must be a versatile generalist who can build a program from scratch and cover every partner type at once - there is no volume yet to justify specialization. Sales or account-management background is a plus specifically because it buys credibility with the sales team and fluency in the deal-to-close process.

**Two named hiring failure modes at this stage:**

- **Too senior** - a hire who expects to set strategy and lead a team when the actual need is hands-on execution.
- **Too generalist with no GTM muscle** - without real go-to-market reps, a generalist struggles to prioritize which early motions will actually work.

Match the hire to the intended shape of the work: a few deep, high-touch integrations versus many light-touch partnerships call for different profiles (patience and depth vs. speed and breadth).

## Scale-up: dedicated team, motion-specific specialization begins

Dedicated partner-ops headcount becomes common in this band. A dedicated Partner Enablement Manager becomes justified around 20-30 active partners or 15-20% partner-sourced revenue. This is also where the specialist/generalist fork becomes a real choice: a traditional partnerships specialist (often ex-AE, deep domain relationships, accelerates deal velocity in one ecosystem) becomes viable once there is enough deal flow in a single lane.

## Enterprise: dedicated headcount per partner tier or hyperscaler

Alliance headcount typically splits by named hyperscaler/GSI relationship rather than pooling into one channel role, because each hyperscaler runs its own program mechanics, tier ladder and certification/compliance load. Certified-headcount tracking - coordinating workforce certification planning against each partner's tier requirements - becomes an explicit director-level responsibility. A platform investment (PRM, account-mapping tooling) substitutes for administrative headcount in this model, not for named-relationship headcount.

Staffing imbalance risk specific to this tier: business development gets over-rotated when the alliance function reports into marketing (too much campaign/asset work, not enough deal structuring) and under-rotated when it reports into sales (program work crowded out by deal-sized work).

## PLG companies: a different job under the same title

PLG-motion companies invest disproportionately more in communities, integrations, affiliates, agencies and referral partnerships than in traditional reseller/channel partnerships - roughly 3x the affiliate-program adoption rate of the broader B2B growth index. Practically:

- A PLG-company "partnerships" req is more likely to screen for integration/marketplace fluency, developer-facing communication, and affiliate/agency program management than for channel deal-registration or co-sell process design.
- Affiliates and creators are treated as PLG-motion partners; referral and reseller partners are treated as sales-led-motion partners. Strong programs keep these as separate hiring tracks past the earliest generalist stage.
- The lines are blurring in both directions - pure-PLG companies are hiring sales teams for enterprise deals, and sales-led companies are building self-serve motions - so read a PLG-labeled posting for which half of the hybrid it actually needs.

# Compensation and offer scoring

Contents: why sources disagree by 2-3x · directional figures by title, with sources · comp structure by sub-discipline · the offer-scoring order.

## No single trustworthy benchmark exists

Sources disagree by 2-3x on the same title. For "Director of Partnerships": Salary.com reports roughly $206-215k median, while PayScale reports roughly $74k average with a 10th-90th percentile base range of $44k-$142k. The gap traces to methodology and population, not error: Salary.com skews toward tech/VC-backed company self-reports at the senior end; PayScale's self-reported sample skews wider and includes smaller/non-tech employers under the same title. Any figure quoted needs its source, population and date attached - quoting one number as "the" market rate misrepresents the spread.

## Directional figures by title (source stated with every number)

- VP Partnerships: Salary.com median ~$215k (2025). Related titles on the same source: Partnerships Lead ~$258k, VP of Strategic Partnerships ~$258k, Partnerships Director ~$207k, Head of Partnerships ~$133k, Partnerships Manager ~$133k, Partnerships Associate ~$78k, Partnerships Coordinator ~$75k.
- Partner Manager (tech-sector, crowdsourced): Levels.fyi reports a median around $226k total comp - a materially different population (large tech employers self-reporting total comp including equity) than the Salary.com figures above; never quote the two against each other as if comparable.
- Affiliate Marketing Manager: ZipRecruiter ~$82k average (most workers $66-99.5k); a separate source reports ~$74-125k progressing to $110-176k at director; another reports ~$64k average; a Glassdoor-derived synthesis reports ~$117k total pay once bonus/commission is included. The spread is partly real (SaaS vs. e-commerce vs. small-business affiliate programs pay very differently) and partly a base-vs-total-comp mismatch across sources.
- A specialist source exists for this field specifically: **Partnership Leaders' own compensation database/calculator**, built from practitioner-submitted data across Director of Partnerships, Partner Manager and Strategic Partnerships titles. Check it live rather than relying on the generic aggregators above.

## Compensation structure, by sub-discipline

- **Affiliate Manager**: commonly three-part - base salary, a performance bonus (roughly 10-30% of base at junior/mid levels, 30-50% at senior levels), and commission tied to revenue managed through the program. This commission-on-managed-revenue component distinguishes affiliate/partnerships comp from a flat-salaried marketing role, and from straight sales commission where the rep closes the deal directly.
- **Channel/Alliance Manager** (enterprise): more often base-plus-variable tied to partner-sourced or partner-influenced pipeline/revenue targets, mirroring quota-carrying sales comp shape - but the underlying attribution mechanics (sourced vs. influenced vs. attached vs. delivered) are contested in the field. Ask specifically which model triggers the variable before comparing two offers on their variable component alone.
- **Equity** appears at executive levels (VP/CPO) per the general VP-comp pattern, not as a partnerships-specific feature.

## Offer-scoring order

Score in this order - value, not the order most candidates negotiate in:

1. **The reporting line and its metric.** Sales, marketing, or its own function - each implies a different measurement and a different day-to-day. Ask outright in the loop.
2. **The attribution model behind any variable pay** - sourced, influenced, attached, or delivered revenue. Confirm before comparing two offers' variable components.
3. **The package itself** - base, bonus/commission structure, equity at senior levels, and whether a published range exists at all.

The package is the most negotiable component and, absent a clean reporting line, not the one that determines whether the job is what it claims to be.

# Entry curriculum

Contents: named practitioner accounts · the internal-transfer sequence, concretely · the external-entry route · certifications and why they don't gate hiring.

## Named practitioner accounts of breaking in

- **Alexis Petrichos** (Chili Piper) - entered via sales; frames the transfer explicitly as communication, negotiation and goal-alignment skills that let him structure partnership programs from scratch once he moved over.
- **Christina Cordova** - the generalist archetype: business development and partnerships combined with product-marketing work, managing engineering teams, running DEI initiatives, and hiring across growth PM and developer-advocate roles. Her path argues for breadth over a narrow partnerships specialization at the earliest stage of a company.
- **Sim Blaustein** - names the trigger for when a company creates its first dedicated partnerships seat: once founders are spending roughly 10+ hours a week responding to inbound or pursuing outbound partner requests, it makes sense to start a partnerships team. This is the internal-transfer route's precondition - someone already doing the work part-time is the default first hire.
- A Strategic Partnerships Manager, quoted in a practitioner roundup, gives the concrete internal-transfer tactic: "Put time on the right people's calendars. Ask them what they look for in a partnerships candidate." An Alliance Manager in the same piece adds the precondition: "you have to be a top performer... you'll be better served if you're at the top of your game."

## The internal-transfer route, concretely

1. Network with the partnerships team already inside the company - coffee chats, shadowing partner meetings.
2. Build a track record while still in the prior role: be the first on a sales team to fold partnerships into deal flow, showing initiative before asking for the move.
3. Build the business case with real numbers - pipeline or revenue attributable to partner-sourced work, and how partnerships shortened speed-to-market in a segment or region.
4. Ask for the move only from a position of standing.

## The external-entry route

For someone with no partnerships experience and no internal team to transfer from: target entry-level business development, account management or sales roles first. The field treats these as the transferable-skill feeder, not partnerships-specific junior roles - there is no equivalent to SDR/BDR as a dedicated first-rung partnerships title.

## Certifications - real, but non-gating

- **Partnerships Experience Academy (PXA)**, run by impact.com - the field's dominant named certification, free, tiered (fundamentals to expert), with over 50,000 professionals reported as having used it. Content covers the partnership lifecycle and the four-player affiliate/partnerships model; expert-tier content targets creators and publishers specifically, not brand-side partner managers.
- **ASAP's CA-AM and CSAP** sit on the alliance-management side specifically, cost money, and carry no independent outcome study.
- General finding: job postings consistently list these as "preferred," never "required." Practical experience and industry-network reputation outweigh any credential in this field - closer to DevRel's portfolio-driven hiring than to a licensed or exam-gated profession. Do not spend interview-prep or roadmap budget on certification-chasing.
- A general Google Analytics certification is cited as a lightweight, generically useful data-literacy signal for affiliate-manager candidates specifically, not a partnerships-specific credential.

# Interview prep playbook

Contents: the channel-manager loop, stage by stage · named case-study themes · the judgment test and negotiation role-play · story bank · employer-diligence questions.

## Channel/Partner Manager loop, documented pattern

1. Recruiter/HR phone screen - background and fit.
2. Hiring-manager round(s), often with cross-functional stakeholders from sales, marketing and product sitting in.
3. Behavioral questions plus scenario/case-study questions on channel strategy and partner conflict.
4. Technical/tooling questions - CRM, KPIs, analytics fluency.
5. At senior levels: a panel with multiple department leaders, often asking for a 30/60/90-day channel plan or a mock partner business review. Practitioners describe this stage as feeling like a general-manager interview - judged on cross-functional leadership, not deal execution alone.

There is no standard loop length or stage set - confirm formats with the recruiter before preparing, the same caution DevRel candidates are taught.

## Named case-study/scenario themes

- **Channel conflict resolution.** A near-simultaneous deal-registration clash between a partner and direct sales is the recurring scenario. The evaluated move is process discipline over loyalty: pull the deal-registration timeline and CRM activity, bring both reps into one conversation, and treat recurrence as a symptom of unclear rules of engagement rather than a one-off to arbitrate by gut feel.
- **Cross-functional collaboration.** How do you operate simultaneously with marketing, product and sales? Strong answers name concrete mechanisms, not "I communicate well" - co-building campaigns with marketing so MDF ties to sourced pipeline, running a feedback loop that carries partner input into the product roadmap, keeping rules of engagement clean so partner and direct teams work the same number instead of colliding.
- **Partner onboarding/enablement design.** How would you evaluate a new partner (expertise, target audience, market reach, compatibility), and what materials/cadence would you ramp them on?

## The judgment test and the negotiation role-play

Prepare both explicitly - they are rehearsable and neither has an obvious "right answer" to memorize, this field's version of DevRel's opinion round.

- **"Would you close this deal in January the exact same way you closed it in December, just to finish the quarter on target?"** The rewarded answer is no - the relationship, not the quarter, is the unit a partner manager optimizes, in contrast to a quota-carrying rep for whom the quarter is the unit.
- **"Walk me through the last partner you de-prioritized, and how you had that conversation."** Tests whether you have actually said no to a partner, not just built relationships.
- **The negotiation role-play**, when included: a two-sided simulation, candidate plus an interviewer or panel playing the counterparty, in a business-partnership or vendor-deal context with hidden constraints or interests you must surface through questioning rather than being told upfront. You are judged on how you structure win-win terms, handle objections, and defend (or find) a rational walk-away point - not on whether you "won." Expect a short brief with a pressure point and one or two optional positions, not a full script; the interviewer is probing improvisation, the same way a sales mock-call probes improvisation over polish.

## What has no comparably documented pattern

Affiliate Manager, Influencer/Creator Partnerships Manager and Referral Program Manager loops are not documented with anything specific to their structure - searches return generic marketing/BD question banks, not a loop pattern tied to these titles. Prepare from the role's own outcome metrics instead:

- **Affiliate:** program performance numbers you've owned, commission-economics literacy, network/tooling fluency.
- **Influencer/Creator:** campaigns you sourced and negotiated, platform-landscape fluency, and disclosure-compliance literacy (FTC rules).
- **Referral:** incentive-design decisions you made and their measured effect, cross-team coordination examples with marketing.

## Story bank

Bank five stories before any loop, each in two lengths (two minutes, thirty seconds):

1. A partner conflict you resolved, and the process fix that followed.
2. A partnership you sourced or negotiated from nothing.
3. A partner you de-prioritized, and how that conversation went.
4. A number you moved (partner-sourced pipeline, program revenue, campaign performance) with the mechanism named, not just the count.
5. A cross-functional fight you navigated between sales, marketing and product.

## Employer diligence questions

- What is the reporting line, and what metric does that department buy (see the CEO-vs-CRO reporting question)?
- Is there a written career matrix? Can I see it?
- What's the actual attribution model for partner-sourced revenue (sourced, influenced, attached, delivered)? This field has not standardized it, and it changes what "success" means in the role.
- For a first dedicated hire: what's the current weekly time-split the founders spend on partner work today?
- For a scale-up or enterprise role: how many active partners, and is enablement centralized or fragmented across teams?

# Posting red flags

Contents: why no named taxonomy exists · the three flagged patterns · the three questions any posting should answer.

## No field-specific taxonomy exists yet

DevRel has a named, citable framework for reading a bad posting (Joe Nash's gatekeeper/pit-trap taxonomy). Partnerships has no equivalent named taxonomy in circulation. What exists is general job-posting red-flag advice that happens to apply with unusual force to partnerships postings, because the role's boundaries - BD, relationship management, contract negotiation, marketing/sales enablement, sometimes program ops - are unusually easy to blur into one underspecified req. State this gap plainly rather than inventing a two-name taxonomy to mirror DevRel's.

## "You'll be wearing many hats"

The single most consistently flagged phrase across job-search red-flag sources, and it lands harder in partnerships than in most functions because the role already spans four adjacent disciplines before "many hats" adds anything. If a company can't clearly define the job, they likely want one person doing three roles at one salary.

**Practical test:** ask directly in the loop for a numeric time-split breakdown across the role's components (deal sourcing vs. account management vs. reporting vs. marketing collaboration). A hiring manager who answers with real numbers is describing an actual job; one who can't is describing a title in search of a job.

**Nuance:** not disqualifying at a true early-stage startup, where broad scope is the honest shape of the role (see the company-type-bar reference). The distinguishing test is whether the posting also shows undefined ownership and no stated ladder - breadth plus a stated path is a startup generalist role; breadth plus no stated path is the trap.

## Buzzword/hybrid titles

"Partnerships ninja," "growth hacker," or similar. General finding: titles like this signal the company doesn't know what it actually needs, will carry unrealistic expectations, or has an immature team culture. In partnerships specifically, this shows up as a posting collapsing partnerships, growth marketing and community-building into one hybrid title with no stated primary metric - the closest partnerships-specific echo of DevRel's "pit trap": ground-floor ownership of everything, no resources, no stated goal.

## Vague or absent compensation

"Competitive salary" with no range. Load-bearing here specifically because published benchmarks already disagree by 2-3x on the same title (see compensation-and-offer-scoring.md): a posting withholding its own number on top of unreliable public data leaves a candidate with no anchor at all. Treat an unpublished range as a stronger warning sign here than in a field with tight, trustworthy public comp data.

"Fast-paced environment" / "whatever it takes" paired with the above is a stronger overwork-culture signal than either alone, though neither is specific to this field.

## The three questions any posting should answer

1. The numeric time-split across the role's stated components.
2. The reporting line - sales, marketing, or its own function - since each measures the role on a different metric.
3. Whether a written career matrix or ladder exists at all.

A posting that can't answer any of the three is this field's closest operational proxy to a named trap.

# Role taxonomy and skills

Contents: the four sub-disciplines in detail · hard and soft skills, junior vs senior · the ladder finding.

## Affiliate Manager

Progression: Affiliate Coordinator -> Affiliate Manager -> Senior Affiliate Manager -> Director of Partnerships -> VP of Affiliate Marketing.

Screened on: demonstrable experience running affiliate programs or performance marketing, web-analytics/data literacy, familiarity with affiliate-network tooling. A marketing or business degree helps at the first job and stops mattering once a track record exists.

The level-defining shift is reporting scope, not tenure: coordinators report activity (clicks, conversions, commissions paid); directors report outcomes (revenue contribution, CAC efficiency, incrementality, channel ROI against paid media). A candidate who can only talk in click/conversion terms reads as capped below director regardless of years in seat. Typical time to mid-level: 4-6 years of good performance at a growing operator - the step into people management is the steep one, since lower levels rarely build management reps on the job.

## Influencer/Creator Partnerships Manager

Almost never a direct point of entry: a specialist track built on top of broader marketing or social-media experience, not an entry-level hire in its own right. Candidates arrive via adjacent roles (social media, brand partnerships, account management, digital marketing) more often than a dedicated junior influencer track.

Rough progression: entry-level social/digital marketing (foundation) -> specialist, 2-4 years, owns outreach/execution/reporting on a channel -> manager, 2-4 years, owns end-to-end campaigns: sourcing, negotiation, timeline, performance -> senior/leadership, broader strategy, team management, cross-functional executive exposure, budget influence.

Screened on: communication and negotiation skill, working knowledge of the current platform/creator landscape, analytics tool fluency, and - increasingly load-bearing - FTC/advertising-disclosure compliance literacy for the campaigns run. Postings commonly ask for roughly 4 years in marketing or user-growth roles inside tech or entertainment for the manager-level seat, not a fixed credential.

## Referral Program Manager

Two unrelated occupations share this title. Disambiguate which one a posting means before anything else applies:

- **Customer/growth referral** - owns refer-a-friend program design, incentive structure, tracking, and CRM-side coordination with marketing.
- **Employee-referral recruiting** - an HR/TA function: internal referral programs for hiring, works with HR and hiring managers, tracks referral-to-hire conversion.

Screened on, for the customer/growth track: program strategy and incentive design, data analysis of referral performance, cross-team coordination with marketing and product, CRM/tracking-platform fluency. No published multi-rung ladder exists for this title; it tends to sit as one IC role inside a growth or lifecycle-marketing team rather than anchoring its own career track. The honest next move from this seat is usually lateral into a broader referral-plus-affiliate-plus-loyalty remit, or into a Partner Marketing lane, not a same-title promotion.

## Channel/Alliance Manager and the strategy-level roles

| Role                                       | Mandate                                                                                                                                | Decides                                           |
| ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- |
| Partner/Channel Manager (CAM/PAM)          | Day-to-day portfolio: recruiting, onboarding, enablement, deal registration, satisfaction                                              | Which deals to support, partner-level plans       |
| Alliance Lead                              | A handful of strategically consequential partnerships (GSIs, hyperscalers, tech alliances); co-sell, co-innovation, exec relationships | Joint GTM motions, joint solution investment      |
| Head of Partnerships / CPO / Channel Chief | Strategy, business planning, operating cadence, attribution reporting, headcount and budget                                            | Program strategy, tiering, budget, partner types  |
| Partner Marketing                          | JVPs, co-marketing, through-channel marketing, MDF-funded activity                                                                     | Campaign design, MDF allocation to marketing      |
| Partner Operations                         | Onboarding workflows, reporting, PRM admin, attribution, integrations                                                                  | Tooling config, data/attribution rules            |
| Partner Enablement Manager                 | Partner onboarding design, role-based learning tracks, certification, content curation                                                 | Curriculum, certification design, refresh cadence |

Sharpest functional distinction: a channel manager is measured on pipeline volume and deal-registration counts across a broad population; an alliance manager on depth of executive engagement and co-sell revenue across a few large partners.

## Hard and soft skills, junior vs senior (applies across the business-partner side of the field)

| Dimension                        | Junior/entry signal                                                   | Senior signal                                                                                                     |
| -------------------------------- | --------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| Relationship read                | Understands the partner org chart - who signs, who blocks             | Also maps motivations and stakes across the partner's org, not just its structure                                 |
| Reporting                        | Reports activity: partners recruited, deals registered, campaigns run | Reports impact: partner-sourced revenue, ACV contribution, retention, CAC or incrementality versus other channels |
| Focus under competing priorities | Executes one motion at a time                                         | Holds partner, customer and internal sales process in view simultaneously without losing the thread               |
| Deal orientation                 | Optimizes to close inside the current period                          | Treats the relationship, not the quarter, as the unit of measurement                                              |
| Judgment on de-prioritization    | Rarely has said no to a partner                                       | Can walk through a specific partner de-prioritized, why, and how that conversation went                           |

## The ladder finding

Unlike sales (Bridge Group's published SDR-to-AE benchmarks) or DevRel (a documented six-rung IC ladder scored on five dimensions), partnerships has no equivalent cross-company published career ladder.

- Title proliferation with no standardization - LinkedIn alone carries roughly 142,000 "Channel," 133,000 "Partnerships" and 23,000 "Alliances" titles, so the same seniority band can carry very different titles at different companies.
- The one formally recognized senior tier is the Chief Partner Officer / VP Partner Ecosystem role - the fastest-growing C-level title tracked in the space, but a single top-of-ladder marker, not a rung-by-rung framework.
- Practitioners distinguish a VP (an execution role, still measured on program delivery) from a CPO/C-level role (sets company strategy) - the closest thing to a two-tier leadership split the field publishes.

Ask a target employer for a written career matrix first. When none exists, use the mandate/decides table above as the closest available level differentiator.

---
name: partnerships-career
description: Plans a partnerships career from the candidate side across the field's four sub-disciplines - channel/alliance, affiliate, influencer/creator, referral. Covers the internal-transfer entry tactic, the company-type hiring bar, channel-manager interview-loop prep including the negotiation role-play and the "same deal in December as January" judgment test, job-posting red-flag reads, and offer evaluation gated on live verification since published comp benchmarks disagree by 2-3x. States plainly that no cross-company career ladder is published for this field. Use whenever the user asks how to break into partnerships, prep a partner-manager interview, read a posting, or evaluate an offer. Do NOT use for the hiring/employer side (mbfinotti/partnerships-skills@partnerships-hiring).
license: MIT
metadata:
  author: Maya-Beth Finotti
  version: "1.2.7"
---

# Partnerships Career

You are a partnerships career coach for one person. Help them choose a sub-discipline, break in from wherever they stand today, prepare for the loop this field actually runs, read a posting for its real shape, and evaluate an offer against a market with no reliable published comp benchmark.

Out of scope, hand off instead: the hiring loop, scorecards, and job postings from the employer side - mbfinotti/partnerships-skills@partnerships-hiring is the mirror image of this skill. If the user is hiring rather than job-hunting, say so in one line and route them there.

## Interview

Ask one question at a time, multiple-choice where possible. Skip anything already answered. Questions 7-9 re-rank the entry-path and interview-prep sections before anything else does - ask them before producing a plan.

1. Which partnerships world: (a) channel/alliance and business-partner strategy, (b) affiliate program management, (c) influencer/creator partnerships, (d) referral program management, (e) undecided - recommend one.
2. Where are you now: (a) not in partnerships yet - sales, BD, account management, or marketing (b) already doing partnerships work informally inside a current role (c) junior/mid partnerships IC (d) senior IC or manager (e) director and above.
3. What's the goal: (a) break in for the first time (b) move from one sub-discipline to another (c) prepare for a specific interview loop (d) get to the next rung (e) evaluate a specific offer or posting.
4. Target company type: (a) early-stage startup, likely the first dedicated hire (b) scale-up building a dedicated team (c) enterprise with per-hyperscaler headcount (d) PLG company where integrations/affiliates dominate over channel sales (e) undecided.
5. If (2a): are you already fielding partner inquiries informally inside your current role, and roughly how many hours a week?
6. What public track record exists: partner-sourced pipeline or revenue you can point to, a program you built, relationships you can name?
7. Deadline: interviewing now, 1-3 months, 6-12 months, or no deadline?
8. One-off move or the first of several - are you optimizing for the next role, or a durable position in this field?
9. Effort ceiling: hours per week available, and whether a lateral or downward move is acceptable to get in.

## Choosing a sub-discipline

Partnerships is not one job. The four sub-disciplines run on different skills, different sourcing pools, and different comp structures:

| Sub-discipline                          | Core of the job                                                                    | Screened on                                                                                                              |
| --------------------------------------- | ---------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| Channel/Alliance Manager                | Portfolio management, deal registration, co-sell, executive relationships at scale | Relationship read of the partner org, cross-functional juggling, negotiation                                             |
| Affiliate Manager                       | Program operations, network/tooling fluency, commission economics                  | Data literacy, performance-marketing track record                                                                        |
| Influencer/Creator Partnerships Manager | Sourcing, negotiation, campaign execution, compliance                              | Communication, platform/creator-landscape fluency, FTC disclosure literacy                                               |
| Referral Program Manager                | Incentive design, tracking, cross-team coordination with marketing                 | Program strategy, data analysis - and disambiguate this title from employee-referral recruiting before applying anywhere |

The sub-disciplines are not ranked against each other - which is efficient depends entirely on the seat you already occupy (Q2) and the world you picked (Q1), so an abstract ordering would be false precision. Full role detail, typical progression, and what separates junior from senior in each: [references/role-taxonomy-and-skills.md](./references/role-taxonomy-and-skills.md).

## Entry paths

**No fixed entry path exists in this field.** Sales, business development, account management, and marketing all feed partnerships, and none is a prerequisite - the field's own version of "every verified path runs through adjacent relationship-owning work, not a credential."

Two routes reach a first partnerships role, and they are not equally efficient:

- **efficiency:** internal transfer > external entry via an adjacent role.
- **effort** (what it costs before anyone pays you for the new title): internal transfer, near zero - the work happens on company time, in a role you already hold > external entry, months of building a track record in sales/BD/marketing first, then applying cold.
- **value** (what it opens): external entry into a sub-discipline-specific seat (e.g. applying directly for an Affiliate Manager role) == internal transfer, since both land the same title; internal transfer wins on speed, not on ceiling.

**Internal transfer, concretely:**

1. Notice you are already fielding partner inquiries, or start noticing on purpose - this is the field's dominant first-hire trigger (see [references/entry-curriculum.md](./references/entry-curriculum.md)).
2. Network with the partnerships team already inside the company - shadow a partner meeting, ask what they look for in a candidate.
3. Build a track record in your current seat first: be the one who folds partnerships into deal flow, and get to a position of standing before asking - "you have to be a top performer" is a repeated condition, not optional politeness.
4. Build the business case with real numbers: pipeline or revenue attributable to the partner-adjacent work you've already done.
5. Ask for the move from that position of standing, not from enthusiasm alone.

**External entry**, for someone with no internal team to transfer from: target entry-level business development, account management or sales roles first, and treat them as the transferable-skill feeder - there is no SDR/BDR-equivalent dedicated junior partnerships title to apply for directly.

**What this order starves.** External entry is the only route into some seats with zero internal partnerships function to transfer from at all - promote it to the only option when Q4 names an early-stage startup with no existing team, since there is nothing to transfer into.

**Re-rank against this user.** A user already at (2b) - doing the work informally - should treat the internal-transfer sequence as already underway, not as a plan to start; skip straight to step 3.

Certifications (impact.com's PXA, ASAP's CA-AM/CSAP) exist and are real, but every posting lists them as "preferred," never "required" - do not spend interview-prep budget chasing a certificate over a track record. Full detail: [references/entry-curriculum.md](./references/entry-curriculum.md).

## Company type and target calibration

Never treat one posting as representative of the whole field - the hiring bar and the actual day-to-day differ sharply by company type:

- **Early-stage startup, first dedicated hire:** a versatile generalist who can build a program from scratch, not a specialist. Two named failure modes to watch for in your own candidacy: being too senior for hands-on execution, or too generalist with no real go-to-market reps to prioritize what will actually work.
- **Scale-up:** specialization becomes viable - a traditional channel/alliance specialist with deep domain relationships fits once there is enough deal flow in one lane.
- **Enterprise:** headcount splits by named hyperscaler or GSI relationship, not one pooled channel role - certification and compliance tracking against each partner's own program becomes an explicit job responsibility.
- **PLG company:** "partnerships" more often means integrations, marketplace, affiliate and agency programs than channel-sales deal registration - read a PLG-labeled posting for which half of the hybrid it actually needs before assuming the title predicts the work.

Full comparison, timing signals for when a company formalizes the role, and the two named hiring failure modes: [references/company-type-bar.md](./references/company-type-bar.md).

## Interview preparation

Coverage is asymmetric across the four sub-disciplines - say this to the user plainly rather than pretending equal prep material exists everywhere.

**Channel/Partner Manager loops are well documented:**

1. Recruiter/HR screen.
2. Hiring-manager round(s), often with sales/marketing/product stakeholders sitting in.
3. Behavioral and scenario questions on channel strategy and partner conflict.
4. Technical/tooling questions - CRM, KPIs, analytics fluency.
5. At senior levels: a multi-department panel, often a mock 30/60/90-day channel plan or a mock partner business review - practitioners describe this stage as feeling like a general-manager interview.

Two named tests to prepare for explicitly, both rehearsable with no obvious "right answer" to memorize - this field's version of DevRel's opinion round:

- **The judgment test:** "Would you close this deal in January the exact same way you closed it in December, just to hit the quarter?" The rewarded answer is no - the relationship, not the quarter, is the unit a partner manager optimizes.
- **The de-prioritization follow-up:** "Walk me through the last partner you de-prioritized, and how that conversation went." Tests whether you have actually said no to a partner, not just built relationships.
- **The negotiation role-play**, when the loop includes one: a two-sided simulation with hidden constraints you surface through questioning. You are judged on how you structure win-win terms and defend a walk-away point, never on whether you "won."

**Affiliate Manager, Influencer/Creator Partnerships Manager, and Referral Program Manager loops have no comparably documented public pattern.** Do not manufacture loop detail that doesn't exist - prepare instead from the role's actual outcome metrics (program performance, commission economics, campaign results you can point to) and treat the channel-manager pattern above only as a loose directional analogue, never as what to expect verbatim.

Full story bank, per-format prep, and employer-diligence questions: [references/interview-prep-playbook.md](./references/interview-prep-playbook.md).

## Reading a job posting

No named gatekeeper/pit-trap taxonomy exists for this field the way DevRel has one - say that plainly. What exists is general job-posting red-flag language that lands with unusual force here, because the role already spans BD, account management, negotiation and marketing enablement before anything else is added:

- **"You'll wear many hats"** - the single most consistently flagged phrase. Not disqualifying at a genuine early-stage startup (see Company type above), where broad scope is the honest shape of the role. The distinguishing test: does the posting also show a stated ownership boundary and a path forward? Breadth plus a stated path is a startup generalist role; breadth with no stated path is the trap. Ask directly for a numeric time-split across the role's components.
- **Buzzword/hybrid titles** ("partnerships ninja", a role collapsing partnerships, growth marketing and community into one title with no primary metric) - signals the company hasn't decided what it needs.
- **Vague compensation** ("competitive salary", no range) - a stronger signal here than in most fields, because the public comp benchmarks already disagree by 2-3x (see Compensation below); a posting withholding its own number on top of that leaves you with no anchor at all.

Three questions any posting should be able to answer: the numeric time-split, the reporting line (sales, marketing, or its own function - each measures the role differently), and whether a written career matrix exists at all. A posting that can't answer any of the three is this field's closest operational proxy to a named trap. Full detail: [references/posting-red-flags.md](./references/posting-red-flags.md).

## The ladder

**No published cross-company career ladder exists for this field**, unlike sales (Bridge Group's benchmarks) or DevRel (a documented six-rung ladder). What exists instead:

- Extreme title proliferation with no standardization - the same seniority band carries very different titles at different companies.
- One formally recognized senior tier: Chief Partner Officer / VP Partner Ecosystem, tracked as the fastest-growing C-level title in the space - a single top-of-ladder marker, not a rung-by-rung framework.
- A two-tier leadership split practitioners do distinguish: a VP is still an execution role, measured on program delivery; a CPO/C-level role sets company strategy.

Say this thinness plainly rather than manufacturing rungs that don't exist. Ask the target employer for a written career matrix first; when none exists, use the mandate/decides columns in [references/role-taxonomy-and-skills.md](./references/role-taxonomy-and-skills.md) as the closest available level differentiator.

## Scoring an offer and compensation

**Never quote an undated, unsourced partnerships salary figure.** Public sources disagree by 2-3x on the same title - Salary.com and PayScale differ by roughly 3x on "Director of Partnerships" alone, because they sample different populations under an unstandardized title. Any figure you use needs its source, population and date attached.

- The field's own specialist benchmark is **Partnership Leaders' compensation database** - check it live rather than relying on generic aggregators.
- Compensation structure itself is informative even where the level is not: Affiliate Manager pay is commonly three-part (base, a performance bonus, and commission tied to revenue managed through the program) - a distinct shape from a flat-salaried marketing role. Channel/alliance comp more often follows a sales-shaped base-plus-variable tied to partner-sourced or partner-influenced targets - ask specifically which attribution model (sourced, influenced, attached, delivered) triggers the variable, since the field itself has not settled this.
- Score components in this order: the reporting line and its metric (does the role report to sales, marketing, or its own function - each implies a different measurement) before the number itself. A senior-sounding title reporting into the wrong function is a worse offer than a lower title with a clean reporting line.

Full comp tables with sources, and the offer-scoring worksheet: [references/compensation-and-offer-scoring.md](./references/compensation-and-offer-scoring.md).

## Failure modes

- Applying to a "many hats" posting at a scaled company as if it were the honest startup-generalist shape - check the company-type row first.
- Treating the channel-manager interview pattern as universal across all four sub-disciplines.
- Quoting a single comp number without its source and population.
- Chasing a certification (PXA, CA-AM) as if it gates hiring, when every posting lists it as preferred, not required.
- Asking for an internal transfer before reaching a position of standing in your current seat.
- Confusing Referral Program Manager (customer/growth) with the employee-referral-recruiting role of the same title.
- Presenting a manufactured career ladder as if this field had one.

## Objective and measurement

A deliverable from this skill passes only when:

1. The target sub-discipline is named explicitly (not just "partnerships").
2. Every entry-path or interview-prep recommendation is labeled for the sub-discipline it actually applies to, and thin coverage (affiliate, influencer, referral loops) is stated as thin, not filled in with invented detail.
3. Any compensation figure carries its source, population and date, or is marked as needing live verification.
4. The plan sets a dated review point.

## Reference

- [references/role-taxonomy-and-skills.md](./references/role-taxonomy-and-skills.md) - full role table across all four sub-disciplines, hard/soft skills junior vs senior, the ladder finding.
- [references/entry-curriculum.md](./references/entry-curriculum.md) - the internal-transfer sequence, external-entry route, certifications and why they don't gate hiring.
- [references/company-type-bar.md](./references/company-type-bar.md) - the four company-type rows, timing signals, and the two named startup-hire failure modes.
- [references/interview-prep-playbook.md](./references/interview-prep-playbook.md) - per-format prep, the judgment test, the negotiation role-play, story bank, employer-diligence questions.
- [references/posting-red-flags.md](./references/posting-red-flags.md) - the red-flag language and the three questions to ask any posting.
- [references/compensation-and-offer-scoring.md](./references/compensation-and-offer-scoring.md) - comp tables with sources, and the offer-scoring worksheet.
- See `mbfinotti/partnerships-skills@partnerships-hiring` for the employer's side of this table.
- See `mbfinotti/partnerships-skills@partner-tiering` for how a target employer's own partner-tier structure works, useful diligence before an alliance-role interview.