The interesting problems are the ones that only appear in production.
A multinational defence service line in The Hague needs a support engineer for the softwaresolutions its users depend on: diagnosing what has gone wrong, configuring what needs configuring,and telling the development side what they need to hear. On site, with a share of the immediateon-call rota.
What you would be doing
- Resolving technical issues across software, hardware and the integrations between them, andgetting to the actual root cause
- Supporting the applications day to day - agreed maintenance, performance statistics, and thedeployment activity around releases
- Contributing to solution architecture in your area: weighing alternatives on cost,performance and scalability, and documenting the decisions that matter
- Specifying cloud or on-premises components and interfaces so they can be designed in detail,in line with the wider architecture and its security requirements
- Helping elicit and document requirements for well-bounded subject areas, and keeping thebaseline honest
- Planning and tracking development activity, keeping stakeholders aware of what is needed, andreporting progress
- Taking your turn on the immediate on-call rota for second-line response
What you would bring
- Real diagnostic ability across software, hardware and integrations, with debugging and loganalysis as habits
- Experience of a cloud platform, and working knowledge of APIs and basic integrationtechniques
- The organisation to run a support effort: tracking resolutions and talking to several teamsuntil something is actually fixed
- A customer-facing background - technical support, service desk or similar - and ITILtraining
- Welcome extras: software design, implementation and testing; the languages and patterns thatgo with it; agile delivery; on-site installation in a military environment
Why this one is worth a look
It sits between operations and engineering, so you see both, and it runs from a standingframework rather than a one-off project.
