Linkedin

I went through the LinkedIn Software Engineer Intern recruitment process through an on-campus opportunity. After my resume was shortlisted, the first major step was a HackerRank online assessment. I had 90 minutes to solve three DSA problems. The set consisted of one easier question and two medium-level questions, so I had to be careful about time management. I decided to secure the easier problem first and then spend the remaining time on the two medium questions. The assessment was also proctored, which meant I had to stay within the platform's testing requirements. A selected on-campus candidate reported the same three-question, 90-minute HackerRank structure. Once I cleared the OA, I received the interview call. My first interview was completely technical and focused heavily on DSA. The interviewer did not spend too much time on introductions before moving into the coding questions. I was given algorithmic problems and was expected to explain the solution before starting the implementation. I discussed the brute-force idea first, then worked towards the optimized solution and explained the complexity. The interviewer also asked follow-up questions to check whether I could adapt the approach when the constraints changed. One of the more interesting parts of the process was that I was not simply judged on whether the final code worked. I had to communicate continuously while solving. Whenever I reached an important decision, I explained why I was choosing a particular data structure or algorithm. This made the interview feel closer to collaborative problem solving than a normal coding test. After clearing the technical round, I had the managerial discussion. The atmosphere was considerably more conversational. I was asked about my projects, the work I had done personally, and some of the challenges I had encountered while building them. I also had questions around teamwork and how I approach unfamiliar problems. A selected LinkedIn candidate reported a similar structure, with the first interview being completely DSA-focused and the subsequent managerial round including project discussion. Another selected internship experience gives a little more detail about the technical stage: the candidate reported two medium-level dynamic-programming questions in the technical interview, followed by a Host Manager conversation. This reinforced for me that LinkedIn's technical interviews can go beyond the exact patterns seen in the OA and require comfortable problem-solving across different DSA topics. I eventually received the selection confirmation. The biggest takeaway for me was that the preparation needed to be consistent across all stages. The OA tested speed, the technical interview tested depth of problem solving, and the managerial round required me to clearly explain my own experiences. I therefore found it much more useful to prepare DSA while simultaneously keeping my projects and resume completely interview-ready.