Top 8 Pricing Interview Questions
Browse 8 real-world technical and behavioral interview questions about Pricing. Review scenarios, edge cases, and architectural best practices.
How would you build a rating engine, and how do you reproduce a quote you gave someone eighteen months ago?
Model the rating algorithm as an ordered set of steps over versioned rate tables, pin every quote to the exact rate version and input snapshot that produced it, and keep eligibility and referral rules outside the price calculation so an underwriter decision never changes the number.
A customer disputes their total and asks why. Can your system answer?
Only if it recorded which rules fired, in what order, against which lines, at the moment of the order. Recomputing today gives a different answer because prices and campaigns have moved, so the price becomes unexplainable exactly when someone needs it explained.
How do you size and price an engagement when the scope is still uncertain, and what do you do when you are told to cut the number?
Estimate bottom-up against comparable work, carry an explicit three-point range with contingency as a visible line, then choose a commercial shape that matches the uncertainty. When asked to cut, change scope, phase or team mix — never re-estimate the same work downwards.
How does the reserve figure your systems produce end up changing next year's rates, and where does that loop break?
Reserving estimates what business already written will ultimately cost, and pricing needs that cost attributed back to the characteristics that were rated. The loop breaks over which period a loss belongs to, over recent years whose figures are still moving, and over premium earned at rates nobody charges any more.
How would you price a feature that no customer asked for?
Absence of requests is a demand signal you have to explain before you price anything; once you know whether the need is latent or absent, choose the packaging first — core, tier upgrade, or add-on — and price against the buyer's alternative rather than your build cost.
Marketing want to raise the price of a plan a million subscribers are already on, and change what it includes. What has to happen in the catalogue?
Three separate requests hide in that sentence. Pricing new sales is a new catalogue version; repricing the base is a commercial migration per subscription with notice; changing contents is both. The usual defect is not an edited offering but a shared object one level down that both versions reference.
A shopper adds items on their phone while logged out, then signs in on a laptop where they already had a cart. What should happen?
You have two carts and no rule that is right for every case, so the merge has to be a deliberate product decision rather than whichever write lands last. Prices and stock have both moved since the older cart was created, which is the part that turns a session problem into a correctness one.
Your promotions engine lets two discounts stack when it should not. How do you fix it and stop it recurring?
Model eligibility, exclusivity, and priority as explicit promotion data rather than accumulated conditionals, pin a deterministic evaluation order because the same two discounts applied in a different sequence produce a different total, and persist a price trace finance can read months later.