/ TEAMS · BGP / EVPN Networking
For a VXLAN EVPN fabric, define the leaf-spine topology, route types, BGP control plane, multihoming, ASIC platforms and change windows before recruiting.
2,000+ engineers in our active talent network · Regional recruiters
/ SYSTEM STACK
eBGP · Leaf / Spine · ECMP
EVPN · MP-BGP · Route Types
VXLAN · VTEP · Anycast GW
VRFs · Route Targets · Segmentation
Telemetry · Rollback · Convergence
/ AVAILABLE TO HIRE
Profiles show the experience we can source. Individual candidate availability is confirmed after enquiry.
Mid+ BGP / EVPN Network Engineer — VXLAN Fabric
Available7+ years of experience · Serbia
BGP / EVPN Network Engineer — VXLAN Fabric with 7 years in production systems, focused on BGP / EVPN Network Engineer — VXLAN Fabric and Production systems.
Languages: Serbian, English C1
Senior BGP / EVPN Network Engineer — VXLAN Fabric
Inquire availability7+ years of experience · Romania
BGP / EVPN Network Engineer — VXLAN Fabric with 7 years in production systems, focused on Production systems and Technical delivery.
Languages: Romanian, English B2+
Senior BGP / EVPN Network Engineer — VXLAN Fabric
Available10+ years of experience · Romania
BGP / EVPN Network Engineer — VXLAN Fabric with 10 years in production systems, focused on Technical delivery and BGP / EVPN Network Engineer — VXLAN Fabric.
Languages: Romanian, English B2+
Mid-level BGP / EVPN Network Engineer — VXLAN Fabric
Available3+ years of experience · Czechia
BGP / EVPN Network Engineer — VXLAN Fabric with 3 years in production systems, focused on BGP / EVPN Network Engineer — VXLAN Fabric and Production systems.
Languages: Czech, English B2+
/ Specialist sourcing
For a VXLAN EVPN fabric, define the leaf-spine topology, route types, BGP control plane, multihoming, ASIC platforms and change windows before recruiting.
Request a production example of MAC/IP route instability, blackholing or failed multihoming convergence with packet captures and routing evidence.
Role-specific sourcing, not a promise of current candidate availability.
/ Engineering teams
Our private-cloud and bare-metal specialist sourcing gives context to datacenter infrastructure requirements. For BGP/EVPN roles we target documented operational responsibility for routing design, convergence behavior, overlays and change management; equipment/vendor experience is checked for each environment.
/ Technical specializations
The right network engineer can trace a packet and its control-plane advertisement through the actual fabric—not just configure a switch template.
eBGP adjacencies, ECMP, addressing, failure domains, BFD and control-plane resilience.
MP-BGP EVPN route types, MAC/IP advertisements, route targets and route reflectors.
VNI assignment, VTEP reachability, ingress replication or multicast choices, L2/L3 VXLAN.
VRFs, anycast gateways, symmetric IRB, tenant isolation and security-policy alignment.
Vendor NOS differences, SONiC/FRR or relevant stacks, configuration templates and validation.
Telemetry, packet tracing, MAC move behavior, convergence testing, staged changes and rollback.
/ Project scenarios
Define leaf-spine underlay, VXLAN segmentation, VRFs and EVPN route policies.
Correlate BGP advertisements, VTEP state, MAC/IP routes and data-plane forwarding.
Plan fabric cutovers, coexistence, validation windows and predictable rollback.
Measure failover, BFD behavior, route reflector health and blast radius during changes.
/ Practical evaluation
Candidates should be able to explain live routing incidents, packet paths and convergence effects—not only recite BGP terminology.
Can the engineer explain route types, next-hop resolution, route targets and reflector behavior?
How would they isolate an unreachable tenant host from physical links through VTEP forwarding?
Have they used templates, source-controlled changes, simulation, telemetry and validation?
How are maintenance windows, rollback, convergence and tenant blast radius handled?
/ Sourcing process
Vendors/NOS, topology, AS design, EVPN/VXLAN, traffic flows and customer isolation.
Identify engineers with hands-on BGP/EVPN datacenter operating experience.
Review real routing changes, EVPN diagnostics, automation and migration experience.
Confirm security access, change windows, timezone, availability and escalation paths.
Profiles, availability and engagement terms are confirmed for each request.
/ Questions
Yes. Share topology, vendors or network operating systems, EVPN route policies and which underlay/overlay responsibilities need ownership.
That may be essential. We can narrow sourcing by Juniper, Arista, Cisco, SONiC/FRR or your actual NOS, without assuming skills transfer automatically.
Yes, when the brief identifies Neutron integration, tenant isolation, provider fabrics and the BGP/EVPN boundary.
Yes. We screen change-plan quality, outage risk, control-plane verification and rollback experience for production network work.
/ Onectus · TEAMS
Tell us the technology, production responsibilities, experience level and working model. We'll activate the appropriate engineering sourcing channels.
