National Partner Manager, AHEAD

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Key sections: Location: Chicago, Illinois — Remote, Chicago-based Travel: Approximately 30–50%, including regular partner meetings and a monthly New York cadence Reports to: Director, Partner Sales Role Overview: description. Level & Scope Definition: description. Responsibilities: bullet list. What Success Looks Like: maybe part of responsibilities or separate? Could be considered part of role overview. But we can include as part of responsibilities or separate? The instruction: include a section ONLY when posting has real, specific content for it. We have responsibilities content. We have qualifications (Must-Have, Preferred, Experience Guidelines). We have Benefits. We have Compensation Transparency (Pay) but not specific numbers; they say click HERE to view compensation ranges. That is not specific numbers; it's a link. Should we include Pay section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (list). It does not state specific pay numbers; it references compensation transparency but not actual numbers. So we should not include Pay section because no specific compensation stated. Schedule: travel 30-50% etc. That's schedule/travel info. Could be considered Schedule section? The posting includes travel percentage. That's schedule info. We could include a Schedule section with that detail. However the rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state travel approx 30-50%, so we can include Schedule. Benefits: they list benefits. So include Benefits. About the role: we have Role Overview, Level & Scope Definition. Could combine into About the role section. Responsibilities: bullet list. Qualifications: Must-Have, Preferred, Experience Guidelines. Could be under Qualifications. Skills: maybe not separate; we could embed in Qualifications. But we could create Skills section if there is explicit skills list. Not really; qualifications include skills. Might not need separate Skills. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. Not include Job ID. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So remove the equal opportunity employer paragraph, privacy notice, recruitment agency note, etc. We must preserve all substantive information. So keep location, travel, reports to, role overview, level & scope, responsibilities, what success looks like, qualifications (must-have, preferred, experience guidelines), about Nasuni (maybe part of About the role? Actually About Nasuni is company description; could be included in About the role or separate? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. About Nasuni is not one of those headings. Could we include it under About the role? Probably yes, as part of role overview. But we might also include a separate section like "About Nasuni" but not allowed headings. So we incorporate into About the role. We need to ensure we don't invent or summarize away detail. Keep specifics. Let's extract details. Location: Chicago, Illinois — Remote, Chicago-based Travel: Approximately 30–50%, including regular partner meetings and a monthly New York cadence Reports to: Director, Partner Sales Role Overview: Nasuni is hiring a National Partner Manager to own and accelerate our strategic partnership with AHEAD. You will turn an established relationship into a scalable growth engine through joint planning, executive alignment, field activation, demand creation, and disciplined pipeline execution. This is a single-partner national role with direct revenue accountability. It is for a channel leader who produces results through people who do not report to them—not a portfolio manager or direct seller who personally runs every opportunity. Level & Scope Definition: You will operate with significant autonomy as Nasuni’s business owner for AHEAD, setting strategy and governance while coordinating Sales, Sales Engineering, Marketing, Customer Success, and executive resources. The role balances long-range strategy with hands-on program execution and has no direct reports. Year-one scope is North America; international planning may follow as the partnership develops. Responsibilities list: - Own annual and quarterly joint business plans, including targets, governance, accountabilities, investments, and executive reviews. - Build durable, multi-threaded relationships across AHEAD sales, alliances, engineering, services, and marketing leadership. - Translate partner economics—including services attach, margin, incentives, and seller compensation—into a compelling reason to lead with Nasuni. - Grow partner-sourced and partner-influenced pipeline, bookings, and forecast accuracy across commercial, enterprise, and strategic segments. - Create account-mapping, field-activation, enablement, and joint-sales programs that reach a distributed organization without depending on deal-by-deal participation. - Design co-marketing and demand-generation motions, define the investment case, and measure return. - Support top-deal strategy and executive escalation while converting wins into documented plays others can run. - Maintain accurate Salesforce reporting and use approved AI-enabled workflows for research, partner intelligence, pipeline analysis, and automation. - Validate outputs, protect confidential data, and retain decision accountability. What Success Looks Like: In the first year, you will establish a signed joint plan and operating cadence, strengthen executive coverage, launch measurable field and demand programs, grow partner-sourced pipeline, and create repeatable motions both companies can run at scale. Qualifications Must-Have: - 8+ years in channel sales, alliances, strategic partnerships, partner development, or enterprise technology sales, including 5+ years owning national or strategic partners. - Direct accountability for partner-sourced or partner-influenced pipeline, forecast, bookings, or revenue. - Experience authoring and executing joint business plans with national solution providers, integrators, or strategic channel partners. - Success influencing executives and distributed field teams without formal authority. - National scope across at least two segments: commercial/SMB, enterprise, or strategic. - Working knowledge of solution-provider economics, CRM discipline, and forecasting. - Practical use of AI-enabled tools to improve partner or sales workflows, with clear validation and data-handling judgment. - Based in the Chicago area, or willing to relocate, and able to travel approximately 30–50%. Preferred Experience: - Experience in enterprise software, cloud, data infrastructure, cybersecurity, cyber resilience, storage, or adjacent SaaS markets. - Co-marketing, market development funds, partner enablement, campaign ROI, Salesforce, or partner ecosystem management experience. - Experience in a private-equity-backed or high-growth SaaS company. - Cross-border partner experience. Ideal: - Prior work with AHEAD as a partner, customer, or former employee. - Ownership of a named national partner with multi-million-dollar annual responsibility. - A record of turning individual wins into programs others adopted. Experience Guidelines: - Successful candidates typically bring 9–15 years of relevant experience. - Scope, ownership, and national-partner outcomes matter more than tenure alone. - No specific degree is required. About Nasuni: Nasuni is the unstructured data foundation for enterprise teams—and the AI that supports them. We manage, protect, and activate the world’s unstructured data so organizations can work smarter, spend wisely, and create safely without limits. As a Vista-backed SaaS data infrastructure company, Nasuni is transforming how enterprises manage file data with a next-generation, AI-ready platform—turning massive file stores into secure, actionable, and AI-ready data for intelligent automation, analytics, and global collaboration. Why work at Nasuni? Benefits: list. Benefits list: - Best in class employee onboarding and training - "Take What You Need” paid time off policy - Comprehensive health, dental and vision plans - Company-paid life and disability insurance - 401(k) and Roth IRA retirement plan - Generous employee referral bonuses - Flexible remote work policy - 10 Paid Holidays - Wide array of wellbeing offerings - Pre-tax savings accounts with company contributions - Great team culture and social activities - Collaborative workspaces - Free on-site fitness centers and stocked kitchens in select office locations - Professional development resources Compensation Transparency: In accordance with U.S. pay transparency laws, Nasuni is committed to providing visibility into compensation for all U.S.-based roles. Click HERE to view our compensation ranges by job grade. Actual compensation will be based on a variety of factors, including a candidate’s experience, skills, education, and work location. We should not include Pay section because no specific numbers. Schedule: travel 30-50% etc. We'll include Schedule section with that detail. Now produce HTML. Structure:

  About the role

  Location: Chicago, Illinois — Remote, Chicago-based. Reports to: Director, Partner Sales. ... maybe combine location and reports in paragraph.

  But we need to preserve all substantive info. Could separate location and reports into paragraph. Better:

  Location: Chicago, Illinois — Remote, Chicago-based. Reports to: Director, Partner Sales.

  Then role overview paragraph(s). Could be multiple

  . We must not repeat job title. We'll include Level & Scope Definition as part of About the role. Thus About the role section will contain multiple paragraphs: location/reports, role overview, level & scope, what success looks like? Actually what success looks like could be separate but we could include under About the role or Responsibilities. The instruction: include a section ONLY when posting has real, specific content for it. We have specific content for what success looks like; we could make a separate section maybe "What Success Looks Like" but not in allowed headings list. Allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit content into those headings. What Success Looks Like could be part of About the role or Responsibilities. I'd put it under About the role as a paragraph. Responsibilities section:

  Responsibilities

  • ... each bullet. Qualifications section:

    Qualifications

    with subpoints maybe as
    • for each must-have, preferred, ideal, experience guidelines. Could separate with headings inside? Not allowed to add extra headings beyond those? The instruction only says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings inside? It says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings as top-level sections. Inside we can use

      • and

        . We could still include or but not extra headings. To keep clarity, we can just list all qualifications as bullet points, maybe grouping with commas. But we need to preserve all detail; we can include sub-bullets? Not allowed to use nested headings but we can use

        • and inside
        • we can have text with line breaks? Could use
          but better to keep as separate
        • for each item. We'll create separate
          for Must-Have, Preferred, Ideal, Experience Guidelines? Could just have one big list with all items; but we risk losing grouping. However we can keep grouping by preceding text inside
          • like "Must-Have: ..." but that's okay. Better: we can have multiple
            each preceded by a

            describing category. That's allowed because we are not adding extra headings; just

            for prose. Thus Qualifications section