Questions to ask at interview

A key way to kind of showcase that is that you're really kind of leaning into, "What will the job look like?" A simple signal that I often look for and have shown in interviews, and that has proved to work well for me, is to quickly adopt the kind of terminology that you would use if you were part of the team. So for example... This is a really simple thing, but rather than saying, "What challenges are you facing?" you can say, "Well, if we are working together on this, what challenges will we be facing?" And it's very kind of subtle, but it's a very strong clue to an interviewer that this person is already a team player.

I always try and keep in mind that interviews are a two way thing. Although you are being interviewed, you should see it as an opportunity to interview the person. At the end of the day, you are going to have to work for this company. You are going to have to invest your time and energy into it. It's just as important that this person can answer your questions and this company can give you the things you want, as much as they do. I think it's quite easy to go into interviews feeling quite pressurised, like it's all on you. That's what I try and do to try and relax myself and to actually try and see it as an opportunity to figure something out, like are you right for me, as well?

As somebody who has been doing a lot of interviewing lately, I really relish the moment when a candidate asks me a question I'm not expecting or gives me the opportunity to talk about something a little bit more interesting or meaningful beyond the basics, because the basics, you can cover over and over again throughout the application process and the interview process, but to be able to have that moment of connection, "Ah, so this is something that's important to you. I've got an opportunity to tell you how we can deliver that for you as a candidate." And it's nice, actually, so in terms of trying to encourage people to feel more confident, I think 9 times out of 10, I think interviewers actually quite like those questions, those questions where they a bit grilled and get a little bit more of a steer on what the candidate is actually looking for.

The first thing would be curiosity. I've seen from experience, once I've gone through various stages and I'm more or less curious as to... The previous stage was like this, the second stage was like this, what's next stage going to be like? Also how intrinsic the knowledge I'm getting from doing the interviews is. I love interviews where I'm even learning something, not just only being asked questions or me answering or them getting more insights from me, I'm also getting a little bit of insight. I'm also getting knowledge from the interviewer as well.

The second interview with the tech team will be crucial for me in order to decide if I will move forward or not. In this case, I'm interested more in the infrastructure of the products and the roadmap and the team and the seniority of the team, and again, in general, the whole organisation of the dev department.