Background
This candidate had spent more than a decade in process control, mostly on the vendor side. They designed control systems, commissioned them and handed them over to the people who would run the plant.
Now they were interviewing to become one of those people: an operator-side process control engineer at an energy producer. The technical depth was not in question.
The challenge
Vendor work and operator work look alike on paper. In the room, they sound different. A vendor designs, commissions and leaves. An operator-side interviewer wants to know how you will keep a live plant safe and running when something goes wrong in the middle of the night.
The first sessions showed two problems. When asked for an example, the candidate reached back to early in their career, to stories from when they were junior. With a decade of senior work behind them, those stories undersold them. They also said "we" where the interviewer needed to hear "I."
The bigger problem was the behavioral questions. The candidate kept stepping around them. Asked about conflict, influence or working with a difficult stakeholder, they drifted back to technical detail.
On the second and third days, it caught up with them. Two sessions in a row scored 2.5 out of 5.
What they did
The coach pointed out something the candidate had not seen. Their vendor years were full of behavioral material. Sitting between a vendor, a project team and a site's operations crew is stakeholder mediation. That was the answer to the questions they had been avoiding.
The next session, they told their stories from that position: the person in the middle, balancing what the project wanted against what operations would accept. The score jumped, and from that session on they never scored below 3.8 again.
They also spread their practice out, usually one session a day with breaks in between. That gave each round of feedback time to settle before the next.
With the structure fixed, the coaching got more specific. The coach asked them to put numbers on reliability improvements, because "improved uptime" is a claim and a figure is evidence. It asked them to map their control-system experience to the platforms the site runs. And it asked them to ground technical disagreements in functional-safety risk, not personal preference.
The results
There was one more wobble. Midway through, a session slipped back from the level they had reached. The coach flagged something subtle: their answers described "educating" operators who resisted a change. It asked them to show how they would de-escalate that resistance instead, and to tighten answers that had started to run long.
The last five sessions were their strongest. Their average coach score went from 3.45 in their first two sessions to 4.7 in their last two. The coach's rating of how confident they sounded rose from 3.25 to 4.8, the largest gain on that measure in these stories.
They didn't tell us how the real interview went, so we won't guess.
What other process control engineers can take from this
Use your most senior examples. Early-career stories can feel easier to tell, but they make you sound junior. Pick the work that matches the role you want.
Treat vendor experience as stakeholder work. Standing between a vendor, a project team and site operations is mediation. Framed that way, it answers the behavioral questions operator-side interviewers ask. The career change interview guide covers this kind of reframing.
Anchor disagreements in safety. In a hazardous-process plant, the strongest reason to push back on a technical decision is functional-safety risk. Leading with it moves the argument away from opinion.
Bring operators along instead of educating them. Operators who resist a control change often have a reason. Describe how you listened and de-escalated. The chemical engineer interview guide covers related plant-operations questions.
If you are moving from the vendor side to the operator side, you can practice those interviews out loud on Revarta and see whether your stories come from the right side of the table.
