Difficulty
Average
Candidate-reported interview insights
Explore commonly reported questions, interview rounds, difficulty, duration, and candidate experiences at Automatiq.
Difficulty
Average
Average rounds
2.6
The interview started with a recruiter call that lasted about 20-25 minutes. After that, I received an email saying they wouldn't be moving forward with my application, and the reason they gave didn't make much sense. I really feel like I should have at least gotten a chance to interview with the hiring manager.
The interview started with an unproctored, timed, custom HackerRank assessment. It wasn't like a typical Leetcode question but focused on making API calls and saving responses based on business rules, similar to a Leetcode Easy or Medium. After that, there was a technical interview with three engineering staff members, including the potential lead. This part lasted about an hour and began with a design problem where we discussed how to handle various aspects (X, Y, Z), database choices, etc., using typing or drawing. Then, they asked about my experience with web scraping, unit testing, and other smaller topics. They seemed particularly interested in experience with Selenium or similar tools.
overall the interview went super smoothly, the person running the meeting was on point and asked really coherent questions, the team was great too and the feedback was fast.
A focused selection of the most detailed candidate-submitted questions.
Practice technical, system design, and behavioral questions with Zitlee.
Interview information is based on candidate reports and may not represent the current official hiring process of Automatiq.