Top 7 Versioning Interview Questions
Browse 7 real-world technical and behavioral interview questions about Versioning. Review scenarios, edge cases, and architectural best practices.
The business wants to change a rating factor next Monday. Walk me through what actually has to happen.
In a filed environment the rate is a regulated artefact rather than a configuration value, so the change is versioned by state and effective date, applies to business written from that date rather than to everything, and must leave every existing quote and policy reproducible against the version that priced it.
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.
Design the contract for a public API. How do you handle pagination, idempotency and versioning?
Model resources around client workflows, paginate with an opaque keyset cursor because offset pagination skips and duplicates rows under concurrent writes, make unsafe operations replayable with a client-supplied idempotency key, and evolve additively so that versioning stays a last resort rather than a routine.
How do you write prompts that survive a model upgrade?
Pin the model version, keep the prompt to stable intent and a schema, and record every model-specific workaround as dated, deletable debt. The durable artefacts are the output schema and the eval set - they are what tells you whether the new model is better before you ship it.
Prices must react to demand within seconds, and two users looking at the same item must not see different prices. Which do you give up?
Real-time pricing system design should publish numbered price versions instead of calculating a different answer per request. Compute prices by region and time window, serve the current version consistently, and freeze quotes briefly so users are not surprised during checkout.
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.
What is a design token, and what breaks when you change one?
A design token is a named design decision - color, spacing, radius or motion - that products reference by name instead of raw value. Changing one token can silently alter contrast, layout and brand consistency across every pinned consumer.