Wiley Interview Questions
& Process

The interview started with an online coding test that focused heavily on data structures and algorithms, covering array manipulation, string problems, recursion, and basic dynamic programming. It also involved questions on time and space complexity analysis, asking for the Big-O complexity of my solutions. After passing the coding round, I moved to a technical interview. Here, we discussed my coding question approaches, explored ways to optimize solutions with follow-up questions, and touched on basic full stack topics like REST APIs, database design, and JavaScript fundamentals. The whole process felt structured, emphasizing problem-solving and algorithmic thinking.

It was a pretty standard interview process. First, I had a chat with a recruiter over the phone. Then, I had a Teams meeting with the hiring manager. About ten days later, I got a rejection email saying they decided to go with someone whose background was a closer match. This was a bit strange because the job was posted again that same day. The main reason I'm rating it negatively is the lack of honesty in the rejection. It felt like they weren't actually moving forward with anyone, but were just starting the search over, and I would have appreciated more straightforward feedback, especially considering my strong background in this field.

The interview process was straightforward and well-communicated. Had a screening with HR and then 1st round interview with the hiring manager. Plus, many people were open to speaking informally about the organization outside of the formal process, and very helpful. The HR contact provided information ahead of time of what to expect (e.g., overall timelines, & to expect competency-based questions in the 1st round).

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.