A Software Engineer at Pacific Gas and Electric (PG&E) plays a critical role in building, maintaining, and modernizing the digital infrastructure that powers northern and central California. Unlike standard tech companies, software engineering here sits at the vital intersection of advanced software development and critical physical infrastructure. The applications and systems you build, integrate, and support directly impact the safety, reliability, and clean energy delivery for over 16 million people. In this role, you will work on complex, high-impact problem spaces that range from grid modernization and asset management to real-time outage tracking and geographic information systems (GIS). You will collaborate closely with cross-functional teams, including electrical engineers, grid operators, data scientists, and project managers, to translate physical utility challenges into scalable software solutions. Your work ensures that the control systems, automation scripts, and enterprise applications running PG&E’s grid remain secure, resilient, and highly available. Preparing for this position requires an understanding that software quality at PG&E is directly tied to operational safety and public welfare. You are not just writing code; you are engineering systems where reliability is measured in continuous power delivery and community safety.
Online Application
reportedSubmit your application and complete a screening questionnaire.
What to demonstrate
- Submit your application and complete a screening questionnaire
- Depth in STAR Method (Interview Response Framework)
How to prepare
- Answer aloud and timed: Describe a situation where a project or task did not turn out as planned. What did you do, and what was the outcome?
- Answer aloud and timed: Tell me about a time when you and a coworker did not see eye-to-eye. How did you resolve the conflict and reach a conclusion?
Pre-employment Tests
reportedComplete any required pre-employment tests, such as the Physical Test Battery or Technical Test.
What to demonstrate
- Complete any required pre-employment tests, such as the Physical Test Battery or Technical Test
- Depth in STAR Method (Interview Response Framework)
How to prepare
- Answer aloud and timed: Describe a time when you realized you could not meet an established deadline. How did you handle the situation with your team and stakeholders?
- Answer aloud and timed: Give an example of a difficult interaction you had with a customer or external stakeholder and how you resolved it.
Panel Interview
reportedParticipate in a virtual or on-site panel interview with two to four interviewers.
What to demonstrate
- Participate in a virtual or on-site panel interview with two to four interviewers
- Depth in STAR Method (Interview Response Framework)
How to prepare
- Answer aloud and timed: Tell me about a time you had to quickly adapt to a major change in project requirements or team structure.
- Answer aloud and timed: Describe a safety issue or risk you identified in a past role and the steps you took to remedy it.
Behavioral and Technical Questions
reportedAnswer pre-determined behavioral and technical questions during the panel interview.
What to demonstrate
- Answer pre-determined behavioral and technical questions during the panel interview
- Depth in STAR Method (Interview Response Framework)
How to prepare
- Prepare three examples from your own work, each with a decision you made and an outcome you can quantify.
- Re-read the description of the behavioral and technical questions above and write down what you would ask to confirm before it.
Candidate Questions
reportedConclude the panel interview by asking questions about the team and role expectations.
What to demonstrate
- Conclude the panel interview by asking questions about the team and role expectations
- Depth in STAR Method (Interview Response Framework)
How to prepare
- Answer aloud and timed: What are your expectations of a company’s safety culture, and how do you contribute to it daily?
- Answer aloud and timed: How would you design, build, and deploy an application across multiple clients in a secure Windows environment?
PracHub editorial advice for the preparation topics above.
Do not skip preparing for the behavioral portion
Many technically brilliant candidates fail the PG&E interview because they did not structure their answers using the STAR format or failed to demonstrate a safety-first mindset.
Prepare a Safety Message
Since safety is PG&E's top priority, starting your panel interview with a brief, professional safety message (e.g., a tip on digital security, ergonomic workspace setup, or emergency preparedness) shows immediate cultural alignment.
Know Your Resume in Detail
The panel will have your resume in front of them and may ask you to explain specific design decisions, technologies used, or project outcomes from your past roles. Be ready to speak to everything you have listed.
Expect a Quiet Panel
PG&E interviewers take detailed notes during your responses to ensure accurate scoring. Do not be discouraged if they do not provide immediate feedback or conversational cues; maintain your confidence and deliver structured answers.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Track a rolling failure rate per destination for circuit decisions
The egress service delivers about 1,500 webhooks per second across roughly 40,000 destinations, each call bounded by a 10 second timeout. Maintain, per destination, the failure rate over the trailing 60 seconds so a caller can ask before dispatch whether the circuit should open. Attempts arrive as (destination_id, finished_at_ms, outcome). Requirement: amortised O(1) per attempt, with total memory bounded by the destination count rather than by traffic. Give the structure, its exact memory, and the rule that stops a destination with three attempts from opening a circuit.
Approach
- Name the exact-deque version and then reject it as the default. Holding timestamps and advancing a tail pointer past anything older than now minus 60 seconds is a correct two-pointer window at amortised O(1) per attempt, but its memory tracks in-window traffic, so one destination in a retry storm holds hundreds of thousands of entries while thousands of quiet destinations hold none.
- Use a ring of 60 one-second buckets per destination, each bucket a pair of counters for attempts and failures. On an attempt, advance the ring by the elapsed whole seconds, zeroing at most min(elapsed, 60) buckets, then increment the head. That is amortised O(1) with a fixed footprint per destination.
- State the footprint: 60 buckets times two 4-byte counters is 480 bytes of payload per destination, so 40,000 destinations is roughly 20 to 25 MB with per-entry overhead, bounded by the catalogue rather than by the rate. The cost is granularity, since the oldest bucket ages out in whole seconds, which is far tighter than the decision needs.
- Require a minimum sample before the circuit may open. A destination with three attempts and three failures reads as 100 percent and is not evidence; a floor of roughly 20 attempts in the window makes the ratio meaningful, and below that floor use a run of consecutive failures as the trigger instead.
Follow-up
- The fleet is 30 instances and each sees roughly a thirtieth of a destination's traffic. Where does the rate actually live, and what does a per-instance answer get wrong?
- A destination answers in 9.5 seconds and succeeds. It is not failing but it is consuming your per-destination concurrency. What signal should open the circuit here?
Identify the heaviest tenants in a five-minute window under memory pressure
The edge service handles about 3,000 requests per second across roughly 50,000 tenants, peaking near 9,000. Expose the 50 heaviest tenants by request count over the trailing five minutes so limits can be tightened before one tenant's backfill starves the fleet. You may not retain five minutes of raw records. Give the exact solution and its memory, then the bounded-memory approximation with its error stated as a formula, and say which you would ship and at what tenant cardinality that choice changes.
Approach
- Do the exact version first, because it is affordable at this cardinality: a ring of 300 one-second counters per tenant, advanced lazily, is 1,200 bytes of counters per tenant and roughly 60 to 90 MB for 50,000 tenants with overhead. Carry a running total and subtract the bucket you overwrite so a window read is O(1) rather than 300 adds.
- Extract the top 50 with a size-k min-heap over the tenant sums: O(d log k) for d tenants, against O(d log d) to sort them all. Maintaining the heap continuously instead of on query requires a tenant-to-heap-index map, because incrementing a count already inside the heap means sifting from a known position, and without that map you rebuild the heap on every request.
- State the approximation precisely rather than gesturing at sketches. Misra-Gries with m counters retains every item whose true count exceeds N/(m+1), and each retained count underestimates the truth by at most N/(m+1). With m = 1,000 and N = 900,000 requests in the window the error is roughly 900 requests, which is fine for spotting a tenant sending 50,000 and useless for ranking two tenants 200 apart.
- Say what breaks when the window slides: Misra-Gries and Space-Saving are insert-only and cannot be decremented as records age out. The workable construction is one summary per sub-window, say ten seconds, with 30 summaries merged at query time, and the merged error is the sum of the per-summary errors, so the bound degrades linearly in the number of sub-windows.
Follow-up
- The heaviest tenant is heavy because of one export job rather than user traffic. Should the limiter treat those as the same tenant?
- Two tenants sit tied at the boundary of the top 50. Does your answer flap, and does the flapping matter?
Collapse a redelivered event batch into per-aggregate high-water marks
You drain a batch of up to 5,000,000 events, each (aggregate_id BIGINT, aggregate_version INT, event_type, payload). The log guarantees order within one aggregate only; the batch merges 64 partitions, and a relay failover has redelivered a range, so an older version for an aggregate can appear after a newer one. Given a map of last_applied_version per aggregate, produce the events worth applying, at most one per (aggregate_id, version), plus the count discarded. Target O(n) time. State the memory for 2,000,000 distinct aggregates and what you do when it does not fit.
Approach
- One pass, one hash map from aggregate_id to the highest version kept, and a discard counter. An event whose version is at or below last_applied_version for its aggregate is dropped without further work, which is the whole reason the event carries its version rather than a delta. O(n) expected time, O(d) space in distinct aggregates.
- Keep the maximum, never the last occurrence. The redelivered range means the final appearance of an aggregate in the batch can be an older version than one seen earlier in the same batch, so last-wins applies stale state over newer state and the projection regresses with no error anywhere.
- Cost the memory instead of calling it large: an 8-byte key plus a 4-byte version is 12 bytes of payload, and an open-addressed table held at a 0.7 load factor costs roughly 17 bytes per entry before per-slot metadata, so 2,000,000 aggregates is tens of megabytes in a native layout and several times that in a runtime that boxes both key and value.
- If the distinct set exceeds memory, partition on hash(aggregate_id) mod P and reduce each partition independently. Every event for one aggregate hashes to the same partition, so the per-partition result is exact and the merge is concatenation rather than a second reduction.
Follow-up
- The payload is a patch rather than a snapshot, so applying only the highest version loses the intermediate changes. What changes in your reduction?
- How do you detect that version 7 arrived while version 6 was never delivered, and what should the consumer do about the gap?
Keep soft-deleted accounts from blocking re-registration
app_user holds user_id, tenant_id, email CITEXT, password_hash (NULL for SSO principals), email_verified_at, auth_version, status ('invited','active','suspended','deactivated'), created_at, updated_at, deleted_at. Two live accounts for one address inside a tenant must be impossible, but an address freed by a soft delete must be reusable, and the same tenant may delete and re-register it repeatedly. Write the uniqueness DDL for PostgreSQL 16, then the equivalent for MySQL 8 where partial indexes do not exist, and say what each permits once three deleted rows already hold that address.
Approach
- Start from what is actually unique: not (tenant_id, email), but (tenant_id, email) among live rows. PostgreSQL says that directly — CREATE UNIQUE INDEX app_user_live_email ON app_user (tenant_id, email) WHERE deleted_at IS NULL. A full constraint over the same two columns burns the address permanently the first time someone deletes an account.
- Keep case-insensitivity in the type or the index, never in the application: CITEXT as given, or UNIQUE (tenant_id, lower(email)) as an expression index where the extension is unavailable. A case-sensitive unique column is exactly how two accounts for one human appear.
- For MySQL 8 the predicate has to move inside the key: add a discriminator column that is a constant 0 while the row is live and is set to user_id on delete, with UNIQUE (tenant_id, email, deleted_marker). Live rows share the constant and still collide; deleted rows differ from each other and stop colliding.
- State the NULL variant and its dependency: leaving the marker NULL for deleted rows also works, because a unique index treats NULLs as distinct — true in MySQL, and true in PostgreSQL only under the default NULLS DISTINCT, which PostgreSQL 15 lets you reverse. Check the polarity against the three existing deleted rows: constant-on-live is what preserves the collision you want, and reversing it silently admits duplicate live accounts.
Follow-up
- A deleted account re-registers with the same address the next day. Do the old resource rows follow the new user_id, and how does the API keep the two principals apart?
- How do you honour an erasure request while resource_revision.actor_user_id still references this table?
Write the update path that detects a concurrent edit
resource carries version INT NOT NULL DEFAULT 1. resource_revision holds revision_id, resource_id, version, actor_user_id, change_kind, patch JSONB, request_id, created_at with UNIQUE (resource_id, version). outbox_event holds aggregate_type, aggregate_id, aggregate_version, event_type, payload, status. A PUT carries the version the client read. Write the exact statements for the single transaction that applies the edit, records the revision and enqueues 'resource.updated', and give the handler's branch on zero affected rows. Then say what PostgreSQL 16 does under READ COMMITTED when two of these updates hit one row at once.
Approach
- One transaction, three writes, no network call inside it: UPDATE resource SET title = $3, version = version + 1, updated_at = now() WHERE resource_id = $1 AND tenant_id = $4 AND version = $2; then INSERT the resource_revision row at version $2 + 1; then INSERT the outbox_event row at the same aggregate_version. The event goes to a table rather than a broker because no transaction spans both.
- Branch on the affected-row count before doing anything else. Zero has three causes — stale version, wrong tenant, row gone — so re-read once and map to 409 carrying the current version, or 404 for an id outside the caller's tenant, which also stops the endpoint confirming that another tenant's id exists.
- State the engine behaviour instead of assuming it. Under READ COMMITTED the second UPDATE blocks on the row lock, and when the first commits PostgreSQL re-evaluates the WHERE clause against the newly committed row, so the version predicate now fails and the statement reports zero rows. Under REPEATABLE READ the identical collision raises SQLSTATE 40001 instead, so the handler must fold both shapes into one conflict response.
- Keep UNIQUE (resource_id, version) even though the predicate already serialises writers. It is what makes a lost update unwritable if any other path ever reaches the revision table, and it converts a logic bug into 23505 rather than into a silently missing history row.
Follow-up
- A client sends the version it read ten minutes ago and the resource has moved three versions. What is in your 409 so it can resolve the conflict without a full re-fetch?
- Two editors, two disjoint fields, no overlap. Does your answer still refuse the second write, and should it?
How would you design, build, and deploy an application across multiple clients in a secure Windows environment
How would you design, build, and deploy an application across multiple clients in a secure Windows environment?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
Walk us through your design process when architecting a data pipeline or integration layer between legacy syst
Walk us through your design process when architecting a data pipeline or integration layer between legacy systems and modern APIs.
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
How do you approach debugging a complex, distributed application when there is no clear error log?
How do you approach debugging a complex, distributed application when there is no clear error log?
Approach
- Establish what changed and when, before forming any theory.
- Pick a bisection that eliminates candidates whichever way it turns out.
- Check the instrumentation before believing the symptom.
- Separate the trigger from the cause; the deploy is rarely the bug.
Follow-up
- What would you look at first, and what would it rule out?
- How would you tell a cause from a coincidence here?
Built from the rounds and topics Pacific Gas and Electric candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Pacific Gas and Electric loop
- Write out the reported sequence: Online Application, Pre-employment Tests, Panel Interview, Behavioral and Technical Questions, Candidate Questions.
- For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.
Deliverable: A one-page map of the 5 reported rounds, with the weakest marked.
02Work STAR Method (Interview Response Framework)
- Spend the session on STAR Method (Interview Response Framework), which Pacific Gas and Electric candidates report being tested on.
- Write one worked example in STAR Method (Interview Response Framework) and time yourself on it.
Deliverable: One timed worked example in STAR Method (Interview Response Framework).
03Work Behavioral Interviewing
- Spend the session on Behavioral Interviewing, which Pacific Gas and Electric candidates report being tested on.
- Write one worked example in Behavioral Interviewing and time yourself on it.
Deliverable: One timed worked example in Behavioral Interviewing.
04Work Coding / Programming Exercises
- Spend the session on Coding / Programming Exercises, which Pacific Gas and Electric candidates report being tested on.
- Write one worked example in Coding / Programming Exercises and time yourself on it.
Deliverable: One timed worked example in Coding / Programming Exercises.
05Answer out loud: Behavioral & STAR Questions
- Answer aloud, timed: Describe a situation where a project or task did not turn out as planned. What did you do, and what was the outcome?
- Answer aloud, timed: Tell me about a time when you and a coworker did not see eye-to-eye. How did you resolve the conflict and reach a conclusion?
Deliverable: Spoken answers to 2 reported Behavioral & STAR Questions question(s), under time.
06Answer out loud: Safety & Company Values
- Answer aloud, timed: Describe a safety issue or risk you identified in a past role and the steps you took to remedy it.
- Answer aloud, timed: Why do you want to work for Pacific Gas and Electric, and how do you see yourself fitting into our safety-first culture?
Deliverable: Spoken answers to 2 reported Safety & Company Values question(s), under time.
07Answer out loud: Technical, Infrastructure & Systems Engineering
- Answer aloud, timed: How would you design, build, and deploy an application across multiple clients in a secure Windows environment?
- Answer aloud, timed: Explain your experience with server environments, client operating systems, and writing automation scripts to streamline operations.
Deliverable: Spoken answers to 2 reported Technical, Infrastructure & Systems Engineering question(s), under time.
Expand any day for tasks and deliverables. Your progress is saved on this device.
Behavioural rounds judge the decision you made and what it cost.
Describe a situation where a project or task did not turn out as planned. What did you do, and what was the ou
Describe a situation where a project or task did not turn out as planned. What did you do, and what was the outcome?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Tell me about a time when you and a coworker did not see eye-to-eye. How did you resolve the conflict and reac
Tell me about a time when you and a coworker did not see eye-to-eye. How did you resolve the conflict and reach a conclusion?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Describe a time when you realized you could not meet an established deadline. How did you handle the situation
Describe a time when you realized you could not meet an established deadline. How did you handle the situation with your team and stakeholders?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Give an example of a difficult interaction you had with a customer or external stakeholder and how you resolve
Give an example of a difficult interaction you had with a customer or external stakeholder and how you resolved it.
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Tell me about a time you had to quickly adapt to a major change in project requirements or team structure.
Tell me about a time you had to quickly adapt to a major change in project requirements or team structure.
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Describe a safety issue or risk you identified in a past role and the steps you took to remedy it.
Describe a safety issue or risk you identified in a past role and the steps you took to remedy it.
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Why do you want to work for Pacific Gas and Electric, and how do you see yourself fitting into our safety-firs
Why do you want to work for Pacific Gas and Electric, and how do you see yourself fitting into our safety-first culture?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
How do you prioritize safety and quality when you are under intense pressure to deliver a software release?
How do you prioritize safety and quality when you are under intense pressure to deliver a software release?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
What are your expectations of a company’s safety culture, and how do you contribute to it daily?
What are your expectations of a company’s safety culture, and how do you contribute to it daily?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Explain your experience with server environments, client operating systems, and writing automation scripts to
Explain your experience with server environments, client operating systems, and writing automation scripts to streamline operations.
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Describe your experience with database management, load flow analysis, or integrating software with physical h
Describe your experience with database management, load flow analysis, or integrating software with physical hardware like PLCs or LabVIEW systems.
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
- 01
Describe a situation where a project or task did not turn out as planned. What did you do, and what was the outcome?
- 02
Tell me about a time when you and a coworker did not see eye-to-eye. How did you resolve the conflict and reach a conclusion?
- 03
Describe a time when you realized you could not meet an established deadline. How did you handle the situation with your team and stakeholders?
- 04
Give an example of a difficult interaction you had with a customer or external stakeholder and how you resolved it.
How difficult are the technical interviews compared to typical Silicon Valley tech companies?
The technical interviews at PG&E tend to focus more on practical systems engineering, architecture, scripting, and logical problem-solving rather than highly abstract, LeetCode-style algorithm puzzles. While the questions are highly practical, they are thorough and require a deep understanding of how software runs in secure, enterprise environments.
Pacific Gas and Electric Software Engineer candidate reports ↗How important is the STAR method during the interview?
It is absolutely critical. PG&E uses a highly standardized behavioral grading system. If you do not structure your behavioral answers clearly using the Situation, Task, Action, and Result format, the interviewers will struggle to score your responses highly, regardless of how impressive your experience is.
Pacific Gas and Electric Software Engineer candidate reports ↗What is the company culture like for software engineers?
The culture is highly collaborative, mission-driven, and focused on public safety and service reliability. Engineers at PG&E take great pride in knowing their work directly impacts the daily lives of millions of Californians. The environment is structured, highly regulated, and prioritizes methodical quality over rushing products to market.
Pacific Gas and Electric Software Engineer candidate reports ↗Does PG&E offer remote or hybrid work options for software engineers?
Yes, many software engineering teams at PG&E operate under hybrid work models, combining remote work days with scheduled collaborative days at key office locations, such as Oakland, San Ramon, or Sacramento. Specific arrangements depend on the team and project requirements.
Pacific Gas and Electric Software Engineer candidate reports ↗What topics does Pacific Gas and Electric test in interviews?
Pacific Gas and Electric interviews most often cover Behavioral Interviewing, Communication Skills, Panel Interviewing, Data Analysis, and Data-Driven Decision Making. The exact emphasis depends on the specific role you apply for.
Pacific Gas and Electric Software Engineer candidate reports ↗Sources & methodology 3 sources ↗
No official company page is cited. Rounds and questions come from candidate reports and PracHub editorial material; each source shows the date it was read.
- 01Pacific Gas and Electric Software Engineer candidate reports ↗
Company-reported rounds, questions and FAQ.
Candidate reports · Accessed 2026-09-22 - 02PracHub Software Engineer practice ↗
PracHub practice material, not company-reported.
PracHub page · Accessed 2026-09-22 - 03PracHub preparation framework ↗
PracHub preparation guidance.
PracHub page · Accessed 2026-09-22
Explore related engineering environments and compare the preparation focus.
Cognition Software Engineer Interview Guide
What Cognition asks Software Engineer candidates, from reported rounds and questions.
Vercel Software Engineer Interview Guide
Debugging practice for Vercel software engineer prep built on a reproduction you trust, narrowing to the smallest failing input, and changing one variable per run so the result stays attributable.
Together Ai Software Engineer Interview Guide
Failure-handling practice for Together Ai software engineer candidates: requests whose outcome a timeout leaves unknown, where a retry is safe, and deduplicating at the receiver instead of assuming exactly-once delivery.
Spotify Software Engineer Interview Guide
Timed practice for Spotify software engineer candidates who lose time to the clock: short problems taken end to end, then reviewed against a written rubric rather than a passing test run.