Example Achievement Log for a Network Engineer

Software & IT

Example Achievement Log for a Network Engineer

Below is a Network Engineer's Achievement Log for a calendar year. It tracks live network incidents, infrastructure upgrades, vendor relationships, and the documentation work that turns emergency fixes into repeatable processes.

A year in the life of a Network Engineer's log

  • Jan - task: Inherited BGP configuration for three Azure ExpressRoute circuits from departing senior engineer. Spent two weeks reading twelve years of Jira tickets and reverse-engineering intent from config comments.
  • Mar - feedback: Jason (Operations Manager) told me in standup: 'You're the only person who actually understands those circuits now. Don't leave us in the dark again.'
  • Mar - achievement: Traced flapping BGP session between London and Frankfurt to misconfigured BFD timers on Juniper MX480. Root cause was 800ms IKE renegotiation collision. Fixed by staggering timers across three sites, restored 99.98% uptime.
  • Apr - task: Led RFP process for core switch replacement at Santa Clara DC. Evaluated Arista 7358, Cisco Nexus, and Juniper QFX against site power budget (2.8kW limit) and existing Netbox schema. Selected Arista; procurement started.
  • Jun - achievement: Commissioned Arista 7358 at Santa Clara after four weeks of staging in lab. Migrated 147 VLANs and 12 BGP AS paths with zero packet loss. Moved workloads off aging Catalyst 6509 three days ahead of schedule.
  • Jun - task: Discovered our change window process didn't account for ISP provider notification delays. Rolled back a Monday morning MPLS circuit swap at 6:15am when Equinix rep never showed. Wrote new runbook requiring 72-hour vendor confirmation.
  • Aug - feedback: Sarah (VP Engineering) in all-hands: 'The network stayed up through that failed ISP window change because Network Engineers learned and rebuilt the process.' That mattered.
  • Sep - achievement: Diagnosed asymmetric latency on US east egress: one direction taking 90ms detour via Newark due to BGP prepend mistake I'd made two years prior. Fixed it. Reduced API tail latencies by 12ms median across three regions.
  • Sep - task: Documented entire BGP state machine and design rationale in Confluence for the first time. Created fifteen pages covering failover behavior, AS path logic, and how London-Frankfurt circuit backs up to NY in emergency. Added three worked examples.
  • Nov - achievement: Negotiated 18-month contract with Zayo for dedicated transport between Singapore and Tokyo at 32% below their opening quote, using competitive bids from NTT and Lumen. Reduced annual ISP spend by $184k.
  • Dec - feedback: Martin (Finance) emailed: 'Your ISP negotiations saved more than half a junior engineer's salary this year. Second year running you've done this.'

What makes a strong entry

What most people write: Diagnosed and fixed latency issue affecting API performance.

What went in the log: Diagnosed asymmetric latency on US east egress: one direction taking 90ms detour via Newark due to BGP prepend mistake I'd made two years prior. Fixed it. Reduced API tail latencies by 12ms median across three regions.

The strong version names the actual cause (BGP prepend mistake), the before/after metric (90ms detour → fixed), and the business impact (12ms median reduction), all facts that a reviewer can verify and remember months later.

What most people write: Negotiated better pricing on ISP contracts.

What went in the log: Negotiated 18-month contract with Zayo for dedicated transport between Singapore and Tokyo at 32% below their opening quote, using competitive bids from NTT and Lumen. Reduced annual ISP spend by $184k.

The strong version includes specific vendor names, the discount percentage, the tactic (competitive bids), and the annual savings figure, making it concrete enough that finance can cite it and a future employer can understand the scope of negotiation skill.

How this becomes your review in November

I spent the first quarter inheriting and stabilizing three critical Azure ExpressRoute circuits, including diagnosing and fixing a BGP flap that was costing us uptime across London and Frankfurt. I've delivered two major infrastructure upgrades this year: commissioning the new Arista core at Santa Clara with zero downtime and a 147-VLAN migration, and negotiating an 18-month transport contract with Zayo that will save the company $184k annually through competitive bidding. Beyond the technical work, I've invested in durability: I documented our entire BGP design for the first time and rebuilt our change window runbook after a vendor coordination failure, ensuring the team can operate safely without me.

Starting your own log

Don't try to reconstruct a year you have already had. Start from today, one line whenever something happens, and let it build. The Perform Review Achievement Log does this for you and can capture wins straight from Slack, and how to start an achievement log covers the wider playbook.

Example Logs for Related Roles

Ready to start your own? Start your Achievement Log free, see how the Perform Review Achievement Log works, or browse performance review phrases for Network Engineer.