ranking

One model, multiple objectives, a single shared backbone. Interviewers want you to explain precisely why sharing helps (regularization, data efficiency) and the failure mode that wrecks naive setups. Here is the answer.

Ranking differs from regression: a wrong absolute score is acceptable, a wrong ordering is not. What shows depth is the pointwise/pairwise/listwise breakdown and why pairwise (LambdaMART) remains the practical default. Here is the answer.

In search and recommendation, A/B tests can be slow and noisy because they pit different users against each other. Interleaving compares two rankers inside the same user's results and spots winners with far less traffic. Here is how.

Top-N-per-group is the window-function question every data round asks, and the trap is RANK vs ROW_NUMBER vs DENSE_RANK. What interviewers want is picking the right ranking function for ties and understanding window frames. Here is the pattern and the tie nuance.

The most common ML system design round. Interviewers reward the funnel structure: candidate generation, then ranking, then re-ranking, with the right model at each stage plus an honest plan for cold start, freshness, and feedback loops. This lays out that structure.

E-commerce search is where retrieval, ranking, and business goals meet, and it carries a strict exact-match requirement (brand, size, SKU). The signal is query understanding plus hybrid retrieval plus business-aware ranking. Here is the design.

Notification systems fail by spamming users until they mute, and a mute is a permanently lost channel. The signal is treating it as a per-user send/hold/batch/suppress decision optimized for long-term trust, not for clicks or volume.

Every keystroke has to return ranked suggestions in tens of milliseconds, at search-engine QPS. The interesting part is the data structure and what you precompute, not the query path. Here is the design that holds up under the latency budget.

PYMK is graph recommendation at billion-node scale. The interviewer is testing for one instinct: do you generate candidates from the social graph, or naively try to score every pair? Here is the design that holds up through the follow-ups.

Rank items by relevance alone and you ship ten near-identical results and a filter bubble. What interviewers want is a re-ranking stage that scores the list as a set, plus the metric that proves it works.

Recommending events (or jobs) breaks ordinary recsys in two spots: items expire and items are local. What matters is how you handle perishability, geography, and the fact that every item is a cold-start item. Here is the design.

Reps only have so many hours, so the model exists to steer them toward the leads worth calling. Interviewers listen for value-weighted prioritization, carefully built conversion labels, and evidence of revenue uplift measured against a holdout.

Showing the top 10 is easy. Showing a player their global rank among 50M others, updated live, is the real challenge. The answer turns on the right data structure, sharding, and approximate ranks for the long tail. Here is how leaderboards scale.

New courses launch every week and most browsers are signed-out or brand new, so the interesting half of this problem is what you recommend when you have almost no behavioral signal. The other half is avoiding the trap of optimizing engagement into a clickbait catalog.

This product succeeds or fails on a feedback loop measured in seconds: every swipe is a label, and the following video must respond to it. The tricky part is exploring widely enough to learn what someone enjoys while avoiding a filter bubble or the amplification of junk.