How we assess
Every applicant goes through 5 gates: application, an AI-assisted screen, a live technical assessment scored by a practice lead, a client-fit interview, and reference and credential checks. The questions below come from the live assessment. We score answers on reasoning and trade-offs, not on recalling definitions.
20 technical questions with model-answer hints
Questions 1–10 (role-specific)
Question 1: How do you structure discovery for a complex deal?
Model-answer hint
Business pain, current state, stakeholders, technical constraints, decision criteria, timeline.
Question 2: Demo a product you know well in 10 minutes.
Model-answer hint
Starts from the buyer’s pain, tells a story, shows value early, invites questions.
Question 3: How do you define PoC success criteria?
Model-answer hint
Written, measurable, agreed with the sponsor, time-boxed, tied to a decision.
Question 4: A buyer asks a security question you cannot answer. What do you do?
Model-answer hint
Honesty, a dated follow-up commitment, expert involvement, documented answer.
Question 5: How do you respond to an RFP written around a competitor?
Model-answer hint
Spots wired requirements, uses clarification questions, reframes value, feeds go/no-go.
Question 6: Your account executive over-promises in a meeting. What next?
Model-answer hint
Private alignment, clear scope language, protects credibility with the buyer.
Question 7: How do you adapt a demo for Arabic-speaking executives?
Model-answer hint
Language choice, business outcomes, localised data and interface.
Question 8: When do you stop supporting a deal?
Model-answer hint
Qualification signals, resource cost, alignment with the account executive.
Question 9: What makes a technical RFP answer score well?
Model-answer hint
A direct compliance statement, evidence, specificity, readable structure.
Question 10: Tell us about a deal you lost on technical grounds.
Model-answer hint
Honest analysis, lessons, feedback passed to product.
Questions 11–20 (Business Development core)
Question 11: How do you build pipeline in a market where you have no relationships yet?
Model-answer hint
research, partners, events, referrals, targeted outreach and realistic timelines.
Question 12: How does public procurement in Saudi Arabia differ from private-sector buying?
Model-answer hint
Etimad, formal tenders, local-content scoring, guarantees, longer cycles, strict compliance.
Question 13: How do you build a stakeholder map for a government account?
Model-answer hint
decision makers, influencers, procurement, technical evaluators, relationships and gaps.
Question 14: How do you turn a technical team’s input into a client-ready message?
Model-answer hint
interview the experts, focus on outcomes, plain language, evidence, expert sign-off.
Question 15: What makes a business case convincing to a board?
Model-answer hint
clear problem, quantified options, stated assumptions, risks, sensitivity analysis, a recommendation.
Question 16: How do you gather competitive intelligence ethically?
Model-answer hint
public sources, customer and partner conversations, no misrepresentation, every claim sourced.
Question 17: How do you price a multi-year services deal?
Model-answer hint
cost build-up, margin targets, indexation, payment terms, risk contingency.
Question 18: How do you work with legal and finance on a bid?
Model-answer hint
early involvement, clear inputs and deadlines, review gates, a sign-off log.
Question 19: How do you measure business development success?
Model-answer hint
qualified pipeline, win rate, deal size, partner-sourced revenue, cycle time.
Question 20: Tell us about a partnership or deal that did not deliver what was expected.
Model-answer hint
early warning signs, actions taken, the lesson applied since.
Interviewer tip: Ask for a real example after every answer. Strong candidates describe what they built, what broke and what they changed.
Practical task
2 hours of preparation, then a 30-minute presentation. Given a fictional enterprise buyer brief and a product overview, prepare a discovery question list, a 15-minute tailored demo storyline, PoC success criteria and answers to 5 technical RFP questions. Present to a panel playing the CIO and the security lead.
How to run it Share the brief 24 hours ahead or run it live. Ask the candidate to talk through trade-offs as they work; reasoning matters more than a finished artefact.
Red flags our practice leads watch for
- Demos features in menu order instead of buyer problems.
- Runs PoCs without written success criteria.
- Bluffs answers to technical questions.
- Sees pre-sales as support work with no stake in the deal.
- Universal flag: Vague answers that never reach a concrete system, number or decision the candidate personally owned.
The scorecard we use
Score each dimension 1–4 (1 = no evidence, 2 = partial, 3 = solid, 4 = exceptional):
| Dimension | Weight | What a 4 looks like |
|---|---|---|
| Technical depth, production judgement and security | 40% | Explains how and why, designs for failure and sensitive data, and knows each tool’s limits |
| Practical task and problem solving | 30% | Delivers a working solution with tests and documented decisions |
| Communication and documentation | 20% | Explains clearly to technical and non-technical audiences, in English or Arabic |
| References and regional context | 10% | References confirm the claimed scope; knows the frameworks and data-residency rules that apply |
Pass bar: weighted average of 3.0 out of 4 or higher, with no dimension below 2. The practice lead approves the final result.