Headstrong Associate Interview Questions
& Process

The process was really slow. First, there was a written technical round after waiting for almost two hours. It had pretty simple .net and coding technique questions divided into two groups, with equal weightage. There were 41 questions in total, and we had half an hour to complete them. It seemed easy enough to pass. Then, after another hour's wait, there was a 1:1 technical round. The interviewer was clueless about OOPs basics and didn't ask any .net questions. He insisted on his incorrect OOPs concepts, trying to force me to agree. I ended up challenging him to prove his points, which apparently offended him, and I was asked to leave. It felt like a waste because I'm sure I got everything right, but I failed due to an incompetent interviewer.

The first step was a written test with 4 sections: quantitative, data interpretation, English (mostly sentence correction and word usage), and programming. The first three were pretty straightforward, but the third section had a lengthy reading passage with questions that required extracting specific information, which was easy but time-consuming given the tight time limit. Following the written test, there were two interview rounds, each lasting 15-30 minutes. These interviews focused heavily on communication skills and the ability to provide descriptive answers. At every stage, you needed to justify your choice to pursue a role in IT services over a job in your core engineering field.

First, there was a phone technical interview. If that went well, I was invited for a face-to-face technical interview. After passing that, I had a managerial interview, and then an HR interview. The managerial part was pretty straightforward, usually involving a technical design problem and asking for solutions. The HR interview was mostly about salary discussions.