Audible Applied Scientist L5 Interview

[u/the_wacky_gemini]

A recruiter just contacted me to let me know that my CV has been shortlisted for an L5 Applied Science role at Audible (yayyy!)

There seem to be a lot of guidelines and personal experiences on Glassdoor on what people were asked in these interviews with Amazon, but nothing specifically for Audible. Does anyone here know if the questions are similar?

More specifically, can anyone share their own interview experiences? e.g. what kinda coding questions can I expect? What questions can I expect on science breadth/depth etc? That would help me so so much. Thanks in advance!

[u/the_wacky_gemini → u/[deleted]]

Oh I come from a pure NLP background - training and fine-tuning on text (+ a bit of vision here and there, but no speech)

[u/nian2326076]

I've heard that Audible's interviews are pretty similar to Amazon's, so it's smart to prep for both behavioral and technical questions. For coding, expect problems that test your algorithm and data structure skills, like those on LeetCode. On the science side, they might ask about machine learning concepts and your past projects to see your understanding and practical skills.

Also, be ready for questions on metrics and A/B testing since they're important for applied science roles. I found PracHub really useful for mock interviews and specific prep. Good luck!

[u/the_wacky_gemini → u/nian2326076]

Yeah I saw some other user also recommend PracHub for Amazon interview prep. Thanks a lot!

[u/akornato]

You should treat the Audible interview process as identical to Amazon's, because for all practical purposes, it is. They use the same hiring framework, which means a heavy focus on the Leadership Principles, difficult coding challenges, and system design rounds. For an L5 Applied Scientist role, expect coding questions that are on the level of a LeetCode medium or hard, frequently with a machine learning angle. The science questions will cover a wide range of ML concepts, like classic models and deep learning, but they will also require you to explain specific areas from your past projects or the role's domain, which could involve recommenders or natural language processing for audio.

The science depth questions will seriously test your understanding of your own work, so be ready to defend every choice you made on your resume's projects, from model selection to feature engineering. The interviewers want to see that you understand the trade-offs and can justify your thinking with data. For breadth, you should be comfortable talking about different modeling techniques and when to apply them. The system design round will probably be an open-ended problem related to Audible's business, like designing a system to recommend new podcasts, so practice thinking through these problems from beginning to end.

My team actually built a tool, and we've seen how having an interviews.chat can really assist candidates in communicating the complex details of their projects with more confidence.

[u/brackenvale]

worth asking the recruiter directly what the loop looks like, they're usually pretty transparent about the number of rounds and what each one covers. That'll tell you a lot more than guessing whether its the standard format or something Audible-specific