Wiley Software Engineer Interview Questions
& Process

The interview covered the fundamentals of Software Engineering, including Object Oriented Programming, Data Structures, and Algorithms. I was asked about each project listed on my CV. They also asked about the difference between var, let, and const in JavaScript and covered basic to intermediate JavaScript questions. It was a 1-hour interview, and overall it was a great experience. The interview panel was very supportive.

The interview process had about 5 to 6 steps. First, there was a 30-minute screening interview. Then, I had to complete a large assignment, like a project. After that, there were two technical interviews. The fifth step was an interview with the technical manager, which was supposed to be the final one, but it was extended to a sixth interview with another manager. Each of these interviews lasted about 1.5 to 2 hours. You really had to get all the questions perfect; failing even one without a perfect answer meant you wouldn't pass. They seemed to be looking for very specific, ideal answers. The interviewers were generally friendly and made good impressions. All interviews were online via MS Teams, except for one which was in person at the office. They do provide feedback on why you were rejected. I actually enjoyed the interviews and thought the questions were good, but I was a bit upset because it took a lot of effort, and the last interview felt a bit off-topic for the role, asking about a framework I used years ago that isn't even used in the frontend, while the focus was supposed to be backend. Even though I answered correctly, they marked it as incomplete and rejected me. There was also a question about a feature that I don't think I answered perfectly.

I applied through a recruiter, and it was a pretty good process with a cool team. They kept me in the loop about what to expect and were fast with feedback and next steps. The first step was a chat with the recruiter. Then, I had a technical interview with the hiring manager where we talked about my background and I solved two problems in my preferred language using my own IDE. The 'on-site' involved several interviews over about 3.5 hours. The first part had a pair programming coding challenge (easy/medium LeetCode style) and a systems design question with an engineering manager. The second part was a more detailed coding exercise with another manager, which was neat because it was related to a zyBooks component and felt more relevant than other coding tests. The third part was a quick chat with the director of engineering about my technical background and how I'd handle certain situations. Finally, I interviewed with team members, including a PM and another dev, which felt like a casual culture fit interview. I turned down the offer because of another opportunity, but thought it was a solid interview process overall.