IntercomAI Product Manager interview preparation

Accuracy and trust are different things. The feature saves no time if people double-check everything, and the fix starts with finding out why experts are cautious.

Explicit ratings are rare, biased and vague. The strongest feedback signals are things users already do. The interviewer wants a design that captures them and turns a few explicit reports into labelled examples.

Trust is easy to survey and hard to measure. The interviewer wants a composite built from behaviour, interpreted carefully, and validated against outcomes the business cares about.

A principal-level question about recovering from failure in public. Apologies are necessary and not sufficient; users come back when the product visibly changes and the company keeps its promises.

Hiding the bot is off the table in many markets and was never a good bet. Disclose on the first turn, then win back the lost sales by testing how you disclose and what the assistant does next.

Models sometimes describe actions they never took. Let the system decide what is done from checks it runs itself, and show users the evidence.

A common dismissal with a two-sided answer. The interviewer wants you to separate what is weak about thin wrappers from what makes many successful software businesses 'wrappers' too.

AI changes pricing because each use costs money and value per use varies. The interviewer wants the trade-offs of each model, matched to the product, and a hybrid that protects margin.

A pricing question about where the value of falling model costs should go. The answer depends on margin targets, competition and whether price or capability wins customers.

The innovator's dilemma in SaaS form. If you don't ship the AI, competitors will; if you do, per-seat revenue shrinks. The interviewer wants a pricing and product transition that grows revenue with the work done.

Matching free is tempting and often ruinous when every use costs money. The interviewer wants a segmented response that protects the customers you can keep, the margin you need, and the value only you deliver.

Everyone knows models make things up. The interviewer wants to hear why, which kinds of hallucination exist, and a layered set of product defences, without promising to eliminate it.

A pipeline design question with an automation trap. Writing summaries is the easy part; writing into the system of record that forecasts revenue is where the design needs care.

A deadline you did not choose and a change that touches every output. The interviewer wants a plan that treats API compatibility and behavioural compatibility as different problems.

A security design question that decides whether enterprise customers will sign. The answer has to make cross-tenant leakage impossible by construction, and then prove it with tests.

A cost lever that can silently serve wrong answers and leak one user's data to another. The interviewer wants the failure modes and a design that keeps the savings where they are safe.

Guardrails are often described as a box in a diagram. The interviewer wants specific checks, where each runs, what it costs in latency, and what happens when one fires.

Handoffs decide how customers remember an AI support experience. The interviewer wants explicit triggers, a view on the two kinds of error, and a handoff the human can act on without re-asking.

Plain language is easy to write and hard to guarantee. Let customers describe procedures in words, make money and identity checks deterministic steps, and require simulation tests before publishing.

Model providers disclaim accuracy, so any guarantee you give is yours alone. Offer measured service levels per action type with credits and a capped liability, backed by independent testing or insurance.

Decide which support tasks an agent can safely own. An 82% pass rate needs a denominator, a breakdown of failures and a comparison with today's service.

A RAG answer can fail in the retriever or in the generator, and one accuracy score cannot say which. The interviewer wants two evals, a production loop and a launch bar tied to what a wrong answer costs.

'Hallucination rate' sounds like one number. In practice it is three different failures, and the one that matters most is the hardest to see.

Green dashboards and angry users at the same time. The strong answer treats the complaints as evidence about the eval, not noise to explain away.

Single-turn test sets miss what breaks over a conversation: forgotten constraints, contradictions and drift. Build conversation-level cases, simulated users with goals, and session metrics.

An estimation question that tests commercial judgment. The inference bill is where the arithmetic starts; the number that decides the answer is somewhere else.

The cheap option per conversation is the expensive one per customer, until you read how the vendor defines 'resolved'. Two calculations, and the second one is where the offer is decided.

The most expensive AI failures are the confident wrong answers that users accept. This question tests whether you can find their footprints in behaviour data.

When the metric is the invoice, every edge case becomes a billing dispute. Principal-level answers design a definition customers can audit and a price that survives the worst month.

First AI features have unknown quality and cost. Write OKRs that reward learning and a measured launch, and keep out key results the team cannot honestly commit to.

The landmark study of AI in a call centre found the same pattern: big gains for new agents, small speed gains and small quality losses for the best. Report by skill tier and give experts a lighter mode.

A transparency question with a regulatory core and a design challenge. The interviewer wants the rules stated carefully, and disclosure that informs users without cluttering the product.

The data flywheel is real, and so is the trust cost of getting consent wrong. The interviewer wants a decision framework: legal basis, contracts, user choice, de-identification and the value actually expected.

RAG is the most common live-build topic. Strong candidates choose the simplest approach that works for 30 documents, make citations real, and test retrieval and answers separately.

An exact Given/When/Then cannot test a model that words things differently every time. The scored answer shows which criteria stay exact and how the rest become measurable.

Overpromising is common in AI because demos impress and capabilities move fast. Panels want to see you reset expectations with evidence, protect the relationship, and fix the process that caused it.

The company owns what its agent says. Show that you honoured the promise, found how many others were affected and moved policy from soft guidance into hard rules and sources.

The central AI UX question. The interviewer wants patterns that make errors cheap to spot and cheap to fix, sized to what an error costs.

A shared vocabulary for one of the biggest decisions in AI product design: how much the AI does on its own. The interviewer wants the levels, and the rule for choosing among them.

Citations are the main trust device in AI answers, and published audits of shipped search engines find many that do not support the sentence they sit on. The interviewer wants citations at the right granularity, checkable in seconds, and honest about what they support.

Users let an assistant act when they can see what it did and take it back. The interviewer wants an activity log, real undo, and clear handling of actions that cannot be undone.

A deceptively simple design question. Numbers feel transparent, but most users cannot act on them, and the numbers are often less meaningful than they look.

Users either expect too much from AI features and churn after the first failure, or too little and never try the useful parts. Onboarding sets the mental model that decides which happens.

Approval screens fail in a predictable way: people click 'approve all'. The interviewer wants a design that focuses attention on the changes that matter and makes careful review fast.

Trust that outruns accuracy is as dangerous as distrust. The interviewer wants design that keeps experts engaged where it matters, without making the tool tedious.