WTW Software Engineer Interview Questions
& Process

So first there was this Hirevue thing with normal questions and some psychometric games. Then a take-home coding assignment for the technical test. After that, an assessment centre. It had a competency interview with two software developers, a technical interview with two software developers where we talked about the technical test, and a group exercise. There was also a networking event, but that wasn't part of the assessment.

The first part of the interview was mostly about non-technical stuff, like asking about times you faced challenges or about your strengths. There were also a few basic technical questions, like about SOLID principles. Then, there was a take-home coding assignment. It was basically a CRUD API with an Angular front-end. They said there wasn't a time limit and kind of suggested that how much time you put into it reflects how much you want the job, so I treated it like a project you'd get at work. I ended up implementing everything and spent most of a weekend on it, but didn't get an offer. It's fine if it wasn't the level they were looking for, but I'm really disappointed with the feedback. They expect candidates to spend hours on a coding task and then only give one sentence of feedback that doesn't specify what could have been improved. Honestly, it's pretty lazy and rude, and I'm very unhappy with how the process went.

So I interviewed at WTW and wanted to share what it was like. First, there was an initial chat with a recruiter. It was basically a screening to see if my background fit and if I was interested. They also told me about the company, how the team is set up, and what's next. It was a pretty standard and chill call. Then, I had a technical interview. It was with the hiring manager and three engineers from the team (one frontend, one backend, one SQL/database). They each hit me with questions specific to their area. The frontend person asked about UI frameworks, managing state, and how components are built. The backend person went into APIs, business logic, and some system design stuff. The SQL person quizzed me on writing queries, making databases faster, and how relational databases work. The hiring manager kept things moving and asked about my past experiences and how I'd handle situations, plus how I work with different teams. It was technical but felt like a good conversation, and the team was nice and clear about what they were looking for.