First was an initial call with the recruiter. Pretty standard stuff, making sure what they are looking for is inline with what the candidate is seeking. Second step was a call with VP of Engineering. Again, pretty standard call here. Nothing technical, it's mostly them selling you on the position and company and providing you a bunch of info. You should have some good questions to ask in return though. 3rd was a technical assessment via hackerrank. Question was take 2 strings as inputs and determine if they are anagrams. Then to increase the level of difficulty, question was altered a bit to take a short string and long text and determine if there are anagrams matching the string inside the long text. After tech assessment another recruiter call. Brief, just to talk about the onsite interview. Last was the onsite interview. Met with people in various functions from HR, PM, swdev team members, and sw manager. Not super technical. sw manager asked a scenario about working with PM's along team collaboration and would increase in difficulty the question. Not hard, just wondering how you think. Technical question was one that was listed here. In Java write a method that to insert a new node into a sorted linked list of integers such that the list still remains sorted. The catch is all the nodes have a final member variable for next, so you cannot alter the node. After all this you quickly finish up with the recruiter. They'll ask you a bunch of questions to get feedback on the interview and the process. They really want feedback. Then you'll get a follow-up email with a survey about your interview experience as they want even more feedback. Then when you get the phone call saying you were not selected you get a brief generic sentence as to why you weren't selected. This left a sour experience. They want detailed feedback on the interview process but then are as brief as possible on their feedback to you.