Questions were difficult but manageable. The initial recruiter did seem to be in a bit of a rush when interviewing me. All the coding questions were around leet code mediums.
J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez Alarm.com (McLean, VA) en sept. 2016
Entretien
I applied online and had a phone screen, then a grueling 8 hour long interview. Each person I spoke to took an hour, lunch was a couple of young people who cared a little too much about their own colleges. I even spoke to Jean-Paul, which meant I had passed the other screeners, but in the end, I think they weren't actually interviewing me for the right position. They wanted an embedded Linux programmer that was good with GUI, and I am a pure embedded guy good with sensors, buses, low-power and everything else but GUIs. They told me that they would get back to me within 48 hours, but it took over 2 weeks, and eventually they declined without explanation.
Questions d'entretien [1]
Question 1
1) Describe the difference between a semaphore and a mutex and when you might use each.
2) when would you use an RTOS over Protothreads or Bare Metal implementation.
3) There was a software test where I had to populate functions with code to make the program print the correct results to the screen.
4) What is your best quality and worst.
5) Why did I want to come work for Alarm.com.
