The scoreboard, and what is not on it. The hard targets, how often each is actually
looked at, and the quiet signals that never reach a dashboard.
Successful Change Implementations
The percentage of network configuration changes you make that go through without needing a rollback or causing an outage.
Target · 98%+ If you push 50 pre-approved firewall rule changes in a month, we'd expect 49 or more to work perfectly first time. That one rollback? We'll learn from it.
Mean Time to Acknowledge (MTTA) for P1/P2 Incidents
How quickly you respond to and acknowledge critical (Priority 1) and high-priority (Priority 2) network alerts.
Target · < 15 minutes A P1 alert comes in at 09:00 GMT for a major office outage. You should have acknowledged it and started initial checks by 09:10 GMT. Speed here is key.
Ticket Resolution Rate (without escalation)
The percentage of network tickets you're assigned that you manage to resolve yourself, without needing to escalate to a senior engineer.
Target · 80%+ Out of 100 tickets assigned, you'd aim to close 80 of them on your own, things like basic port activations, VPN resets, or simple connectivity checks. The other 20 are learning opportunities.
Documentation Accuracy & Updates
How well you keep our network diagrams and runbooks up-to-date after changes, and how accurate your incident notes are.
Target · Minimal errors, 100% completion for assigned tasks After adding a new switch to the Frankfurt office, you'd update the relevant Visio diagram and add notes to the NetBox entry, making sure all port allocations are correct. Missing a detail could confuse the next engineer.
Proactive Learning & Skill Development
Your willingness to dive into new network concepts, ask smart questions, and actively seek out opportunities to expand your technical knowledge.
- You'll be asking 'why' things are done a certain way, completing online courses, experimenting in lab environments, and showing initiative in understanding complex network issues beyond your immediate task. We'll see you taking notes during incident reviews and applying those lessons next time.
Adherence to Process & Best Practices
How consistently you follow our established Method of Procedures (MOPs), change management processes, and security guidelines.
- You'll be submitting change requests with all the right details, following troubleshooting runbooks step-by-step, and always getting approvals before making any network changes. We'll see you double-checking your work against our standards, not just rushing through it.
Clear & Concise Communication
Your ability to explain technical issues clearly to both technical and non-technical colleagues, especially during incident calls.
- During an outage, you'll be able to articulate what you've checked, what you're seeing, and what the next steps are, without using too much jargon. Your incident updates will be easy to understand, even for someone who doesn't know a router from a modem.
Team Collaboration & Support
How well you work with your team, offer help when needed, and contribute to a positive working environment.
- You'll be jumping in to help colleagues with their tickets when your queue is clear, sharing interesting findings, and generally being a good sport. We'll see you actively participating in team meetings and offering constructive feedback.