Deepgram Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 30 interview experiences · FREE TO READ
Which role are you interviewing for?
17 roles · 30 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Deepgram.
Deepgram
Applied Engineer
Mid Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen Background check
Interview formats
Behavioral
Applied on the website, and then the recruiter reached out. It took about 2 weeks after I gave them my availability to set up the first call. They scheduled the second call with the hiring manager pretty fast. I never heard back after that second call with the hiring manager. I followed up with the recruiter, and still nothing back. Not sure what happened, but it seems like they're overwhelmed with all the candidates they're interviewing. Ghosted after the call with the hiring manager.
Confirmed questions1 question
- How do you quickly build customer trust during the sales cycle?
Deepgram
Solutions Architect
Mid Average Negative experience No offer 3 rounds
Interview process
Recruiter call Phone screen Take home
Interview formats
Behavioral Technical Coding
The job was remote. I spoke with HR first, which went fine. Then I had an interview with the Hiring Manager. They clarified they weren't just looking for a Solutions Architect but also someone for Senior Technical Support and a Developer. They want one person for all three roles and pay for just a regular Solutions Architect with experience in all three. I told them I have coding experience but it's not my strongest suit. They said I'd have to do a coding test. I agreed, and that's the last I heard from them. They ghosted me. It was unprofessional.
Confirmed questions1 question
- Do you have developer and coding experience?
Deepgram
Frontend Software Engineer
Entry Average Positive experience No offer 4 rounds
Interview process
Recruiter call Technical screen Take home Onsite Background check Offer
Interview formats
Technical Coding Behavioral
First, there was a recruiter screen, then a technical screen where we discussed my experience and data structure fundamentals without any coding. After that, I had a take-home assignment to build a basic app. The final part was a 2.5-hour virtual onsite, which included 90 minutes to expand on the app I built, followed by a 15-minute break, and then a 45-minute meeting with the hiring manager. Everyone was super professional and friendly, and I could really sense the great culture at Deepgram. Even though I didn't get the job, I genuinely enjoyed the whole process and found it both tough and worthwhile. Adam Steinharter, the recruiter, was awesome - very professional and organized.
Confirmed questions3 questions
- Can you describe your experience integrating with the Deepgram APIs on the frontend?
- Describe how you would build the frontend, focusing on utilizing the Deepgram APIs.
- Behavioral type questions
Deepgram
Engineering Manager
Manager Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Presentation Onsite
Interview formats
Behavioral Presentation
The hiring process was swift and respected my time, offering chances to connect with key team members. Everyone was friendly and engaged. The recruiter, Adam, communicated clearly and was helpful. Post-offer, his check-ins were appreciated, without any pressure to accept quickly. Senior leaders were open about the company. The process included a recruiter screen, a hiring manager screen, an "onsite" with Product, CTO, and another EM, and a technical presentation. It took a month from application to initial contact and three weeks from contact to the offer.
Confirmed questions1 question
- Can you give a 15-minute technical presentation about a technical goal or milestone where you supervised the engineering team?
Deepgram Interview Questions
Quoted word for word from Deepgram interview reports.
“In the given fictional network setup, what might cause latency for a web service?”
Read reports →“Can you build a model for speaker change detection?”
Read reports →“How would you detect a change in the active speaker?”
Read reports →“How would you analyze a message to separate words and perform subsequent processing?”
Read reports →“What data inputs are required for this screen?”
Read report →“Given these designs, can you outline how you would construct this screen?”
Read report →“Describe how you would build the frontend, focusing on utilizing the Deepgram APIs.”
Read report →“Are there any aspects of the designs that raise concerns for you?”
Read report →“How do you quickly build customer trust during the sales cycle?”
Read report →Formats, difficulty and experience
Across all 30 Deepgram interview reports.