Me postulé a través de un reclutador. El proceso tomó 4 semanas. Acudí a una entrevista en Axon (Seattle, WA) en abr 2016
Entrevista
4 different phone screens which should have been at most 2. On-site process could have been fine if they had space to actually interview somebody and upheld a more professional attitude with co-workers. One of the engineering team members continually disagreed with my use of JSON syntax, even after showing them the documentation. Overall, not the engineering team is not bad but I get the feeling many are very junior in the industry and their technology stack is about 5 years behind.
Me postulé a través de un reclutador. El proceso tomó 3 días. Acudí a una entrevista en Axon en dic 2014
Entrevista
I first met with a manager for coffee, it was a great experience and was shown the product and talked about the company. Had a good chat overall. I came away with a really good feeling about the company and their environment.
I was then scheduled for a 30-45 minute tech screen via google docs
I was asked two questions in the tech interview: fizzbuzz and looksay
fizzbuzz was pretty straightforward, however, the looksay question was a bit un-intuitive.
Preguntas de entrevista [1]
Pregunta 1
I felt that asking the looksay question is the wrong caliber for a front-end developer. I had some difficulty with it because I have never heard of this question/algorithym before (I googled it later). It felt like the interviewer was looking for one specific answer and I could tell that he was getting frustrated that I didn't know the answer. He quickly ended the interview.
To me it seems like this is not the type of question to be asking if they are looking for a front-end developer. Seems like a good question for a senior DB role.
Me postulé a través de un reclutador. El proceso tomó 3 días. Acudí a una entrevista en Axon
Entrevista
Worked with a recruiter who initially scheduled a one-hour meet-and-greet with an Engineering Manager over coffee. The two of us discussed the company, the position, and talked in general about web development technology. Was great. Loved talking shop with this guy.
A day later, I was scheduled for a technical phone screen with a Sr. Engineer. The interviewer described his role for about a minute, then went straight into having me do coding exercises.
We signed into an online code editor that allowed the interviewer and myself to see each other type in the editor, real-time.
The first question was FizzBuzz. I had heard this question before, years ago, and knew it was a simple loop with some modulus operators and if statements.
After that, we proceeded onto the next question: write the algorithm to generate the "look-and-say sequence." He explained it and showed me example output in the code editor. It was easy enough to grasp.
I stumbled for a bit, feeling panicked and nervous. He asked me to talk through how to solve it, which I did--and that helped a bit. I still struggled to translate my thought process to code under the pressure though.
After about ten or fifteen minutes, I came up with a solution that was approximate but didn't produce the right output right away.
The interviewer ended the call after this exercise. I felt like I was probably close enough that they would be fine proceeding, but they chose not to continue any interviews with me, ending my candidacy then and there.
After I got off the phone, I spent about five minutes looking over and modifying my algorithm before I got the correct output.