Intro to Sales Engineering and Solutions Consulting: SE Interview Process (Mock Demo, Discovery Role‑Play, Technical Q&A)

SE Interview Process (Mock Demo, Discovery Role‑Play, Technical Q&A)

SE Interview Process Study Guide: Mock Demo, Discovery Role-Play & Technical Q&A

For Engineers Transitioning to Presales, BDRs Upskilling, and SEs Sharpening Their Craft

What This Is

This guide prepares you for the SE interview gauntlet—where you’ll face mock demos, discovery role-plays, and technical deep dives under pressure. Why does this matter? Because in real deals, you’ll need to qualify fast (MEDDIC), uncover pain in discovery, demo with precision, and handle objections—all while building trust. Example: A cybersecurity SE in a competitive POC must prove SOC 2 compliance in 15 minutes while a skeptical CISO watches. If you can’t demo this flawlessly in an interview, you won’t win the deal.

Key Terms & Frameworks

• MEDDIC: Qualification framework (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion). Used to filter out bad-fit deals early and focus on winnable ones.
• POC (Proof of Concept): Time-bound technical evaluation (e.g., “Let’s test your API latency for 2 weeks”). Used when the prospect needs hands-on validation before buying.
• Discovery Call: A structured conversation to uncover pain, stakeholders, and decision criteria before demoing. Goal: Avoid “show up and throw up” demos.
• Demo Flow: A repeatable, story-driven sequence (e.g., “Problem → Our Solution → Proof → Next Steps”). Used to keep the prospect engaged and avoid feature dumping.
• Technical Q&A: Deep-dive questions (e.g., “How does your encryption handle key rotation?”). Used to prove credibility and address security/integration concerns.
• Objection Handling: Responding to pushback (e.g., “Your competitor is cheaper”). Used to reframe objections as buying signals.
• Champion: A power user or influencer who advocates for you internally. Used to navigate the buying committee.
• Economic Buyer: The person who signs the check (e.g., CFO, VP of Engineering). Used to align pricing and ROI.
• Decision Criteria: The must-haves for the prospect (e.g., “Must integrate with Snowflake”). Used to tailor your demo and POC.
• Competitive Battle Card: A cheat sheet on how to position against rivals (e.g., “When they say X, we say Y”). Used to differentiate in demos and POCs.
• Whiteboard Session: A collaborative, visual deep dive (e.g., mapping your architecture to their workflow). Used to build trust with technical stakeholders.
• Next Steps (NEXT): Clear, mutual commitments after a call (e.g., “We’ll send a POC plan by EOD”). Used to keep deals moving forward.

Step-by-Step / Process Flow

1. Mock Demo (The “Show Me” Test)

Goal: Prove you can demo like a pro—not just features, but business impact.
How to execute:
1. Prep the story (Problem → Solution → Proof → Next Steps).
- Example: “You’re struggling with slow CI/CD pipelines (Problem). Our tool cuts build time by 40% (Solution). Here’s a live demo of a 10,000-line repo building in 2 mins (Proof). Let’s schedule a POC to test this in your env (Next Steps).” 2. Tailor to the persona (e.g., CTO cares about scalability; DevOps cares about ease of use).
3. Practice “demo jiu-jitsu”—if they ask about a feature you don’t have, pivot to a strength.
- Example: “We don’t have X, but we automate Y, which saves your team 10 hrs/week. Let me show you.” 4. End with a CTA (e.g., “What’s the next step for you?”).

Sample Demo Flow (DevOps Tool):
- Hook: “How much time does your team waste waiting for builds?” - Problem: “Slow builds = delayed releases = lost revenue.” - Solution: “Our tool parallelizes builds across 100+ nodes.” - Proof: Live demo (or pre-recorded video if risky).
- Next Steps: “Let’s run a 2-week POC on your repo.”

2. Discovery Role-Play (The “Listen First” Test)

