AAudible·Software Engineer

Audible Software Engineer interview experience

No offer

Medium

Neutral

Jersey City, NJPosted Aug 2025 · Candidate report, summarized by Dataford

My first call started with a short Q&A focused on my experience—about half an hour of discussing use cases and what I’d done before.

Then I moved into a technical session where I had to write code as the solution.

The technical part felt frustratingly mismatched because the question was too abstract and didn’t include enough context, like missing API details that would normally make the task executable. Without that grounding, I couldn’t realistically turn the prompt into a functional solution, so the whole round became more about guessing than solving.

I didn’t get the offer, and what lingered with me was how the format asked for implementation, but the prompt itself didn’t give the context needed to implement

Create a free Dataford account to unlock the full round-by-round breakdown, the questions asked and the outcome.

Read the full report Read the full report

Preparing for this interview?

Audible Software Engineer interview guideThe full process, round by round, with the question bank Practice Software Engineer interview questionsReal questions from this role across companies All Audible interview guidesEvery role we cover at this company