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%
Drug test: 1%
Background check: 1%
IQ intelligence test: 1%
Other: 1%
Here are the most commonly searched roles for interview reports -
I applied online, and then got scheduled for an online technical interview. I was told that I would receive a follow up email the following week after the interview. However, I never heard back from them (not even a reject email). On top of that, another recruiter reached out to me again a couple of weeks after this entire ordeal and asked if I was interested in the software engineer position. Because of my negative experience, I decided not to pursue the second opportunity. Recruiters / HR need to have a better system of knowing which candidates are already in the loop.
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.