Define the equipment, sites and service responsibility

Start with the work the engineer will actually encounter. Servicing hydraulic power units in a controlled production environment is different from diagnosing mobile equipment outdoors or commissioning a bespoke system at a customer site. Explain whether the role is primarily planned maintenance, reactive breakdown response, installation, commissioning or a combination.

  • Typical hydraulic, pneumatic and control systems
  • Customer sectors and working environments
  • Balance of planned work, breakdowns and project activity
  • Individual responsibilities and available technical support

Look for a repeatable diagnostic approach

Relevant products matter, but good field engineers also show how they work through an unfamiliar fault. Ask candidates to describe a real breakdown: what information they gathered, how they isolated the cause, which tests they performed and how they confirmed the repair. Listen for safe isolation, clean working practices and an understanding of how mechanical, electrical and control issues interact.

  • Logical fault-finding rather than parts swapping
  • Safe isolation and risk awareness
  • Ability to interpret schematics and technical documentation
  • Clear reporting of causes, actions and follow-up work

Be direct about travel, call-out and customer contact

Field-service vacancies often lose suitable candidates when the practical expectations appear late in the process. Define the territory, normal travel pattern, overnight stays, call-out rota, overtime arrangement and van policy at the start. Also explain how much responsibility the engineer has for customer updates, quotations, recommendations or identifying further work.

  • A realistic home-base and service territory
  • Expected overnight stays and international travel
  • Call-out frequency and how time is compensated
  • Vehicle, tools, expenses and home-to-site arrangements

Run an interview that reflects the job

Use the interview to explore technical judgement and customer behaviour together. A short scenario can reveal how someone prioritises safety, communicates downtime and decides when to escalate. Keep any practical assessment relevant to the systems they will support, and make space for the candidate to understand your service operation, training and progression.

  • Use one or two realistic fault scenarios
  • Ask for examples of handling pressure on customer sites
  • Discuss documentation, handover and escalation
  • Confirm training needs without expecting every skill on day one