Redgate Software Software Engineer Interview Questions
& Process

First, you submit your CV and some info about yourself for the application. Then, they send you a coding assignment via email with a decent deadline to check your developer skills. I really like this approach over those big companies that use game tests. They actually value you here and give you an assignment that makes sense. If you pass the assignment, you move on to a technical interview. The interviewer will ask you to explain your thought process while pair programming. They also check if you'd fit in with Redgate's culture. If you pass this, they'll send an offer. That's it. My advice for interviews: practice Leetcode medium problems and review your CV. Be yourself, be honest, and good luck!

I applied through LinkedIn and got a quick response from the people team with a programming task. It was about counting and ordering words. I sent it back, and again, they got back fast and scheduled an interview for the next week. The whole initial process was great, and the team was super helpful and informative. I found plenty of parking when I got there. Receptionists greeted me at the door, offered a drink, and I waited in an area with books, instruments, and coffee machines. After about 5 minutes, two software developers who would interview me met me and offered another drink. The interview felt pretty casual, not too much pressure, and I actually enjoyed chatting with them. I learned a lot, and they seemed keen to help and guide me. They asked standard questions about my past experience, university work, teamwork, and personal projects. Then we moved to two programming challenges done on the computer in the interview room using C#, not on a whiteboard. One was parsing an integer, which I didn't expect but enjoyed. The second was a doubly linked list traversal to find nodes within a specific range. I messed up the second one, probably due to nerves and not asking clarifying questions. After the coding part, there were more general software questions, like how garbage collection works. I didn't know much, but they explained it well, and I researched it later. Then I got a tour of the offices and more coffee.

I had a 30-minute technical interview with one person first. Then, a two-hour technical interview with two people where I had to understand and improve a codebase. Finally, a two-hour behavioral interview with two people.