> Markdown version of [/jobs/ext/4757195-network-patching-engineer](https://www.wearedevelopers.com/jobs/ext/4757195-network-patching-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Network Patching Engineer - **Company:** gb Oscar Associates (UK) Limited - **Location:** Nottingham, United Kingdom (Remote available) - **Salary:** £117,000 - £130,000 - **Contract:** Temporary contract - **Skills:** Network Monitoring, Routing, Data Logging, Network Routing, Scripting, Load Balancing, System Availability, Firewalls (Computer Science) - **Published:** November 17, 2026 - **Apply:** https://www.totaljobs.com/job/it-networks-technician/oscar-associates-uk-limited-job108328725 ## About the Role Engineers should have practical experience with: * Network routing protocols and routing troubleshooting * LAN technologies and switching * WAN connectivity and carrier dependencies * Firewalls and security policy concepts * Load balancers and traffic-flow concepts * High availability and failover * Network monitoring, alarms and logging * Configuration backup and restoration * Connectivity and service validation * Basic scripting or automation literacy * They don't need expert-level knowledge of every platform. They do need enough breadth to understand how a change in one part of the network could affect another. ## Description The role will require weekend work & OOO but will only be 40 hours per week. They are putting together a shift pattern. Engineers will be shift work so we need flexible candidates., Execute approved network patching activities safely and consistently, complete pre- and post-change testing, and troubleshoot or escalate issues using established procedures., Engineers must be able to: * Review an approved change plan. * Identify missing prerequisites or unsafe assumptions. * Complete pre-change health checks. * Capture a reliable baseline before the change. * Follow process scripts accurately. * Use change control and escalation procedures. * Run defined post-change tests. * Compare test results against the baseline. * Recognise abnormal results. * Troubleshoot using monitoring, logs, configuration comparison and connectivity tests. * Escalate when the issue is outside their authority or competence. * Execute an approved rollback plan. * Record clear implementation evidence and handover information. * Expected behaviours The strongest candidates will: * Follow procedures without treating them as a substitute for judgement. * Ask questions when a script or change plan is unclear. * Stop when acceptance criteria are not met. * Avoid unauthorised improvisation in production. * Communicate clearly during incidents and handovers. * Understand that 'the device is reachable' doesn't necessarily mean 'the service is healthy'. * Balance delivery speed with operational safety.