Planning Engineer

Planning Engineer Jobs at Tarrad – Job Overview

Tarrad Development is recruiting a Planning Engineer for ongoing and upcoming high-rise building projects in Dubai, UAE. For applicants exploring Planning Engineer UAE Jobs, this vacancy sits within the construction sector. The notice lists the address as Suite 28, U Bora Tower, Business Bay, Dubai. The advertised profile combines high-rise construction experience with technical knowledge, project execution capability, and familiarity with UAE construction standards.

Job description

On high-rise projects, planning engineers normally turn construction scope into a linked programme of work. The following workflow describes general planning practice, rather than employer-specific duties. First, the engineer reviews drawings, contract milestones, quantities, and the proposed building sequence. These inputs show what must finish before another activity can start. For example, floor layouts help separate structural work from later finishing activities. The engineer also checks which dates reflect firm commitments and which remain estimates. If information is missing, the programme should show that uncertainty clearly. In turn, this prevents an early assumption from becoming an unexplained promise to the project team.

The listing also the engineer builds activity durations around quantities, likely output, and available work areas. A floor cycle means the repeated sequence needed to construct each floor. However, repeating floors do not always take the same time to complete. Changes in layout, access, or structural details can affect the sequence. The engineer checks these differences before copying durations across the tower. Links between activities must reflect physical limits, not simply produce an attractive finish date. Once the team agrees the logic, an approved baseline provides the reference for later comparisons. That baseline preserves the original plan while progress updates show changes.

Checks and exception handling

During progress updates, the engineer compares site evidence with the reporting date. Installed quantities, completed work areas, and inspection records help support progress figures. A percentage alone may hide work that cannot yet support the next trade. Therefore, the engineer separates physical completion from any remaining approval or access constraint. Actual start and finish dates should match evidence from the people overseeing the work. If reports disagree, the engineer checks the difference with the relevant site lead. The update then uses a consistent reporting date for all activities. As a result, this makes comparisons useful and avoids mixing recent progress with older information.

Consider a general example where a tower's passenger lift delivery moves beyond its planned date. First, the planning engineer checks the supplier's revised date and the remaining installation sequence. The engineer then tests whether testing and final handover depend on that delivery. The critical path identifies linked activities that directly control the project finish date. If the delay reaches that path, the engineer compares practical recovery options with construction leads. Moving unrelated finishing work forward may help resource use without recovering the completion date. Therefore, the report should distinguish useful resequencing from genuine time recovery. The project manager needs the likely effect, available choices, and a clear decision date.

Coordination and completion

After reviewing the wider programme, the engineer helps teams understand the next workable activities. A short-term look-ahead draws near-term tasks from the main schedule. However, a planned start is useful only when the work area is ready. The engineer checks constraints such as outstanding drawings, material approvals, and access with responsible colleagues. Each unresolved item needs an owner and a date for action. Procurement staff need required delivery dates, while site leads need realistic work fronts. When teams propose changes, the engineer checks their effect on connected trades. This keeps local decisions from creating hidden delays elsewhere in the building.

The same notice progress reporting should explain why the forecast changed, not just display new dates. The engineer compares the current finish forecast with the baseline and records the main causes. Where quantities support the comparison, planned and actual output can show whether production is improving. However, the report should separate measured facts from assumptions about future output. Clear records also help the team trace changes to instructions or revised information. As completion approaches, the programme needs time for inspections, testing, and outstanding work. The final planning record should explain the actual sequence and unresolved items. That information supports an orderly handover.

Planning Engineer Jobs at Tarrad – Typical Duties & Responsibilities

• Break down project scope into manageable work packages, with clear boundaries that prevent missing or duplicated activities.
• Check subcontractor programme submissions for scope coverage and flag gaps before combining them with the main programme.
• Prepare resource forecasts that show changes in labour demand and help teams identify peaks needing discussion.
• Maintain a programme revision register so colleagues can identify the latest issue and trace earlier versions.
• Review activity coding so reports group floors, zones, and work types consistently across programme updates.
• Prepare progress charts with clear units and reporting periods so readers can compare like-for-like measures.
• Record planning meeting decisions and action owners, then check whether agreed follow-up items remain outstanding.
• Check proposed schedule changes against contractual milestones and highlight deviations for the project manager's review.

Candidate Profile

Applicants can prepare a truthful example of correcting an overstated progress figure in a previous building programme. Explain the evidence you checked, the correction you made, and how it changed the forecast. If sharing work samples, remove confidential project and client details first. Also, make your own contribution clear rather than claiming the whole team's work. Before accepting an offer, ask about reporting lines, planning software, project allocation, and site attendance. Confirm the work arrangement and expected joining date with the employer. These preparation suggestions are general guidance, not additional advertised requirements.

Qualifications & Requirements

• Experience: Other Positions: Minimum 5 years of relevant UAE experience.
• High-rise building construction experience is mandatory for ALL positions.
• Strong technical knowledge, project execution capabilities, and familiarity with UAE construction standards and regulations.
• Excellent communication, coordination, and problem-solving skills.
• Preference will be given to candidates who are available to join immediately or within a short notice period.

Employer-stated Skills & Competencies

• Strong technical knowledge
• Project execution capabilities
• Familiarity with UAE construction standards and regulations
• Excellent communication, coordination, and problem-solving skills
• Strong technical knowledge, project execution capabilities, and familiarity with UAE construction standards and regulations.
• Excellent communication, coordination, and problem-solving skills.

How to Apply

Apply Now: career@tarrad.ae Interested candidates are requested to send their updated CVs, clearly mentioning the position applied for in the email subject line.

About Tarrad Development

Tarrad Development operates in luxury real estate. Its portfolio includes Mackerel Tower and the Celesto series.