Passa al contenutoPassa al piè di pagina
  • Lavori
  • Aziende
  • Stipendi
  • Per le aziende

      Migliora la tua carriera

      Scopri le tue potenzialità di guadagno, trova lavori da sogno e condividi approfondimenti su lavoro e vita privata in forma anonima.

      employer cover photo
      employer logo
      employer logo

      Octopus Energy

      Azienda coinvolta

      Circa
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su Octopus Energy | Offerte di lavoro di Octopus Energy | Stipendi di Octopus Energy | Benefit di Octopus Energy
      Colloqui di Octopus EnergyColloqui per Senior Software Engineer presso Octopus EnergyColloquio di Octopus Energy


      Glassdoor

      • Chi siamo
      • Contattaci

      Aziende

      • Account Business gratuito
      • Spazio per le aziende
      • Blog per le aziende

      Informazioni

      • Aiuto
      • Linee guida
      • Condizioni d'uso
      • Privacy e scelte pubblicitarie
      • Non vendere né condividere le mie informazioni
      • Strumento per l'accettazione dei cookie

      Lavora con noi

      • Inserzionisti
      • Carriere
      Scarica l'app

      • Cerca:
      • Aziende
      • Lavori
      • Località

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Glassdoor LLC.

      Aziende seguite

      Non lasciarti sfuggire opportunità e informazioni privilegiate seguendo le aziende dove vorresti lavorare.

      Ricerche di lavoro

      Ricevi suggerimenti e aggiornamenti personalizzati avviando le tue ricerche.

      Colloquio per Senior Software Engineer

      18 nov 2020
      Candidato anonimo a colloquio
      Londra, Inghilterra
      Nessuna offerta
      Esperienza negativa
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto 2 settimane. Ho sostenuto un colloquio presso Octopus Energy (Londra, Inghilterra) nel mese di mar 2020

      Colloquio

      1) Internal recruiter chat, 2) 1h chat with CTO, 3) home test in python, 4) 1.5h chat with Head of Eng. The process was quite personal although not particularly challenging. The take home task wasn't particularly well suited for the role I was aiming for. After all the time both sides invested, the internal recruiter, who was the only point of contact, went silent. Waste of time. I hope this level of disorganisation doesn't extend across the company.

      Domande di colloquio [1]

      Domanda 1

      The usual get to know senior engineer questions...
      1 risposta
      1
      avatar
      Risposta di Octopus Energy
      5y
      Thank you for your feedback, we are always looking to improve our processes. We are so sorry that you had a negative experience with us. March was a unique time for us as we began to scales rapidly and simultaneously deal with the beginnings of the pandemic. Please reach out to our Head of Talent at talent@octoenergy.com so we can discuss further.

      Altre recensioni di colloqui per Senior Software Engineer presso Octopus Energy

      Colloquio per Senior Software Engineer

      14 mag 2024
      Dipendente anonimo
      Berlino
      Offerta accettata
      Esperienza positiva
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Octopus Energy (Berlino) nel mese di apr 2024

      Colloquio

      I applied through the company's career page, and the entire interview process comprised four rounds. First Round: This was a phone interview with the company's internal recruiter. The recruiter was articulate and listened attentively to everything I had to say. I was asked to provide a brief introduction, discuss my current job and company, explain why I wanted to switch jobs and join Octopus Energy, and describe my experience with the tech stack. Second Round: The following day, the recruiter called to invite me to the second round, which took place four days later. This was an online interview via Google Meet with two Senior Software Engineers. The session was more of a discussion aimed at understanding my background, experience, and career aspirations. I introduced myself and explained a project I was particularly proud of. Both interviewers were polite and listened carefully. They asked a few cultural fit questions, inquired about my teamwork approach, and how I handle conflicts. That same evening, the recruiter informed me that I had progressed to the third round. Third Round: This was an offline tech challenge. The task was to implement a Django application that processes files, extracts information, and stores it in a database. I was given several days to complete the challenge but was advised to spend no more than 3-4 hours on it to minimize the burden on applicants. Any incomplete tasks needed to be documented in a README file. Final Round: A few days after submitting the tech challenge, I was invited to the final round of interviews. This round involved two Senior/Lead Software Engineers. They asked questions about the tech challenge and general queries relevant to a Python/Django backend engineer. There were no algorithm questions, online coding tasks, or trick questions, and the interviewers did not intend to grill the candidate. I will list some of the specific questions in a later section. I believe I received a conditional offer the next day (or perhaps two days later). The recruiter was highly diligent and managed the entire process with exceptional care and efficiency.

      Domande di colloquio [1]

      Domanda 1

      Database Model Selection: I was asked why I chose a particular database model, especially in terms of normalization. The interviewers were interested in understanding my reasoning behind the database structure and how it ensures data integrity and efficiency. Database Transactions: The interviewers inquired about how well I had considered database transactions. They wanted to know if I had implemented strategies to ensure data consistency and handle potential errors effectively. Design Approach: Questions were also asked about my approach to the tech challenge and why I chose certain design patterns. While they did not require explanations of specific terminology or design patterns (as it is assumed that a senior role would be familiar with these concepts), the focus was on understanding my problem-solving process and the rationale behind my decisions.
      Rispondi alla domanda
      5

      Colloquio per Senior Software Engineer

      9 feb 2024
      Dipendente anonimo
      Manchester, Inghilterra
      Offerta accettata
      Esperienza positiva
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto 3 settimane. Ho sostenuto un colloquio presso Octopus Energy (Manchester, Inghilterra)

      Colloquio

      Started with a take home test, followed by two 1 hour interviews (behavioural and technical). I appreciated how efficient the whole process was, and how responsive my recruiter was when I had questions. Everyone was very friendly and it was actually kind of fun, for a series of interviews :)

      Domande di colloquio [1]

      Domanda 1

      Discuss performance improvements for a given system design.
      Rispondi alla domanda

      Colloquio per Senior Software Engineer

      19 apr 2024
      Dipendente anonimo
      Tokyo
      Offerta accettata
      Esperienza positiva
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto 6 settimane. Ho sostenuto un colloquio presso Octopus Energy (Tokyo) nel mese di feb 2024

      Colloquio

      I applied via Octopus Energy website. The whole process took one and half month. 1- Code Challenge: I requested to create a project for an API integration. 2- Behavioral Interview: We talked about my past experiences. I was asked some questions about them. 3- Technical Interview (System Design): I received the problem before the interview. It is open-ended so I can't say it is easy or hard. It was a friendly chat about this problem. 4- Offer Call People were very friendly. I think code challenge review took a bit longer but it's understandable when we consider huge number of applicants.

      Domande di colloquio [2]

      Domanda 1

      First interview was not technical so I can say that I mostly talked about my past experiences and questions related with it.
      Rispondi alla domanda

      Domanda 2

      On the second interview (system design), we discussed a technical problem (kind of cloud communication issues) which i got the details before the interview.
      Rispondi alla domanda