Check out your Company Bowl for anonymous work chats.
Bowls
Get actionable career advice tailored to you by joining more bowls.
Followed companies
Stay ahead in opportunities and insider tips by following your dream companies.
Job searches
Get personalized job recommendations and updates by starting your searches.
Liatrio interviews FAQs
Devops Engineer applicants have rated the interview process at Liatrio with 3.5 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 40% positive. This is according to Glassdoor user ratings.
Candidates applying for Devops Engineer roles take an average of 30 days to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at Liatrio overall takes an average of 45 days.
Common stages of the interview process at Liatrio as a Devops Engineer according to 2 Glassdoor interviews include:
Presentation: 25%
Personality test: 13%
Group panel interview: 13%
Background check: 13%
Skills test: 13%
Phone interview: 13%
IQ intelligence test: 13%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 4 weeks. I interviewed at Liatrio in Mar 2023
Interview
There seem to be numerous interview stages, including a screening call, a technical interview, and two presentations of an assignment. However, everyone is kind and willing to answer any questions.
Interview questions [1]
Question 1
What would you tell DevOps is for you?How do you secure inner traffic in Kubernetes? Tell me about SDLC?
I applied through a recruiter. I interviewed at Liatrio (Oakland, CA) in Dec 2017
Interview
Liatro's interview process was relatively straightforward at first. It involved a few introductory calls with Chris and Ravi, followed-up by a technical challenge and presentation over video conference with them and the tech team. Finally, there was an in-person interview at Liatrio's office (or client's office depending on what they're doing at the time).
Overall, I'm rating them a neutral because while the first parts of their interview process were straightforward, their in-person interview was quite bizarre. They asked questions that had nothing to do with DevOps, and I suspect it was because they were smaller at the time, and every new hire had to do a bit of everything. However, none of that was mentioned in their job description. The in-person interview finished with beers at a local pub, and by then, I was so bamboozled with what they had asked that I decided it wasn't for me; the feeling was mutual on their side I'm sure.