MOD 02
The Pre‑Sales Career Ladder
One function, six or seven title bands, and a fork in the road at the senior end.
| Band | Typical title | Scope |
|---|---|---|
| Entry | Associate / Junior Sales Engineer | Shadowed demos, single‑product scope, scripted deals |
| Core | Sales Engineer / Solutions Consultant | Owns discovery‑to‑close on assigned accounts, full demo/POC ownership |
| Senior | Senior SE / Senior Solutions Consultant | Larger, more complex accounts; mentors juniors; handles competitive deals |
| Staff / Principal | Principal SE, Solutions Architect | Multi‑product, multi‑stakeholder enterprise deals; owns technical strategy on the deal, not just execution |
| Architect tier | Pre‑Sales Architect / Enterprise Architect (Pre‑Sales) | Portfolio‑level solutions across a customer's whole estate; blends business, enterprise and technical architecture; often the named technical authority the CTO/CIO on the client side actually trusts |
| Leadership fork A | Practice Lead / Director of Pre‑Sales | People leadership — hires, coaches, and scales a pre‑sales team |
| Leadership fork B | VP Pre‑Sales / Field CTO / Chief Solutions Officer | Strategic technical voice for the company externally; sits with the executive team; shapes product roadmap from market signal |
The fork at the top is worth naming early because it changes what you should be building evidence of now. The people-leadership path rewards coaching, hiring judgement, and team-level metrics. The Field CTO / individual-expert path — the more natural landing spot for a long architecture career — rewards depth, a public point of view, and the ability to be the room's most credible technical voice without managing anyone. Module 20 covers building that voice deliberately. How the package is actually assembled — and the questions that matter more than the headline figure — is the sheet that follows this module.
A day in the life (core to senior band)
- Deal support (the bulk of the week): discovery calls, tailored demos, technical Q&A on active opportunities, RFP sections, competitive positioning.
- Deal strategy: qualification reviews with the AE (is this real, can we win it, should we even chase it), internal deal desk / pricing exception requests.
- Enablement & internal: keeping demo environments current, writing up win/loss notes, briefing delivery on what was promised.
- Non‑linear hours: pre‑sales calendars are reactive to the sales cycle — a POC deadline or an RFP due date routinely overrides a "normal" week. This is the trade‑off for the role's variety and its proximity to revenue.