Expedia rejection, but that OA problem was kind of fun
Replies (8)
Rough that the follow ups tanked it after you actually solved the base problem, sounds like you knew the material though.
Had something kinda similar pop up in an OA a while back, definitely a fun one to think through even under time pressure.
Did they let you pick any language for the OA or was it locked in?
Any language, I just used python since the math logic was simple enough either way.
OA sounds way more interesting than most of the LC mediums companies recycle, appreciate you writing it out.
What'd they actually want out of the payment SD round, just high level flow or did they want you down in the weeds on idempotency?
Mostly flow and failure handling, didn't get too deep into implementation specifics before time ran out.
Their loss honestly, sounds like you handled the harder follow ups better than you're giving yourself credit for.
The little values BQ at the start of every round was the same when I went through too, caught me off guard the first time.
GCD giving you the largest shared factor but not necessarily the cheapest packet count is a good instinct, curious if they pushed back on that at all.