Channel Sales Manager, NVIDIA

We need to output HTML fragment with sections: About the role? The posting includes description. We need headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We have content: description of role, responsibilities (Work You'll Do), skills (The successful candidate would possess these skills, Additional key skills related to the role), Qualifications Required, Preferred, Key Success Measures, Pay (wage range), Travel (maybe schedule? Not schedule but travel). Benefits not mentioned. Schedule not mentioned. So we include sections: About the role (maybe intro), Responsibilities (Work You'll Do), Skills (combined skills), Qualifications (Required and Preferred), Key Success Measures, Pay. Possibly also "Travel" but not required heading; we could fold into Responsibilities or a separate section like "Travel" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use Requirements maybe same as Qualifications? But we have Qualifications Required and Preferred. Could put Requirements as a subsection? Probably better to use Qualifications for required and preferred. Use Skills for skill list. Use About the role for introductory paragraph. Use Responsibilities for Work You'll Do. Use Key Success Measures maybe as its own section? Not in list but could be under Responsibilities? But we have to follow allowed headings; we could put Key Success Measures under Responsibilities or maybe as a separate section not listed? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should prefer those headings. It also says "include a section ONLY when the posting has real, specific content for it". So we can create sections with those headings if content matches. For Key Success Measures, we could put under Responsibilities or maybe under Qualifications? But better to create a separate section maybe "Key Success Measures" not in list but maybe acceptable as it's specific. However instruction says use those headings for section headings (e.g...). It doesn't forbid other headings, but says use

