ValueLabs logo

ValueLabs Fullstack Engineer Interview Questions
& Process

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

Based on 9 interview experiences · FREE TO READ

3.3 Rounds average
Average Typical difficulty
33.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at ValueLabs.

Showing 3 of 9
ValueLabs logo
ValueLabs

Full Stack Developer

Engineering · a year ago

Mid Average Neutral experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Coding

An HR recruiter contacted me about this job. They were in a rush and set up my first round, which was about JavaScript, for Sunday afternoon. I passed that round and qualified for the second. Still in a rush, we scheduled it for that same day at 8 PM. But, nobody showed up from their end. The next day, the recruiter called again, and we rescheduled for the same day. Unfortunately, again, nobody showed up. A day or two later, I had a day off, so I emailed them saying I was free all afternoon and they could schedule the interview. I got no reply. The problem isn't just being kept waiting twice and wasting my time – I get that things happen. That's why I suggested scheduling during normal working hours to make sure an interviewer would be available. I think the HR recruiter should keep candidates updated. This kind of poor communication isn't good for the company or the recruiter's career. I suggest they respect people's time and be honest about updates. I usually don't say bad things about people because I don't want to spread negativity. But Glassdoor needs an annual review for genuine community insights. I'm sharing this feedback constructively so others can learn from my experience. Personally, I believe in moving on and forgiving easily.

Confirmed questions1 question
  • Can you explain the Event Loop, Callback Queue, and Call Stack in javascript?
ValueLabs logo
ValueLabs

Full Stack Developer

Engineering · a year ago

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

Worst interview process ever. They took 2 rounds and got confirmation that I have been selected. After that they stopped responding. Even after calling recruiter doesn't respond. They are just ghosting the candidate. VALUELABS DONT HAVE THERE OWN VALUE

Confirmed questions1 question
  • What is callback hell and how can it be prevented?
ValueLabs logo
ValueLabs

Full Stack Developer

Engineering

Mid Easy Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Coding Behavioral

The interview process involved an initial recruiter call, followed by a technical screen where I was asked about different types of searches like Fibonacci Search and Binary Search, including their code and time complexity. We also discussed how to calculate time complexity. I was asked to provide the code for an Armstrong number with a step-by-step explanation. Then, there was an onsite interview where I had to explain each project in detail, talk about the challenges I faced, the technologies I used, and my career achievements.

Confirmed questions7 questions
  • Can you discuss various search algorithms like Fibonacci Search with an example and Binary Search with its code and time complexity?
  • How do you determine the time complexity of an algorithm?
  • Could you write the code for an Armstrong number and explain it step by step?

ValueLabs Fullstack Engineer Interview Questions

Quoted word for word from ValueLabs interview reports.

How do you determine the time complexity of an algorithm?

Read report

Formats, difficulty and experience

Across all 9 ValueLabs interview reports.

Interview formats

Technical 46.7%
Behavioral 26.7%
Coding 16.7%
Group 6.7%
System Design 3.3%

Interview difficulty

Easy 22.2%
Average 66.7%
Difficult 11.1%

Candidate experience

Positive 33.3%
Neutral 44.4%
Negative 22.2%