Project Engineer Job Description
Define engineering discipline, project phase, authority, site travel, contract interfaces, standards, and professional requirements.
Candidate-facing template
Edit the description for your organisation
Replace bracketed details, remove anything that is not genuinely required, and obtain the appropriate internal approval before advertising.
Ready-to-edit job description
Copying excludes all recruiter notes below.
Project Engineer
- Location
- [Location or working arrangement]
- Employment type
- [Full-time, fixed-term, or contract]
- Reports to
- [Engineering Manager or Project Manager]
About the role
[Company name] is hiring a Project Engineer for [project and discipline]. You will coordinate technical requirements and interfaces, review supplier and design information, resolve site questions, maintain engineering records, and support testing, commissioning, and hand-over.
What you will be responsible for
- Maintain requirements, deliverables, interfaces, technical queries, reviews, actions, and design-change records.
- Coordinate designers, suppliers, construction, operations, quality, safety, commercial, and client stakeholders.
- Prepare or review specifications, calculations, drawings, test plans, inspections, commissioning, and hand-over evidence within authority.
What success looks like
- Technical interfaces and decisions have owners, evidence, dates, and controlled baselines.
- Installed work and hand-over records match approved requirements and verification.
Essential qualifications
- Engineering project experience in a relevant discipline, sector, and delivery phase.
- Strong requirements, interface, document, supplier, site, test, and stakeholder skills.
- Ability to recognise design, safety, quality, commercial, and programme issues requiring escalation.
Preferred qualifications
- Relevant engineering degree, apprenticeship, charter, licence, or registration where required.
- Experience with [contract, standard, asset, project controls, BIM, commissioning, or supplier model].
Tools and working knowledge
- Engineering document, requirements, and change systems
- CAD or model review, field, quality, test, and commissioning platforms
- Programme, issue, cost, collaboration, and reporting tools
Compensation: [Add approved range or rate, currency, project duration, travel, site, overtime, professional support, and benefits.]
[Company name] will discuss reasonable adjustments for site work, travel, document review, assessment, and work.
How to apply
Apply through [method] with a technical interface or delivery problem showing your contribution and verification.
Performance expectations
What good performance looks like
Use these outcomes to replace vague activity lists with the evidence the hiring manager expects to see after the person joins.
Engineering actions close with approved evidence rather than email agreement alone.
Design, procurement, construction, and commissioning work from the same current technical baseline.
Hiring-manager intake
Questions to settle before advertising
Record specific answers so sourcing, screening, and interview decisions use the same definition of the role.
- 1
Which discipline, project, phase, contract, sites, standards, deliverables, and interfaces apply?
- 2
What design, review, instruction, supplier, inspection, test, and commissioning authority is delegated?
- 3
What travel, rotation, site hours, overtime, and local credentials are required?
Evaluation criteria
Evidence to use in a Project Engineer scorecard
Agree the criteria before interviews begin, then score examples against the same evidence standard.
Structured interview
Project Engineer interview questions and strong signals
Ask the same core questions in the same order, then use follow-ups to understand the candidate’s individual contribution.
Tell me about a technical interface nobody initially owned.
Strong answer signal
Defines the boundary, gathers evidence, assigns authority, coordinates solution, and verifies it.
Describe a site query that required a design change.
Strong answer signal
Shows containment, review, approvals, affected records, implementation, inspection, and hand-over.
Related titles
Check the scope behind the title
Common hiring mistakes
Problems to remove before publishing
Using Project Engineer as generic coordination without naming the engineering discipline.
Making the role accountable for programme and cost without delegated authority.
Continue the hiring workflow
Related roles and recruiter resources
Related job descriptions
Helpful recruiter resources
Source and review notes
How this template was prepared
- Language
- International English
- Prepared by
- ATZ CRM Editorial Team
- Review
- ATZ CRM Recruitment Editorial Review
- Last reviewed
- 2026-08-05
O*NET: Engineers, All Other
Reference for occupation tasks, knowledge, skills, abilities, and work activities.
ESCO: occupations and skills
Reference for internationally recognised occupation and skills terminology.
Qualifications, compensation, licences, working conditions, and equal-opportunity wording must be checked for the role and location before use.
Recruiter questions
Project Engineer job description FAQs
What should a Project Engineer job description include?
State discipline, project, phase, contract, standards, authority, suppliers, site, testing, travel, systems, and credentials.
How is a Project Engineer different from a Project Manager?
Project Engineers coordinate technical scope and evidence. Project Managers usually own the wider programme, budget, risk, contract, and stakeholder plan.
