Nanonets logo

Nanonets Software Engineer Interview Questions
& Process

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

Based on 6 interview experiences · FREE TO READ

4 Rounds average
Average Typical difficulty
50% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Nanonets.

Showing 3 of 6
Nanonets logo
Nanonets

Senior Software Engineer

Engineering · more than a year ago

Senior Average Positive experience Accept offer 4 rounds
Interview process
Technical screen Technical screen Recruiter call Onsite
Interview formats
Coding System Design Behavioral Behavioral

So, there were 4 rounds in total. First was a live coding session where I had to write code for a given problem. Then, we had a system design discussion, focusing on low-level design for a real-world tech problem. After that, I had a chat with the CTO about general tech stuff. Finally, there was an in-person meeting to check for culture fit.

Confirmed questions1 question
  • Could you design an ATM and explain how it works from start to finish, covering all potential real-world situations?
Nanonets logo
Nanonets

Software Engineer

Engineering · more than a year ago

Entry Easy Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Technical Coding Behavioral

The interview vibe was really nice and welcoming, which helped me share my thoughts and ideas easily. It was a productive and comfortable chat.

Confirmed questions1 question
  • What are your ideas on enhancing web application performance?
Nanonets logo
Nanonets

Software Engineer

Engineering · more than a year ago

Mid Difficult Neutral experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical System Design

I had a call with HR and then the following interviews were scheduled one after the other. There were a total of three rounds: First was the HM round where we discussed my past projects and my career goals. Then there was an LLD round where I had to design an ATM machine. Finally, there was an HLD round where I had to design a system service that depends on two downstream services with varying rates. This system needs to scale to serve different tiers of users (paid and unpaid) and prioritize asynchronous requests over synchronous ones. I also had to address how to ensure fairness and priority scheduling of API requests.

Confirmed questions3 questions
  • Design an ATM machine
  • Design your application service that is dependent on two downstream services which support different rates to scale the system that serves different tiers of users, paid and unpaid, considering synchronous requests have lesser priority than asynchronous requests. Also, ensure fairness and priority scheduling of API requests.
  • Design how we can scale our system that serve different tiers of users -> paid and unpaid and takes into consideration that synchronous requests have lesser priority than asynchronous requests. Also, how we can ensure fairness and priority scheduling of API requests.

Nanonets Software Engineer Interview Questions

Quoted word for word from Nanonets interview reports.

Design your application service that is dependent on two downstream services which support different rates to scale the system that serves different tiers of users, paid and unpaid, considering synchronous requests have lesser priority than asynchronous requests. Also, ensure fairness and priority scheduling of API requests.

Read reports

Design how we can scale our system that serve different tiers of users -> paid and unpaid and takes into consideration that synchronous requests have lesser priority than asynchronous requests. Also, how we can ensure fairness and priority scheduling of API requests.

Read reports

What are your ideas on enhancing web application performance?

Read report

Could you design an ATM and explain how it works from start to finish, covering all potential real-world situations?

Read report

Were there questions about basic data structures and a puzzle?

Read report

Did they ask about basic data structures and a puzzle?

Read report

Tell me about a time you demonstrated a certain behavior.

Read report

Formats, difficulty and experience

Across all 6 Nanonets interview reports.

Interview formats

Behavioral 36.8%
Technical 26.3%
Coding 21.1%
System Design 15.8%

Interview difficulty

Easy 16.7%
Average 50%
Difficult 33.3%

Candidate experience

Positive 50%
Neutral 16.7%
Negative 33.3%