Senior Network Engineer resume example

• Designed BGP policy standards for hybrid enterprise and cloud interconnects, defining peer classes, accepted prefixes, communities, and maximum-prefix actions; required a route-leak test and named rollback owner before approving a new peering pattern.
• Led network design reviews for EVPN-VXLAN fabrics, separating underlay reachability from tenant overlays and documenting failure domains; challenged shared uplink and control-plane dependencies before accepting the proposed redundancy design.
• Established Python and Ansible change checks in Git-based review using REST API inventory data: intended-route assertions, configuration diffs, and post-change TCP/IP probes; kept production execution behind explicit approval rather than treating a successful dry run as authorization.
• Coordinated a routing incident across NOC, security, and service owners; separated immediate traffic restoration from root-cause analysis, preserved packet and configuration evidence, and converted the failed assumption into an owned regression test.
• Led capacity management using interface utilization, NetFlow demand, queue loss, and N-1 failure scenarios; compared circuit upgrades with traffic-engineering changes and recorded cost, resilience, and delivery dependencies for the investment decision.
• Compared BGP route advertisements before and after a peering change, checked prefix filters and maximum-prefix limits, and rehearsed withdrawal without affecting unrelated peers.
• Owned a BGP network-design validation using isolated routing fixtures, resolved asymmetric paths and completed redundancy tests before the migration review.
• Built Python log-analysis checks using REST inventory data, reduced root-cause-analysis preparation from 50 to 20 minutes and published the capacity-management worksheet.

• Planned network migrations across OSPF-to-BGP routing boundaries for a data-center expansion; documented redistribution rules, prevented feedback loops with route tags, and required a stable old-path fallback through each migration gate.
• Owned an IPv6 rollout plan spanning address management, DNS, firewall policy, and service testing; made IPv6 failure cases visible in the acceptance criteria instead of approving dual stack on address assignment alone.
• Standardized VLAN, VRF, and access-control-list reviews for shared infrastructure; paired each allowed flow with a service owner and expiry condition, then reconciled exceptions during customer moves and contract changes.
• Standardized preventive maintenance with carrier and operations teams: optical thresholds, error-counter baselines, dependency owners, and user-path tests; used exceptions to schedule replacements and rehearsed rollback before cross-connect changes.

• Investigated recurring WAN congestion through syslog log analysis, SNMP interface counters, and traffic samples; separated queue pressure from physical-link errors and tested a proposed QoS policy against voice and bulk-transfer traffic before rollout.
• Maintained BGP and OSPF operational baselines during branch expansion; compared expected next hops with the forwarding table and captured exceptions in the acceptance record so monitoring could distinguish an intended change from route drift.
• Mentored NOC engineers on evidence-led escalation, using packet captures, routing snapshots, and a chronological incident log; reviewed handovers for missing tests and prevented configuration changes from being used as a substitute for diagnosis.

• Defined SIT and UAT acceptance conditions for BGP route acceptance, OSPF redistribution, VLAN isolation, and IPv6 reachability; assigned each test an owner, expected evidence, and a reason to stop or roll back the change.
• Led a tabletop exercise for a shared-fiber outage and stale route policy; traced which services would share the failure, challenged the N-1 capacity assumption, and assigned design corrections before procurement approval.
• Published a review pack with architecture decisions, Ansible dry-run output, monitoring baselines, and tested rollback; separated unresolved risks from completed checks so approval could not be inferred from a green summary alone.
• Owned the recovery rehearsal using an isolated test account, resolved a missing permission prerequisite and completed the restore without changing the working baseline.

Relevant coursework: Algorithms, operating systems, databases, computer networks

• Published an independent troubleshooting guide using annotated logs, separating connectivity, authentication and application failures and documenting the rollback decision at each step.