Data Scientist applicants have rated the interview process at LogRhythm with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 50.9% positive. This is according to Glassdoor user ratings.
Candidates applying for Data Scientist roles take an average of 14 days to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at LogRhythm overall takes an average of 19 days.
Common stages of the interview process at LogRhythm as a Data Scientist according to 2 Glassdoor interviews include:
Group panel interview: 29%
Phone interview: 29%
Presentation: 29%
IQ intelligence test: 14%
Here are the most commonly searched roles for interview reports -
I applied through other source. The process took 2 weeks. I interviewed at LogRhythm (Boulder, CO)
Interview
The interview process consisted of data science and engineering evaluations. Phone screens followed by a brief take-home coding challenge followed by an on-site interview with multiple groups (with a follow-up in my case).
Great team who know what they are looking for. Felt respected throughout the process and received a lot of feedback.
Ultimately, did not get the offer, but glad for having had the experience nevertheless. Advice to data science applicants - make sure to hone your engineering game as well as theory. LogRhythm, after all, is a software company.
Interview questions [1]
Question 1
How to debug slowdowns on the worker nodes in the distributed setting?
I applied through a recruiter. I interviewed at LogRhythm (Boulder, CO) in May 2017
Interview
I interviewed in May 2017. The process took about 6 weeks. I interviewed on the phone twice, completed a project, and interviewed in person. The first part of the in person interview really confused me. They asked questions completely outside of data science. They explained that there are multiple positions and are looking to see which skill gaps I would fill. That does make sense I suppose. If they had asked me if I could fill that skill gap early on, I would have told them no. In the end, the recruiter called me and politely told me that they liked me a lot, but they need a data scientist with more dev ops experience.
Interview questions [1]
Question 1
Linux doesn't contain 'real' files. Where can runtime system information (e.g. system memory, devices mounted, hardware configuration, etc) be found?