Sales engineering manager: what to ask before you say yes

01

How many deals you keep

Manager ads differ a lot in how much deal work they leave with the manager:

Vercel's head of Solutions Architecture for EMEA should "step in yourself when it matters most: architecture reviews, migration plans, and high-stakes executive presentations."

Glean's Solutions Engineering manager is "willing to roll up your sleeves and get directly involved in important customer and deal situations, but your primary measure of success is the performance and growth of your team."

CoreWeave's player-coach keeps hands on "the occasional deployment you run yourself."

Sanity's EMEA manager gets "hands-on in the team's highest-impact opportunities, from discovery through close."

Gorgias's head of Solutions Engineering will "scope deals, build prototypes, review code and sit in customer Slack channels next to your team, especially in your first months."

Sierra's manager should "own your own enterprise deals as an individual contributor, running discovery, demos, and technical deep dives alongside your team, while leading and growing a team."

Glean's manager joins important deals but is measured on the team's performance and growth, and Vercel's steps in when it matters most. CoreWeave and Sanity keep the manager hands-on in the occasional deployment or the highest-impact deals. Gorgias puts it especially in the first months, which raises the question of whether the load falls as the team grows. Sierra's manager carries their own deals as an individual contributor and also runs a team. Vercel, Glean and Sanity say which deals the manager joins and leave the number open. Ask how many, and then three more things: whether you keep a territory or a number of your own, who takes over your current deals, and who decides which deals count as strategic. If deal work stays in the job, put it early, in the deal reviews, where risk can still be found and dealt with before the quarter ends.

The offer may carry another title, such as Solutions Architecture manager. The questions are the same, though ads for Sales Engineers, Solutions Engineers and Solutions Architects weigh the demo, discovery and the business case differently, so the deals you keep may look different.

02

The standard you will hire to

If the role includes hiring, you need a standard before the first interview, and it is fair to ask whether the company has one. When I led Sales Engineering at Leapwork, we assessed Sales Engineering candidates on value messaging, how they ran a meeting with executives, how they tied a demo to the customer's objectives, qualification, and their style and creativity. As a scorecard, each point gets its own score and a note of what the candidate did:

Value messaging: the customer outcome the candidate tied the product to.

The executive meeting: how they ran it, from the opening to an agreed next step.

The demo: which of the customer's objectives each part of it answered.

Qualification: what they found out about the deal, and what they said was still unknown.

Style and creativity: how they communicated and adapted their approach.

The notes matter more than the scores. Two interviewers can give qualification the same score for different reasons, and the note shows what each of them saw. If the company already assesses candidates, ask to see its scorecard and compare it with these five points. If it has none, writing one is your first piece of work.

03

Onboarding and deal reviews

Onboarding may land on you even when the ad does not name it. Ask who owns a new Sales Engineer's first months and how progress is checked. A good answer has milestones and a weekly review with the manager.

Every deal has a technical puzzle, a business value puzzle and a qualification puzzle. The Sales Engineer leads the technical puzzle and shares the other two with the account executive. A deal review that walks through all three judges the situation of the deal rather than the person presenting it. Ask how reviews run today, and whether you would inherit them or set them up. If the role names KPIs, ask which, and agree what a PoC win rate or technical win rate counts.

04

If you would rather not manage

A senior Sales Engineer who wants to grow may take a manager role because there is no other way up. At Leapwork, career paths in Business Value Consulting, Partner Sales Engineering and Principal Sales Engineering gave experienced Sales Engineers routes other than management. GitLab's Solutions Architect ladder states the same choice: "A Solution Architect can progress through the various individual contributor levels or leadership roles and associated levels." Above Senior Solutions Architect it has Staff and Principal, beside Manager, Senior Manager and Director.

A specialist track needs work for it and a way to be promoted into it. The work can be partners who need Sales Engineering support, customers who need help building a business case, or complex technical or commercial questions a principal could own across the team. As for promotion, at GitLab the justification for a Staff or Principal promotion is due two quarters before the promotion date, a Principal candidate collects letters of recommendation and presents to a panel, and such promotions are "limited to a predetermined number of candidates per quarter." Ask the company that made the offer how its senior track works on each of these points. If the answer is vague, assume management is the step up on offer, and decide knowing that.

05

If you are the one making the offer

Agree the answers to these questions with the head of Sales Engineering before you make the offer. Hiring, onboarding and deal reviews are what managers learn in Leading Sales Engineers, and hiring and onboarding decisions across countries and commercial regions are part of the advisory for Sales Engineering leaders.