Real, anonymous reports from people who interviewed for Software Engineer at Qlik, newest first and distilled into what to expect across the loop.
After a recruiter call, I moved into a hiring manager conversation and then into a take-home assignment. The assignment was broad: I was asked to build a microservice where a user could interact with an LLM in different ways. They gave multiple possible directions, and the goal wasn’t just to wire up an API—it was also to think through how I’d test the system. I remember them emphasizing testing beyond basic correctness: scalability, handling different traffic scenarios, and similar concerns. There wasn’t a strict deadline, but they said people often spend around 8 hours.
My process started with a recruiter-style touchpoint and then moved into a hiring-manager discussion that set the tone for a frontend-heavy path. It ended up feeling smooth and fairly relaxed, and the interviewers came across as friendly and polite, which really helped me settle in instead of trying to guess what they wanted. The questions were generally easy to medium, but they were still technical in a grounded way—focused on JavaScript fundamentals and React concepts, along with machine-coding style problems.
The interview process typically starts with an HR screen, followed by a hiring manager discussion, and then progresses through multiple technical rounds, including coding challenges and discussions about past experiences. The timeline can vary, with some candidates experiencing longer processes with multiple touchpoints and others moving quickly through the stages.
Candidates are often required to complete a take-home coding assignment that emphasizes not only coding skills but also design, testing, and architectural reasoning. This assignment is usually followed by a discussion with engineers to walk through the solutions and decisions made.
Technical interviews are heavily focused on core programming concepts, data structures, and problem-solving, often requiring candidates to write and reason through code in real-time. The technical bar can be specific, with some candidates finding the questions detail-driven rather than conversational.
Throughout the process, there are several discussions aimed at assessing cultural fit and understanding the candidate's background, motivations, and how they approach work. These conversations are generally friendly and low-pressure, helping to create a comfortable environment for candidates.
Candidates have reported mixed experiences regarding communication throughout the process, with some feeling a lack of timely updates and closure after interviews. Clear communication is noted as an area for improvement, as delays in feedback can lead to frustration.
The overall atmosphere during interviews is described as supportive and constructive, with interviewers being friendly and approachable. However, the intensity of the technical evaluations can create a challenging environment, particularly in coding assessments.