Developer applicants have rated the interview process at Linden Lab with 2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 25% positive. To compare, the company-average is 68.2% positive. This is according to Glassdoor user ratings.
Candidates applying for Developer roles take an average of 37 days to get hired, when considering 4 user submitted interviews for this role. To compare, the hiring process at Linden Lab overall takes an average of 28 days.
Common stages of the interview process at Linden Lab as a Developer according to 4 Glassdoor interviews include:
Phone interview: 36%
One on one interview: 36%
Group panel interview: 9%
Skills test: 9%
IQ intelligence test: 9%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 months. I interviewed at Linden Lab (San Francisco, CA) in Oct 2009
Interview
very positive, with one conspicuous exception (initial telephone screening w/ HR manager--it was obvious that he had a few dozen telephone interviews just like this one to make that day). The people are very bright and obviously enjoy their work and work very hard. They are, of course looking for those attributes but also for "decency"--character is clearly important to them.
Interview questions [1]
Question 1
What factors would you consider when evaluating various web development frameworks--i.e., what makes one better than another?
The process took 2 months. I interviewed at Linden Lab
Interview
I was connected by the recruiter via email. One phone screening round with the Hiring Manager. After that 5 rounds virtual onsite interview with different team members. No technical questions asked in virtual onsite. Felt like a dummy position interview. They interview a million of other applicants and then reply back. Very fishy hiring process.
Interview questions [1]
Question 1
Tell me about yourself. No coding question or coding / technical exercise.
I applied through a staffing agency. The process took 1 week. I interviewed at Linden Lab (Brighton, England)
Interview
Google style; multiple segments (5) of chat and questions on different technical areas, by different team members, both at manager level and with other developers I'd be working with. Included a whiteboard pseudocode problem-solving challenge and questions finding out whether I knew and understood basic ideas in technologies and design patterns/techniques for the skills involved in the role applied for. A chance to ask questions of the staff during each part too. Then at the end a non-computer related problem to solve a well-known physical puzzle/toy in a set state (only a few repeated pattern of moves away from solved), if I could.
Interview questions [1]
Question 1
What HTTP response codes are and to list some/what they're used for
I applied through an employee referral. The process took 2 weeks. I interviewed at Linden Lab (San Francisco, CA) in Jun 2015
Interview
1. Phone Screen
2. All-day on-site interview
Interview was okay. If the interview did not go well (even if it seemed like it did), they don't call back to tell you that you didn't get the job.
They are extremely focused on how to build REST applications so be prepared to answer architectural questions on how you would build certain types of systems.
Interview questions [1]
Question 1
What is Ruby on Rails good for? What would you build with it?