The first technical round started with easier DSA-style questions and some machine coding, along with a smaller set of prompts overall. After that, the second round got into project scenario-style thinking and more machine coding—one piece involved building carousel functionality using React.
Across the rounds, I also saw a pattern of being asked to connect practical coding with a bit of theory. In a manager-led technical step, I worked through a small coding task using a simple mapping input (colors and fruits) and then answered conceptual questions about things like exception handling, future/completable constructs, and differences between related framework concepts. It felt like they were evaluating both my ability to write code and how I explained design/behavior while doing it.
> 1 year
Average Negative London, England
My DAZN process started through a recruiter, with a first phone call that lasted about 30 minutes. It was pretty straightforward—talking about my current role, my tech stack, and how I approached agile methodologies. The next step was two technical tests to complete at home, one focused on backend and one on front end.
What dragged things down was the timeline around the interviews and then the feedback. The phone interview took longer than I expected, and even after I finished the tests, I waited what felt like forever for any response. I eventually gave up after waiting about two weeks, since there was no feedback or next step—just uncertainty. The lack of urgency and communication made the whole experience feel like it was wasting my time.
> 1 year
Difficult Positive Amsterdam
My process started with a quick 30-minute call with a technical recruiter, followed by another 30-minute technical phone interview with an engineer fr…
Unlock every Full Stack Engineer interview experience
