Nearform logo

Nearform Fullstack 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

2.3 Rounds average
Average Typical difficulty
50% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Nearform.

Showing 3 of 6
Nearform logo
Nearform

Full Stack Developer

Engineering · a year ago

Entry Easy Positive experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Coding

The interview started with an assessment from HR, and if I passed that, I moved on to a live coding round. I didn't make it past the coding round because I only completed 75% of it due to time limits.

Confirmed questions4 questions
  • Create an array of 52 cards for a Blackjack game, using specific notations (e.g., 'AS' for Ace of Spades, 'KC' for King of Clubs, 'TD' for Ten of Diamonds).
  • Shuffle the deck of 52 cards.
  • Deal a hand of N cards (where N is a positive integer less than or equal to 52) from the top of the deck, returning an array of these cards.
Nearform logo
Nearform

Fullstack Developer

Engineering · a year ago

Entry Average Positive experience No offer 2 rounds
Interview process
Recruiter call Technical screen Offer
Interview formats
Technical Coding

The interview process started with an easy and warm first interview. Then, a live coding interview followed. While live coding isn't my favorite, the interviewer was nice. Unfortunately, I got an email saying they wouldn't proceed, and the rejection tone was really cold, like they were disgusted. Maybe they could be more human with rejections. The live coding involved basic tasks like fetching and displaying data.

Confirmed questions2 questions
  • Do you have experience with Node.js?
  • Can you fetch data?
Nearform logo
Nearform

Fullstack Engineer

Engineering · more than a year ago

Mid Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Behavioral

An internal recruiter from the company reached out to me via a job board. I had a first stage HR interview with them, which I felt went well and I got positive feedback. We communicated by email about scheduling the next stage, which was supposed to be a technical challenge. However, after two weeks of attempting to find a suitable time for their developers, I eventually heard back from HR that they were actually looking for someone with more backend experience. It's frustrating because they had my CV from the start, and could have identified this requirement then instead of wasting three weeks of my time and building up my expectations. I'd advise against applying here unless you're absolutely certain you meet every single requirement listed in the job description, as you might end up going through their interview process only to be rejected later on.

Confirmed questions1 question
  • Can you tell me about your experience with the testing libraries Jest and Cypress?

Nearform Fullstack Engineer Interview Questions

Quoted word for word from Nearform interview reports.

Create an array of 52 cards for a Blackjack game, using specific notations (e.g., 'AS' for Ace of Spades, 'KC' for King of Clubs, 'TD' for Ten of Diamonds).

Read reports

Can you implement the blackjack card game and provide test cases?

Read reports

Can you tell me about your experience with the testing libraries Jest and Cypress?

Read reports

Formats, difficulty and experience

Across all 6 Nearform interview reports.

Interview formats

Coding 40%
Technical 40%
Behavioral 20%

Interview difficulty

Easy 16.7%
Average 83.3%
Difficult 0%

Candidate experience

Positive 50%
Negative 33.3%
Neutral 16.7%