Solicité el puesto a través de un captador. El proceso duró 1 semana. Acudí a una entrevista en LinkedIn (San Jose, CA) en abr 2016
Entrevista
After phone conversation with recruiter, I had phone interview in following week. Interviewer called me on time. But I was given the wrong interviewer. First he went through my experience. and then gave two coding problems. I felt he did not prepare for his interview problems well. We spent lots of time on the time complexity. Also it seems that he wanted the answer he wanted, and not realized there are several solutions.
Preguntas de entrevista [1]
Pregunta 1
nested list sum; design algorithm to add integer and check if there is two integers which sum up to the targeted sum.
Envié una solicitud electrónica. Acudí a una entrevista en LinkedIn (San Francisco, CA) en mar 2026
Entrevista
Had an initial phone screen round-
Questions - Regular Medium level question, string manipulation
Follow up - Concurrency related on top of the first question.
Waiting for the second round right now
Solicité el puesto a través de un captador. Acudí a una entrevista en LinkedIn (San Francisco, CA)
Entrevista
Was greeted by a person who basically walked me around the office during my interview, did a couple of rounds with a group on a whiteboard solving a coding challenge, and one to solve a software architecture challenge. Had lunch onsite. And one round of interview with someone who wasn't technical.
Preguntas de entrevista [1]
Pregunta 1
Write the code to generate an English language rendition of any integer up to 100,000,000.
Acudí a una entrevista en LinkedIn (San Francisco, CA)
Entrevista
Failed at initial screening
Asked about mutex and how 2 processes can communicate with each other, I got nervous and coulnt explain my thoughts properly
Then asked the simple backtracking interview question, solved it, but also didnt do good job communicating
Preguntas de entrevista [1]
Pregunta 1
mutex and communication between processes
backtracking easy question (count islands)
