mediumPalantirDatabricksScale

Find the customers whose return rate exceeded 30% last quarter.

Everyone writes the join and the ratio. Then the result comes back dominated by people who bought one thing and sent it back, and the list is useless to the person who asked for it.

Updated Aug 2026 · Grounded in real Forward Deployed Engineer interview loops and written to a senior-engineer editorial bar.

Everyone writes the join and the ratio. Then the result comes back dominated by people who bought one thing and sent it back, and the list is useless to the person who asked for it.

20 answers per topic instead of 10, plus saved progress and bookmarks · no cardor unlock all 531 remaining answers · ₹2,000 / $25

Every answer, concept and course, all hands-on FDE Lab missions, Premium PDF guides and companion files, the full practice-test bank and work-sample downloads. Referral Premium excludes guide PDFs and their companion files.

6 months · One payment · No auto-renewal

Study alongside free video lessons.

UP NEXT ON YOUR JOURNEY

Next in this trackSync a customer's on-prem Postgres to your cloud at 10,000 updates/sec. You may not install anything on the DB server.Popular right nowWalk me through what actually happens when an LLM generates a response.Popular right nowWhat is a context window, and what are its practical limits in production?

FEDITOR'S NOTE

The SQL is not the test. Three decisions inside the question change the answer completely and none of them are stated: whether the rate is by order count or by value, whether a return is attributed to the quarter of the order or the quarter of the return, and what to do about tiny denominators. The last one is what makes the output usable, because without a minimum-order threshold the top of the list is entirely customers with two orders and one return, which is noise that looks like a finding.

DISCUSSION · 0

No comments yet — be the first to share your approach.