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

      Utility Warehouse

      Azienda coinvolta

      Chi siamo
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su Utility Warehouse | Offerte di lavoro di Utility Warehouse | Stipendi di Utility Warehouse | Benefit di Utility Warehouse
      Colloqui di Utility WarehouseColloqui per Software Engineer (Golang) presso Utility WarehouseColloquio di Utility Warehouse


      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. Indeed, Inc. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Indeed, Inc.

      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 Software Engineer (Golang)

      26 giu 2026
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza negativa
      Colloquio nella media

      Candidatura

      Ho sostenuto un colloquio presso Utility Warehouse

      Colloquio

      Easily the worst interview process I have been through. It started positively, with a technical chat and competency-based questions involving both the recruiter and hiring manager. They explained how the team works, the technology they use, and the direction they want to take the product in. At that stage, the role and the engineering environment sounded genuinely interesting. After that, however, communication became very poor. I did not hear anything for weeks until I reached out myself. I was repeatedly told that the process would move faster, and I received several apologies about how slow things had been. I was then progressed to the next stage, which involved both a system design interview with two engineers and a live coding problem. This was a two-hour interview completed in one session, with no option to split the stages across different days. I had previously been assured that I did not need to worry about not being fully familiar with Go, and that I could use Java for the coding interview. During the interview, the engineers said they wished they had been told this beforehand and apologised again for the lack of communication. To their credit, both the coding interview and system design discussion went well, and the feedback I received was very positive. However, the following week I again had to keep reaching out to understand where I stood in the process. I was eventually told there would be another interview and that someone would be in contact to arrange availability. I am still waiting for that communication. At this point, the process has taken around three months and still appears to be ongoing. While the product and technology stack looked interesting, the lack of organisation and poor communication throughout the hiring process has completely put me off. My time is also valuable, and candidates should not have to repeatedly chase for basic updates.

      Domande di colloquio [1]

      Domanda 1

      How would you define a good outcome of a feature not through code
      Rispondi alla domanda
      avatar
      Risposta di Utility Warehouse
      4d
      Thank you for taking the time to share such detailed and constructive feedback about your interview experience. First and foremost, we want to sincerely apologise for the extended timeline and the gaps in communication you experienced. A three-month process is not the standard we aim for, and we fully recognise that your time and effort deserve better. During the course of your interviews, we experienced changes in team ownership and internal hiring coordination that affected continuity across the process. While this provides context, it does not excuse the delays or the lack of clear communication you experienced. We also identified a misalignment internally regarding the programming language expectations for the technical stage, and we regret that this created unnecessary pressure during your live coding session. While we are glad to hear that you found the product interesting and had positive interactions with our engineering team, the overall experience you describe fell short of the standard we expect to provide. We are reviewing our interview ownership, interviewer alignment, and scheduling processes to improve accountability and ensure candidates receive a more consistent and timely experience. Thank you again for your honesty and for the time you invested in speaking with us. While we missed the mark with you, your review is directly shaping a better experience for future software engineers. If you are open to it, we would love the chance to connect with you directly to provide proper closure on your application and listen to any further insights you might have. Please feel free to reach out to Martyna at mzbyszewska@uw.co.uk or myself Ketna kramchandani@uw.co.uk