Educative (WA) Interview Questions
& Process

It was the first round, basically a screening round where some senior engineer came, and asked me leetcode medium questions to solve with him. First, they asked me the a fibonacci series question, it was easy but the way he framed it and asked to return output was actually a bit confusing and i messed things up a bit. He wanted me to return the nth fibonacci number. The function would be passed a number n, and we would have to return that specific fibonacci number. I messed up when i ended up going one iteration ahead than what was required. it was on paper. The second question was a bit difficult, he asked me to return the nth largest number from a binary search tree without using recursion or a stack. Because, he wanted me to have O(1) space complexity. There was a bit complicated algorithm behind it which i didn't know at that time, hence, I couldn't do this question. My way of trying to reach the solution was a bit flawed too.

The interview process was straightforward and the recruiting staff were quick to respond. Generally, the interview felt relaxed but challenging, with a focus on technical concepts, how you approach problem-solving, and your ability to communicate your thoughts clearly.

I applied for a Customer Service role in early September and had a frustrating recruitment experience. First, HR called me at the beginning of September to discuss the position and promised more details via email. A few days later, I was called to set up an interview with a manager on September 8th. After attending that interview, I was told I'd get confirmation by email. Several days later, HR called for a third interview on the 14th. I attended this interview and was again assured I'd hear back soon. However, days passed with no word. On the 20th, I called HR for an update and they vaguely said they'd 'inform me soon.' The next day, I got an email saying they decided to 'move forward with other applicants.' It took them so long to tell me this. I'm not upset about the rejection itself, but the lengthy process where candidates have to wait so long to get this kind of news. In today's job market, this long wait is tough. If you're interviewing with this company, be aware of this. The recruitment process can be as important as the job itself when evaluating an employer.

This hiring process was one of the best I've experienced, with a really detailed screening plan. It all wrapped up in about 4 weeks, from the initial HR call to getting the final offer. First, an HR person called to see if I was interested in a TCE role. Then, about a week later, I had a tech-screen interview which involved two coding problems focusing on linked lists. After passing that, I went through a full-loop interview which consisted of two technical interviews and one non-technical one. I had to explain my thought process, write the code, and document it. The technical questions covered linked lists, stacks, and binary trees, like reversing a linked list k times. They extended an offer about a week after this full-loop.