Netomi logo

Netomi Frontend Engineer Interview Questions
& Process

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

Based on 8 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 Netomi.

Showing 3 of 8
Netomi logo
Netomi

Frontend Engineer

Engineering · more than a year ago

Mid Average Positive experience Accept offer 5 rounds
Interview process
Take home Technical screen Technical screen Background check Recruiter call
Interview formats
Coding Technical Behavioral

The interview process was really smooth and well coordinated, with interviewers being helpful and friendly throughout. There were a total of 5 interviews: an initial assignment in React, followed by two technical rounds with senior developers. After that, there were two more rounds with the HR manager and the head of engineering, which were also technical. Finally, there was an HR round for discussing past experience and general conversation.

Confirmed questions8 questions
  • Can you explain Closures in JavaScript?
  • How do Timeouts work in JavaScript?
  • What are some common DSA problems involving basic Arrays?
Netomi logo
Netomi

Frontend Software Engineer

Engineering

Entry Difficult Positive experience Accept offer 5 rounds
Interview process
Technical screen Technical screen Technical screen Technical screen Technical screen
Interview formats
Coding Coding Coding Coding System Design

The interview was a pretty thorough and engaging experience, meant to check out a bunch of skills. It started with two coding rounds where we really dug into object-oriented programming with JavaScript. I had to solve problems that showed how I could make good coding solutions and write code that's clean and can scale. They also hit me with regular React interview questions, so I had to show I knew React's main stuff like component lifecycle, managing state, and hooks, and that I could build UIs that look good on different devices. After that, I did a system design interview that was both tough and cool. The challenge was to design a system like Instagram. This meant I had to really know architecture design, how to scale things, and how the app flows. I had to explain how I'd set up the backend for things like user profiles, uploading pics, feeds, and notifications, making sure it could handle millions of users and tons of data smoothly. We talked about database setup, how to deploy servers, and where things might go wrong, all while keeping user experience and system stability in mind. All in all, it was a well-organized process that let me really show off my tech skills and how I solve problems, plus my ability to design big systems.

Confirmed questions1 question
  • They asked me to design a scalable system that's like Instagram, which led to a deep dive into system architecture, database design, user management, and efficient media uploads.
Netomi logo
Netomi

Frontend Engineer

Engineering

Mid Average Negative experience No offer 1 round
Interview process
Take home Technical screen
Interview formats
Coding Technical

So I had to do this assignment first, make a PokeDex with features they listed, took me like 10 hours. Honestly, felt like a red flag and probably no one even looked at it. Then they set up an interview. Got rejected like 2 hours after. The interviewers seemed kinda new, only like 2 years of experience. They made me introduce myself and then straight into questions. They wanted my webcam on, but kept theirs off, which was weird. I had to ask them to introduce themselves at the end, didn't even say what they did, had to check LinkedIn later. One interviewer was silent the whole time. Asked JS concepts, coding stuff (struggled with Array.flat), and a bunch of guess the output questions (got one wrong out of 10-15). Thought I did okay, but HR said my basics and coding weren't up to par.

Confirmed questions2 questions
  • Some basic coding questions in js
  • Guess the output questions, with promises to make them a bit more tricky

Netomi Frontend Engineer Interview Questions

Quoted word for word from Netomi interview reports.

Implement a calculator with multi-chain functionality (function/class/object).

Read reports

Explain the difference between object reference and values in JavaScript.

Read reports

Given some JavaScript code, what do you think the output will be?

Read report

Could you implement a polyfill for the Array.prototype.reduce method?

Read report

What are some common DSA problems involving basic Arrays?

Read report

Formats, difficulty and experience

Across all 8 Netomi interview reports.

Interview formats

Coding 40%
Technical 28%
Behavioral 24%
System Design 8%

Interview difficulty

Easy 25%
Average 37.5%
Difficult 37.5%

Candidate experience

Positive 50%
Neutral 12.5%
Negative 37.5%