Sales · Chapter 5 of 5
The loop, and moving into sales from a technical role
What the process looks like, and the honest version of the career change.
| Round | What it tests |
|---|---|
| Recruiter | Motivation, comp expectations, quota history |
| Hiring manager | Deal history, territory approach, why this company |
| Mock discovery or pitch | The round that decides it — usually a role-played customer call |
| Panel / cross-functional | How you work with SE, marketing, product |
| Executive | Whether you can be in front of a customer's CxO |
Bring, whatever the level: a deal you won and why it was actually won, a deal you lost with the real reason, your attainment history with context (which quarter, what territory, what was inherited), and a specific account you would target here with a reason.
Crossing over from engineering
- The technical half is your asset and it is not sufficient. The gap is comfort with rejection, with pursuing people who have not replied, and with a number that resets every quarter.
- Solutions engineering is the usual bridge, not a direct move to AE. It uses the technical depth immediately, is customer-facing, and carries a shared rather than individual quota — which is a much softer landing.
- Be honest with yourself about the variable half. Compensation here is genuinely uncertain in a way engineering pay is not, and that suits some people and corrodes others.
- Ask what percentage of the team hit quota last year. If it is under half, the on-target number in the offer is a marketing figure.
The rounds, and what actually gets assessed
| Round | What it tests | The failure |
|---|---|---|
| Recruiter screen | Whether you can describe your number and your motion clearly | Vagueness about quota, attainment and what you personally closed |
| Hiring manager | Whether you understand their motion — deal size, cycle length, buyer | Describing your last job's motion as though it were universal |
| Mock discovery or demo | Whether you ask before you pitch | Pitching. Interviewers plant an obvious wrong assumption to see whether you check it |
| Deal review / pipeline | Whether you are honest about a deal that is not real | A pipeline where everything is going well. Nobody believes it |
| Cross-functional | Whether engineering and support will want to work with you | Talking about the technical team as an obstacle to be routed around |
The mock discovery round is the one that decides most loops, and the preparation is not a script. It is a set of questions you would genuinely ask, and the discipline to spend the first third of the time asking them. Interviewers routinely plant an obvious-looking solution to see whether you take it or check the assumption underneath.
On the deal review, say the uncomfortable thing.
The strongest answer to ‘walk me through your pipeline’ includes a deal you expect to lose and why, and one that is stalled because you could not reach the economic buyer.
A pipeline in which everything is progressing is not credible, and every experienced sales leader knows it — so presenting one signals either inexperience or a willingness to forecast optimistically, which is the most expensive trait a sales hire can have.
The related question they are really asking is about forecast discipline: what makes you move a deal to committed, and what has made you move one back? Having a specific, unflattering answer is worth more than a strong attainment number, because attainment is partly territory and forecasting is entirely you.
Check yourself