Overview
You're a pre-sales systems engineer supporting HPE account executives selling to universities and colleges in Tennessee. You design campus networking solutions (Aruba wireless, switching), data center infrastructure, and security products. Your typical buyer is an IT director or CIO working through 6-18 month evaluation and procurement cycles with committee decisions and state/federal budget constraints.
Role Snapshot
| Aspect | Details |
|---|---|
| Role Type | Pre-sales Systems Engineer (technical sales support) |
| Sales Motion | Account-based enterprise, relationship-driven |
| Deal Complexity | Enterprise - multi-stakeholder, technical evaluations, formal RFPs |
| Sales Cycle | 6-18 months (higher ed procurement is slow) |
| Deal Size | $200K-2M+ (campus-wide infrastructure refreshes) |
| Quota (est.) | SE typically measured on revenue influenced, not direct quota |
Company Context
Stage: Public (NYSE: HPE)
Size: 85,000+ employees globally
Growth: Established enterprise infrastructure vendor, competing in campus networking (Aruba), hybrid cloud, edge computing
Market Position: Top-tier player in enterprise networking and infrastructure, competing against Cisco, Juniper, and cloud vendors
GTM Reality
Pipeline Sources:
- 60% Existing accounts - HPE has deep existing relationships with most universities; deals are refresh cycles and expansion
- 30% Competitive displacement - taking share from Cisco or legacy vendors during infrastructure refresh cycles
- 10% Net new - rare in higher ed; most institutions already have HPE or competitor gear
SDR/AE Structure: No SDRs. You support 2-3 named account executives focused on higher education. These are strategic, multi-year relationships.
SE Support: You ARE the SE. Likely 1 SE per 2-3 AEs in this territory.
Competitive Landscape
Main Competitors:
- Cisco (dominant in campus networking - you'll face them in 70%+ of deals)
- Juniper/Mist (AI-driven wireless competitor)
- Dell/VMware (data center/hybrid cloud)
How They Differentiate: Aruba's AI-powered network management, HPE GreenLake consumption model (pay-as-you-go vs capex), edge-to-cloud integration story
Common Objections:
- "We're already standardized on Cisco" (migration risk/cost)
- "Your wireless works but can it integrate with our Cisco core?"
- Budget constraints - universities defer infrastructure spending
- "We're moving to cloud, why invest in on-prem?"
Win Themes: Total cost of ownership vs Cisco, simpler management (Aruba Central), flexible consumption model, better wireless performance in dense environments (dorms, lecture halls)
What You'll Actually Do
Time Breakdown
Customer meetings/demos (30%) | Solution design (25%) | Proposals/RFPs (20%) | Internal coordination (15%) | POCs/labs (10%)
Key Activities
- Discovery calls with IT teams: You're on Zoom or onsite asking about their current network (VLAN structure, wireless coverage gaps, security posture). Taking notes on building layouts, user counts, bandwidth needs. These meetings have 4-8 people from the university side.
- Designing campus network solutions: You're in Visio or HPE tools drawing out wireless coverage maps, switch stack designs, firewall placement. Calculating port counts, power budgets, fiber runs. Lots of spreadsheet work on BoMs (bill of materials).
- Running product demos: You're screen-sharing Aruba Central dashboard, showing how they'd manage 500+ access points across campus. Walking through security policies, guest access workflows, network analytics. Questions get technical fast.
- Responding to RFPs: Universities issue 50-page RFPs with 200+ questions. You're writing technical responses about 802.11ax support, RADIUS integration, GDPR compliance. Tedious, detail-oriented work with tight deadlines.
- Building and running POCs: You're shipping gear to campus, working with their network team to set up a test deployment in one building. Troubleshooting configs remotely, gathering performance data, documenting results for the evaluation committee.
- Internal coordination: You're in pipeline reviews with your AE, pricing calls with channel partners, product roadmap calls with HPE engineering. Lots of internal Slack/email traffic.
The Honest Reality
What's Hard
- Long, unpredictable cycles: Deals you work on in January might not close until next fiscal year. Budget freezes, committee delays, scope changes. You lose momentum constantly.
- RFP grind: Higher ed loves formal procurement. You'll spend weeks responding to RFPs where HPE isn't even the front-runner. Lots of work that goes nowhere.
- Cisco incumbency: Most campuses are Cisco shops. You're fighting inertia and migration risk even when your solution is better/cheaper. IT teams are risk-averse.
- Committee decisions: You never sell to one person. There's the network team, the security team, the CIO, procurement, sometimes faculty input. Consensus is slow and painful.
- Budget constraints: Universities are cost-sensitive. You're constantly value-engineering solutions down, removing features to hit budget. Then the budget gets cut again.
What Success Looks Like
- You influence $2-4M+ in annual bookings across your AE's accounts
- Your technical designs win competitive bids against Cisco 50%+ of the time
- Universities reference you by name and request you on future projects
- Your POCs convert to purchases 70%+ of the time (if you're setting them up right)
Who You're Selling To
Primary Buyers:
- Director/VP of IT Infrastructure (day-to-day technical evaluator)
- CIO (final budget authority, strategic direction)
- Network/Security Architects (deep technical validation)
- Procurement (vendor management, contract terms)
What They Care About:
- Reliability: Cannot have network outages during registration or exams
- Cost: Limited budgets, need to justify vs status quo
- Manageability: Small IT teams managing large networks - they want simple
- Security: Protecting student data, research data, FERPA compliance
- Longevity: 7-10 year refresh cycles - they need gear that lasts
Requirements
- 3-5+ years in pre-sales systems engineering for enterprise networking
- Deep hands-on experience with campus/branch networking - you need to speak fluently about VLANs, wireless controllers, switch stacks, routing protocols
- Aruba/HPE product knowledge (or equivalent from Cisco/Juniper - they'll train on HPE stack)
- Data center experience (servers, storage, virtualization) is a plus
- Security background (firewalls, NAC, zero trust) increasingly important
- Comfortable presenting to technical and executive audiences
- Willingness to travel 30-40% (campus site surveys, onsite POCs, higher ed conferences)
- Experience with higher education customers is helpful but not required - you'll learn the vertical