Netlight Interview Questions
& Process

So it all started with the recruiters, and then went on to the hiring managers, seniors, and even partners. We had three interviews in total. The first one was just to see if we click. Then, we had a more technical one that included a challenging consulting case study. The last one was with a partner. I found every part of this process really engaging and motivating. I learned so much about the company and how I might perform as a consultant. What was great is that they offered clear feedback and were upfront about what the next steps would be. The entire experience was so positive that it made me incredibly excited to accept their offer!

For new grads, don't bother applying unless you have at least three relevant experiences like summer jobs. I applied online and heard back from HR about a week later. When I got to the office, they seemed friendly but a bit fake. The chat was super light, no tough questions. After 20-30 mins, they said no offer because I didn't have enough documented experience, which was obvious from my resume. I don't get why they even called me in. They seem to care more about their image than anything. I'd say it was easy, but I don't think it was a real interview.

The interview process had three phases, which aligns with what others have reported for the Netlight IT consultant position. The hiring manager's approach was very supportive, transparent, and feedback-oriented throughout. I was ultimately not selected after the final partner interview, and received feedback afterward. The main reason cited was that my communication and demonstrated competence weren't sufficient for the role's seniority level. For context, I had 2.5 years of experience as a working student, not full-time. The second and third interviews were onsite, and travel expenses were covered.

I applied for a graduate Backend & Cloud Engineer role that was open to recent grads or people with 1-2 years of experience. I have over 2 years of experience from full time jobs, student roles, and freelance work. Even though I was qualified, I got rejected after just one interview that wasn't even technical. They asked basic questions about the tech I've used and know well, but didn't test my actual technical skills. I didn't get to solve problems, discuss architecture, or go deep on my past work. They said they wanted someone with 'more technical experience,' which was weird for a graduate role and since they didn't test my tech skills. If they wanted someone more senior, they should've said so. The feedback felt off, like a gut feeling instead of a real assessment. It felt like they judged me on general vibes, not what I can actually do. I was shocked they said I lacked tech skills without even checking. Recruiters who don't know tech shouldn't be judging candidates' tech skills without input from someone who does. The whole thing felt like the decision was already made. It made me wonder if the job was really for early-career people or just a formality. Since it was an onsite interview, it felt like an even bigger waste of time because I put in the effort to go there but didn't get a fair shot.