Box Onsite Interview
Hi Guys, I have Box interview coming up with Box, for the backend general role. I was told by the recruiter that the following would be covered 1. coding/ debugging/ cs fundamentals 2. multithreading/concurrency Anyone with any pointers on what can I expect from this (especially in concurrency and multithreading) Also, any pointers to resources for multithreading would be great! Update : Well I cleared the phone screen and I have got the first onsite round :) Here, I will have one hour of Algo and Design (where my knowledge on multithreading, concurrency and distributed design would be tested) and 2 hours of Coding. Would like to know what is exactly expected in first round( is it system design?) and what resources should I refer? #engineering #software #swe @Box
Congrats on clearing the phone screening! To my surprise I did not have a system design round. 3 coding interviews, including the 2h long one, 1 behavioral, and 1 to explain in detail some complex project I had worked in the past. About your "knowledge on multithreading, concurrency and distributed design", I was asked in all coding interviews if my solution would work with multiple threads (of course not) and why, and potential solutions. Only in one of them I have to actually implement the solution.
Thanks for sharing your experience :) I appreciate it!!
@Box can I DM you? I have an onsite coming up with Box
Thank you guys for the information. The 3 coding rounds are they LC style or general real world progression type problems?
Hi! It's real world progression. Expect LC medium (according to my experience). Do concertrate on multithreading topics.
Hey @zwUc75! It's been more than a week since my 3 hour interview. I did follow up with the recruiter, but he has no update yet. Is this normal? Or should I just consider that my application is rejected?
@op Can I DM you? I have an onsite coming up with Box. Your inputs will be very valuable
I interviewed last November and I was told the same. I followed this course https://www.educative.io/courses/java-multithreading-for-senior-engineering-interviews, but at the end, none of the coding interviews required any knowledge of concurrency besides a synchronized block in Java.
Lol. "For this exercise please use concurrency in such a way that nobody would ever actually do it in production code..." (Oh, maybe a block would be fine. I thought you meant synchronized method... But even blocks are usually avoidable)
A couple of the coding interviews were more of less like this: - Implement this assuming you handle only one request at a time - now assume you have multiple requests concurrently, how do you handle that? - oh a synchronized method/block, that's not very efficient, explain how else how can you do it in a more efficient way (didn't have to implement the solution though)