
ValueLabs Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 657 interview experiences · FREE TO READ
Which role are you interviewing for?
30 roles · 657 reportsCandidate interview experiences
First-hand accounts from people who interviewed at ValueLabs.
Software Engineer
So I interviewed with ValueLabs. After the technical rounds, they wanted all my education docs, PF account details, payslips, bank statements, and other personal stuff for what they called Pre-BGV, saying only the HR round was left. After the HR round, they asked for more docs. I asked why they needed this stuff before an offer, and they said it was about moonlighting. But honestly, I feel like you should only give that kind of sensitive info after getting an offer letter. If you decide not to join for any reason, like the offer not being good enough, why should they have your personal data? I gave them everything they asked for, but I never got an offer. This makes me worry about how they handle and store this data. We live in a digital age, and data misuse is a real thing. If they don't trust us, we have the right to question their practices. ⚠️ My advice to job seekers: Don't share your personal or financial documents before you have a real offer letter. Guard your data and check out your employer before sharing anything sensitive.
- Were you asked to submit all your personal and professional documents, such as educational certificates, payslips, PF details, and bank statements, for pre-BGV before an offer letter was provided?
Full Stack Developer
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.
- Can you explain the Event Loop, Callback Queue, and Call Stack in javascript?
.NET Developer
The interview process was good and involved a nice conversation with the panels. They started with basic c# questions, moving to advance Frameworks in SQL SERVER, and Angular. Some basic coding questions were asked, along with javascript questions. A good aspect was receiving feedback at the end of the interview itself.
- Tell me about yourself?
- Do you have C# questions?
- Can you do BASIC CODING?
Senior Node.js Developer
So, I had 3 technical rounds for this ENBD client at ValueLabs, and I passed all of them. It was a pretty good interview experience, and I was feeling good about getting an offer. HR called on Jan 16, 2025, to set up the interview. Then, Round 1 was on Jan 17, 2025, and I cleared it. Round 2 was Jan 20, 2025, cleared. The Client Round was Jan 27, 2025, and I cleared that too. After that, they said HR talks would follow and things would move forward. They collected all the documents for offer processing. I waited for a whole week, expecting the offer. I followed up a bunch of times, and each time it was the same old story – 'We're processing the offer' or some other lame excuse. Even after more follow-ups and sending more papers, nothing changed. Then today, Feb 7, 2025, when I asked again, HR just told me to 'move on' because there's a 'client issue.' Can you believe it? After wasting weeks of my time, acing all the rounds, and endless follow-ups, they just hit me with this? Totally absurd and unprofessional.
- What do you know about ES6?
- Can you explain Node.js core and fundamentals?
- Let's do a few coding exercises.
ValueLabs Interview Questions
Quoted word for word from ValueLabs interview reports.
“Can you find the subarray with a sum of 0 from the given array of numbers?”
Read reports →“What's the shortest distance between two points that are vertices of a triangle?”
Read reports →“In terms of speed, what's the difference between `import {}` and `require`?”
Read reports →“What is the difference between an interface and an abstract class?”
Read reports →“How would you print even and odd numbers using goroutines and channels?”
Read report →“How do you determine if a year is a leap year?”
Read report →“Can you tell me the maximum size for an environment variable in Node.js?”
Read report →“What is the output of a function with a for loop and settimeout inside?”
Read report →“Can you write a program to determine the nth Fibonacci number?”
Read report →Formats, difficulty and experience
Across all 657 ValueLabs interview reports.