How many interview rounds does Next insurance have for a Full Stack Engineer, and what does the loop look like?

For Full Stack Engineer candidates, the process includes an initial conversation and then rigorous technical evaluations. In total, candidates reported 6 interviews, with difficulty reported as average. The early stage aligns on company mission and role expectations, then the technical part focuses on practical coding and theoretical knowledge.

What topics do Next insurance test for Full Stack Engineer interviews?

Expect a strong focus on JavaScript, including closures and variable capture, plus asynchronous JavaScript such as setTimeout. React is tested with distinctions between functional and class components, and there is also coverage of React component concepts related to the evolution from class components to hooks. On the algorithms and CS fundamentals side, you should be ready for string or encoding problems like Caesar cipher, and data structures like linked lists.

Do Next insurance Full Stack Engineer interviews include JavaScript event loop and closure questions?

Yes. The JavaScript foundations section explicitly includes questions about how the event loop handles setTimeout within a loop and what output results. It also includes JavaScript variable scope and closures, where you may be asked what prints to the console for a provided snippet.

How hard are Next insurance interviews for a Full Stack Engineer, and what is the reported difficulty?

Candidate-reported difficulty is listed as average for Next insurance Full Stack Engineer interviews. The technical evaluations are described as rigorous, emphasizing both theoretical knowledge and practical coding. The guidance also stresses communication during technical sessions and writing clean, maintainable code.

What coding and web-framework questions show up in Next insurance Full Stack Engineer interviews?

You may be asked to compare React versus Angular, and for React specifically, explain the differences between functional and class components. There are also sample patterns around resolving a high-stakes technical problem and functional versus class components. On coding, linked list reversal and Caesar encryption pseudocode are explicitly reflected in the question patterns.

What compensation should I expect for Next insurance Full Stack Engineer roles?

No compensation figures are included for Next insurance Full Stack Engineer in the provided data. The only candidate-reported pay-related datapoint available here is an offer rate of 0%, and pay varies by level and location, but specific numbers are not provided.

Next insuranceFull Stack Engineer

Updated Apr 13, 2021

Next insurance Full Stack Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Full Stack Engineer at Next insurance, newest first and distilled into what to expect across the loop.

Get your personalized Next insurance Full Stack Engineer prep plan

Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.

Build my free plan

Hot & recentNewest first

> 1 year

Average Positive Israel

The process began with a conversation to get to know each other and cover details about the company. After that, I had a technical interview that lasted about 1 hour 30 minutes.

In the technical discussion, we talked about my previous projects as part of the interview, not just abstract questions. That made it feel more connected to my actual experience.

> 1 year

Difficult Positive Tel Aviv-Yafo

After applying, I had an initial test with questions across Java and JavaScript, plus object-oriented design and some general problem-solving. It felt like a real filter rather than a casual screen—if I passed, the process moved to interviews.

The next stage was two technical steps followed by HR. In the first technical interview, I was asked to write Caesar encryption code, and then I went into an HR conversation. The whole sequence had a clear, structured flow: test first, then focused coding, and finally the more people-oriented discussion. The difficulty felt high from the start, and I didn’t end up getting an offer, but I walked away knowing exactly what areas mattered—coding fundamentals and clean problem execution.

Unlock every Full Stack Engineer interview experience

Real Full Stack Engineer interview experiences

Difficulty, sentiment and outcomes
New reports added every week

See all experiences

Share your interview experience

Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.