It was an extremely smooth and good process. Recruiter reached out from my application to first set up a HM system design screen. The system design screen was smooth and conversational, we discussed some approaches on making a commenting system on social media and the tradeoffs therein. Got moved to the final loop, almost all the interviews were very warm and conversational, focusing on my skillset as an engineer, delving into challenging problems in my career and analyzing them, and quizzing me on general concepts ( caching strategies, request tracking etc. ), but decidedly not throwing a random number of LC Hard problems at me. The coding questions asked were very simple ( one was create Doubly Linked List, forget the other ), the goal was not really to get to the solutions ( anybody can ) but to talk through thought processes. I ended up being rejected, i believe cause 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 was pleasantly surprising to find in a company of Adobe's size.