Nagarro logo

Nagarro Frontend Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 39 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
41% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Nagarro.

Showing 3 of 39
Nagarro logo
Nagarro

UI Developer

Engineering · more than a year ago

Senior Difficult Positive experience Accept offer 7 rounds
Interview process
Recruiter call Technical screen Take home Technical screen Technical screen Technical screen Background check Offer
Interview formats
Technical Coding Technical Technical Technical Technical Behavioral

This was a pretty good interview experience, so I wanted to share. There were 7 rounds total. First, an aptitude test with 30 questions in 20 minutes – gotta be fast and try to answer them all. Then a coding test with 3 medium to hard questions. After that, there were three technical interviews, each about 30 minutes with professional interviewers. The first one covered JS basics up to medium level. The second was a tricky MCQ round on the domain, but doable if you know your stuff. The third technical interview had very difficult questions, but the interviewer was great. The fourth was with a senior architect, very knowledgeable, and focused on Angular and RxJS operators since that was my area. I felt good about my answers in these. The last round was HR, which was basically a formality. They asked about location and experience. Documents were requested before this. The recruiter was super active and helpful. The offer came the same day. Just a heads up for Nagarro: you really need solid domain knowledge to get selected.

Confirmed questions4 questions
  • What are some Rxjs operators?
  • Can you explain Js basics?
  • Tell me about Services in angular.
Nagarro logo
Nagarro

Senior Front End Developer

Engineering

Senior Average Negative experience Decline offer 5 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen Background check Offer
Interview formats
Technical Coding Technical Technical

So I applied for a senior position. The process had 3 main rounds, plus 2 HR salary talks at the end. First up was a coding round, 90 minutes total, split into 3 parts. Part 1 had 20 MCQs covering reasoning, aptitude, and English. Part 2 was 2 coding questions. Part 3 had 40 MCQs on React, JS, HTML, and CSS. Then, round 2 was a 30-minute technical chat about React and JS concepts. Round 3, another 30-minute technical discussion, focused on design patterns, Redux flow, and React hooks. I passed all these and then had the HR salary talks. Honestly, they messed up and sent a different offer than promised, which was a bummer and felt like a waste of time. Definitely not interviewing there again.

Confirmed questions8 questions
  • Convert C++ to java variable name
  • Filter unique values
  • What is React Virtual DOM?
Nagarro logo
Nagarro

Front End Developer

Engineering

Entry Average Negative experience No offer 1 round
Interview process
Take home
Interview formats
Technical Coding Other

They have an online test for the first round and it has 3 sections 1. general aptitude and puzzle solving 2. coding test 3. MCQs related to your tech stack. I started the test and when I finished and submitted the test and checked my email there was a mail from Nagarro that I did not qualify for the test because my score does not meet the criteria, and that mail came to me 30 minutes before I submitted the online test. One more thing I noticed most developers have a habit of hitting 'ctrl+s' and during the online coding round is if you accidentally hit "ctrl+s" that will open a save page dialog window and you will be disqualified because you moved to another window their system will think you moved to a new tab for cheating. they should disable ctrl+s on the coding round.

Confirmed questions2 questions
  • General aptitude questions involving percentages, puzzles, and arithmetic progression.
  • Coding test problems focusing on arrays and strings.

Nagarro Frontend Engineer Interview Questions

Quoted word for word from Nagarro interview reports.

What's the difference between HTTP error codes 401 and 403?

Read reports

What is the difference between 'em' and 'rem' units in CSS?

Read reports

Considering the provided CSS selectors (`#id_abc`, `.abc`, `div`) and the HTML element (`<div id="id_abc" class="abc">Test</div>`), which CSS rule would take precedence and apply to the div?

Read reports

What is treeshaking in Javascript and how does it work?

Read report

How is it possible to call a function in a child component from its parent component?

Read report

What is the purpose and implementation of error boundaries within React components?

Read report

What is the difference between a component and a directive?

Read report

Can you tell me if a given string is in camelCase or snake_case, and if so, convert it to the other format?

Read report

Formats, difficulty and experience

Across all 39 Nagarro interview reports.

Interview formats

Technical 53.1%
Coding 32.7%
Behavioral 10.2%
Other 4.1%

Interview difficulty

Easy 10.3%
Average 69.2%
Difficult 20.5%

Candidate experience

Positive 41%
Negative 46.2%
Neutral 12.8%