Expedia rejection, refund processor SD ran long
Replies (5)
had a similar SD round a few months back, different problem but same vibe where the constraint changes everything you'd normally design. easy to get tunnel visioned on the first approach
was the house robber variant close to the actual LC one or did they twist it
pretty close honestly, just a slightly different constraint on adjacent picks, nothing that threw me off
sorry to hear about the reject, that BQ values thing every round sounds exhausting ngl
wait the refund processor being sync is wild, doesn't that kill your throughput under load? did they push back on that at all
yeah I pushed back a little but they said it's a hard constraint from the payments team, something about needing sync confirmation before charging
4 rounds total including phone screen seemed pretty standard from what I've seen, felt like a fair loop even with the reject