Real, anonymous reports from people who interviewed for Software Engineer at BC Hydro, newest first and distilled into what to expect across the loop.
I started with a panel interview on Microsoft Teams. The whole thing felt structured and straightforward: we went through behavioral questions and scenario-style prompts, then I had a brief case discussion. After that, there was a Q&A where I could ask things back, and the interviewers clearly walked me through what would happen next and what the timeline looked like for the hiring process.
My process felt unusually quiet and a bit frustrating. I went into what was described as a fairly standard set of questions—roughly twenty—and the topics ended up being very generic and not closely tied to the role. The delivery surprised me more than the content: there were long, awkward silences while the interviewers typed my responses.
The interview process typically begins with a pre-screening call followed by a structured interview that includes behavioral questions, technical assessments, and a Q&A session. Candidates reported a clear timeline and understanding of the process, which contributed to a low-stress atmosphere.
Candidates can expect a strong emphasis on behavioral questions focusing on teamwork, strengths, weaknesses, and personal motivations, often following a STAR format. This aspect is crucial as it helps interviewers gauge cultural fit and collaboration skills.
The technical portion of the interviews generally includes straightforward questions that assess problem-solving abilities rather than deep technical knowledge, often allowing candidates to explain their reasoning in pseudocode or through thought processes.
Candidates noted that the interviewers emphasized a scoring system to evaluate responses, which created a structured but sometimes tense atmosphere. This scoring approach made it clear that performance against set expectations was critical.
The interaction style varied, with some candidates experiencing long silences and a lack of follow-up questions, which hindered the flow of conversation. Others reported a friendly and responsive environment that encouraged back-and-forth dialogue.
Many candidates reflected on the importance of articulating their thought processes and experiences clearly, noting that the ability to connect answers to the role was as significant as technical knowledge. Some wished they had prepared more for the reasoning-based questions.