Candidatei-me online. O processo levou 2 semanas. Fui entrevistado pela LinkedIn (San Francisco, CA) em jun. de 2016
Entrevista
Received an email from LinkedIn recruiting team for Software Engineer In Test position at Mountain view/ San Francisco office. Had HR screening after a week. After clearing HR screening, I was provided preparatory material for the phone interview round. The HR would brief you in detail about the process and what should be expected in the phone interview. Recruiting team at LinkedIn is helpful and reachable.
Technical phone screen round has coding algorithm question. Go through Glassdoor, careercup and practice LinkedIn coding questions. Expect a similar question on your phone screen.
Perguntas de entrevista [1]
Pergunta 1
HR Screening -
Talk about your resume and previous work experience
Why LinkedIn?
Basic Java questions -
How do you make a class/ method thread-safe?
How do you make sure a class is not instantiated?
Technical Phone screen -
First 20 - 30 minutes - Discuss projects on your resume, Basic Java questions (Singleton class, mutable and immutable, difference between string literal and new String(), mock objects)
Remaining 30 - 40 minutes - Coding problem
Given the following relationships:
Child Parent IsLeft
15 20 true
19 80 true
17 20 false
16 80 false
80 50 false
50 null false
20 50 true
You should return the following tree:
50
/ \
20 80
/ \ / \
15 17 19 16
Candidatei-me online. O processo levou 4 semanas. Fui entrevistado pela LinkedIn (San Jose, CA) em out. de 2016
Entrevista
Got a recruiter message from LinkedIn on LinkedIn. First had technical phone screen, later was called for onsite where i met multiple software engineers. Experience at LinkedIn was kind of weird since i thought few employees who interviewed me had some attitude problems, which made me loose my interest in the company while interviewing. I was interviewing for Software engineer in test position and my experience lies in UI automation and in code analysis, i was asked OS concepts, multi threading, thread pool etc. which was not needed totally. When i asked the interviewers how much multi-threading you guys use at LinkedIn for automation, they said 'No we don't use multi-threading.' It was a great set back that i was being checked for the skills, that i don't have experience with or in job description or thats not used in the company itself! Overall, i was not that happy with the interview experience and even if i would have got the offer, i would have declined the offer.
Perguntas de entrevista [1]
Pergunta 1
String manipulation, What are your challenges, Test Strategy Plan, Code Analysis etc.
Candidatei-me por meio de recrutador(a). O processo levou 1 semana. Fui entrevistado pela LinkedIn em mai. de 2016
Entrevista
Contacted by recruiter who was very friendly and straightforward. Had a general screen with the recruiter and she set up with a phone screen with a couple of their devs. Phone screen lasted one hour and I was not able to understand their accents most of the call. They also sounded, well, rather rude and abrupt.
I stumbled through a fairly benign coding problem and got to an eventual solution, although they did not seem particularly happy with it. Wasn't the best interview but it honestly felt hostile during the call. Could hear exasperations when I asked questions at the end and chose to forego asking more about the position/company just because I didn't want to waste everyone's time.
The company and culture sounded great other than that.
