Software Engineer, Full Stack Interview Experience

Can you walk me through your background and what you're looking for?

I gave a quick overview of my backend-heavy background, the AI tooling work I'd done, and why I was interested in a full-stack/backend-leaning role. It was very normal and conversational. Nothing felt like a trick question.

What product experience do you have, why did you build these products, and what were the challenges?

I walked them through my projects, why I built them, and the product decisions and challenges behind them. The pressure point was basically that they thought the projects were cool but wanted to know why none of them had actually hit production. That made me feel like they really value people who've shipped for real, almost ex-founder energy.

I said this was one of the few companies where I could immediately see myself using the product in my own life. There were a lot of cool things I'd want to build with their API, so my interest felt real. The people I talked to also seemed genuinely into audio and music, which made it feel mission-driven.

Instead of tracking dubbing work in a giant spreadsheet, can you write functions that handle edits and propagate which lines or files need to be re-reviewed?

I treated it like a practical Python problem around a dubbing workflow. Each row was basically a line, editors could approve it or ask for tweaks, and if a voice actor re-recorded something then that line had to get surfaced again for review and the status had to propagate upward. I used dictionaries and hash maps and wrote functions around those status updates. My read was that this came from a real customer workflow, not just an interview toy problem.