Most STAR examples online are written for a software interview. If you are preparing for a refinery operator, board operator, board operator trainee (BOT), process technician, or turnaround role, the questions still start with “tell me about a time,” but the stories that score are about a procedure you held, an abnormal condition you did not guess through, and a handoff you would not skip. Candidates getting ready for those rounds, including refinery operator and BOT interviews at places like Valero Corpus Christi, keep asking how to put plant work into STAR without turning it into a tech answer. Public write-ups of those panels keep landing on the same subjects: a procedure versus a shortcut, a disagreement with a coworker or a supervisor, and an unforeseen condition you did not ride out. This guide is that version: why these interviews still ask for behavior, what candidates actually report being asked, 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. If the framework itself is new, read our complete STAR method guide first, then come back.
STAR is the same four parts in a refinery interview as anywhere else: one specific incident, what you were responsible for, what you personally did, and a result you can point to. For oil and gas operations roles, build a few strong stories around a safety stop when someone wants the step skipped, an unforeseen condition you named and escalated, and a shift or turnaround handoff the next person could not have guessed. Rehearse each one out loud to about two minutes, with the option you rejected and the person you told still in the story. Use a number only when you can point to it. 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 refinery or oil-and-gas operations interview is not a classic tech loop, and it is not an Amazon-style leadership round. You should not prepare as if it were. The plant knowledge (the unit, the board, the permit, the procedure you actually run) 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, sit a board, or walk down a job in the room.
Those questions are looking for evidence of future behavior. Will you hold a step when the rate says keep going? Will you call an abnormal condition what it is, and escalate, before you ride it? Can you hand a job to the next crew or to maintenance so the isolation, the permit, and the condition of the equipment are still true when they start? A polished line about safety does not answer any of those. A specific shift does.
The nouns change with the seat. A board operator, an outside operator, a process technician, and someone in the middle of a turnaround are not telling the same shift. They are answering the same kind of question. If the role is a control room or a field job outside refining (a utility, a grid desk, a plant that is not a refinery), the procedure-hold shape in our STAR guide for ops, utility, and grid interviews is the closer cousin. Swap the feeder for the unit. Keep the hold.
A hold you would sign
The story they want is usually the time you slowed the unit down or stopped a step, not the time you kept it online. Running past an open check is not a result you recover in the next investigation.
The procedure is the action
Interviewers in these roles listen for the step you held, who you called, and what you had them repeat back. "I follow procedure" is a topic. The permit line, the alarm you did not silence, and the order of the calls are the answer.
Something the next shift can use
A unit left in the state the procedure allows, a turnover that names the open isolation, a log note the oncoming board can find. "We got it back to normal" gives the interviewer nothing to write down.
This is a preparation map from public sources, not a leaked question bank. Valero's careers page says many of its interview questions are behavioral and tells applicants to bring past examples. Glassdoor write-ups for Valero operator interviews describe a panel and answers in the STAR shape; reports name human resources with a production supervisor and a manager. A community-posted outline for Benicia refinery operator-trainee hiring names the STAR method for the in-person interview, after an online risk assessment and a resume review. On r/oilandgasworkers, people who reached a Valero operator or BOT interview, including a 2023 Corpus Christi operator-trainee thread and a later Corpus Christi process-operator thread, describe the same round: STAR, safety, teamwork, and judgment on a rotating shift. Several of those threads also describe an online assessment and a mechanical or aptitude step before anyone sits down. That sequence is site-specific. Ask the recruiter what is still in front of you.
Phillips 66 process-operator write-ups on Glassdoor add a question that shows up across refiners: what you do when the job can be finished in a way that breaks procedure, and a disagreement with a coworker or a boss. Those are not a Valero transcript. They are the same judgment a refinery panel is scoring. None of the lines below is a quote from a particular interview. They are the subjects those reports keep naming.
What the operator seat actually is
Glassdoor operator reports include a plain question about your understanding of the role. Answer with the shift you would be responsible for (the board, the field, the permit), not a speech about the company.
A procedure you held when a shortcut was available
Candidates describe safety scenarios and “do it by the book when a shortcut is tempting.” The paired shape, from refiner process-operator write-ups, is: the job can be done a way that violates procedure. What do you do?
A disagreement with a coworker or a supervisor
A 2023 Corpus Christi operator-trainee thread names conflict with a coworker, a time your plan differed from your boss’s, and an idea you had to introduce. The story they can score is the call you made, not who was difficult.
An unforeseen condition, or a mistake you caught
The same threads point at unforeseen circumstances, catching a mistake before it becomes the incident, and staying calm without riding an abnormal condition. A guessed cause is not the answer. The check and the escalation are.
The next crew on a rotating shift
Operator and BOT reports talk about the team and the rotation. Public descriptions of process-operator work name the handover, the permit, and lockout before maintenance starts, including a turnaround window. The interview version is what the next person received from you.
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 the refinery. 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 unit or the job, and the thing that was wrong. Skip the history of the plant. If the listener cannot picture the open step, the abnormal condition, or the handoff in front of you, 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 rate" is often the pressure, not the task. The task is the thing you were accountable for if the step was skipped or the condition was misread.
What you did, in order, in the first person.
Include the option you did not take and why. Holding the step, refusing to silence an alarm that the procedure says to answer, escalating with what you know and what you do not, walking the next crew through an isolation that is not finished. Those are actions an interviewer can score. "We communicated" is not.
What the next person could verify, and what you kept.
The unit left in the state the procedure allows, a turnover that names the open condition, a log note the oncoming board can find. If you do not have a rate, a duration, or a count you can defend from a log, a permit, or a shift report, say the outcome in words 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 refinery, company, unit, or interview. They follow the themes candidates actually describe: a procedure held when a shortcut or a supervisor's plan pointed the other way, an unforeseen condition you did not explain away, and a handoff the next crew or a turnaround job could not have guessed. Swap the nouns for the unit you actually operate. Where a sketch would be tempted to quote a rate, a yield, a downtime, or a timeline, it leaves a blank on purpose: in the room, use a figure you can point to, written here as [your number], or leave the number out.
“I have a strong safety background from my last job and I always follow procedure. One time we were behind and I found a way to keep the unit online. We worked as a team, nobody got hurt, and we didn't miss any production.”
That is the failure mode these panels are screening for. It is a resume tour plus a shortcut that “saved the rate,” which is the opposite of the procedure-versus-shortcut question candidates report. There is no open step, no person you told, and no result the next shift could check. 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 the refiner version candidates and Glassdoor write-ups describe: the job can be finished a way that breaks procedure, or your plan is not the one your supervisor wants. Interviewers use it for safety, for procedure adherence, and for disagreement. One story can serve all three if you know which part to lead with.
You are on the board, or you are the outside operator the board is waiting on. The unit is supposed to stay online. A step the procedure requires before the next move (a sample, a verification, an isolation check) is not done. A supervisor or the lead who owns the rate has already said the step can wait, or a coworker has lined up the shortcut. The unit is not in alarm. The step is still required.
Decide whether this step can be skipped. Keeping the rate is the pressure. It is not the task.
You hold the step. You do not “catch it on the next round.” You state what the procedure requires and what is still open: the check, the permit condition, or the device that has not been verified. In your real story, name that step; in this sketch, only the shape of one. You tell the person who owns the rate (the supervisor, the console, or the lead who asked you to proceed) before anyone treats the unit as clear to continue. You write the hold where the next person will see it, not only on the radio. The option you reject is “we are already behind, do the check after we bring it back.” A step done after the move is not the step the procedure required.
The unit stays in the state the procedure allows until the step is done. Production waits. If that wait had a duration you can point to in the log or the shift report, say it as [your number]; otherwise leave the number out. You add the check to the pre-job brief or the turnover so the next crew does not discover the same open step the same way. If you are asked what you would do differently, the honest answer is to catch the open step before the rate conversation starts, not in the middle of it.
The same incident answers “tell me about a time you disagreed with a supervisor” if you lead with the call before anyone continued, and “tell me about a time you followed a procedure when it cost the schedule” if you lead with the hold. The shift does not change. The opening line does. Keeping the unit online by skipping the step is the story that fails this question.
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 something went wrong on the unit,” or the version operator-trainee threads actually name: an unforeseen circumstance, or a mistake you caught before it became the incident. The failure mode is narrating the whole upset, or adopting the explanation already in the room. Pick one condition, one check, one escalation.
An abnormal condition that someone has already explained. A trend that is not the one the procedure calls normal, an alarm that does not clear the way it should, or a field reading that does not match the board. The story in the room is a bad instrument, a transient, or “the last crew already checked that.” You do not yet know which story is true, and the unchecked version is the mistake.
You are not there to invent a cause. You are there to say what you know, what you are still checking, and to get the right person on it before the condition becomes a step you cannot take back.
You separate the symptom from the guess. You do not silence the alarm to make the board quiet, you do not accept “the last crew already checked it” as the check, and you do not keep operating as if the trend were already explained. You run the check the procedure tells you to run first. In your real story, name that point. In this sketch, keep only the shape of one. When that check does not clear it, you escalate in three sentences: what changed, what you have already ruled out, and what you want the next person to do. You tell the supervisor or the lead before you put a more certain story on the radio than you actually have. The option you reject is riding it for another [your number] because the unit is “still on spec.” On spec is not a diagnosis.
The condition is either explained and logged, or it is in someone else's hands with the facts you actually had. You do not claim a recovery you cannot point to. If the unit came back inside a duration you can defend from the log, that duration is [your number]; otherwise the result is the escalation itself and what you wrote down. If your first check was the wrong one, say so. The correction belongs in the Action. Do not decorate the ending with a yield or a loss figure you cannot show.
Spend the Action on the check and the call, not on how calm you stayed. The interviewer already assumes the board was busy. They are scoring whether you distinguished a guess from a condition, and whether the next person received the condition instead of the guess.
The question sounds like: “Tell me about a time you worked with another crew,” which is how operator and BOT reports talk about a rotating shift. The workplace version is a turnover, or maintenance about to start on a permit during a normal day or a turnaround. The hazard is the next person treating the equipment as they find it, when the procedure says a condition has to travel with the job.
You are turning the board over at the end of a rotation, or maintenance is about to start on equipment your crew has been running, including a turnaround window. The oncoming operator or the maintenance lead is ready to take it. Something the procedure says must travel with the job is not in the handoff: an isolation that was started and not finished, a permit condition, a valve lined up for the job and not for normal operation, or a bypass that is still in. If you skip it, they will start from the wrong picture.
Make the handoff true before they start. Do it without turning the other crew into the problem.
You stop at the missing piece. You do not let them “start the safe steps.” You walk the condition with the receiving lead (maintenance, or the oncoming board) and you show them what is still open: the isolation, the permit line, or the device that is not in the state the procedure assumes. You do not treat the turnover as done until they repeat that condition back. You write it in the log or on the permit, so it is not a hallway sentence the next person cannot find. The option you reject is “they know this unit, they will see it.” The thing they would not see is the incident.
The job starts from the real condition, or it waits until the condition matches the permit. Nobody opens equipment the isolation does not cover. On the next turnover you check that line before you hand off the radio, instead of remembering it after they have started. If your real handoff had a count (devices, permits, people who repeated the condition back), that count is [your number], from the record, or it stays out of the story.
Notice the pattern across all three sketches. Each one names a single piece of work, says what you were on the hook for, includes a rejected option, and ends with something the next shift could verify. That is the whole method. The domain vocabulary changes with the unit. 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. A folder of every upset you have ever stood will not. Under pressure you are picking from a short list, not searching an entire career. A thin story collapses on the second question. Our post on building four strong STAR stories, not twenty is the general version of that choice. For this kind of role, the four below are the ones worth the rehearsal time.
Build the list from shifts you can still check: a log, a permit, a shift report, the turnover note where someone repeated a condition back. Write the outcome next to each one in words. If a number exists, copy it from that record. If it does not, do not upgrade the story later into a yield, a downtime, or a process-safety statistic you cannot defend.
Also serves disagreement, procedure over rate, and "tell me about a time you caught an error." Lead with whichever part the question is actually about. The hold stays in the story.
Also serves prioritization and communication under time pressure. The first guess can be wrong. Show the check, then the call, then what you wrote down.
Cross-crew, maintenance, or a turnaround window. Also serves influence without authority. Spend the Action on the repeat-back and the document.
Plant interviews ask this directly. Name the call you would reverse. "I would communicate earlier" is not a decision. "I would have escalated when the first check did not clear it" is.
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 console, the outside operator, the maintenance lead, or the supervisor when you are crediting them. "We" across a whole unit 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 step to protect the rate.
Field, board, supervisor, maintenance, the oncoming crew. The order is the judgment. Have it ready.
State the hazard in operational terms: a step done after the move, an unexplained condition left on the board, equipment opened on an isolation that was not finished. Skip the speech about safety culture.
A rate, a duration, a count of devices or permits. If you cannot point to the log, the permit, or the shift report, take the number out. [your number] is a blank, not a suggestion to invent one.
A line on the turnover, a pre-job check, a log note the next shift can 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, the alarm, or the turnover.
Telling a software story to a plant panel
A sprint, a launch, or a leadership-principle anecdote can be a real accomplishment. It is the wrong evidence for a board, field, process-tech, or turnaround role unless you translate it into a procedure, a condition, and a handoff. Prefer the shift.
Heroics that keep the unit online
Staying late to "make rate," silencing an alarm so the board looks quiet, or skipping a check so the window survives reads as a risk, not as ownership. If the point is urgency, show how you stayed inside the procedure while you moved the step.
Narrating the whole unit as "we"
Credit is good. Vagueness is not. The interviewer needs your hold, your check, your call, and your log entry.
Inventing a metric
A made-up yield, downtime, loss figure, or process-safety statistic falls apart on "how did you know?" Use [your number] from the log, the permit, or the shift report, or describe the outcome without one.
Hiding the hold
A story that only contains the unit back online, with the stop edited out, cannot answer a safety question. The open step is the Situation. The unit left in the allowed state is the Result.
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 “what did the procedure say?” 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 "strong safety culture" is a topic. The interview needs the step you held, the person you called, and what the next shift could verify.
Cut each one to about two minutes
Unrehearsed answers run long because the history of the unit keeps growing. Two minutes forces that out 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 about a shift. Keep the set small and strong: a handful you know cold, not a pile you will not remember. Replace any number the draft smoothed over with one you can point to, or take it out.
More than one bank when the role changes
A board-operator interview and an outside-operator or turnaround 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 handoff 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, what the procedure required, who you told. Run those on your own stories after you listen.
Practice between the shifts you already have
If you are on a rotation, a turnaround, or a board schedule, prep has to fit around it. 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