Phone screen round, good questions, variation of max stack. Couldnt solve it, but i managed to solve the normal variant, was not selected. they also asked some behavioural questions. Thats about it
Preguntas de entrevista [1]
Pregunta 1
Max Stack variation with time and space complexity
Interview Process (7 Rounds):
3 Coding Rounds:
Medium to hard algorithmic problems focused on data structures and problem-solving.
1 Craftsmanship Round:
Assessed code quality, structure, testing, and adherence to best practices.
2 Design Rounds:
Standard system design interviews covering scalability, architecture, and trade-offs.
1 Host Manager Round:
Informal discussion about past projects, team collaboration, and role alignment.
Preguntas de entrevista [1]
Pregunta 1
Design a search index (basically designing an distributed inverted index system like Elasticsearch)
Envié una solicitud electrónica. El proceso duró 1 semana. Acudí a una entrevista en LinkedIn (Bengaluru) en sept 2015
Entrevista
Applied in LinkedIn portal for Staff Engineer. Got a call from recruiter on the next day and she explained the details very nicely. Recruiter response was prompt. Recruiter scheduled the Phone Screen (PS) very next day for the Staff Engineer role.
I've 8+ years of experience in software development (working in world's #1 online retailer for 3.5 years).
Preguntas de entrevista [1]
Pregunta 1
Questions were simple (same as described in glassdoor). Interviewer called on time, but didn't introduce himself. Directly jumped into questions (lags professionalism).
There was no NDA. So, I think I can share the questions,
1) Search for "WordDistanceFinder linkedin".
http://www.careercup.com/question?id=5725709041401856
2) Search for "TwoSum with test()/store()" methods.
https://github.com/fcarriedo/algorithms/blob/master/exercises/twosumtest/TwoSumTest.java
I discussed and coded more than two solutions for both problems. Wrote bug free code (verified my code after the interview in other websites).
My mistakes:
1) I explained that we can use Set instead of HashMap verbally. I didn't type it in the editor. Looks like the lazy interviewer didn't make a note on that. Seems hiring committee raised concern on data structures (actually I used HashMap to support future enhancement - again didn't type that in the editor).
2) I didn't add comments in the code - Its an interview, don't expect someone to type comments - thats why I was explaining.
3) Used short variable names (asked interviewer is short notation fine with him... i.e., Used "idx" instead of "index". He was fine with that). Again I didn't mention that in the editor.
Based on above three mistakes, the hiring committee said they'll consider me for Sr. software engineer. but definitely not for Staff Engineer. That too after another PS. Now I'm wondering whether I've to proceed my candidature with LinkedIn (I've an offer for a director level position with another $3B company).
I've taken more than 100 interviews for my company. But this experience disappoints me.
Advice to LinkedIn: Please give trainings to your interviewers. Make sure you collect right data points about your candidates (either ask your interviewer type a detailed feedback, or you talk to the interviewer). Because what you see is not the complete picture of the truth.
My advice: Whatever you want to convey in a phone screen, make sure you type them in the editor.
