Me postulé a través de un reclutador. El proceso tomó 1 semana. Acudí a una entrevista en Axon (Seattle, WA) en ago 2015
Entrevista
Phone prescreen with HR rep. Was told i'd be having a technical interview with one person but then on the day of it was someone else. Neither of the interviewers were embedded engineers, which is the position i was applying for, not that it mattered for the type of questions they asked.
I was asked some logic puzzles and asked to solve the problems in coding language of my choice. But i didn't have to use perfect syntax.
The fizz/buzz was easy to solve by converting each number to a string then searching the string for a '3' or '5'. But apparently this wasn't the solution the interviewer was looking for. So i'm not sure if he wasn't prepared or had some preconceived ideas on how it should be solved that didn't match how i solved it.
The Sudoku solver was a bit trickier without having a whiteboard or pen and paper to write things down to visualize the board. I solved it with a brute force method. I was then asked to provide the more elegant solution which I did. The interviewer didn't seem to like the fact that i used a single dimensional to represent the board instead of using a two dimensional array. Not that it really matters.
At this point it had been less than 30 minutes and he turned it over to me for questions. That is usually a bad sign. It seemed like he wasn't impressed so i asked a few questions then the interview ended. I received a rejection email the next day.
Overall the HR staff and interviewer were friendly and responsive, but the technical interviewer didn't seem to have working knowledge of the questions he asked or had very narrow ideas on how he wanted the problems solved.
Preguntas de entrevista [2]
Pregunta 1
Write a program that prints the numbers 1 to 100 but for any number that has a '3' or '5' (not a multiple a 3 or 5) in it print Fizz/buzz or both. This is a harder variation of the normal fizz/buzz problem.
4 rounds of interviews, one behavioral/get to know the team and yourself, one system design style interview and two technical rounds in C++ with a couple of different engineers. Fairly spaced out meetings over a couple of weeks from start to finish.
Preguntas de entrevista [1]
Pregunta 1
One of the technical interview questions was a compound data structure question, i.e combine two data structures to solve a novel problem.
Me postulé en línea. Acudí a una entrevista en Axon en feb 2025
Entrevista
One live coding interview with two interviewers. Coding interview questions were very related to low-level C programs. One interviewer showed up late and had not reviewed my resume prior to discussing with me.
Preguntas de entrevista [1]
Pregunta 1
Discussed technical experience and preferred coding language then immediately began interview. Interview was one question with a strict 30 minute time frame to complete the question. Initially the interviewer suggested pseudocode was allowed but then corrected my syntax as I began writing.
Four rounds of interview all in one day totaling about five hours of non-stop interviews: 1 system design question related to their products, 2 coding challenge with focus in OOP, 1 team fit
Preguntas de entrevista [1]
Pregunta 1
How would you design our products. Coding question about designing minesweeper