Pre-Sales Solutions Manager

We need to produce HTML fragment with sections: About the role? The posting includes Overview, Responsibilities, Required Qualifications, Preferred Qualifications, Travel Requirements, Education And/or Certifications. Also maybe Benefits, Pay, Schedule not present, so omit. Also need to include a short

for minor metadata like Job ID? There is none. Remove boilerplate like EEOC statement. Also remove navigation etc. Keep substantive info. We need headings:

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real content. The posting has Overview (could be About the role). Responsibilities. Required Qualifications (maybe Requirements). Preferred Qualifications (maybe Qualifications or Skills). Travel Requirements (maybe Schedule? but it's travel). Education And/or Certifications (maybe Qualifications). We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use About the role for Overview. Responsibilities for Responsibilities. Requirements for Required Qualifications. Qualifications for Preferred Qualifications? Or maybe Skills for certifications? But we have both Required and Preferred. Could combine? Better to have Requirements (Required Qualifications) and Qualifications (Preferred Qualifications). Skills maybe for certifications? But we can omit Skills if no specific skills list besides those in qualifications. Travel Requirements could go under Schedule? But schedule heading is for schedule info like hours, shift. Travel is not schedule. Could maybe put Travel Requirements under a paragraph within About the role? But we should preserve all substantive info. Travel Requirements is a separate piece; we could put it under a heading Schedule? Not appropriate. Could we create a custom heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings only; we shouldn't invent other headings. So we need to fit Travel Requirements into one of those. Perhaps Schedule is the closest (travel expectations). Could treat travel as part of Schedule. Or we could put it in a

under About the role. But we need to preserve all info; we can include a paragraph about travel under About the role or under Responsibilities? Probably better to add a short paragraph under About the role mentioning travel expectations. However the instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if we put Travel Requirements under Schedule heading, we need to have content for Schedule. Travel is schedule-related, so okay. Education And/or Certifications could go under Qualifications or Skills. Since we already have Qualifications for Preferred, maybe we put Education under Qualifications as well? But we need to avoid duplication. Could combine Education and Certifications into Qualifications section (Preferred). But we also have Required Qualifications separate. Could have Requirements (Required) and Qualifications (Preferred + Education). Skills maybe for certifications? Hmm. Let's think: The posting has: - Overview (About the role) - Responsibilities - Required Qualifications - Preferred Qualifications - Travel Requirements - Education And/or Certifications We could map: About the role -> Overview + Travel Requirements (maybe mention travel) Responsibilities -> Responsibilities Requirements -> Required Qualifications Qualifications -> Preferred Qualifications Skills -> maybe we could list specific skills like "consultative selling methodologies" etc. But we already have those in Preferred. Could omit Skills if no distinct content. But we need to preserve all substantive info; if we omit Skills heading, that's fine as long as we included the content elsewhere. The content about certifications is in Preferred Qualifications; we can keep it there. Education And/or Certifications could be merged into Qualifications (Preferred) as well, but we need to ensure not losing info. We could add a paragraph under Qualifications about education and certifications. Thus sections:

About the role

Overview text + travel expectations.

Responsibilities

• ... each responsibility as list items.

Requirements

• ... required qualifications.

Qualifications

Preferred qualifications plus education and certifications.

We must not repeat job title heading. No markdown. We need to preserve all substantive information: let's extract. Overview paragraph: "WEI is a service and solution technology provider that focuses on building quality relationships with clients. Our sales and engineering teams work closely with our clients to optimize their environments and work efficiently by using cutting-edge technologies and best practices. Our clients benefit from our technical talents, value-added services, demonstration labs, knowledge transfer center, integration/testing labs, proof of concept labs and commitment to quality. From solution design through implementation, our sales and technical team will remain focused on providing unwavering support throughout the project. WEI is your strategic IT partner delivering custom, innovative business technology solutions that deliver real business outcomes. Overview The Pre-Sales Manager leads WEI's Pre-Sales Solutions team, serving as the primary technical leader for the group and acting as a senior trusted advisor to both customers and internal stakeholders. This individual brings broad, cross-domain technical fluency spanning WEI's full portfolio—including compute, storage, networking, security, virtualization, cloud, data protection, and end-user computing—and translates that depth into winning technical strategies across complex sales campaigns. Beyond individual contributor excellence, the Pre-Sales Manager is responsible for the hiring, development, and day-to-day coaching of Pre-Sales Solutions Consultants. This leader sets the standard for technical quality, consultative selling, and customer engagement across the team, and works closely with Sales leadership, Practice Managers, to align pre-sales resources to revenue and customer success objectives. The Pre-Sales Manager reports to senior Sr. Director Revenue Operations and maintains a dual mandate: driving customer-facing technical sales outcomes while building and retaining a high-performing pre-sales team." We need to include travel expectations: "Travel Requirements Up to 50% travel expected (mix of local and air travel)". We'll add that to About the role paragraph. Now Responsibilities list: The responsibilities are given as a paragraph with sentences separated by periods but no bullet list. We need to convert to

• . Let's extract each responsibility: - Lead, coach, and mentor a team of Pre-Sales Solutions Consultants, fostering professional growth through regular one-on-ones, performance feedback, and structured development plans. - Establish and model best practices for technical discovery, solution design, presentation delivery, and proposal development. - Recruit, interview, and onboard pre-sales talent aligned with WEI's technical and cultural standards. - Identify skills gaps across the team and coordinate targeted training, certification paths, and OEM enablement programs to close them. - Serve as an escalation point for high-complexity or high-stakes sales campaigns, providing hands-on guidance and technical oversight. - Promote a collaborative, customer-first team culture that rewards curiosity, accountability, and continuous improvement. - Maintain working knowledge across WEI's core practice areas—compute, storage, networking, security, virtualization, cloud (public, private, hybrid), data protection, data center management/automation, and end-user computing—enabling credible engagement on virtually any customer opportunity. - Stay current with market trends, emerging technologies, and competitive landscape to ensure WEI's pre-sales motions remain differentiated and relevant. - Collaborate with Practice Managers and Subject Matter Experts to deepen the team's capabilities across new or expanding technology domains. - Engage directly with business executives, IT leadership, and technical practitioners across the customer base, adjusting messaging and depth to each audience. - Lead executive business reviews and strategic briefings, positioning WEI as a long-term strategic partner rather than a transactional vendor. - Partner with Senior Account Managers on account planning, pipeline strategy, and key opportunity pursuit to maximize win rates and deal size. - Translate customer business objectives and pain points into compelling, outcome-based solution narratives that resonate with both technical evaluators and business decision-makers. - Manage pre-sales standards for solution scoping, Bill of Materials accuracy, Statement of Work quality, and collaboration/handoff to the post-sales/consulting team. - Oversee the development of High-Level Designs (HLDs), ROI/TCO business cases, and executive-level proposals across the team. - Manage pre-sales resource allocation, ensuring consultants are aligned effectively across the sales pipeline without overextension. - Provide accurate forecasting, activity reporting, and KPI management to senior leadership on team performance and pipeline health. - Act as a bridge between the pre-sales, sales, and post-sales consulting Note the last sentence incomplete: "Act as a bridge between the pre-sales, sales, and post-sales consulting". Probably missing "team". We'll keep as is. Now Required Qualifications list: - 8+ years of pre-sales or solutions engineering experience, with a minimum of 2-3 years in a team lead, principal, or management capacity. - Demonstrated broad-based technical fluency across the majority of WEI's practice areas: compute, storage, networking, security, virtualization, cloud (public/private/hybrid), data protection, data center management/automation, and end-user computing. - Proven ability to engage and influence both business stakeholders (C-suite, VP, Director) and technical audiences (architects, engineers, IT operations) within the same sales campaign. - Track record of mentoring and developing pre-sales professionals, raising individual and team performance over time. - Experience leading complex, multi-vendor solution engagements from discovery through proposal and technical validation. - Excellent written and verbal communication skills; executive-level presentation and facilitation ability. - Strong analytical and problem-solving skills; ability to synthesize customer requirements into strategic solution frameworks under time pressure. - Collaborative leadership style with the ability to influence across organizational boundaries without direct authority. - Experience working within or alongside a Value Added Reseller (VAR) or multi-OEM technology environment. - Must be obsessed with customer service and satisfaction. Preferred Qualifications: - Active certifications from one or more major OEM vendors (e.g., Cisco, Dell, HPE, NetApp, VMware, Microsoft, AWS, Palo Alto Networks) demonstrating depth in at least one domain. - Hands-on deployment or architecture experience in one or more practice areas, providing credibility in technical deep-dive discussions. - Familiarity with consultative selling methodologies. - Background in building or contributing to a pre-sales practice, including process development, onboarding playbooks, or enablement programs. Education And/or Certifications: - Bachelor's degree in computer science, Engineering, or equivalent experience We also have EEOC statement to drop. Now we need to embed Education into Qualifications section perhaps. Thus Qualifications section will contain:

  Preferred qualifications: Active certifications from one or more major OEM vendors (e.g., Cisco, Dell, HPE, NetApp, VMware, Microsoft, AWS, Palo Alto Networks) demonstrating depth in at least one domain; Hands-on deployment or architecture experience in one or more practice areas, providing credibility in technical deep-dive discussions; Familiarity with consultative selling methodologies; Background in building or contributing to a pre-sales practice, including process development, onboarding playbooks, or enablement programs. Education: Bachelor's degree in computer science, Engineering, or equivalent experience.

  We could also make a
  but the instruction says use
  • for any list of duties/requirements/benefits. For qualifications, it's a list; we could use
    . But we already used
    for Responsibilities and Requirements. For Qualifications we could also use
    . However the instruction: "Use
    • for any list of duties/requirements/benefits". Qualifications is a list of qualifications, so we should use
      . Similarly for Requirements we used
      . Good. Thus:

      Qualifications

      • Active certifications from one or more major OEM vendors (e.g., Cisco, Dell, HPE, NetApp, VMware, Microsoft, AWS, Palo