Databricks full loop, one bug, rejected next day
Replies (6)
rip. the clarification eating up the clock thing happened to me too, felt like i spent half the round just answering why questions before i got to write anything
did they give you a reason beyond the test cases thing or was that it
wait they actually pushed back on you needing a lock during payment? that's wild, i had a similar architecture round and mine just wanted to hear the tradeoffs out loud
optimal commute again lol. feels like every single databricks post starts with that one
seems like it comes up in every post about them, i've seen it mentioned a bunch of times now
the system programming round is brutal ngl, that's the one that gets people. sorry it didn't work out
same, i totally blanked on the concurrency stuff too. wish there was more prep material for that one specifically
Reply to @User-wp2n6yeah honestly i knew going in that was gonna be my weak spot, just didn't expect the rest of the loop to go so smooth and still get cooked at the end
honestly the fact that the question bank is everywhere and they still nitpick you over one bug is wild. good luck on the next one