The Roles · Who supports it

Field network engineer

Held this role - at vendors, in the field, 1996-2000, 2005-2007

The vendor engineer who goes to where the equipment is. Field engineers install, commission, troubleshoot and repair in the customer's building, on the customer's schedule, with whatever the site turns out to contain. The role sits between support and services: it carries the vendor's name into the room and answers for the product in front of the people who bought it.

What the day looks like

  • Installing and commissioning equipment, which begins with discovering how the site differs from the plan.
  • Diagnosing a fault with the customer watching, using the evidence available on site.
  • Replacing hardware and proving the replacement resolved the thing it was sent for.
  • Auditing what is already installed, because the site is frequently the only accurate record of itself.
  • Migrating a customer from equipment that works to equipment that works better, inside a window that ends on time.
  • Improving what was found: the configuration that predates the current design, the thing everyone has learned to live with.
  • Writing the environment down, so the next engineer arrives informed rather than exploring.
  • Training the customer's operations staff on what was built, in the room, on their own equipment.
  • Capturing what happened in a form the support organisation can act on later.
  • Explaining to the customer's staff what occurred, in terms they can repeat to their own management.

What it answers for

  • The equipment working when the visit ends.
  • The evidence trail: what was found, what was changed, and what remains open.
  • Representing the vendor accurately, including about the parts still under investigation.
  • Leaving the customer's own engineers able to operate and troubleshoot what was installed.

What it is measured on

  • Time to restore, and visits closed on the first attempt.
  • Customer satisfaction recorded after the visit.
  • Utilisation and travel efficiency, which are a scheduling function rather than an engineering one.

Who it receives from

The support organisation
The case, its history, and the reason a person is being sent.
Logistics
Parts, which arrive on their own schedule.
The customer
Access, escort, and the account of what happened that they were able to observe.

Who it serves

The customer's engineers
A working system and an explanation they can use.
The support organisation
Ground truth that a remote case cannot produce.
Engineering
Field evidence of how the product behaves outside a laboratory.

Who else has a stake

  • The account team, for whom every visit is a reference in progress.
  • The customer's management, who experience the fault as downtime.
  • Product engineering, for whom recurring field findings are a defect signal.

What it takes

  • Hands and head together: the role is diagnostic and physical in the same hour.
  • Working alone with authority, since the decision on site is made on site.
  • Tolerance for travel, and for the schedule that travel imposes on a life.
  • The composure to be the visible face of a product that is currently failing.
  • Teaching as a routine part of the visit, because the people who will live with the system learn it from whoever installed it.

What the job turns on

The dispatch is written as an installation or a fault, and the visit is an audit, a migration, an improvement, a piece of documentation and a training session wrapped around it. The measurement is time to restore, and the lasting value is the record left behind. A visit that fixes the symptom and captures the evidence turns one customer's fault into a defect the vendor can address for everybody; a visit that fixes the symptom alone leaves the same engineer travelling to the same problem at a different address next quarter. The engineers who understand this write their notes as though a stranger will read them, because one will.

Where it leads

Roles that lead here

The work itself

The Practice covers how this work is done — triage, escalation, evidence, handover — across the whole corpus.

Read The Practice