The interview process was 3 stages: 1. Recruiter call 2. Hiring manager call 3. Virtual on-site The recruiter call was very standard. Basically exchanging info about my background and the position. The hiring manager call was a 60 minute interview split into three 20 minute chunks. The first part was an intro and discussion about my resume. The second part was a short frontend coding challenge using a frontend framework. You are allowed to choose between a few popular ones (I chose React). It was a fairly simple challenge where you are given a buggy, incomplete piece of code and are asked to fix it plus add a feature. Anyone familiar with React should have no trouble solving it. The last part was a brief architecture overview of something on my resume where I was asked to talk about a project I worked on and the architecture behind it. Decisions made, mistakes, trade-offs and all that. The final round is a virtual on-site consisting of a 3 hr coding exercise, 1 hr architecture whiteboard and 45 minute behavioral/"lunch" chat. A breakdown of each interview: The behavioral interview was very casual. It was mostly common behavioral questions and talking about different situations that had come up in my professional experience. The architecture whiteboard was an in-depth overview of a past project. You are asked to draw a diagram of the architecture and walk through it, explaining key decisions, trade-offs etc. You can either sketch the architecture out live or before the interview. The coding exercise was a practical exercise more akin to the kind of work you would do on the job and comes in a variety of languages. You connect to a virtual machine and are given a design document, skeleton code and a few broken unit tests. You'll spend some time going over everything with the interviewer and then they will log off the call. A personal Slack channel is made available to you to ask for help, and they will also rejoin the call every so often to check in. The goal here is to write good, clean code that can be easily extended. You are not expected to complete everything in the document but I would say you may fail this round if you can't get the unit tests to pass given the allotted time. At the 2.5 hour mark the interviewer will reconnect and end the exercise. They will run your code through a series of bad inputs, and then you will be asked to walk them through your code and answer questions along the way. Overall, I really enjoyed my experience interviewing with Asurion. It's one of the best in the industry because it's very practical.

I had a phone screen, then a take-home challenge, followed by a round of 4 interviews, a final interview, and then the HR call with the offer. The process was more comfortable than what I experienced with other technical interviews

After chatting with the recruiter on Linkedin, I was scheduled for an interview. The date/time came and went without anyone actually calling me. I have not received any communication either. Not sure what game they are playing but I would stay away from these people.