🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
Senior Datacenter Network Build and Migration Engineer Contract engagement | Pune, Chennai, Bengaluru, Mumbai | On-site We're recruiting for a global payments fintech expanding its APAC datacenter footprint and consolidating legacy environments into a target architecture. The estate carries live transaction traffic for banks, merchants and financial institutions. Every build and every migration runs through strict change control, and unplanned service impact isn't an option. This is a hands-on engineering role. The client owns the architecture and the change approval. You'll work inside their Network Services team, turn HLD and LLD material into workable implementation plans, and support production cutovers with minimal supervision. If you're after a design or oversight position, this isn't it. The work spans build, migration and relocation activity across Cisco and Arista: preparing runbooks, methods of procedure, rollback and validation plans; configuring and troubleshooting switching, routing and fabric components; and documenting to a standard the operations team can still use after the project closes. Essential experience Very strong hands-on Cisco Nexus datacenter switchingVery strong hands-on Arista EOS datacenter fabricExperience in hyperscale, global financial services, large service-provider or comparably complex network environments. Payments, PCI-sensitive segmentation or tightly controlled production networks are particularly relevantSpine-leaf and fabric designs, aggregation and access layers, secure DMZ and datacenter interconnectAdvanced BGP, OSPF and IS-IS, including route policy, redistribution, segmentation and traffic engineeringVRFs, VLANs, trunks, LACP, port channels, MLAG and vPC-style designs, redundant datacenter connectivityMPLS, VXLAN/EVPN, FabricPath or equivalent datacenter and transport technologiesMigrating production traffic paths, covering overlapping services, NAT dependencies, client and application flows, and rollback planningEnough awareness of Palo Alto firewall, F5 ADC, NFV and cloud connectivity to coordinate with the specialist teamsAWS and Azure connectivity: Direct Connect, ExpressRoute, VPN routing and cloud route controlTroubleshooting L1 to L4, covering routing, forwarding, asymmetric paths, MTU, packet loss, failover and performanceDocumentation and implementation evidence to a standard that stands up to change governance and operational handoverAutomation using Python, Ansible, APIs or similar, and a track record of improving runbooks, validation tooling and repeatable implementation patterns Exposure to SD-WAN, internet edge, cloud backbone or international backbone environments is an advantage. Apply through LinkedIn or contact me directly. .
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.