PG&E logo
PG&ESoftware Engineer
Updated Jun 23, 2026

PG&E Software Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Software Engineer at PG&E, newest first and distilled into what to expect across the loop.

Get your personalized PG&E Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
Build my free plan
Hot & recentNewest first
4 months ago
Average Positive Fresno, CA

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.
11 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, and the rest of the interview leaned heavily into behavioral stories—especially anything that demonstrated good judgment, teamwork, and handling situations responsibly.

They asked questions in a STAR-style format, so I had to structure my answers around the specifics of what happened, what I did, and what the result was. The panel composition brought together different perspectives, and the flow felt like they wanted to understand how my past work mapped to safety culture and day-to-day collaboration.

Unlock every Software Engineer interview experience

Real Software Engineer interview experiences
  • Difficulty, sentiment and outcomes
  • New reports added every week
See all experiences
Share your 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.

Technical QuestionsAnalytical SkillsDomain Knowledge

Behavioral Focus & Safety Culture

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.

PreparationExpectationsTechnical Topics