Interview Type: Face-to-Face Timeline: Interview scheduled at 9:30 AM (Weekend)

The interview process was not well-organized. Even though all candidates were asked to arrive at 9:30 AM, interviews were conducted based on the order of arrival. I reached on time, but my turn came around 12 PM.

Round 1: The first round went well. The interviewer was friendly and interactive, and I received positive feedback after the session.

Round 2: The second round was scheduled around 4 PM with the Head of Engineering. Unfortunately, the experience was not great. The interviewer started with the question “Why Nike?” I might not have given the strongest answer, but instead of ending the discussion there, he continued with a technical question on flattening a nested object (tree structure).

He insisted that I write the actual code (not pseudocode) on paper. After completing it, he repeatedly said, “This solution won’t work,” without explaining what was wrong or giving any hints. Even when I asked for clarification — whether it was a logic or syntax issue — he just said, “I’m not sure.” I tried to explain my logic and even dry-run the code, but he wasn’t willing to listen and kept asking me to rewrite it on fresh paper.

After multiple attempts and no constructive feedback, the discussion became quite unproductive. I later received feedback that I “don’t know how to code,” which didn’t seem fair considering the interaction.

Overall Feedback: The process could have been better organized. Candidates spend an entire day at the venue, so the interview schedule should be managed more efficiently. It would also help if interviewers provided clear, constructive feedback instead of simply rejecting answers without explanation. Transparency and basic communication would make the experience much more professional and respectful for candidates.

React, Node.js - Core concepts to advanced questions.

Event Loop DS - Robbery sum (DP) System Design - Google Docs Flattening a nested object (tree structure)