Databricks backend loop, rejected after System Programming round
Replies (6)
their loss honestly, sounds like you handled the rest of the loop well. good luck with whatever's next
went through something similar a few months back, got the Log Writer question too and also ran out of time on the concurrency part. feels like that round is built to catch people off guard
"but shipped a bug under time pressure" wondering what is the bug that costed you the round that was otherwise going good? Also no starter code is going to be so time consuming, do they expect to run any inbuilt tests in system coding round or pseudo code is sufficient?
how'd you even think to switch off LCA mid round? that seems like a hard pivot to make under pressure
honestly just panicked when LCA wasn't working and started thinking about the subtree size pattern instead, kind of a lucky guess ngl
damn the System Programming round again lol. did they give you any starter code or did you have to design the whole interface yourself?
no starter code, had to define the interface myself which ate into the time too tbh
sorry to hear man, sounds like you did everything right except that one round. rough way to go out