I am a recent BS graduate in computer science and I applied to a front end role on Indeed via Venture Staffing and got a reply from an Aruba recruiter after 2 days. He set up a 30 min phone interview with an engineer. The first 5 mins or so was about my resume and background. The next 10 mins was about the role and the team. The rest was technical questions and I was asked the following: 1) Javascript concepts: closure, function context, 'this' keyword 2) What happens when you type in a URL on the browser? I told him how DNS works but he was expecting a reply around HTTP protocol. 3) On linux how do you access the last 10 lines of a file? I said I would use the 'vim' command to view the file and do 'shift+G' or similar command to go to the bottom of the file. He replied saying that works but was expecting an answer that has to do with 'tail' command. 4) Python question: what are some in built functions? how would you override them? After about a week, I was invited onsite for a series of 4 interviews (45 min each) with about 6 engineers and a manager. This was purely technical. Here's what I faced: 1st interview: I was shown a piece of javascript code and asked what the output would be. If you know the concept of "scope" you should be able to answer it. Then I was shown a piece of code written in google closure and was asked to at least walk through it explaining what's going on. It was my first time looking at a google closure code so I had hard time in the beginning but after a few hints here and there I was able to get the hang of it. They were trying to see if you understood the logic and are able to cope up. 2nd interview: This was pair programming with a front end engineer. You literally sit in front of a computer with him and do some programming in HTML5, CSS and Javascript. They use NodeJS specifically. If you know your basic CSS selectors and Javascript concepts you should be fine. It was more like a discussion and not an interview. I could sense that the interviewer was testing my thought process. 3rd interview: This was with 2 backend engineers testing your skills in data structures. I was asked to write pseudocode to implement the Mind scrapper game. They give you enough information for you to brain storm and write the code. I used two dimensional arrays to do this. Not sure if it is right or not. 4th interview: This was again with 2 engineers testing your OOP skills. I was asked to write pseudocode to implement a software/system for police to track their vehicles in terms of maintenance (oil life, engine life, brakes etc). It is hard to explain but they give you enough information. Then, they make the problem trickier by saying what if the vehicles also include boats/ships and horses? Again, they were looking for your approach and how you would implement this system. The more in depth you dive into the problem, the better. It was quite a stressful 3 hours but I was glad I was done with it. After a day, I heard back from the recruiter saying "the team unfortunately didn't think you were a good fit. Sorry this did not work out." and that they would "continue to look for someone who would be a better fit". I nicely thanked him and Aruba for considering me. End of story. On the whole, I felt the expectations were quite high especially for me as I am a recent college graduate. Oh well, life moves on.

Phone screen, then an onsite.