It started with me reaching out to a recruiter through LinkedIn. I was then told that if a hiring manager was interested in my resume, I would be contacted shortly. I heard back the following week and was then set up for a Skype interview. This interview lasted for an hour and the questions were pretty straightforward (one coding question and one testing/design-related question).

In the week following the Skype interview, I was contacted once again and invited onsite for four interviews.

Interview 1: A lunch interview which included learning more about the team and what they were working on. After lunch, we returned to the office for whiteboard coding questions. This round lasted for about 90 minutes.

Interview 2: The interview began with me describing (using a Sequence Diagram) my current project. Afterward, I was asked a coding problem and to determine the test cases. This interview lasted for about 60 minutes.

Interview 3: A purely testing question followed by some whiteboard coding. This interview also lasted for about 60 minutes. After this interview, the interviewer told me that my next interview would be with the Hiring Manager.

Interview 4: A purely behavioral interview where the hiring manager assessed if I was a good fit for the team.

I heard back in a week and was extended an offer.

Tips: Don't be scared. I was a little overwhelmed when I walked onto the campus, but then HR and the other interviewers really eased me into the interview. Speak your thought process aloud so the interviewer knows what you're thinking. I was given a few hints when I was stuck, and those hints were very helpful. I was also very comfortable writing code on the whiteboard because I spent two weeks before the onsite interview practicing on a whiteboard. This really helps. It's a must-do!

Approach the testing questions in a very structured manner, as they really appreciate that. Cracking the Coding Interview has those steps mentioned.

Resources: GeeksforGeeks - This was the only online resource I referred to, as I had gone through Cracking the Coding Interview and Programming Interviews Exposed in the past.

Nothing too difficult. Just know your basics about Data Structures, Algorithms, and Testing if interviewing for an SDET position.