Software Engineer applicants have rated the interview process at Duolingo with 3.1 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 49% positive. To compare, the company-average is 47.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 22 days to get hired, when considering 53 user submitted interviews for this role. To compare, the hiring process at Duolingo overall takes an average of 28 days.
Common stages of the interview process at Duolingo as a Software Engineer according to 53 Glassdoor interviews include:
Phone interview: 35%
One on one interview: 33%
Presentation: 13%
Skills test: 11%
Group panel interview: 3%
Background check: 1%
IQ intelligence test: 1%
Other: 1%
Drug test: 1%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 weeks. I interviewed at Duolingo (Pittsburgh, PA)
Interview
Applied online, got an e-mail from a recruiter the following day. Quick phone screen with the recruiter, then a take-home coding challenge that was relevant to the particular role I applied for. After that, had a coding interview over Skype with an engineer. Fairly standard interview. The engineer doesn't care much if you come up with the best solution right away, just ask for hints and explain your thought process.
After that, got invited for an interview on-site which consisted of two whiteboard coding problems and a pair programming session.
Overall, the process was super smooth and everyone was really friendly and easy-going. Seems like a great company!
Interview questions [1]
Question 1
The white board coding problems required knowledge of data structures, recursion, and dynamic programming. That being said, they would probably qualify as "medium" level difficulty problems - nothing too crazy. The pair programming session involved editing an API endpoint in their code to do some simple data manipulation before returning it to the frontend.
It's a standard recruiter screen followed by a phone screen and then another phone screen before finally reaching an onsite. It's a long tedious process. Would not recommend for people looking for a smooth process.
Was given an OA on code signal that had 4 questions. A lot of it was about graph traversal algorithm. I did not pass all of the hidden test cases for one of the questions, probably why I did not get moved to the next round.
I applied online. I interviewed at Duolingo (Pittsburgh, PA)
Interview
Onsite Interview:
1. Code review round on codesignal, reviewing a pull request, comment on code quality and errors
2. Whiteboard leetcode problem, Medium level
3. Pair programming w/ Senior Engineer on a toy demo, using VS Code Codesharing
Interview questions [1]
Question 1
Prep questions and ask about their job responsibilities.