Staff Software Engineer applicants have rated the interview process at Applied Research Associates with 2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 70.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Staff Software Engineer roles take an average of 35 days to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at Applied Research Associates overall takes an average of 21 days.
Common stages of the interview process at Applied Research Associates as a Staff Software Engineer according to 2 Glassdoor interviews include:
Group panel interview: 25%
Phone interview: 25%
Background check: 13%
IQ intelligence test: 13%
One on one interview: 13%
Presentation: 13%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 5 weeks. I interviewed at Applied Research Associates
Interview
There was a 30 minute phone interview with a staff member of the team that was interested in hiring me. The team that wanted to hire me was on location at a testing facility, which is not normally where they are located so they then flew me out onto the location for a face to face interview. It was very casual and everyone was extremely friendly.
I applied online. I interviewed at Applied Research Associates (Albuquerque, NM) in Sep 2021
Interview
Had a phone screening first, then was setup for an onsite interview.
Onsite Interview:
Asked several fairly straightforward behavioral questions with the division lead. She also asked me a couple questions about my resume.
After this, I spoke separately with 2 different team leads, both of which had my resume on hand and asked me questions about it. There were no coding questions, but they did mention some of the technologies they were currently using and we talked about them. I assume they mostly wanted to know if I could hold conversation around important topics.
Topics were mostly C++. Honorable mentions were given to C#, Databases, Python, but more like a "We've used these on occasion and only when necessary."
Interview questions [1]
Question 1
Are you comfortable working in C++?
Are you comfortable asking questions when you're stuck?
Are you comfortable with code reviews?
Are you familiar with version control (git/svn)
(No coding questions)