What they're really askingAre you running toward this, or away from something? A career‑change answer that sounds like escape makes them nervous.

Your frameYou've done the architecture half of this job for decades — designed the solution, defended it to boards, owned whether it could actually be delivered. What you haven't owned is the win itself. You want the full cycle, and you want it now because you've got the credibility to do it at the senior end rather than learning it from the bottom.

What they're really askingWill you be bored, or worse, condescending to the team?

Your frameName the parts that are genuinely harder than architecture work: compressed timelines, no formal authority over anyone on the deal, and having to be right in the room rather than right in a document three weeks later. Respect for the discipline is what they're listening for.

What they're really askingWill you stay long enough to be worth the ramp, and is the movement a warning?

Your frameSeparate contract engagements from permanent roles first — a run of contracts is a working pattern, not instability, and conflating the two is what makes the history look worse than it is. For each permanent move, give the specific reason in one clause, without criticising the employer. Then close on what you are optimising for now, in terms the role can actually satisfy. Ramp is expensive; they are asking whether they will get it back.

What they're really askingIs there a story here I need to worry about?

Your framePlain, unapologetic, one line — then pivot to what you built with the time. An independent practice, a published framework and a body of writing is a stronger answer than any continuous‑employment story, because most candidates have nothing like it. Don't over‑explain; the length of the answer signals how much you think it needs defending.

What they're really askingDid you prepare — and can you run discovery on us?

Your frameDon't recite their website. Bring one observation about their market position or service mix, and one question only someone who'd actually done the homework would think to ask. You're demonstrating the skill they're hiring for, not proving you can read.

What they're really askingDo you own a structured method, or do you improvise and call it experience?

Your frameStart from a quantified statement of what the customer was trying to achieve — not a product or a feature list — and say how you forced the quantification. Then: how you mapped any vendor claims against the organisation's own governance and policy constraints, what you produced (architecture plus the items flagged as must‑resolve), and how the narrative stayed continuous into delivery. Name the hand‑over point explicitly. The structure is the answer; say it out loud as structure.

What they're really askingWill you be the obstacle, the rubber stamp, or something more useful than either?

Your frameDon't fight the choice — it has momentum and somebody's name on it, and you have no credit to spend yet. Split it into two written lists: what the business can decide for itself, which you leave alone, and what has to be resolved before it can safely proceed, each with the risk named and what would close it. The decision stands, its conditions become visible, and you've shown them what "earlier next time" would buy.

What they're really askingAre you someone who keeps relitigating, or someone who can be overruled and still be useful?

Your frameSay it once, plainly, with the consequence and the mitigation attached — and put it in writing where it survives. Then help the thing succeed. A risk that's been raised and accepted is a legitimate outcome: the business is carrying it knowingly rather than blindly. Add the honest check, too: confirm you were actually overruled and not just working the wrong stakeholder for six weeks, because that's a qualification failure, not a political one.

What they're really askingDo you understand that most deals are lost to nothing, and do you know that the reflex answer is usually the wrong one?

Your frameDiagnose before prescribing. Find out whether they want to move and can't commit, or don't want to move — those need opposite treatment. If they want to move, adding urgency makes it worse; you find the specific unproven thing the decision is resting on and you retire it structurally. If they don't want to move, you press the cost of inaction or you qualify out honestly. Saying "I'd chase with a follow‑up deck" is the answer they're expecting and the one that doesn't get you the job.

What they're really askingWill you serve requests, or will you take a position?

Your frameMore options is what a customer asks for when they can't choose between the ones they have — the request is a symptom, not a requirement. The useful move is to give them a recommendation with your name on it and say what would change your mind. Note that this is the hardest habit for an architect, who is trained to present trade‑offs neutrally; say that out loud, because knowing your own default is what they're listening for.

What they're really askingDo you have a repeatable structure, or do you improvise?

Your frameConfirm who's in the room and what each of them needs from the meeting. Business before technical: what's the cost of how this works today. Quantify it in their numbers. Then current environment and constraints. Then decision process — who else, what steps, what timeline. Close with one specific, dated next step. Say the structure out loud as structure; it reads as discipline.

What they're really askingWill you become an order‑taking quote machine?

Your frame"Happy to — price for what, exactly?" Then trade: you'll get them a real number fast if they'll give you fifteen minutes on seat count, sites, servers and after‑hours expectations, because a number without those is a number you'd both have to renegotiate later. You're not refusing; you're making accuracy the reason.

What they're really askingDo you know what the call is for?

Your frameA good one ends with them having told you something they hadn't articulated to anyone before — including themselves. A bad one ends with you having presented. If you did most of the talking, it wasn't discovery.

What they're really askingDo you read this as an obstacle or as data?

Your frameIt's a qualification signal first — either the champion lacks the standing they claim, or the deal isn't real yet. Coach the champion rather than going around them: build them something worth taking upstairs, then offer a session the buyer would actually want to attend (the business case, not a demo). If access never comes, that's a forecast decision, not a persistence problem.

What they're really askingWill you resent being measured, and will you keep the CRM up to date?

Your frameAnswer honestly about quota, then move immediately to commercial consequence: point at specific instances where your recommendation determined whether an investment proceeded. Finish by naming the discipline explicitly — forecast hygiene, qualification rigour, CRM as the record of truth — as a system you respect rather than admin you'll resist. That last sentence is the one they're waiting for.

What they're really askingDo you understand recurring revenue, or only project cost?

Your frameSay what you'd need before pricing: site count, server and cloud footprint, line‑of‑business app complexity, after‑hours expectations, and the state of their documentation. Then the shape: per‑seat recurring for managed support, a separate security stack line, backup/DR, plus a one‑off transition project sized to the mess you inherit. Note that the transition is where margin is most often lost.

