Senior · Oil & Gas

Reservoir Engineer interview questions

Common interview questions and sample answers for Reservoir Engineer roles in Oil & Gas across Oman and the GCC.

The 10 questions below are compiled from interviews our consultants have run with Oil & Gas employers across Oman and the wider GCC. Each comes with a sample answer and what the interviewer is really listening for.

Category

Opening & warm-up

How interviewers test your communication and preparation right from the start.

Walk me through your reservoir engineering career.

Sample answer

I've been a reservoir engineer for eleven years, the last six in Oman. Started at an Indian E&P operator on conventional sandstone reservoirs, then moved to Petroleum Development Oman (PDO) where I've worked on three major fields: a mature waterflood field in north Oman, a heavy oil thermal recovery development in the south, and most recently EOR optimisation on a tight carbonate. I hold a master's in petroleum engineering and SPE membership. I'm comfortable in static and dynamic modelling, history matching, EOR screening, and increasingly the integration of data science with traditional reservoir engineering.

What they're really listening for

Specific field types worked on, technical depth, and professional credentials.

Category

Behavioural (STAR)

Past-experience questions. Use the STAR framework: Situation, Task, Action, Result.

Tell me about a complex reservoir study you led.

Sample answer

Last year I led the EOR screening study for the tight carbonate field. The decision was whether to pilot chemical EOR (polymer flood) or stick with waterflood. Took six months. Steps: built a sector model in CMG Stars, calibrated against pilot-pattern data, ran sensitivity on polymer concentration, slug size, and injection strategy. Also ran economics with three oil-price scenarios. The recommendation: polymer pilot ahead of full-field expansion, with go/no-go gates after each phase to control investment risk. Senior management adopted the staged approach. Pilot is currently running. The lesson: complex technical recommendations need to come with phased commercial decision points; otherwise they get rejected.

What they're really listening for

Technical depth combined with commercial sensitivity.

Describe a disagreement with a senior colleague or contractor on a technical matter.

Sample answer

On the heavy oil project I disagreed with our consultants on the recovery factor estimate. They were projecting 35% under thermal recovery; my analysis suggested 28-30% was more realistic given the heterogeneity I'd observed in the static model. I prepared a detailed counter-analysis: alternative interpretation of the seismic, statistical analysis of analogue fields globally, and uncertainty quantification on my own model. Presented it to the asset team. The senior reservoir engineer initially defended the consultants' number; I held my ground, citing specific evidence. After two more workshops we agreed on a range of 28-33% with proper uncertainty bands. The lesson: technical confidence requires evidence; conviction without data is just an opinion.

What they're really listening for

Confidence to challenge with evidence, plus the maturity to land at a defensible compromise.

Tell me about a time your model predictions did not match production reality.

Sample answer

Two years ago my model predicted 12% production decline in year one of a new waterflood; actual was 18%. Honest discrepancy. I went back to the model: history match showed I'd over-estimated reservoir continuity between injector and producer wells. The reality was more compartmentalised than the static model suggested. I retuned the geomodel using the actual production data as constraint, re-ran the forecast, and updated the field-development plan. The revised plan included more infill wells than originally proposed to drain the compartments. Painful to deliver but better than continuing with a wrong model. The lesson: model results are hypotheses, not facts, until production confirms them.

What they're really listening for

Intellectual honesty and willingness to update beliefs when reality conflicts.

Category

Technical & role-specific

Questions that test your specific skills for this role.

How do you approach a history-matching exercise?

Sample answer

Start with the static model: are the structural framework, reservoir property distributions, and rock-fluid properties as good as the data supports? History matching can't fix a bad geomodel. Then dynamic: I match in stages. Pressure data first (RFT/MDT, then static pressures at wells), then water cut and GOR trends, then individual well rates. I'd rather match aggregate field behaviour well than over-tune individual wells. Use assisted history matching tools (CMG-CMOST or similar) for sensitivity, but I always validate the matching parameters are physically meaningful, not just mathematical. Beware of over-matching; a model that fits perfectly today is often wrong for the future because it's over-constrained.

