Partner Business Manager

We need to output HTML fragment with sections: About the role? Actually "About The Role" is a heading. Also "Background And Experience", "What you'll do", "What we're looking for", "Nice to have", "What we offer". Also location info maybe part of About The Role? The location appears in "Location: North East (NY, PA, NJ) or Chicago only." Also later "This role can be based in NY, PA, NJ and Chicago only." Should we include location? It's not a section heading like Pay/Schedule/Benefits. We can embed location in a paragraph under About The Role or separate? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map sections accordingly. The posting has sections: About DevRev (company description) maybe not needed? 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. We need to preserve all substantive information. Should we include About DevRev? It's not a required heading but we could include as a

maybe under a heading? The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can have sections like About the role, Responsibilities (maybe "What you'll do"), Requirements/Qualifications (maybe "What we're looking for" and "Background And Experience"), Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have content: - About DevRev (company overview) - could be a short paragraph before sections. - About The Role: description of role. - Background And Experience: details about candidate's background (maybe not needed as requirement? It's describing ideal candidate's background? Actually it's describing the candidate's current situation? It reads like a description of a specific person? Might be a sample candidate? It seems like they are describing a hypothetical candidate's background? It's weird. But we can treat as part of "What we're looking for" or "Background And Experience". Might be considered as part of qualifications. - What you'll do: responsibilities. - What we're looking for: qualifications/requirements. - Nice to have: preferred qualifications. - What we offer: benefits. - Location: mention location restrictions. - Pay: Not explicitly stated; only "Competitive base salary + commission structure." That's pay info. So we can include Pay section with that sentence. - Benefits: "Full benefits package." plus equity participation, opportunity to shape program. So Benefits section. - Schedule: Not mentioned. So we should not create Schedule section. - Skills: Could be extracted from qualifications: strong communicator, etc. But we could put under Skills section. We need to avoid filler like "commensurate with experience". Not present. We must not include boilerplate like EEO etc. Remove that. We must not include application instructions. We must preserve all substantive information. Let's extract substantive content: Company description: "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." About The Role: "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. Location: North East (NY, PA, NJ) or Chicago only." Background And Experience: This section seems to describe a specific candidate's background, but it's part of the posting? It reads like they are describing the ideal candidate's current role? Actually it's describing a candidate's profile: "Currently a solo marketer covering marketing, events, SDR, and pipeline follow-up — broad, high-autonomy scope. Mentors junior field marketers and founders on event strategy. Previously partnered with Christopher Martin on ~3 sponsored events via Startup Grind, so she comes with an existing tie into DevRev's network. Business acumen Demonstrated strong judgment: turned down a misaligned Dreamforce partnership because the partner was targeting enterprise rather than her ICP — prioritizes pipeline quality over volume. Bias to action: when SDRs produced zero invites for an upcoming dinner, she personally stepped in and invited 12 guests. Frequently mistaken for the CEO at events — executive-level presence and ownership. Network Self-described "super connector" in the Bay Area startup scene. Strong relationships with Startup Grind and similar organizations, which approach her to recruit sponsors rather than the reverse. Fit for the role Comfortable with the dual scope of field marketing plus events and understands how the two connect. Bay Area based — aligns with the West Tier-1 city requirement. Strong communication and rapport; described her first call with Laura as a "tête-à-tête, not an interview." Areas to validate in later rounds Metrics rigor: how she attributes events/campaigns to sourced vs. influenced pipeline. Handoff discipline: how she passes engagements into sales/SDR follow-up and retargeting so momentum compounds. AI and tooling: where she uses AI to speed up research and personalization." This seems like they are describing a candidate's background as an example? Might be part of "What we're looking for"? But it's very specific to a person. However we must preserve all substantive information. So we need to include it somewhere. Perhaps under a section "Background And Experience" as a heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those categories. It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for those sections if present. It doesn't say we cannot use other headings, but better to stick to those. However "Background And Experience" could map to "Requirements" or "Qualifications". But the content is describing a candidate's current role, not a requirement. Might be better to treat as part of "What we're looking for" (qualifications). But it's very narrative. We could create a section "About the candidate" but not in list. Safer to keep as a paragraph under "What we're looking for" or maybe under a separate heading "Background And Experience" but that is not in the prescribed list. The instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but the examples are those. I'd stick to those headings only. So we need to map content to those headings. Let's map: - About the role: includes description of role, location. - Responsibilities: "What you'll do" list. - Requirements / Qualifications: "What we're looking for" (mandatory) plus maybe "Background And Experience" as part of qualifications? Could combine. - Skills: maybe extract communication, etc. - Benefits: "What we offer". - Pay: "Competitive base salary + commission structure." - Schedule: not present, omit. We also have "Nice to have" which could be under "Qualifications" as preferred qualifications. We need to preserve all substantive information, so we need to include the nice-to-have items. We also need to include the location restriction. We need to include the company description maybe as a preamble before sections, as a

. We must not include boilerplate like EEO. Now craft HTML. Structure:

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.

About the role

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. Location: North East (NY, PA, NJ) or Chicago only.

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.

Qualifications

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,