Enterprise Account Executive, SLED

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. From description: "About the role" paragraph: we have description about role. That's the "About the role" section. Then "What You'll Be Doing" is responsibilities. So

Responsibilities

with list of duties. Then "About You" includes qualifications, requirements, skills. We need to split into Requirements, Qualifications, Skills maybe. The instruction: Use headings for those sections if content exists. We can decide to put Requirements (experience, years, etc.) Qualifications (education, etc.) Skills (specific abilities). But we must not create filler sections. We need to see if there is distinct content. "About You" bullet list: - 5 to 8+ years of enterprise SaaS sales experience with a proven record of success in the OH, IN, MI, KY & TN SLED market - Proven experience landing and expanding enterprise-level public-sector accounts with multi-year, high-value contracts - Deep understanding of SLED procurement ecosystems, including cooperative purchasing agreements, RFP cycles, and state contracting vehicles - Established network across OH, IN, MI, KY & TN government and education institutions, with demonstrated ability to open doors and influence complex buying centers - Comfortable navigating multi-stakeholder environments, including IT, security, procurement, and executive leadership - Skilled at tailoring solutions to public-sector requirements and aligning with mission-driven initiatives - Strategic thinker with knowledge of budget timelines, political landscapes, and regional priorities - Experience collaborating with lobbying or government affairs teams to support GTM success - Strong communicator with executive presence and the ability to build trust quickly - Proficient in Salesforce or similar CRM for pipeline management and forecasting - Bachelor's degree or equivalent experience preferred - You align with our values Curiosity, Integrity, Kindness, Humility, and Builders and are committed to creating an environment where these values flourish in our teams We can categorize: Requirements: years of experience, proven experience, deep understanding, established network, comfortable navigating, strategic thinker, experience collaborating, strong communicator, proficient in Salesforce, Bachelor's degree. Skills: Skilled at tailoring solutions, etc. But many overlap. Simplify: Use Requirements for the experience/qualifications, Skills for abilities like tailoring solutions, strategic thinker, etc. Qualifications maybe education. But we must avoid thin sections. Could combine Requirements and Qualifications into one? But headings are prescribed; we can omit sections if no real content. We need to decide which headings to include. We have content for Responsibilities definitely. We have content for About the role. We have content for Requirements (experience, years, etc.) and Skills (specific abilities). We also have Benefits and Pay info later. Benefits: "What You’ll Love" section: collaborative, kind, curious community; full-time hybrid remote; comprehensive benefits package includes medical, dental, vision insurance; 401(k) plan; unlimited PTO; opportunity for growth and advancement. Also later: "The benefits available for this position include medical, dental, vision, 401(k) plan, life insurance coverage, and PTO." So we have benefits. Pay: "Starting pay for the successful applicant depends on a variety of job-related factors..." plus salary ranges for MD/NJ/NY. This is pay info but it's conditional. The posting does state pay ranges for certain locations, but not for Ohio/Tennessee. It says starting pay depends on factors; also gives ranges for MD/NJ/NY. There is some pay info, albeit not specific to role location. Should we include Pay section? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Here we have some pay info: "Starting pay for the successful applicant depends on a variety of job-related factors, including but not limited to location, market demands, experience, job-related knowledge, and skills." That's vague but still some content. Additionally they give specific ranges for MD/NJ/NY. That is specific content. So we can include Pay section with that info. Schedule: No mention of schedule (full-time hybrid remote is about work arrangement, not schedule). No explicit schedule like hours. So we omit Schedule. Now we need to output HTML fragment with

headings and appropriate

