Nexxen Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 32 interview experiences · FREE TO READ
Which role are you interviewing for?
14 roles · 32 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Nexxen.
Nexxen
Devops Engineer
Mid Difficult Neutral experience No offer 2 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Coding System Design
The interview process involved a long technical interview on Zoom lasting 45 minutes, followed by a 2.5-hour technical interview with a lab component at their offices. There was a lot of networking involved, with deep questions about understanding flow and traffic, and it was much longer than other interviews.
Confirmed questions1 question
- Can you thoroughly explain the entire process that occurs when you hit enter after typing google.com, covering networking and protocols?
Nexxen
Data Scientist
Senior Difficult Negative experience No offer 1 round
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical Coding
This was a bad interview. I was told there would be no coding for the round, but there was. The interviewer seemed really unprepared and was pretty rude. He asked resume questions and then with only 8 minutes left, he had me open a doc on my computer and type out what was supposed to be a coding question.
Confirmed questions7 questions
- Questions about my resume and deep learning concepts like recurrence, transformers, and CNNs, as well as the math behind loss functions. There was also a graph coding question, but it wasn't provided formally; he spoke out a question off the cuff that I had to solve. I'd avoid this one.
- Resume questions
- Deep learning questions about recurrence
Nexxen
Senior Software Engineer
Senior Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Panel Background check Offer
Interview formats
Behavioral Technical Coding System Design
The hiring process kicked off with a 30-minute HR call to align expectations. Next, there was a technical Zoom interview with the team leader and a seasoned developer. They gave me a rundown of the company and team's activities, then asked me to share my past experiences, emphasizing one project I significantly contributed to. The following technical interview was on-site, lasting about 2 hours. It had two parts: tackling architectural challenges on a whiteboard, followed by a "day in the life" simulation. I was given a laptop with a functional project and Jira tickets that included setup instructions and "customer complaints." It was a really neat experience, and the interviewers were available to help, ensuring I didn't get stuck. Finally, I interviewed with the VP, CTO, and HR. The initial meetings with the VP and CTO were more introductory, focusing on future plans and ensuring mutual benefit from the role. The entire process concluded within 10 days, culminating in an offer. Throughout, the atmosphere was friendly and welcoming, and the technical questions were relevant to actual job requirements, avoiding obscure algorithms or 'leetcode' style problems.
Confirmed questions7 questions
- Can you detail the project you led, providing diagrams and explaining the decisions made?
- How would you approach solving these architectural problems based on the actual Nexxen application?
- Could you demonstrate your coding skills with this fully functional sample application?
Nexxen
Group Leader
Lead Average Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Panel Presentation
Interview formats
Technical Coding System Design Behavioral Presentation
First was a zoom call where I had to describe a system I worked on, then a technical code and design question. The second interview was with the R&D manager, who wanted to know about my management style, what difficulties I managed, and how I envision my team. The third interview was with the company's architect, regarding the current technology they used, and my background and knowledge about streaming.
Confirmed questions2 questions
- Can you describe a system you have worked on, detailing its strengths and potential improvements?
- How would you design a system to stream a large volume of content effectively, addressing load balancing for unknown content types and ensuring maximal output?
Nexxen Interview Questions
Quoted word for word from Nexxen interview reports.
“How would you implement a class for O(1) add, remove, and random element retrieval?”
Read reports →“Can you explain the distinction between the `==` and `===` operators in JavaScript?”
Read reports →“Can you explain the functionality of this code snippet, which implements a circuit breaker design pattern?”
Read reports →“Can you thoroughly explain the entire process that occurs when you hit enter after typing google.com, covering networking and protocols?”
Read reports →“What are the use cases for the circuit breaker design pattern as shown in this code sample?”
Read report →“Was sponsorship needed now or in the future?”
Read report →“Tell me about compression algorithms.”
Read report →“What are your methods for ensuring thread safety in Java?”
Read report →“Could you elaborate on the circuit breaker design pattern implementation presented in the code?”
Read report →Formats, difficulty and experience
Across all 32 Nexxen interview reports.