My technical screen was fairly direct: I answered normal questions about my resume, and then I got a few technical questions where I ended up needing a calculator for the problems. There were only three technical questions total, but that unexpected requirement threw me for a moment.
I handled it by being straightforward about what I knew versus what I hadn’t learned in school. One part I hadn’t come across before was still solvable, but it wasn’t something I could pretend I’d seen through the usual coursework.
3 months ago
Easy Positive Vacaville, CA
Because I was going through contracting, my process started with a call with the recruiter at the contracting agency. After that, if I was still interested, they scheduled the hiring-manager conversation with PG&E.
The recruiter also set expectations around timing and commitment: I was told not to agree to numbers with the contracting agency until I’d met the hiring manager and had a real discussion about what the role actually looked like—who I’d be working with and what the job was like day to day. That contract gating was the main thing that stood out, since it felt like the early stage was really about alignment before any concrete commitments.
10 months ago
Average Positive San Ramon, CA
A recruiter conversation and then a panel interview shaped most of my experience. Before the panel really dug in, there was a clear safety briefing, a…
11 months ago
Average Positive United States
After joining through Teams, I had a single interview that was mostly technical plus behavioral questions, and it stayed fairly contained—about an hou…
> 1 year
Easy Positive United States
My interview began like a straightforward single-panel conversation where the structure stayed pretty light. I met with a panel of three—two superviso…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Flow
The interview process typically starts with a recruiter call followed by a panel interview, often structured around behavioral and technical questions. Many candidates noted a STAR format for responses, emphasizing structured storytelling.
STARPanelBehavioral
Technical Assessment
Candidates reported a mix of technical questions, often focused on analytical and domain knowledge rather than pure coding, with some mentioning a written test prior to interviews. The technical discussions aimed to connect past experiences to practical engineering tasks.
There is a strong emphasis on behavioral questions, particularly around teamwork, judgment, and safety culture, with many candidates feeling that their responses needed to align with the company's values. Safety-related questions often appeared early in the interviews.
SafetyTeamworkJudgment
Recruitment Process Length & Communication
Candidates experienced varying timelines, with some reporting long waits for feedback and a lack of communication after interviews, which contributed to a feeling of uncertainty about their application status.
CommunicationTimelineFeedback
Interview Environment & Tone
The overall tone of interviews was described as formal and sometimes rigid, with some candidates feeling a lack of warmth or personal engagement. This contributed to a perception of a tightly controlled process.
FormalRigidEngagement
Preparation & Expectations
Candidates expressed the importance of preparing for both technical and behavioral components, with some wishing they had practiced more on specific technical topics relevant to the role. Understanding the company's focus on safety and teamwork was also highlighted as crucial.