Octopus Energy Software Engineer Interview Questions
& Process

I had a quick chat with the recruiter, then got sent a technical test. Turns out it was for the wrong role, which they apologized for, saying they were overworked and looking forward to a holiday. I'd prepped a lot for that first test, so I was pretty burnt out and bummed when I got the correct test. Then, the second recruiter was kinda quiet, even when I asked for more time because of their mistake. It was a super frustrating process, maybe the worst ever.

My interview experience with Octopus Energy started well. After the first technical interview, I was given a take-home assignment. I could use any tech I wanted, but the base was Next JS. I was told my code wasn't up to par with my experience, focusing on three things: design decisions, store management, and documentation. I disagreed with the feedback, especially since the instructions said 'simple React app.' For store management, they expected Redux or context for cart quantity, which seemed unnecessary as the state was only used once. The documentation feedback was also unclear, as the provided bootstrap had enough instructions.

I ended up interviewing for a Backend Engineer role at Kraken Technologies. It all started when I met the hiring manager at a Django Meetup in London, and after a good chat, I got interested in the backend role. I'd already visited the Kraken office for another Meetup and talked to some employees, and after another catch-up with the hiring manager to learn more about the team and their work, I decided to go for it. The entire process was a really positive experience! Everyone was friendly and helpful, and things moved quickly. It was broken down into 5 parts: First, a 45-minute screening with an internal recruiter to go over my background, technical skills, and reasons for looking for a new role, plus I got to ask about the company culture and tech teams. It was a good chat and helped me understand the company better. Second, a 45-minute technical/cultural interview with two engineers from the tech teams. It felt pretty informal, we actually asked each other questions, and we talked about my past projects, the pros and cons of technical choices, what excites us about our work, their projects at Kraken, the technical hurdles they face, and their problem-solving methods, both technical and otherwise. It was like chatting with future colleagues and I found it really insightful. Third, a take-home test that took about 3-5 hours, where I had to build a Django app with a GraphQL API. It was a well-sized and engaging task. Fourth, a 45-minute final interview with two engineers from the team I'd potentially join, focusing on the technical choices I made in the take-home test and what I'd do differently with more time. It was a thorough discussion without any tricks, feeling much like a code review session with my team, which is something I really enjoy. We discussed my data modeling, design pattern choices, testing strategies, and potential code refactoring. We also covered the team's technical challenges, the role's expectations, and how my skills align with the team's needs and growth opportunities. Fifth, an offer!