Insider One logo

Insider One 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

2.6 Rounds average
Average Typical difficulty
25% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Insider One.

Showing 3 of 8
Insider One logo
Insider One

Frontend Engineer

Engineering · nearly a year ago

Entry Difficult Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Background check
Interview formats
Other

I had a good first call with the recruiter, and they were encouraging. Then, I was given a case study to complete. I dedicated three full days to it, making sure to finish all the required tasks, tackle the optional 'plus' items, and even add some extra features beyond what was asked. After submitting my work, I didn't hear anything back for about 2.5 weeks. When I reached out to inquire about the status, I was finally told I didn't get the role, but without any specific reasons or feedback. I'm a bit let down by this, especially considering the significant time and effort I put into the case study. Some brief, helpful feedback would have made the experience feel more respectful and worthwhile, even with a negative outcome. So, for other candidates, be ready for a potentially long waiting period and don't count on getting detailed feedback, even if you really go above and beyond on the case study.

Confirmed questions1 question
  • Build a Sudoku game using Vue 3.
Insider One logo
Insider One

Senior Frontend Developer

Engineering · a year ago

Senior Average Positive experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Behavioral Technical Coding

So I interviewed with Insider. It started with HR asking me some behavioral and motivational stuff to see if I'd fit in. It was a pretty standard chat. Then, they gave me a case study to do in 3 days, which was basically a practical task related to the job, so I could show what I know. I sent it back on time and got feedback pretty fast. After that, I had a technical interview where they asked me about frontend tech, how I code, and design choices. It was a good, deep chat. I didn't get past this stage though. If I had, the last step would've been a meeting with the CTO. The whole thing was smooth and they communicated well.

Confirmed questions1 question
  • Imagine a junior dev changes a button's color, tests pass, and it goes to production, but then something breaks. What steps could have prevented this before deployment?
Insider One logo
Insider One

Front End Developer

Engineering

Mid Average Neutral experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Technical Coding

I had a HR interview and then got a technical test where I had to build a horse race game in 2 days using a JS framework, including storing and UI components. After finishing the project, I had a technical interview with 4 developers. It seemed positive, but they didn't offer me the job in the end.

Confirmed questions1 question
  • Could you explain your reasoning for using atomic design in the project you built?

Insider One Frontend Engineer Interview Questions

Quoted word for word from Insider One interview reports.

Create an online editor for JavaScript, CSS, and HTML as a take-home assignment.

Read report

Imagine a junior dev changes a button's color, tests pass, and it goes to production, but then something breaks. What steps could have prevented this before deployment?

Read report

Could you explain your reasoning for using atomic design in the project you built?

Read report

Formats, difficulty and experience

Across all 8 Insider One interview reports.

Interview formats

Technical 50%
Coding 28.6%
Behavioral 14.3%
Other 7.1%

Interview difficulty

Easy 25%
Average 62.5%
Difficult 12.5%

Candidate experience

Negative 62.5%
Positive 25%
Neutral 12.5%