It was an extremely smooth and good process. The recruiter reached out regarding my application to first set up a hiring manager system design screen.

The system design screen was smooth and conversational. We discussed some approaches for making a commenting system on social media and the tradeoffs therein.

I was moved to the final loop. Almost all the interviews were very warm and conversational, focusing on my skillset as an engineer. They delved into challenging problems in my career and analyzed them, and quizzed me on general concepts (caching strategies, request tracking, etc.), but decidedly did not throw random "LeetCode Hard" problems at me.

The coding questions asked were very simple (one was to create a Doubly Linked List; I forget the other). The goal was not really to get to the solutions (anyone can) but to talk through thought processes.

I ended up being rejected, I believe because I was not really a good fit. It was a strongly Java role, which I've lost touch with in the last few years. Despite that, this was easily one of the best interview loops I've done in recent memory, and it was pleasantly surprising to find in a company of Adobe's size.

General system design principles, concepts on typical data structures, etc.