What they're really listening for

Methodology rooted in physics, not just curve-fitting.

Walk me through how you would screen a field for EOR potential.

Sample answer

Multi-stage process. First, screening using analogue databases (SPE EOR screening criteria): reservoir depth, temperature, pressure, fluid properties, rock characteristics. This narrows to feasible EOR methods. Second, laboratory work: core flooding for the candidate EOR methods, fluid PVT analysis, rock-fluid compatibility tests. Third, simulation: build a sector model and run pilot-scale forecasts for each viable method. Fourth, economics: each method has different capex, opex, and chemical cost profiles. Recommend the method that combines technical feasibility with commercial robustness across oil-price scenarios. Pilot ahead of full-field expansion; learn before committing capital.

What they're really listening for

A complete, multi-disciplinary process showing real EOR experience.

How do you incorporate uncertainty into your reservoir studies?

Sample answer

I use Monte Carlo and scenario-based approaches. For static models: build multiple realisations of the geomodel using different stochastic seeds; sensitivity on key parameters (porosity, permeability, structural framework). For dynamic: run the simulation across the realisations and across price decks. Output is a P10-P50-P90 range, not a single number. Critical when communicating to management: never present a single forecast number without uncertainty; senior leaders make better decisions when they see the range. I also clearly mark which parameters drive most of the uncertainty so we know where to invest in data acquisition.

What they're really listening for

Probabilistic thinking, not deterministic single-answer culture.

Category

Situational

Hypothetical scenarios designed to test your judgement and approach.

Production drops sharply on a key well. What is your investigation?

Sample answer

First: confirm the drop is real, not a metering issue or shut-in for maintenance. Then segment causes: reservoir, completion, or surface. Reservoir: check water cut and GOR trends, pressure if available; sharp pressure drop suggests reservoir depletion in that compartment. Completion: check for sand production, scale, or wax buildup; production logs if available. Surface: choke setting, flowline integrity, separator pressure. From there the diagnosis informs the intervention: workover, stimulation, artificial lift change, or reservoir-level (infill drilling, water injection adjustment). Throughout, document the hypothesis and the test; don't just throw interventions at the well.

What they're really listening for

Structured diagnosis showing the integration of subsurface, completion, and surface thinking.

Category

Cultural fit & motivation

Why this role, why this company, and how you work with others.

How do you work with the geoscience team to align on a reservoir interpretation?

Sample answer

Multi-disciplinary collaboration is essential. I try to integrate early; once a study is in flight, geo-disagreements are expensive. We run joint workshops at the start to align on the structural framework, the rock-property model, and the fluid model. I respect the geoscientist's interpretation of the geology; they respect my translation into flow units. When we disagree, we go back to the data: well logs, cores, seismic. Healthy disagreement is part of good subsurface work; the answer is rarely 'one of us is right'; it's usually 'we need more data'. Building those relationships is as important as the technical work itself.

What they're really listening for

Maturity around the geo-engineering interface, where many subsurface studies fail.

Category

Closing

The final stretch. Often where deals are won or lost.

What are your salary expectations?

Sample answer

For a senior reservoir engineer role in Oman with major operator experience I'd target OMR 2,500 to 3,200 total package depending on the bonus structure, housing allowance, and asset criticality. Reservoir roles on flagship fields typically carry a premium. I'd want to understand the field portfolio I'd cover and the technical authority level. I'm on 90 days' notice from my current employer. Beyond pay I'd value the technical complexity; my career is built on the studies I've led, and a routine maintenance asset role at higher pay is not as valuable as a complex EOR pilot at lower pay.

What they're really listening for

Researched range, asset-aware thinking, and career-led prioritisation.

Practise these with AI

Get 5 fresh questions tailored to Reservoir Engineer, type your answers, and get per-answer feedback from AI. Free, 10 minutes.

Start AI mock interview

Install Talent Arabia

Get instant access to jobs and career tools on your device.