RazorpayAI Product Manager interview preparation

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 strategic decision with a clear default and specific reasons to deviate. The interviewer wants a framework grounded in evals, volume, constraints and team capacity.

The partner brings more paid accounts but retains part of every payment. Compare contribution and acquisition payback, then negotiate the dependency behind the spreadsheet.

The first vocabulary word of AI product management. Tokens are the unit of cost, speed and memory, and a PM who can't reason in them can't price, budget or design an AI feature.

A small-sounding problem that becomes a big one at volume. The good answer explains why free-form generation produces malformed output and which controls make it near-impossible.

A design trade-off with cost, accuracy and latency all pulling differently. The interviewer wants a measured comparison on real receipts and a hybrid that sends each image down the cheapest path that works.

There is no single best model, and the choice will change within a year. Principal answers design a selection process and an architecture that make the next choice cheap.

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 regulated pipeline where the model reads documents but must not be the one deciding who gets an account. The interviewer wants extraction, checks against authoritative sources, fraud signals, human review and data minimisation.

A runaway agent is a cost problem, a reliability problem and a product problem at once. The answer is part diagnosis, part guardrails, and part design for what happens when a budget runs out.

A principal-level design question with money, regulation, fraud and a dozen languages in one queue. The answer that scores separates complaint types by what the agent may do, and keeps every money decision in deterministic systems.

Card networks have not settled liability for agent purchases. Make the evidence exist at payment time: the mandate the user granted and the cart the agent confirmed. Then route disputes on whether the purchase stayed inside the mandate.

Leaderboards move every few weeks and every team feels the pull. The interviewer is checking whether you have a repeatable switching process or just enthusiasm.

Routing is one of the biggest cost levers in AI products, and one of the easiest to get subtly wrong. The interviewer wants the savings arithmetic and the misrouting risk in the same answer.

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.

India's Digital Personal Data Protection framework is now in force in phases. The interviewer wants the principles turned into product requirements, stated as of a date and checked with counsel.

Activation is the developer platform's equivalent of a product's first-run experience. The interviewer wants a diagnosis from real sessions and a set of fixes that remove each step of friction.

Vague prompts are deliberate. The first five minutes show whether you can turn ambiguity into a buildable, testable scope, and the interviewer is watching that more than the code that follows.

The tool choice is the easy part. Interviewers screen for how you decide on evidence, what you allow near code and data, and how you stop prototypes becoming unowned production code.

Companies that shipped MCP servers exposed reads widely and held back money-moving actions. Start with a few consolidated read tools, test descriptions against real tasks, and gate anything irreversible.

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.