Most STAR examples online are written for a software interview. If you are preparing for a transmission operator, system operator, control-room, field, or utility operations role, the questions still start with “tell me about a time,” but the stories that score are about safety, procedures, outages, and who you called, not a product launch. This guide is the STAR method for that work: a short reminder of the structure, three sketches you can use as a shape for your own shifts, and how to keep a few strong stories ready instead of a long list of thin ones. If the framework itself is new, read our complete STAR method guide first, then come back.
STAR is the same four parts in an ops interview as anywhere else: one specific incident, what you were responsible for, what you personally did, and a result you can point to. For grid, utility, and control-room roles, build a few strong stories around a safety stop, an outage you coordinated, and a time you got another crew onto the right procedure. Rehearse each one out loud to about two minutes, with the option you rejected and the person you notified still in the story. Star Interview turns your own history into a Story Bank of those answers, and company-specific coach audio is there when you want to hear how a behavioral round actually gets probed.
A transmission-operator or utility interview is not a classic tech loop, and you should not prepare as if it were. Technical knowledge (switching, clearances, restoration, reliability rules, the system you actually operate) is its own part of the process, and this post does not try to teach it. Confirm the format with your recruiter. What this post covers is the other part: the behavioral questions, where the interviewer asks for a past example because they cannot watch you run a shift in the room.
Those questions are looking for evidence of future behavior. Will you stop a job when the paperwork and the equipment disagree? Will you follow the procedure when it costs the schedule? Can you say what you know, what you are still checking, and who you told, in that order? A polished opinion about safety does not answer any of those. A specific shift does.
Safety judgment, not heroics
The story they want is usually the time you slowed down or stopped, not the time you pushed through. Operating the wrong device fast is not a result you can recover in a debrief.
Communication as a sequence
Interviewers in these roles listen for who you called, on what channel, and what you had them repeat back. "I communicated with the team" is a topic. The order of the calls is the answer.
An operational result
Restored, contained, held, or written into the next brief. "It went well" gives the interviewer nothing to write down. A time, a count, or a procedure that changed does.
You already know the letters if you have been told to practice STAR. The useful version is short, spoken, and about one incident, not a tour of how your desk usually runs. Aim for about two minutes, then stop so there is room for follow-ups. For the in-the-room sequence (decode the question, pick the story, open with a headline), see our step-by-step guide to answering behavioral questions.
Where and when, in two or three sentences.
Name the shift, the job, and the thing that was wrong. Skip the history of the station. If the listener cannot picture the mismatch, the clearance, or the outage, you are still in background.
What you were responsible for, in one sentence.
Separate your job from the crew’s job and from the supervisor’s job. "Keep the outage window" is often the pressure, not the task. The task is the thing you were accountable for if it went wrong.
What you did, in order, in the first person.
Include the option you did not take and why. A hold, a readback, a call off the open radio, a number you refused to publish. Those are the actions an interviewer can score. "We handled it" is not.
What changed, and what you kept.
A delay you accepted, a device nobody operated in error, a restore time taken from the crew instead of a guess, a step you added to the next brief. If you do not have a number you can defend, say the operational outcome plainly and do not invent one.
The stories below are composite sketches of the shape of an answer. They are not a script, and they are not an account of a particular utility or a particular interview. The first is shaped like transmission switching, the second like distribution restoration, the third like a procedure change between a desk and a crew. Swap the nouns for the system you actually operate. Every number is a placeholder. In the room, use figures you can defend from a log, a ticket, or a brief, or leave the number out.
“Safety is my top priority. Any time something doesn't look right I speak up, and I'm a big believer in communication. We had an issue on a job once and I made sure everyone was on the same page, and we got it done without anybody getting hurt. Teamwork is really important in this line of work.”
Nothing in that answer is offensive, and none of it can be scored. There is no incident, no decision, and no result. The sketches that follow are the same kind of moment told so an interviewer can write something down.
The question sounds like: “Tell me about a time you stopped work or challenged a plan because it wasn't right.” Interviewers use it for safety, for procedure adherence, and for judgment under schedule pressure. One story can serve all three if you know which part to lead with.
You are the operator on a planned outage. A field crew calls in ready to start switching. The device number on their switching order does not match the clearance you issued or the one-line in front of you. The outage window is already tight, and the crew is on site.
Confirm the clearance covers the equipment they are about to operate before anyone opens a switch. Keeping the window is the pressure. It is not the task.
You tell the crew to hold. You do not let them start the steps that happen to match. You read your device ID and have them read theirs back. Then you compare the switching order, the clearance, and the print: the order lists a breaker in the adjacent bay. You call the person who wrote the order, state the mismatch, and ask for a corrected order rather than a verbal “it's the right one.” You keep the crew held until that order is in hand, then you re-brief the first steps before you release them. The option you reject is starting the matching steps while someone checks the rest, because a partial match is how the wrong device gets operated.
The job starts later than planned. Nobody operates the wrong device. You add a device-ID readback to the pre-job brief for that desk, so the next crew compares IDs out loud before they are standing at the equipment. If you are asked what you would do differently, the honest answer is to catch the mismatch when the order is issued, not when the crew is already on site.
The same incident answers “tell me about a time you disagreed with a supervisor” if you lead with the call for a corrected order, and “tell me about a time you followed procedure when it cost the schedule” if you lead with the hold. The shift does not change. The opening line does.
Save your strongest STAR stories in one place, then practice with a coach for the company you're interviewing at.
Start free practiceThe question sounds like: “Tell me about a time you dealt with an unplanned outage” or “a time you had to prioritize under pressure.” The failure mode is narrating the whole storm. Pick one feeder, one desk, one decision.
A storm evening. A feeder locks out. The first word from the field is that it could be a tree or a pole, and the people answering customer calls want a restore time. You have a customer count from the outage system and no confirmed cause.
You are coordinating, not climbing. You need a sequence a crew can actually run, and a time estimate honest enough that the call center is not inventing one for you.
You separate what is known from what is still being checked: lockout time, customers affected, cause unconfirmed. You refuse a short restore time you cannot support, and you give the call center a next-update time instead. You ask whether critical load is on that feeder and which crew is closest. Critical load is not; a crew can be there inside half an hour. You send them to patrol the section that picks up most of the customers, not the whole feeder, and you tell them to call when they have eyes on the device. When they find a tree on the primary, you set the restore window from their work estimate. You keep the update cadence until the outage is closed.
Customers are back on the crew's actual work window, not on the first guess. You do not close early and cause a second trip. The piece you keep is the update cadence: the call center stops publishing a time you never gave them. If your real outage had a critical customer, lead with how you sequenced that load first. That is a different Action, and it should be yours, not this sketch's.
The question sounds like: “Tell me about a time you had to get another team to change how they were working,” or a communication question that is really about procedure adherence. Control-room and field interviews both ask some version of this, because the hazard is two groups using two versions of the same job.
A revised step (a new way to verify absence of voltage, or an added check before a switching step) went out in a bulletin that morning. The crew you are about to switch with is still on last week's sheet. You hear it when they skip the new step on the radio.
Get this job onto the current procedure before the next step. Do it without turning the open radio into an argument the rest of the shift has to listen to.
You stop the sequence at the missed step. You do not lecture on the open channel. You call the crew lead directly and show them the bulletin line: the step, the date, and the hazard it was added for. You agree they will brief their people before you resume, and you do not resume until they confirm the brief is done. You log who you spoke to and that the job continued on the new step, so the next shift is not relying on memory of a phone call. The option you reject is “they've done this a hundred times, let it go this once.” One skipped step is the incident, not a small exception.
The job finishes on the revised procedure. Nobody is left guessing on the radio. You send the crew lead the bulletin afterward so the change does not live only in your phone call. On the next shift you check the brief before the first switching call, instead of discovering the old sheet in the middle of the job.
Notice the pattern across all three sketches. Each one names a single job, says what you were on the hook for, includes a rejected option, and ends with something that outlasted the shift. That is the whole method. The domain vocabulary changes with the role. The shape does not.
Quality matters more than quantity here. Four to six incidents, each one known well enough to survive follow-up, will cover a behavioral round. Twelve half-remembered shifts will not. Under pressure you are picking from a short list, not searching an entire career. A thin story collapses on the second question.
Build the list from real shifts while you can still see the record: switching logs, outage tickets, briefs, the message where someone confirmed a readback. Write the baseline and the outcome next to each one. If you cannot find a number, write the operational outcome in words and do not upgrade it later into a figure you cannot defend.
Also serves disagreement, procedure over schedule, and "tell me about a time you caught an error." Lead with whichever part the question is actually about.
Also serves prioritization, communication under time pressure, and a time your first estimate was wrong. The wrong estimate is a feature if you show how you corrected it.
Also serves influence without authority and training. Spend the Action on the conversation, not on how important teamwork is.
Ops interviews ask this directly. Name the decision you would reverse. "Communicate more" is not a decision. "I would have checked the order before the crew rolled" is.
That is a Story Bank: a small set of incidents you can retell cleanly, each labeled with the questions it can answer. Our post on the five STAR stories every candidate should prepare is the general version of the same idea. For this kind of role, swap the generic leadership story for the safety stop if you only have room for a few.
The two-minute version is the opening. In a structured interview the follow-ups are where most of the evidence comes from. Prepare the story one level deeper than you tell it.
Say "I" for your own actions. Name the crew lead, the dispatcher, or the supervisor when you are crediting them. "We" across a whole shift makes it impossible to score you.
Know the step you held on. If you deviated, say why, who approved it, and how you documented it. Do not imply you improvised a switching step.
Field, supervisor, neighboring desk, call center. The order is the judgment. Have it ready.
State the hazard in operational terms: wrong device, second trip, a time estimate the call center would have had to walk back. Skip the speech about safety culture.
A brief, a checklist line, a log note the next shift could see. If nothing changed, say so, and say what you would add now.
Answering with a value instead of a shift
"Safety is my priority" and "I always follow procedure" are claims. The question asked for a time. Start with the job.
Telling a tech story to an ops panel
A software outage or a slide deck can be a real accomplishment. It is the wrong evidence for a control-room or field role unless you translate it into the judgment they are hiring. Prefer the shift.
Heroics that skip the procedure
A story about working around a step to save the outage window reads as a risk, not as initiative. If the point is urgency, show how you stayed inside the procedure while you moved faster.
Narrating the whole control room as "we"
Credit is good. Vagueness is not. The interviewer needs your calls, your holds, and your log entries.
Inventing a number
A made-up customer count or a made-up delay falls apart on "how did you know?" Use a figure from the ticket, or describe the outcome without one.
Memorizing the sketch
These examples are a shape. A memorized script sounds memorized, and it breaks the moment someone asks what you personally did. Practice your own incidents out loud until the structure holds without a script.
Writing the story is half of it. The version that gets scored is the one you can say while someone interrupts you. Time each story to about two minutes. Record one and listen once. You will hear a Situation that ran too long, a Result you mumbled, or a stretch of “we” that silent review never catches.
Then have someone break in with “what did you do?” and “who did you call?” Recovering from that interruption is a separate skill from delivering a clean answer. If you want a fuller week-by-week plan around the rehearsal itself, our behavioral interview preparation checklist covers the surrounding schedule. The stories in it should still be yours.
Write four to six incidents, not topics
A line on a resume that says "coordinated storm restoration" is a topic. The interview needs the feeder, the call you refused to make, and how it ended.
Cut each one to about two minutes
Unrehearsed answers run long because the Situation keeps growing. Two minutes forces out the station history and leaves room for the follow-ups, which is where you do your best work.
Practice the structure, not the wording
Know the headline, the rejected option, and the result. Let the sentences change. A script fails the first time the interviewer asks you to back up.
The slow parts are pulling a few real incidents out of your own history and getting enough spoken practice that the structure survives a follow-up. Star Interview is built around those two, so you can prep for the round that decides the offer without starting from a blank page.
A small Story Bank from your own experience
Upload your resume, pick the company you are interviewing with, and your Story Bank comes back as Situation-Task-Action-Result answers built from your history. Edit them until they sound like the way you talk on a shift. Keep the set small and strong: a handful you know cold, not a pile you will not remember.
More than one bank when the role changes
A field-supervisor interview and a desk-operator interview do not want the same lead. You can keep more than one Story Bank for the same employer and put the safety stop first in one and the outage first in the other.
Company-specific coach audio
Podcast-style episodes walk through how behavioral rounds run at specific companies, with worked examples, so you can hear where the follow-ups land before you are in the room. Use the company you are actually interviewing with.
Hear the probing, then ask it of yourself
A two-host conversation pulling an answer apart is a useful model for the questions in the section above: what you did, who you called, what you changed. Run those on your own stories after you listen.
Practice on time you already have
If you are covering shifts, prep has to fit around them. Audio turns a commute into review, and you can pick up where you left off.
Save your strongest STAR stories in one place, then practice with a coach for the company you're interviewing at.
Start free practice