J'ai passé un entretien chez Audible (New York, NY) en août 2013
Entretien
I received an email from a recruiter and we setup a time for a phone interview with an engineer. On the first phone interview I was asked several questions about software engineering and had to provide the solution to a couple of puzzles (no live coding, just talking). I did well on this interview and a follow up interview was scheduled. On this second interview I had to code using a collaborative coding tool. The questions were easy (general theoretical CS questions and solve a simple OOP problem). I think it went well, but they did not want to move forward after this interview.
The interview was for returnship , folks with break in career . the breaks needs to be 2+ years . The interview was with data structures and algorithm questions along with behavior questions
Questions d'entretien [1]
Question 1
Give a business case and was asked how to solve the problem . Involved suing stacks or queue and string operations
J'ai passé un entretien chez Audible (Jersey City, NJ)
Entretien
Half an hour q&a about experience and use cases from the prior experience.
Next half an hour, a technical session question was asked to write code as a solution. However the question was too abstract and has no api context available to write any functional code
Online coding assessment followed by a virtual onsite loop with 3 coding and 1 system design. Each interview session in the full loop has a behavioral component based on the Audible people principles followed by a technical portion.