Skip to contentSkip to footer
  • Community
  • Jobs
  • Companies
  • Salaries
  • For Employers
      Notifications

      Loading...

      Elevate your career

      Discover your earning potential, land dream jobs, and share work-life insights anonymously.

      employer cover photo
      employer logo
      employer logo

      Utility Warehouse

      Engaged Employer

      About
      Reviews
      Pay & benefits
      Jobs
      Interviews
      Interviews
      Related searches: Utility Warehouse reviews | Utility Warehouse jobs | Utility Warehouse salaries | Utility Warehouse benefits
      Utility Warehouse interviewsUtility Warehouse Software Engineer (Golang) interviewsUtility Warehouse interview


      Glassdoor

      • About / Press
      • Awards
      • Blog
      • Research
      • Contact Us
      • Guides

      Employers

      • Free Employer Account
      • Employer Center
      • Employers Blog

      Information

      • Help
      • Guidelines
      • Terms of Use
      • Privacy & Ad Choices
      • Do Not Sell Or Share My Information
      • Cookie Consent Tool
      • Security

      Work With Us

      • Advertisers
      • Careers
      Download the App

      • Browse by:
      • Companies
      • Jobs
      • Locations
      • Communities
      • Recent Posts

      Copyright © 2008-2026. Indeed, Inc. "Glassdoor," "Worklife Pro," "Bowls," and logo are proprietary trademarks of Indeed, Inc.

      Company Bowl sample

      Want the inside scoop on your own company?

      Check out your Company Bowl for anonymous work chats.

      Bowls

      Get actionable career advice tailored to you by joining more bowls.

      Followed companies

      Stay ahead in opportunities and insider tips by following your dream companies.

      Job searches

      Get personalized job recommendations and updates by starting your searches.

      Software Engineer (Golang) Interview

      Jun 26, 2026
      Anonymous Interview Candidate
      No offer
      Negative experience
      Average interview

      Application

      I interviewed at Utility Warehouse

      Interview

      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.

      Interview questions [1]

      Question 1

      How would you define a good outcome of a feature not through code
      Answer question
      avatar
      Utility Warehouse response
      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