Razorpay AI Product Sense interview questions

The question behind every AI product decision: a repeatable test, applied step by step, and the willingness to say 'a rule does this better' when it does, and 'a model, with a reviewer' when it does not.

A design question with a regulatory constraint arriving halfway. The interviewer wants a useful product on both sides of it, and a clear line between preparing a decision and making one.

Analysts spend most of a case gathering evidence and little of it deciding. Build the copilot around assembling the case and explaining signals, keep the decision with the analyst, and measure decision quality as well as speed.

Shopkeepers want to know where their money is, in their language, without opening a dashboard. Start with answers that need no permission, add one-tap confirmed actions, and keep refunds and credit behind explicit approval.

Repeat items are predictable; meal plans are a nice demo. Start with replenishment, expose ordering to outside assistants with one confirmation, and keep household preferences inside your own app.

A classic AI product sense prompt. The trap is a chat box bolted onto a grid. The strong answer picks a user, runs every job through an AI-fit test, and treats a silently wrong number as the main risk.

A growth prompt with a hard constraint. Three engineers rules out most ideas, and doubling usage also doubles the compute bill. The interviewer wants a funnel diagnosis and two or three bets that fit.

A product design question where the obvious feature, answering homework questions, works against the user's real goal. Strong answers design for learning, for the exam, and for the phone the student actually has.

Tenfold growth is not an optimisation problem. The interviewer wants to see you find new users the product does not serve today, and protect reliability and margins while doing it.

Often the first question in an AI PM loop. Generic answers ('AI is uncertain') score poorly; concrete changes to specs, testing, cost and launches score well.

Explain the task a product handles well, compare the current alternative and defend one improvement with evidence from actual use.

Small sellers have little time, uneven digital skills and thin margins. The strong answer finds the two jobs where AI changes their week, and avoids an assistant that sounds helpful and does nothing.

An accessibility prompt that tests empathy and judgment together. The design is easy to sketch; the hard part is deciding what the system must never guess about.

The most common story in AI product development. A demo proves the model can do something; a product needs it to do that thing reliably on inputs nobody chose. The strong answer separates those milestones and resets expectations without losing the sponsor.

The user is driving. Every design choice follows from that, and candidates who sketch a chat screen fail the question in the first minute.

A craft question that separates PMs who have shipped AI features from those who have read about them. The answer is a document organised around failure modes, thresholds and evidence.

Chat is the default answer to 'add AI', and often the wrong one. The interviewer wants you to match the interface to each job, and to say where a button beats a conversation.

A strategy-sized design question. The tempting answer replaces the search bar with a chatbot. The scoring answer keeps fast keyword search for the shoppers who know what they want and uses AI for the shoppers who don't.

A principal-level design and strategy question. Every default assumption (literacy, a good phone, fast data, English, a credit card) fails. The answer has to pick a job worth solving and an economic model that survives.

Standard prioritisation frameworks miss the thing that makes AI ideas risky: nobody knows yet whether the model can do it reliably. The strong answer prices that uncertainty in.