Planning Engineer interview questions
Common interview questions and sample answers for Planning Engineer roles in Construction & Engineering across Oman and the GCC.
The 10 questions below are compiled from interviews our consultants have run with Construction & Engineering 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 planning engineering background.
I've been a planning engineer for nine years, five in Oman. Started in road and infrastructure planning in India, moved to commercial buildings, and for the past three years I've been senior planning engineer on a major infrastructure programme in Oman (water and wastewater). I'm proficient in Primavera P6, MS Project, and Asta Powerproject. My work covers baseline scheduling, progress tracking, EOT and acceleration claims, and resource planning. I've testified as a planning expert in one formal dispute resolution.
Tool depth, project types, and ideally claims/dispute experience.
Category
Behavioural (STAR)
Past-experience questions. Use the STAR framework: Situation, Task, Action, Result.
Describe a complex schedule you developed.
Last year I developed the baseline schedule for a 110M OMR water infrastructure project: 28-month duration, 12 contract zones, multiple interfaces with existing services. About 4,800 activities in P6. I structured the WBS by zone and by trade within each zone, with proper logic links honouring both physical sequence and resource constraints. The critical path went through three key zones because of geotechnical complexity. I delivered the baseline ahead of schedule and the consultant approved with minimal comments because the logic was defensible. That baseline has held as the project's reference throughout.
Scale, structure, and the discipline of building a defensible baseline.
Tell me about a successful EOT claim you prepared.
On a previous project we encountered unforeseen rock conditions that delayed excavation by 11 weeks across multiple zones. I prepared the EOT claim using forensic delay analysis: time-impact analysis methodology, with contemporaneous evidence (daily site reports, geotechnical reports, photo records of the rock conditions). Demonstrated through windows analysis that the delay was non-concurrent and on the critical path. We claimed 11 weeks; client granted 9 with proper justification for the 2-week reduction. Outcome was reasonable on both sides. The key was thorough documentation kept throughout, not built up after the fact.
Forensic claims discipline and the importance of contemporaneous records.
Describe a time you challenged the contractor or project manager on schedule logic.
On the water project the contractor's recovery plan showed they'd accelerate by adding crew on two specific activities. I disagreed; those activities weren't on the critical path so adding crew wouldn't help the end date. I prepared a clear analysis showing the actual critical path went through different activities. The contractor's planner resisted initially; he'd done the analysis quickly. I shared my workings; he checked and agreed. Recovery plan revised to focus crew on the right activities. Saved both sides from a misallocation of resources. Planners need conviction to push back on senior contractor staff when the analysis warrants.
Technical confidence and willingness to defend correct analysis under pushback.
Category
Technical & role-specific
Questions that test your specific skills for this role.
How do you structure a project baseline schedule?
Start with the contract programme requirements and the project scope. Build the WBS hierarchy first; usually by zone or trade depending on project type. Activities at the right granularity: not so fine that they're noise, not so coarse that progress is hard to measure. Logic links honoring physical, contractual, and resource sequences. Calendar with proper non-working days (weekends, public holidays, Ramadan working hours). Resource loading where the contract demands it. Verify the critical path is sensible; if the critical path goes through something trivial, the logic has gaps. Get client and consultant sign-off before going live with the baseline.
Methodology, not just listing P6 features.
Walk me through how you track and report progress.
Weekly cycle. Friday: collect actual progress from each work zone (percentage complete by activity, actual start/finish dates). Saturday: update the schedule and run the P6 calculation. Sunday morning: review variances against baseline, identify trends, flag risks. Sunday afternoon: produce the progress report with key indicators (SPI, CPI if cost is loaded, critical-path variance, forecast completion date). Monday: present to project leadership and the contractor. The report is one page summary plus appendix; nobody reads a 30-page progress report.
Operational discipline and concise communication.
How do you analyse delay and prepare recovery plans?
First, quantify the delay: how many days behind the baseline, on which activities, and is it on the critical path? Then root cause: weather, materials, design changes, contractor performance, or client decisions. Each category has different remedies. Recovery options: re-sequencing (changing the order of remaining work to compress), parallel-tracking (running activities concurrently that were planned sequentially), acceleration (adding resources to compress duration), or scope deferral (moving non-critical scope out). I model each option in P6 and compare cost and risk. Recommend the option with best risk-adjusted outcome.
Structured recovery thinking, not just adding more workers.
Category
Situational
Hypothetical scenarios designed to test your judgement and approach.
The contractor refuses to update their schedule on schedule. What do you do?
First, understand why. Are they short-staffed in planning, or are they hiding bad progress? Polite but firm reminder via email with copies to the project manager. If it continues, formal correspondence citing the contract's planning obligations. If still no progress, I'd reconstruct the schedule independently using site reports, daily logs, and physical observation, and use that as my reference. The contractor's resistance becomes a documented pattern that can later support claims or disputes. Planning isn't optional under most contracts; I make that clear without being adversarial.
Calm escalation and contract-discipline awareness.
Category
Cultural fit & motivation
Why this role, why this company, and how you work with others.
How do you handle pressure from senior leadership to show better schedule status than reality?
I don't falsify. The schedule reflects reality; my job is to make reality clear, not to make it look better than it is. If senior leadership presses, I'll show them the same data structured differently so they can see what's going well and what isn't, but I won't change the underlying numbers. If they don't like the message, they need to act on the project, not the report. I've had this conversation a few times; usually leaders appreciate the honesty once they realise the alternative is being blindsided later when truth surfaces.
Professional integrity and the courage to defend reality.
Category
Closing
The final stretch. Often where deals are won or lost.
What are your salary expectations?
For a senior planning engineer role on a major infrastructure project in Oman I'd target OMR 1,500 to 1,900 total package depending on the project size and the seniority within the planning team. Lead planning roles on flagship projects (oil and gas, major rail or road) pay more. I'm on 60 days' notice. Beyond pay I care about the project complexity; planning a routine villa job at 1,800 OMR isn't as good for my career as planning a flagship infrastructure project at 1,500.
Researched range and project-quality awareness.
Related roles
Other Construction & Engineering roles
Practise these with AI
Get 5 fresh questions tailored to Planning Engineer, type your answers, and get per-answer feedback from AI. Free, 10 minutes.
Start AI mock interview