Goal: Prove you can uncover pain, stakeholders, and decision criteria—not just pitch.
How to execute:
1. Start with open-ended questions (e.g., “What’s the biggest challenge in your current workflow?”).
2. Dig deeper with “impact questions” (e.g., “How does this problem affect revenue/customer retention?”).
3. Map responses to MEDDIC (e.g., “Who else needs to sign off on this?” → Decision Process).
4. Summarize and confirm (e.g., “So your top priority is reducing cloud costs by 30%—is that correct?”).

Sample Discovery Questions:
- Pain: “What’s keeping you up at night about [their current tool]?” - Metrics: “How do you measure success for this project?” - Decision Criteria: “What are the must-haves for this solution?” - Competition: “Who else are you evaluating?” - Timeline: “When do you need this in place?”

3. Technical Q&A (The “Prove It” Test)

Goal: Show you can handle deep technical questions without BS-ing.
How to execute:
1. Clarify the question (e.g., “When you say ‘scalability,’ do you mean requests per second or data volume?”).
2. Answer concisely (e.g., “We handle 10K RPS with <100ms latency. Here’s how…”).
3. If you don’t know, say:
- “Great question—I’ll find out and follow up by EOD.”
- “Here’s how we’d approach this…” (then pivot to a related strength).
4. Bridge to business impact (e.g., “This means your team can scale without hiring more engineers.”).

Sample Technical Q&A:
- Q: “How does your encryption handle key rotation?” - A: “We use AWS KMS with automatic key rotation every 90 days. This ensures compliance with SOC 2 and HIPAA. For your team, this means zero manual work—just set it and forget it.”

Common Mistakes

SE Interview / Practical Insights

What Interviewers Probe For

1. Can you demo like a pro?
2. Tricky situation: “The prospect interrupts your demo to ask about a feature you don’t have.”

3. How to handle: “We don’t have X, but we automate Y, which solves the same problem. Let me show you how.”

4. Can you uncover real pain?

5. Tricky situation: “The prospect says, ‘We don’t have any problems.’”

6. How to handle: “What’s one thing you’d change about your current setup if you could?”

7. Can you handle technical deep dives?

8. Tricky situation: “You don’t know the answer to a technical question.”

9. How to handle: “Great question—I’ll find out and follow up by EOD. In the meantime, here’s how we’d approach this…”

10. Can you differentiate vs. competitors?

11. Tricky situation: “Your competitor does X for half the price.”
12. How to handle: “What’s the cost of not solving this problem? Our customers find that X saves them $Y/year in [time/money/risk].”

Quick Check Questions

1. A prospect says, “Your competitor is 30% cheaper.” How do you respond?

2. Answer: “What’s the cost of not solving this problem? Our customers find that we save them $X/year in [time/money/risk]. Let’s run a POC to quantify that for you.”

3. During a demo, the prospect asks about a feature you don’t have. What do you do?

4. Answer: “We don’t have X, but we automate Y, which solves the same problem. Let me show you how.”

5. A technical stakeholder asks, “How does your solution handle [complex edge case]?” and you don’t know the answer. What’s your next move?

6. Answer: “Great question—I’ll find out and follow up by EOD. In the meantime, here’s how we’d approach this…”

Last-Minute Cram Sheet

1. MEDDIC: Qualify fast—Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion.
2. Discovery: Listen 80%, talk 20%—ask “What’s the impact?” not “Do you have this problem?”
3. Demo Flow: Problem → Solution → Proof → Next Steps—never feature dump.
4. Objection Handling: Reframe as a question (e.g., “What’s the cost of not solving this?”).
5. Technical Q&A: Clarify → Answer → Bridge to impact—never BS.
6. Competition: Differentiate on outcomes (e.g., “We save you $X/year”).
7. Next Steps: Always end with a mutual commitment (e.g., “I’ll send the POC plan by EOD—does that work?”).
8. ⚠️ Never demo without a backup video—technical glitches kill trust.
9. ⚠️ Don’t talk over the prospect—let them reveal pain.
10. ⚠️ If you don’t know, say: “I’ll find out and follow up by EOD.”

Final Tip: The best SEs practice like athletes—record your demos, role-play discovery, and refine until it’s muscle memory. Now go win that interview (and the deal). ?