Service Providers Sales Systems Engineer at Nutanix
Dallas, TX
$196,000–$294,000from the description
Jun 30, 2026
Dallas, TX
Jul 21, 2026
What this job asks for AI summary
A presales systems engineering role supporting managed service providers across the Americas, sitting within a channel-focused SE team. Day-to-day work centers on technical sales support, proof-of-concept management, proposal sizing, and building partner relationships, with subject-matter depth expected across virtualization, networking, cloud platforms, and storage. Suits an experienced presales professional with a background in the service provider or systems integrator space.
Senior level · 10+ years · Remote · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Rare in this occupation — lead with these, and say what you built with them.
What the occupation pays Median $108,178 (middle half $84,682–$137,059). This posting is about at that midpoint.
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (7)
The role is a pre-sales Systems Engineer focused on Managed Service Providers (MSPs) across the AMER region — it sits between a pure technical SE (15-1252) and a business/systems analyst (15-1211); 15-1211 was chosen as the primary code because the day-to-day work is solution scoping, proposal development, POC facilitation, and partner advisory rather than building software.
Two experience gates are stated: 5+ years of presales experience in the Service Provider/SI space AND 10+ years of customer-facing/technical experience overall; the overall years minimum is set to 10 (the higher, role-level gate).
AWS and Azure are listed together as a single public-cloud requirement ('specifically AWS and Azure'); they are treated as interchangeable alternatives on one skill node because the JD presents them as a paired example of the same requirement rather than two distinct mandatory platforms.
Ansible and Terraform appear under a 'familiarity with' qualifier ('e.g., Ansible, Terraform') within the requirements section, suggesting illustrative examples of automation/scripting tools rather than hard gates; marked as preferred accordingly.
Cloud-native technologies and security practices are grouped in a single bullet with understanding-level language; cloud-native is captured as a preferred skill. Security practices is a methodology concept and is omitted per extraction rules.
The posting describes a hybrid/remote arrangement with ~50% travel; remote=true reflects the explicit 'primarily remote' work arrangement statement.
This posting reads as a fully-remote role, so it was scored against the national candidate pool rather than a single metro.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.