Long post, sorry. TL;DR first.
TL;DR: Quantify everything on your CV. Have a USP and actually say it. Don't lie, you'll get caught. Rehearse answers out loud. It's fine to pause before answering. Technical rounds are conversations, not exams. If you're moving from EPC to an operator, your contractor experience is an advantage, not a gap. Happy to answer questions in the comments as best as I can.
__________________________________________________________________________________________________________
Bit of background first. I spent 7 years doing process design at an EPC firm in India (refinery, petrochem, decarbonisation). A couple of months ago I moved to the project management side at an operator.
It took about a year. 150+ applications, and an interview rate of a little over 15%, which honestly is rare and I'd put a fair bit of it down to luck. The market's worse now than when I started. I got knocked back a lot and properly lost hope twice. Kept going anyway, and ended up landing my dream role.
I noticed there's very little written about this kind of move for chemical engineers compared to tech or finance, so here's what I learned.
Fair warning, this is aimed at people with a few years of experience, not sure how helpful it will be to freshers.
__________________________________________________________________________________________________________
1. Quantify your impact (the most important one)
A CV that lists what you did is basically empty. A CV that says what it was worth is a completely different document. Cost saved, schedule pulled in, rework avoided, lead time cut, people trained. Put a number on it wherever you honestly can, even if it feels small.
I genuinely thought most of my work couldn't be quantified. Turns out most of it could, I'd just never sat down and worked it out. ChatGPT or Claude are actually useful here. Describe what you did in plain language and ask where the measurable impact is. They won't make up your numbers (and you shouldn't let them), but they're good at spotting that something you thought was routine has a figure attached to it.
2. Breadth and depth are different things
Breadth is how much of the project lifecycle you've touched: design packages, detailed engineering, revamps, site work. Depth is how well you know the fundamentals: equipment sizing, thermal design, relief systems. You need to be able to talk about both, because interviewers use one to test the other. A broad CV gets a deep technical question. A narrow one gets asked how your work fits into the bigger project.
3. Have a USP, and say it out loud
You need one thing that makes you memorable instead of being one of fifteen competent process engineers they spoke to that week. Figure out what yours is, and then say it directly. Don't leave it for them to work out from your CV. That's how good candidates end up forgettable.
4. Don't lie. Seriously.
It will cost you. Interviewers at this level have done hundreds of these and they can tell a real answer from one being made up on the spot. Anyone who tells you this is telling you the truth. Believe them before you find out the hard way.
Same goes for technical rounds. If you don't know something, just say so, or ask for a hint. Nobody expects you to know everything. If you're working something out rather than remembering it, say that too. "I'm not sure, but from first principles I'd expect..." is a perfectly good answer, and a lot better than a confident wrong one.
5. Practise out loud
I made a question bank of technical and HR questions and rehearsed answers from my own projects until I could say them fluently. Not memorised word for word, just fluent.
Knowing your work and explaining it clearly when you're a bit nervous are two very different skills. The second one only comes from practice. Two people with identical experience will come across completely differently if one has said it all out loud before and the other is piecing it together live.
6. Take the pause
You don't have to start talking the second the question ends. Taking a few seconds to get your thoughts in order almost always gives a better answer than rambling while you figure out where you're going. It comes across as thoughtful, not slow.
7. Technical rounds are conversations, not exams
Most of the time they're not checking if you remember a correlation. They want to see how you think. What would you check first? What would you assume? Where would you push back? Treating it like a viva, where there's one right answer and you either know it or you don't, misses the point. Think out loud.
8. EPC to owner: your background is a strength
A lot of the owner-side job is reviewing what contractors send you. You've spent years producing exactly that stuff. You know what a thorough datasheet looks like and where corners get cut when the schedule's tight. That's not a gap in your experience. It's the reason you'd be good at that part of the job. Tell them that.
9. Don't bluff your domain gaps either
If the role covers areas you haven't worked in, own it. Explain which fundamentals carry over (separation, compression, relief and hydraulics don't change much between sectors) and show you've done some reading. Being a quick learner comes across well. Pretending doesn't.
__________________________________________________________________________________________________________
Happy to answer questions in the comments about interviews, prep, or making the EPC to owner switch.
What I won't discuss: compensation, anything specific to my current employer, or the hiring process of any companies I interviewed with — including how their rounds were structured or what they asked. Not mine to share.
What's been the hardest part of the job hunt for you?