Top 8 Migration Interview Questions
Browse 8 real-world technical and behavioral interview questions about Migration. Review scenarios, edge cases, and architectural best practices.
When your infrastructure is heavily coupled to proprietary managed services, how do you design and execute a cloud provider exit strategy without obliterating the business?
An examination of strategic foresight, the realities of vendor lock-in, and the technical necessity of abstracting proprietary dependencies during a large-scale migration. Use this engineering leadership answer to show the decision, trade-off, and evidence rather than a memorised definition. It also connects vendor management to the point an interviewer is testing.
A better embedding model has come out. What does moving to it cost you?
Vectors from two models live in unrelated spaces, so there is no incremental path — you re-embed and reindex the whole corpus. The real cost is running both indexes side by side long enough to compare them on a gold set, keeping query and document models in step, and retuning thresholds calibrated on the old scores.
You are mapping data from a legacy system into a replacement and the two define a customer differently. How do you work that out?
Agree the business meaning and the grain of each entity before touching field names, profile the real data to find the overloaded and sentinel values, then write a mapping where every target field has a source, a rule, a default and a decision for records that cannot be mapped.
Where does OSS end and BSS begin, and how would you break up a monolithic BSS without stopping the business?
OSS vs BSS architecture separates commercial systems such as catalogue, ordering, charging and billing from network systems such as inventory, activation and assurance. The boundary works because commercial products and network capabilities change at different rates.
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.
The 3G network is being switched off in eighteen months. What work does that create in the BSS and OSS?
Mostly the work of identifying who loses service and moving them, which network data alone cannot tell you. Device capability comes from the IMEI, packet voice needs subscription and IMS provisioning in bulk, and the machine-to-machine base is the population that cannot be reached by a campaign.
You discover two teams have independently built notification services that do roughly the same thing. What do you do?
Find out why it happened before deciding what to do about it, because duplication is usually a symptom of a discovery or ownership failure that consolidation alone will not fix. Then choose deliberately between merging, keeping both, and letting one wither, on the basis of migration cost rather than tidiness.
Pick a product you know well. Which feature would you remove, and how would you know it was safe to remove?
Argue from the cost the feature imposes on everyone who does not use it — surface area, decision load, engineering drag — then quantify who depends on it, find where their need lands afterwards, and stage the removal so you learn before you are committed.