• for lists,

  for prose. We must not repeat job title as heading. Not include Job ID etc. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all points from About the role, Responsibilities, About You (split into Requirements, Qualifications, Skills), Benefits, Pay. We must not include boilerplate like EEO etc. At end there is EEO statement; we should remove. Also remove "Additional Information" about visa sponsorship, Chicago city limits, etc. That's minor metadata; we can fold into short

  or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include a short

  for that metadata if we want, but better to drop? It says fold minor metadata into a short

  or drop it. We can drop it entirely to keep concise. However we need to preserve ALL substantive information; is that metadata substantive? It says "Due to operational policies, NinjaOne is unable to hire for this role within the city limits of Chicago." That's a restriction; maybe substantive. Also "This position is NOT eligible for Visa sponsorship." That's also substantive. We could include them in a short

  under maybe a heading? But there is no heading for that. Could add a

  after Pay section. The instruction: fold minor metadata into a short

  or drop it. So we can include a short

  with that info. We must not include the EEO boilerplate. Now structure:

  About the role

  NinjaOne is making bold investments to expand our presence in the Public Sector, especially across State, Local, and Education (SLED) markets, and we're looking for a proven, high-performing Enterprise Account Executive based in Ohio or Tennessee to help drive growth across the Ohio Valley region. This is a strategic, high-impact role focused on shaping how we engage large, complex public-sector organizations and drive long-term transformation. As part of our growing SLED team, you'll be at the forefront of landing enterprise logos and expanding relationships across key agencies, municipalities, and higher education systems. You bring deep knowledge of the public-sector landscape, including procurement cycles, funding timelines, and state-led initiatives, and know how to build trust with senior stakeholders. Backed by a strong cross-functional and channel ecosystem, you'll help position NinjaOne as the go-to partner for modernizing IT operations in government and education. Location: Ohio, Tennessee (Remote)

  Then Responsibilities:

  Responsibilities

  • Own the full enterprise sales cycle across SLED: pipeline generation, discovery, solution mapping, proposal development, negotiation, and close
  • Build and execute a go-to-market SLED strategy for assigned territory focused on OH, IN, MI, KY & TN state agencies, flagship education systems, and major municipalities
  • Develop and grow a pipeline of net-new enterprise opportunities in state and local government, aligned to statewide initiatives, funding priorities, and procurement timelines, with flexibility to pursue opportunities in public higher education institutions
  • Manage and expand existing OH, IN, MI, KY & TN SLG customer relationships, identifying upsell and cross-sell opportunities within state agencies, large municipalities, and public sector consortiums
  • Serve as a trusted advisor to senior technical, procurement, and executive decision-makers, positioning NinjaOne as a long-term solution partner
  • Navigate public-sector sales motions with confidence, leveraging cooperative purchasing agreements, bid processes, and state-specific contracting vehicles
  • Engage lobbying and government affairs teams to inform regional strategy and support alignment with policy and funding trends
  • Partner with our SDRs, marketing, and channel teams to launch targeted account-based campaigns that open new doors and deepen existing relationships
  • Execute strategic growth plans for inherited accounts with clear expansion potential
  • Collaborate with legal and compliance teams on RFPs, procurement documentation, and public-sector regulatory requirements
  • Accurately manage pipeline health and forecast performance in Salesforce
  • Represent NinjaOne at key regional events, SLED conferences, and partner summits to amplify visibility and fuel engagement
  • Other duties as needed
  Now Requirements: we need to decide content. Let's extract items that are about experience, years, proven record, network, etc. We'll create

  Requirements

  with list: - 5 to 8+ years of enterprise SaaS sales experience with a proven record of success in the OH, IN, MI, KY & TN SLED market - Proven experience landing and expanding enterprise-level public-sector accounts with multi-year, high-value contracts - Deep understanding of SLED procurement ecosystems, including cooperative purchasing agreements, RFP cycles, and state contracting vehicles - Established network across OH, IN, MI, KY & TN government and education institutions, with demonstrated ability to open doors and influence complex buying centers - Comfortable navigating multi-stakeholder environments, including IT, security, procurement, and executive leadership - Strategic thinker with knowledge of budget timelines, political landscapes, and regional priorities - Experience collaborating with lobbying or government affairs teams to support GTM success - Strong communicator with executive presence and the ability to build trust quickly - Proficient in Salesforce or similar CRM for pipeline management and forecasting - Bachelor's degree or equivalent experience preferred Now Skills: maybe items about tailoring solutions, aligning with mission-driven initiatives, etc.

  Skills

  • Skilled at tailoring solutions to public-sector requirements and aligning with mission-driven initiatives
  But that's only one item; could be thin. Maybe combine with Requirements? But we need to avoid thin sections. Could we merge Skills into Requirements? The instruction: Prefer a few substantive sections over many thin ones. So maybe we should not create a Skills section if it's just one bullet; we could incorporate that skill into Requirements or Qualifications. However we already have many items; we could add that bullet under Requirements as well. But we already have "Skilled at tailoring solutions..." which is a skill. Could add to Requirements list. Thus we may omit Skills section entirely. Qualifications: maybe education (Bachelor's degree) but we already have that in Requirements. Could create Qualifications section for education and values alignment. But we risk thin. Better to have Requirements covering experience, skills, education. Then we can have a separate section for "Values" maybe not in headings list. Not required. Thus we will have sections: About the role, Responsibilities, Requirements, Benefits, Pay. Now Benefits:

  Benefits

  • Medical, dental, and vision insurance
  • 401(k) plan
  • Unlimited PTO
  • Life insurance coverage
  • Opportunity for growth and advancement
  • Collaborative, kind, and curious community
  • Full-time hybrid remote work
  We need to ensure we don't duplicate. The "What You’ll Love" includes collaborative, kind, curious community; full-time hybrid remote; comprehensive benefits package (medical, dental, vision); 401(k); unlimited PTO; opportunity