Exodus Point data engineering interview questions sit where quant-adjacent hiring meets implementation discipline: you keep SQL grain honest when facts meet dimensions, you pick ROW_NUMBER or RANK with explicit tie-break columns instead of hand-wavy ordering, you defend heapq versus full sorted() when K is tiny next to n, and you narrate k-way...