What they're really askingDo you actually understand the business model you'd be selling?

Your frameProject margin is realised once and can be estimated with reasonable confidence. Managed‑service margin is cost‑to‑serve spread over years, and it's destroyed quietly — by non‑standard kit the service desk can't script against, by undersized onboarding, and by scope that was never written down. Which is why the SOW's exclusions matter more than its inclusions.

What they're really askingAre you a blocker, a pushover, or a partner?

Your frameNeither yes nor no — a trade. Reduce scope rather than price, price the risk in explicitly, or take it up with numbers attached: here's the cost‑to‑serve, here's what we'd need to remove to make it work, here's what it looks like if we win it as‑is. Make the decision someone else's, but make it an informed one.

What they're really askingWill you claim breadth you don't have? Every candidate who answers "all of them" gets probed until they break.

Your frameName one you're genuinely deep in. Name a second you're actively growing into. Then give the operating model for the rest — foundations solid enough to ask the right questions, and a clear sense of who to pull in and when. It's almost certainly the same answer the person asking would give about themselves, which is why it lands.

What they're really askingDo you know the channel exists, and will you use it before you commit rather than after?

Your framePull in the vendor's channel SE or the distributor's design desk, before anything is presented to the customer. Say what you'd ask for by name — design validation, sizing sanity check, competitive positioning, evaluation licences. Add the boundary: they help you win with their product, so you keep the customer relationship and the pen. Mentioning that boundary unprompted is what separates this answer from a generic one.

What they're really askingHave you thought honestly about ramp, and will you be a cost centre for two quarters?

Your frameDon't say "straight away" — nobody believes it, and it suggests you don't respect the catalogue. Give a shape instead: shadowing and certification first, contributing on live deals under review by the second month, scoping unsupervised by the end of the first quarter. Then turn it into a question: "what's your own expectation — how long before you'd want me scoping without review?" You've just signalled that you intend to be measured.

What they're really askingDo you understand that margin is made in the wording and in the channel, not in the price line?

Your frameThree places, in order. The exclusions — a loose sentence is a variation you can't charge for. The delivery review — hours you didn't verify are hours somebody else eats. And the commercial position: deal registration lodged early, licensing verified by the distributor's desk, pricing model matched to how the thing is actually bought. Most candidates answer this with "accurate estimates," which is the least of the three.

What they're really askingWill you protect the team's time and the service desk's sanity?

Your frameThree tests: can we deliver it on the standard stack; is the cost‑to‑serve real once you count the environment's actual state; and is there a decision process with a date attached. Fail two of three and it's a requalify or a no. One caveat worth adding out loud: before calling it on the date test alone, ask whether they'd move if the risk were removed — a frightened buyer and an uninterested one look identical on a forecast and need opposite treatment. Then add that saying no early is cheaper than saying no in month four of onboarding.

What they're really askingDo you understand where deliverability actually breaks?

Your frameThree options, priced honestly: explicitly out of scope with a documented escalation path to their vendor; in scope as a priced exception with named engineers trained on it; or in scope at a defined "best endeavours" tier with the limits written down. What you don't do is leave it unstated — that's the ticket that eats the account's margin in month two.

What they're really askingHave you seen the consequences of pre‑sales optimism?

Your frameDocumentation. The environment was never properly captured, so every ticket becomes a discovery exercise, first‑call resolution collapses, ticket volume runs at two or three times what was priced, and the client's experience of month one defines the relationship for years. Onboarding is where the deal is actually won or lost, not at signature.

What they're really askingCan you sell standardisation as a benefit rather than a limitation?

Your frameExplain the support model as the product: the reason we can resolve their issues fast is that our engineers see the same stack across every client, and every exception makes their own service slower. Then offer the honest path — if the requirement is genuinely business‑critical, price it as a supported exception rather than pretending it away.

What they're really askingDo you have the spine to protect delivery, and the tact to keep the relationship?

Your framePick a case where you refused something technically unsound or undeliverable, offered a credible alternative, and kept the account. The Result should include the relationship surviving — a story where you were right and the customer left teaches them something they don't want to hire.

What they're really askingCan you operate at executive altitude without authority?

Your frameBoard or steering‑committee material is your strongest ground here — most competing candidates have never presented above IT manager level. Emphasise what you led with (the business consequence, not the technical detail) and how you handled the pushback.

What they're really askingAre you honest about failure, and did you learn the deliverability lesson?

Your frameOwn the miss without theatrics, describe the recovery, and land on the process change you made so it couldn't recur. Refusing to produce a failure story is itself the answer they'll record.

What they're really askingThis is the core mechanic of the job — can you do it?

Your frameA cross‑functional programme where you had accountability without authority. Name the mechanisms, not just the outcome: a shared view of the truth, a standing cadence, one named owner per open item, disagreements surfaced in the room rather than afterwards.

What they're really askingWill you pitch on reflex, or run discovery?

Your frameDon't perform. Ask what they use it for, how often, what annoys them about the one they've got, what happens when it dies mid‑meeting. Then position against that. The trap is that the question invites a pitch; the pass mark is refusing to give one until you know something.

What they're really askingHow senior is your read on this function?

Your frameThree that make you sound like you've done the job: How is pre‑sales measured here — technical win rate, influenced revenue, something else? Where does pre‑sales stop and delivery start, in practice rather than on the org chart? And: tell me about a deal you lost recently and why. That last one gets you an honest read on the team, and hiring managers remember being asked it.