Robinhood Onsite Fulltime SDE Interview: Load Factor and API Design Challenges

Yunnan-Burma: Classic load factor (https://www.hack2hire.com/companies/robinhood/coding-questions/67cf7c4eaca6a2fa74a72d1c/practice?questionId=67cf7ef7aca6a2fa74a72d1f) VO: PDD: Normal behavioral ques

Yunnan-Burma: Classic load factor (https://www.hack2hire.com/companies/robinhood/coding-questions/67cf7c4eaca6a2fa74a72d1c/practice?questionId=67cf7ef7aca6a2fa74a72d1f) VO: PDD: Normal behavioral questions. Presenting a project requires a PPT; the recruiter told me a maximum of two pages. SD: Classic job scheduler, but unique in that job run failures do not require retrying.

Coding Seems to be a new question (at least I haven't seen it on Geography). Given a list of APIs ["1/REGISTER/user1/100", "2/REGISTER/user2/200"", "3/FRIEND_REQUEST/user1/user2", "4/ACCEPT_FRIEND/3", "5/SEND_MONEY/user1/user2/50"], write a function to return the final balance of all registered accounts. This example returns "1:50, 2:250". This mainly tests extensibility and design patterns. The first number for each API is the request_id. The parameters for the register API are user_id and the initial balance. friend_request is user1 and user2, and accept_friend is the request_id. Money cannot be sent between two users who are not friends.