Site engineer or Perth-based consultant? What actually separates the two roles

By Bosco Ahn, Senior Mining Consultant

It is a question I get asked reasonably often, usually by engineers weighing up a move: what is the actual difference between working as a site engineer and working as a Perth-based consulting engineer?

Having done both, my honest answer is that they are different jobs that happen to share a discipline. Neither is a step up or a step down from the other. But the day-to-day, the pressures and the skills that get rewarded are genuinely different.

The site engineer: executing the plan

Site engineers are far more focused on operations and on executing the plan — whether that is a weekly or a monthly schedule — on a day-to-day basis.

The defining feature of the role is immediacy. Things come up, and they come up constantly: an area is not available, ground conditions are not what was expected, a piece of equipment is down, a design needs to be adjusted before the next shift. Site engineers need to be very adaptive and able to address on-site issues quickly and, above all, safely.

There is a real skill in that which is easy to underestimate from the outside. Making a sound technical decision with incomplete information, under time pressure, where the consequences are physical and immediate, is not the same exercise as producing an optimal answer with a week to think about it.

The other part of the role that surprises people is how much of it is coordination. Site engineers usually interact and coordinate with a much broader group of people than you might expect — different departments, managers, contractors — all to produce the best outcome for the operation. The technical work is real, but a large share of the value comes from getting alignment across a lot of parties with competing priorities.

The consulting engineer: breadth and optimisation

For a Perth-based consulting engineer, I think the biggest difference is the range of work you get involved in — which is usually defined by the scope your clients set.

On one contract you might be working on a mine scoping study. On another you could be providing offsite support to a site for a three-monthly planning period. The variety is significant, and it comes at you in a way that site work generally does not. You move between commodities, mining methods, operations at completely different stages of maturity, and clients with very different levels of internal capability.

That breadth is the main attraction of the role, and it builds a particular kind of judgement quickly. When you have seen a dozen operations approach the same problem, you develop a much clearer sense of what genuinely works versus what simply happens to be how a given site has always done it.

As a consulting engineer, you are also responsible for providing the most optimal solution — and for identifying areas where your client can make further improvements. That second part is important and often under-appreciated. You are not only asked to answer the question in the scope. You are expected to notice what else is worth their attention, and to raise it.

The other difference is distance, in both senses. You are usually not on site, so you rely more heavily on data, on documentation and on the relationships you build with the people who are there. You have to work harder to understand the operational reality behind the numbers — and if you don't, you will produce recommendations that look excellent and cannot be executed.

Both matter, and they need each other

I do not think there is a hierarchy here. One role keeps things running today; the other helps shape a smarter tomorrow. An operation needs both, and the best outcomes come when the two work closely rather than at arm's length.

For an engineer deciding between them, my suggestion would be to think about what you want to get good at. Site work builds decisiveness, operational instinct and the ability to work with anyone. Consulting builds breadth, analytical depth and the discipline of having to justify your reasoning to someone who was not in the room.

Time on site makes you a better consultant. Consulting exposure makes you a better site engineer. If you can get both, get both.

Want the best of both worlds for your project? Get in touch with the Go Engineering team.