Solutions Sales Executive Interview Questions UK: 8 Real Questions and What Interviewers Want

Most Solutions Sales Executive interviews in the UK follow a pattern, and knowing it beats guessing. Below are eight questions from our bank of 12, each with a note on what the interviewer is really after.

Eight Solutions Sales Executive interview questions, and what the interviewer is thinking

1. Walk me through how you would run discovery with a prospect who knows they have a problem but is not sure what solution they need.

Why they ask: They want to see that you diagnose before you pitch.

2. Tell me about a complex solution sale you won that combined several products or services.

Why they ask: They want evidence you can orchestrate a multi-part deal, not just close a single product.

3. How would you build a total cost of ownership case when a competitor's solution is cheaper on paper?

Why they ask: They are testing your commercial thinking beyond price.

4. What does a typical week as a Solutions Sales Executive involve, and what makes someone good at it?

Why they ask: They want to check you understand how the role differs from standard sales.

5. A customer says they will buy only if you can deliver a feature that is not available yet. What do you do?

Why they ask: They are checking integrity and how you handle product gaps.

6. How do you work with a pre-sales engineer to plan a demo or proof of concept?

Why they ask: They want to see you can partner with technical colleagues and keep demos purposeful.

7. Tell me about a time you lost a deal after a proof of concept or pilot. What did you learn?

Why they ask: They are looking for honest reflection and learning from setbacks.

8. How do you handle security and compliance questionnaires from a customer's IT team during a deal?

Why they ask: They want to know you can handle technical due diligence without stalling the sale.

A sample answer to question 1

Walk me through how you would run discovery with a prospect who knows they have a problem but is not sure what solution they need.

I start by agreeing an agenda and asking permission to dig into the detail. Then I work from the business outcome backwards: what is the problem costing them, who feels it, what have they already tried, and what happens if nothing changes. I'd map the current process, the systems involved and any integration points, because that is where complex solutions succeed or fail. I always ask who else needs to be involved and what a good decision looks like for them, including budget and timing. I take notes in the CRM straight afterwards, then write the customer a short summary of what I heard and ask them to correct it. That playback does two jobs: it proves I listened, and it gives me a shared problem statement to build the proposal on. Only then do I bring in a solutions engineer to shape something that fits, rather than demonstrating features nobody asked for.

Common mistake to avoid: Jumping to a demo too early; asking only about features rather than outcomes

Want the rest?

Full model answers, key points and common mistakes for all 12 questions are on the Solutions Sales Executive interview questions page. The first five are free, no sign-up needed.