Embedded Software Engineer applicants have rated the interview process at Alarm.com with 2.8 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 60% positive. To compare, the company-average is 51.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Embedded Software Engineer roles take an average of 15 days to get hired, when considering 5 user submitted interviews for this role. To compare, the hiring process at Alarm.com overall takes an average of 27 days.
Common stages of the interview process at Alarm.com as a Embedded Software Engineer according to 5 Glassdoor interviews include:
Phone interview: 36%
One on one interview: 18%
Skills test: 18%
Drug test: 9%
Personality test: 9%
Presentation: 9%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 5 weeks. I interviewed at Alarm.com
Interview
Prepare to have 1-on-1s with an undisclosed number of engineers. After each interview, the recruiter will contact you to schedule more. There is seemingly no process or reasoning behind the interview process.
Also prepare to get hit with a lowball offer well below the salary range posted on the job listing and below what you previously discussed with the recruiter.
Interview questions [1]
Question 1
Each interviewer had some whiteboard questions. Most were about thread safety or streaming data.
Pretty Straight forward process. Interviewer asked me mostly behavioral questions and a few technical questions regarding my experience. I applied through a recruiter and was contacted by their HR department so everything was a smooth transition.
I applied online. The process took 2 weeks. I interviewed at Alarm.com (Tysons Corner, VA) in Sep 2022
Interview
Standard interview process:
- Phone screening
- Initial interview
- Hackerrank Test
- Followup Interviews (2 in my case)
Questions started pretty conceptual, "describe your resume", and then moved to more technical questions.
Interview questions [1]
Question 1
How much experience do you have with communication protocols?