LinkedIn Sr. Software Engineer interview questions

-- 2 Telephonic rounds. First telephonic was kind of profile related discussion with hiring manager. Second telephonic was codepad coding round. -- Scheduled f2f in the following week. Recruiter told me that there will be total 5 rounds but they did only 3 interviews and rest of the time I was idle waiting for the interviewers. Recruiter did not update on the progress. Full day got wasted. -- I got the call from recruiter almost after 2 weeks to schedule another telephonic. Finished this telephonic round in the following week. -- No update/feedback from recruiter for next 3 weeks until I mailed them and asked for it. Overall, I felt the sense of unprofessionalism.

Initial round was a phone screening. Two problems were given to be solved . One was a straight forward implementation of a dynamic list of integers with methods to add to the list,delete from the list, fetch the integer at an index and return the size . Other one was a complex recursion problem . Once the telephonic round is cleared, I was invited to their office for a Face to Face interview . It consisted of 5 rounds - 2 rounds of coding, algo and DS , one designing round, one host manager round and a last technical communication round. The coding rounds are the most crucial ones as it basically forms the screening criteria for hiring a candidate. You are required to solve the problem and then write an error free code on the whiteboard, handling all the possible edge cases. It will be a piece of cake if you can explain the approach first and then put that down to code. You will be mostly asked to do a dry run at the end. Designing rounds were the usual brainstorming session. You should be able to back your design with proper metrics (throughput, responsiveness,data scale etc.) . Keep an eye on scalability as that's what the panel will be hinting at. Host manager round was a different flavour of designing round . It was a bit tougher for me , be as innovative and spontaneous as you can with the technologies that you are aware of. Technical communication is where you need to describe your current project in layman's terms.