for section headings (e.g...). Likely they expect to use those headings only. So we should map content to those headings. Thus: - About the role: introductory paragraph describing role and team. - Responsibilities: the "Work You'll Do" bullet list (but we need

• for any list). So we will convert the responsibilities into list items. - Skills: combine the skill lists (The successful candidate would possess these skills: ... and Additional key skills related to the role: ...). We'll list as
  • . - Qualifications: combine Required and Preferred. Could split into Required and Preferred subheadings? But we only have Qualifications heading. Could include both within
    • with maybe marking required vs preferred. But we must preserve all substantive info. Could do two sublists: Required and Preferred as inside
    • . That's okay. - Pay: wage range and sales incentive program. - Benefits: none, so omit. - Schedule: not mentioned (travel up to 25% maybe considered schedule? But schedule refers to work schedule; not given. Travel is not schedule. So omit Schedule. - Requirements: maybe we could treat Qualifications as Requirements? But we already have Qualifications. Could omit Requirements. Thus output HTML fragment with sections: About the role, Responsibilities, Skills, Qualifications, Pay. Make sure not to repeat job title as heading. No Job ID. We must not include boilerplate like cookie/navigation/legal/EEO etc. The posting didn't have that. We must preserve all substantive info. Need to include details like team description, responsibilities bullet points, skills bullet points, qualifications required and preferred, key success measures? Wait we omitted Key Success Measures. That is substantive. Should we include it somewhere? Could include under Responsibilities as a subsection? But we need to preserve it. Could add a section "Key Success Measures" but not in allowed headings. However instruction says use those headings (e.g...). It may be okay to add other headings if needed, but they said "Prefer a few substantive sections over many thin ones." Adding a section for Key Success Measures may be thin but it's substantive. Could we incorporate Key Success Measures into Responsibilities or Qualifications? It's about metrics; could be part of Responsibilities (tracking and reporting). The responsibilities already include "Tracking and reporting on key success measures, including NVIDIA-generated leads, partner-generated leads, and total joint pipeline" etc. So we can keep that as part of responsibilities list. Indeed the responsibilities list includes that line. So we don't need separate section. Thus responsibilities list includes all bullet points from Work You'll Do. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now craft HTML. We'll start with

      About the role

      then

      ...

      . About the role paragraph: combine first paragraph: "Deloitte is currently seeking candidates for our national Channel Sales Manager role focused on the NVIDIA alliance. The NVIDIA Channel Sales Manager will bring strong alliance relationship management, project management discipline, attention to detail, outstanding oral and written communication skills, and the ability to operate effectively in a fast-paced, matrixed organization. This role is designed for a professional who can build trusted relationships across both NVIDIA and Deloitte, uncover and accelerate joint opportunities, and help drive coordinated go-to-market activity across a portfolio of strategic target accounts. The Team The Channel Sales Managers are members of Deloitte's Growth Platforms focused on our AI, Data, and Engineering consulting portfolios. Channel Sales, working closely with our AI, Data & Engineering leadership, alliance leaders, industry sales executives, and Account Principals/Managing Directors (PMDs), focus on building relationships with vendor sales and alliance teams to uncover opportunities, develop territory strategies, and support joint pursuits throughout the sales process." We can split into two paragraphs maybe. Then Responsibilities:

      Responsibilities

      • ... each bullet. We need to extract bullet points from Work You'll Do. Let's list them: - Act as a primary point of contact for the NVIDIA sales, alliance, and solution leadership teams in the United States. - Build strong working relationships with NVIDIA account managers, solution architects, development relationship leads, industry business development teams, and alliance leaders to help Deloitte identify and advance joint opportunities early. - Requires strong connectivity into Deloitte account teams so the Channel Sales Manager can quickly align Deloitte target account leaders with NVIDIA sales teams as new opportunities emerge. - Developing fluency in NVIDIA technologies, offerings, and go-to-market motions, and creating awareness of Deloitte's NVIDIA-related capabilities with both NVIDIA teams and internal Deloitte stakeholders - Building strong relationships with NVIDIA account managers, solution architects, development relationship leads, industry business development teams, and alliance leaders to position Deloitte as a trusted and responsive alliance partner - Using those relationships to help Deloitte become one of the first GSIs aware of emerging opportunities and to accelerate those opportunities through the joint sales funnel - Building strong relationships with Deloitte target account leaders, industry sales leaders, and pursuit teams to rapidly connect the right Deloitte and NVIDIA stakeholders around new opportunities - Monitoring and managing pipeline activity across a portfolio of approximately 40-50 target accounts where Deloitte and NVIDIA have go-to-market activity - Connecting the dots across multiple GTM motions within an account, including AI factory, agentic AI, and physical AI, to help account teams identify broader opportunity pathways and cross-sell potential - Coordinating and supporting account-specific and sector-specific "sales day" activations to align Deloitte and NVIDIA teams on whitespace, priority opportunities, and joint pursuit plans - Partnering with Deloitte alliance, industry, and account teams to develop and execute territory and account-level sales strategies for the NVIDIA ecosystem - Assisting with business development activities by connecting the appropriate Deloitte account teams, sales executives, PMDs, and solution leaders with the appropriate NVIDIA sales and technical stakeholders for specific clients - Leading NVIDIA alliance opportunity management processes, including relationship management system updates, reporting, pipeline tracking, and co-sell activity management - Tracking and reporting on key success measures, including NVIDIA-generated leads, partner-generated leads, and total joint pipeline - Supporting alliance planning sessions and quarterly business reviews, including agenda development, research, materials consolidation, stakeholder coordination, note capture, and follow-up actions - Proposing and helping execute alliance programs, client activations, and marketing efforts that strengthen Deloitte's market position with NVIDIA and priority clients - Supporting the alliance team in collecting, organizing, and centrally storing relevant client and pursuit materials - Establishing internal relationships across Deloitte teams to help coordinate and support joint sales cycles - Providing recommendations to NVIDIA alliance leadership and Deloitte business leaders related to alliance management, opportunity acceleration, and pipeline growth - Traveling to key client, Deloitte, and NVIDIA meetings and events, including periodic time in NVIDIA's Santa Clara headquarters as appropriate That's many. We'll put each as
      • . Skills: combine two lists. First list: Ability to work independently and collaborate as part of a team; Effective written and verbal communication skills; Ability to build and sustain professional relationships; Ability to lead projects or workstreams; Ability to manage and prioritize multiple tasks in a fast-paced and dynamic environment; Strong interpersonal skills and professional demeanor; Ability to meet deadlines; Ability to mentor and provide clear guidance to others. Second list: Exceptional relationship-building and relationship-management skills, with the ability to establish rapport, trust, and credibility across both NVIDIA and Deloitte stakeholder groups; Strong collaboration skills and the ability to work effectively across a large, matrixed organization; Strong project and pipeline management capabilities, including the ability to coordinate multiple stakeholders and workstreams at once; Demonstrated success helping uncover, shape, and advance alliance-driven sales opportunities; Excellent written, oral, and interpersonal communication skills; Strong problem-solving and analytical skills, with the ability to connect disparate GTM motions into a coherent account strategy; Ability to take initiative, operate independently, and drive follow-through in a fast-moving environment; High attention to detail and the ability to adapt quickly as priorities evolve; Familiarity with enterprise AI market dynamics and the ability to understand how NVIDIA-led opportunities map to client transformation priorities. We'll combine into one
        . Qualifications: Required and Preferred. Required: Bachelor's degree; 5+ years of experience in technology, alliance, channel sales, business development, or client relationship roles; Experience working within or alongside complex technology ecosystems and partner-led go-to-market motions; Familiarity with NVIDIA technologies, offerings, or ecosystem relationships preferred (actually that's preferred? It says preferred. We'll treat as preferred); Experiences with AI ecosystems including hyperscalers, hardware OEM/distributors/resellers, AI natives, data platform providers, or ISVs/SaaS companies strongly preferred; Experience supporting pipeline management, sales reporting, and alliance-driven opportunity tracking; Ability to build and influence relationships across vendor, alliance, and internal account teams; Proficiency in leveraging GenAI/agentic toolkit for developing dashboards and tracking activities and pipeline; Ability to travel up to 25%, on average, based on the work you do and clients and industries/sectors you serve; Must be legally authorized to work in the United States without the need for employer sponsorship, now or at any time in the future. Preferred: Master's or advanced degree a plus; Experience working with NVIDIA account teams, alliance teams, or NVIDIA-enabled solutions; Ability and willingness to spend time in NVIDIA's Santa Clara headquarters as needed. We'll put Required and Preferred as subheadings maybe

        but not allowed? We could just list with Required: ... and Preferred: ...