Partner Business Manager (NY,NJ,PA)

We need to output HTML fragment with sections: About the role (but we already have a heading "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. We have content: "About DevRev" (company description) then "About the role" (intro). Then "What you'll do" (responsibilities). Then "What we're looking for" (requirements/qualifications). Then "Nice to have" (maybe skills). Then "What we offer" (benefits). Also location info: "Based in or willing to work from New York or Texas." and later "This role can be based in NY, NJ or PA." So location details. We need to decide sections: About the role (maybe we can combine company description? The instruction says use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should have headings: About the role (maybe includes company overview?), Responsibilities (What you'll do), Requirements (What we're looking for), Skills (Nice to have?), Benefits (What we offer). Possibly also Pay? Not given explicit salary numbers, just "Competitive base salary + commission structure." That's pay info, so we could include Pay section. Schedule? Not given. So we may omit Schedule. We must not create sections with filler like "commensurate with experience". We have actual content for Pay: "Competitive base salary + commission structure." That's substantive. So include Pay. Benefits: "Equity participation. Full benefits package. Opportunity to shape DevRev's partner program from the ground up." That's substantive. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all bullet points. We need to use

• for any list of duties/requirements/benefits, and

  for prose. Thus:

  About the role

  At DevRev, we're building the future of work with Computer – your AI teammate. Unlike traditional tools, Computer unifies all your data sources, tools, and workflows into a single AI-ready platform, giving employees real-time insights, proactive suggestions, and powerful agentic actions. It extends your existing software with AI-native apps and agents that work alongside your teams and customers – updating workflows, coordinating across teams, and eliminating repetitive work. We call this Team Intelligence: human-AI collaboration that breaks down silos, brings people back together, and frees you to solve bigger problems. Backed by Khosla Ventures and Mayfield with $150M+ raised, DevRev is trusted by global companies across industries.

  We're looking for a Channel Partner Manager with a startup mindset and a builder's instinct. You'll own the full lifecycle of partner relationships end to end — from acquisition through business outcomes — with no hand-offs and no waiting for someone else to figure it out. You'll identify and recruit high-potential partners, onboard them effectively, build joint business and channel plans, develop co-created solutions, and relentlessly measure and drive results. This isn't a maintain-the-program role. It's a build-the-program role — high-impact, high-visibility, and central to DevRev's go-to-market expansion across the United States.

  Then Responsibilities:

  Responsibilities

  • Drive partner acquisition — Identify, prospect, and recruit high-value channel partners (VARs, resellers, SIs, and technology alliances) aligned with DevRev's ICP and growth strategy.
  • Own partner onboarding end to end — Design and execute a structured onboarding experience that gets partners productive fast — including technical readiness, sales alignment, and go-to-market activation.
  • Build and drive business plans — Co-develop joint business plans and channel plans with each partner, setting clear revenue targets, pipeline commitments, and milestones.
  • Measure and drive business outcomes — Define partner KPIs, track pipeline contribution, revenue attainment, and deal velocity. Hold partners accountable and course-correct when results fall short.
  • Develop joint solutions — Work with partners and DevRev's product team to co-create integrated solutions, use cases, and offerings that differentiate in the market and accelerate customer adoption.
  • Enable continuously — Deliver ongoing training, certifications, and enablement programs that deepen partner expertise and independence.
  • Align with direct sales — Collaborate closely with DevRev's sales organization to coordinate on accounts, avoid channel conflict, and maximize co-sell impact.
  • Advocate internally — Be the voice of your partners inside DevRev, working with marketing, product, and customer success to ensure partner needs are met.
  • Represent DevRev externally — Attend partner events, QBRs, and industry conferences to strengthen relationships and build brand presence.
  Then Requirements/Qualifications: The "What we're looking for" includes required qualifications. We'll put under

  Requirements

  maybe also Qualifications. But we have both Requirements and Qualifications headings possible. The instruction says we can use those headings. We need to decide: maybe combine into Requirements (or Qualifications). Since they ask for both headings as examples, we could split: Requirements (experience, mindset, etc.) and Qualifications (maybe specific skills). But the content includes: "4–7 years of experience in channel sales, partner management, or alliances — ideally in SaaS or enterprise software." That's experience. "Startup mindset — you operate with urgency, resourcefulness, and zero entitlement." etc. "Builder at heart — you've created something from scratch before..." etc. "End-to-end owner — you take full accountability..." etc. "Proven track record of acquiring partners and scaling those relationships into measurable revenue." "Experience building joint business plans and holding partners to outcome-based metrics." "Strong understanding of the SaaS go-to-market landscape and partner ecosystem dynamics." "Excellent communicator — comfortable presenting to C-level stakeholders at partner organizations." "Based in or willing to work from New York or Texas." These are requirements/qualifications. Then "Nice to have" includes: "Experience co-developing joint solutions or integrations with channel partners." "Background in CRM, customer support, or DevOps tooling." "Existing relationships with SIs or resellers in the mid-market or enterprise space." Thus we can have:

  Requirements

  • 4–7 years of experience in channel sales, partner management, or alliances — ideally in SaaS or enterprise software.
  • Startup mindset — you operate with urgency, resourcefulness, and zero entitlement. You don't wait for playbooks; you write them.
  • Builder at heart — you've created something from scratch before (a partner program, a territory, a team) and you're energized by ambiguity, not paralyzed by it.
  • End-to-end owner — you take full accountability from strategy through execution through outcomes. No "that's not my job" in your vocabulary.
  • Proven track record of acquiring partners and scaling those relationships into measurable revenue.
  • Experience building joint business plans and holding partners to outcome-based metrics.
  • Strong understanding of the SaaS go-to-market landscape and partner ecosystem dynamics.
  • Excellent communicator — comfortable presenting to C-level stakeholders at partner organizations.
  • Based in or willing to work from New York or Texas.
  Then maybe

  Qualifications

  could be empty? Better not to create empty heading. So we could incorporate Nice to have under Skills heading. Thus:

  Skills

  • Experience co-developing joint solutions or integrations with channel partners.
  • Background in CRM, customer support, or DevOps tooling.
  • Existing relationships with SIs or resellers in the mid-market or enterprise space.
  Then Benefits:

  Benefits

  • Competitive base salary + commission structure.
  • Equity participation.
  • Full benefits package.
  • Opportunity to shape DevRev's partner program from the ground up.
  But note that "Competitive base salary + commission structure." is pay info; we could also have a Pay section. However we already included it in Benefits. The instruction says: "Prefer a few substantive sections over many thin ones." So we could combine pay and benefits into Benefits. But they gave example headings including Pay, Benefits. If we put pay in Benefits, it's okay. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states "Competitive base salary + commission structure." That's pay. It also states equity participation, full benefits package, opportunity to shape program. So we could have a Benefits section that includes all those. That's fine. We also have location info: "Based in or willing to work from New York or Texas." and later "This role can be based in NY, NJ or PA." That's location details. Should we include location? Not a heading given. Could be placed in a

  under About the role or maybe as a separate section like Location? Not in allowed headings. Probably we should incorporate location into Requirements (since it's a requirement) or maybe as a separate

  after Requirements. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." Location is minor metadata? Could be folded into a short

  . But we already have location in Requirements list as an item. That's okay. We also have "Based in or willing to work from New York or Texas." and later "This role can be based in NY, NJ or PA." Slight discrepancy. We need to preserve all substantive information; we should not drop either. So we need to include both statements. Could combine: "Based in or willing to work from New York or Texas; this role can be based in NY, NJ, or PA." That preserves both. Thus in Requirements list we could have two items: one for location? Or we could have a separate

  after Requirements:

  Based in or willing to work from New York or Texas; this role can be based in NY, NJ, or PA.

  But we already have location as a bullet; maybe better to keep as bullet but also include the second statement. Let's incorporate both: "Based in or willing to work from New York or Texas; this role can be based in NY, NJ, or PA." as a single bullet. Thus Requirements bullet list includes that. Now we need to ensure we don't create any empty sections. We have About the role, Responsibilities, Requirements, Skills, Benefits. That's five sections. Check that we haven't missed any substantive info: The "About DevRev" description we included in About the role section. The "About the role" introductory paragraph we included. The "What you'll do" we turned into Responsibilities. The "What we're looking for" we turned into Requirements. The "Nice to have" we turned into Skills. The "What we offer" we turned into Benefits. We also need to include the statement about "This role can be based in NY, NJ or PA." We incorporated into Requirements bullet. Check for any other info: "Competitive base salary + commission structure." included in Benefits bullet. "Equity participation." included. "Full benefits package." included. "Opportunity to shape DevRev's partner program from the ground up." included. We also have "Based in or willing to work from New York or Texas."