Dropbox Software Engineer interview experience

One coding track included a key-value transaction problem plus a multithreading/resource-management style challenge that was similar in spirit to a token bucket. I ended up spending a lot of time on rollback logic, and what hurt was realizing my approach was more complex than it needed to be—rollback only mattered in the simplest scenario where another transaction was accessing the same key during a read or write.

Later, I also went through a deep, standalone database-style coding round that required supporting transactions including nested transactions, plus rollback of individual