Fourteen systems. One person who knows how all of them behave at 3am.

That person is the Chief Technician. If you like being the one everyone comes to when a system nobody outside the building has heard of stops behaving, read on.

What you would actually keep alive

NAMIS, CoreGIS, REACT, Intel-FS, ANB, Release Server, HMART, CSD IPL/IWS, ICMT, AOSS, NABI and more. You would install them, monitor them, maintain them, and fix them when they break.

What the day looks like

Level 2 and service management support: incidents, service requests, change requests and tasks, all traceable through ITSM and Azure DevOps. Daily planning and reporting with the service delivery managers, plus the workshops, events and conferences where you are the technical voice in the room. On call comes with the territory.

Who you would work with

An integrated military and contractor team, in a Chief Technician role at G14 equivalent level. You would be a senior technical anchor, not a ticket closer.

What you will need

Solid Level 2 support and IT service management experience, comfort with ITSM and ticketing workflows, and flexibility around on call and on site working. Exposure to intelligence support systems is a real advantage, though the systems above can be learned by the right engineer.

Where

On site in Mons, Belgium, at SHAPE. Contract engagement.

What next

Do not worry about a polished CV. Send what you have, or message me directly and tell me which systems you have kept running. Everyone gets a response.