Real, anonymous reports from people who interviewed for Software Engineer at DAZN, newest first and distilled into what to expect across the loop.
After a recruiter touchpoint, I had a technical round where the focus leaned heavily on theory. The questions went deep on Node.js and on HLS streaming, and I ended up walking through the full implementation flow rather than just answering isolated prompts.
My process started with a recruiter profile evaluation. They went through my resume and then asked basic questions about my current role, my projects, my notice period, and what I expected on salary. That set the tone—less coding, more alignment on whether my background matched what they were hiring for.
The process typically begins with a recruiter evaluation, focusing on the candidate's background, current role, and salary expectations, setting the tone for alignment with the company's needs rather than immediate technical skills.
Candidates can expect multiple technical rounds that cover a breadth of topics including data structures, algorithms, system design, and specific technologies like Node.js and streaming architecture, often requiring detailed project discussions and problem-solving.
Interviews often include behavioral questions aimed at understanding problem-solving approaches and cultural fit, with managers assessing both technical skills and communication during scenario-based discussions.
Candidates reported varying experiences with communication, with some expressing frustration over long wait times for feedback and a lack of transparency regarding their application status, which can affect overall satisfaction with the process.
The interview environment is generally described as professional and supportive, with interviewers aiming to create a comfortable atmosphere, though some candidates noted instances of less engaging or overly critical interactions.
The interview process is typically well-structured and organized, with candidates appreciating clear timelines and expectations, although some experienced delays that affected their perception of the company's efficiency.
