Duolingo

I looked through the interview logs, and it seems like Greenbird rarely posts on them; most of them are from several years ago, which is indeed outdated. Many interviews are with Karat, and not many go directly to their own VO (Voice of the Occupation). I chatted with HR for a while. The interview was supposed to end on the 25th, but they need to hire 20 NGs for a new project. Let me describe the whole process: OA (Online Assessment), Codesignal (4 questions). Since it's a question bank, I won't go into detail. VO at Karat. You have two chances. If you're not satisfied with the first one, you can schedule a second one within 24 hours. This is a third-party VO. Only after passing this will you get to their own VO. These are the old questions mentioned on the interview logs; you can refer to the ones posted on the logs before. I took the second question, and the short answer was also mentioned here. (Duolingo Karat Interview Experience (Summary of 3 coding + 6 short answer questions) | Duolingo Interview Experience | 1point3acres Overseas Interview Experience Edition) Greenbird's own VO, which took a total of 5 hours. I thought it would be all done in one day, but maybe due to the time difference, HR gave me two days. The tech section actually lasted about three hours. The rest of the time was spent chatting with them and learning about their culture. The tech sections included: Code review: Previously, you could choose between Java and Python, but now it's only Python. It was done on a coding platform and required sharescreen. It mainly involved being given a pull request (PR) and you providing suggestions. This included coder refactoring, edge cases, etc. No coding was required; you just added comments with your suggestions. Pair programming: This was Java, although they said it was possible to switch, but their entire codebase was Java. It was also quite unique, requiring a VS Code live share. The interviewer gave you a link, connected via VS Code, and the front-end user had to view the interviewer's screen (they needed to share their screen). It was almost entirely related to sorting, first alphabetically sorting the list and then adding priorities. Initially, I had to switch back and forth (because the front-end user needed to view the interviewer's screen). Later, I added some print statements to debug, so I didn't have to constantly ask the interviewer to test for me. The interviewer then showed you the front-end user interface, showing you what it looked like and how they wanted to implement it. Many tasks require you to consult the codebase, project structure, and the call functions of the functions you need to implement. The "whiteboard" part, well, it's not really a whiteboard; it's just questions provided in Google documentation (similar to algorithm interviews). You write down your thought process in the documentation while they explain it, and finally, you write the code—you can write pseudocode. The question I received was roughly: given a list of sentences, return the word or words in each sentence that would make its boolean value true. After passing that, it's team matching. HR lets you choose your preferred teams, or you can choose teams that aren't a match. I don't know how they do it, but you can choose your preferred teams first, and if there aren't any matches, they'll let you choose.