Gandhi Nagar, Vijayawada. Full-time, on-site, paying up to ₹71,500 a month. This role is built around 42 months of hands-on network administration experience, and the person hired will be responsible for keeping the company's connectivity running rather than sharing that load across a larger team. The company has roughly 150 employees across two floors right now, with plans to add a third within the year, so the network this person inherits is already at a size where informal fixes stop scaling.
Day-to-day responsibilities
- Configure and maintain switches, routers, and firewalls across the office network
- Troubleshoot connectivity issues, from a single workstation dropping off the network to a broader outage affecting an entire floor
- Monitor network performance and security continuously, not just when something's already gone wrong
- Plan capacity ahead of growth, so new hires or new offices don't strain infrastructure nobody upgraded in time
A recent example: the office added a new floor last quarter, and the existing switch stack wasn't sized for the extra load. Nobody caught it until users on the new floor started reporting intermittent drops during peak hours, and tracing the cause back to switch capacity took longer than it should have because nobody had documented the original sizing decisions. Getting ahead of that kind of gap, before users notice it, is exactly what this role is meant to prevent. Proper documentation of the network's current state, something the previous setup lacked, is one of the first deliverables expected once someone starts.
Skills you'll need
- Network configuration across routers, switches, and firewalls
- Routing and switching fundamentals, comfortable enough to design a network segment, not just maintain an existing one
- Firewall management, including rule sets that actually get reviewed rather than left untouched for years
- Troubleshooting instincts sharp enough to isolate a problem quickly under pressure
These four cover the daily reality of the job more than any certification does, though certifications certainly help demonstrate them on paper to a hiring manager who hasn't seen your work firsthand.
Beyond the core skills, a CCNA or CompTIA Network+ certification strengthens an application meaningfully, even though it isn't strictly required. Exposure to network monitoring tools like SolarWinds or PRTG helps too, and some scripting ability, Python especially, goes a long way toward automating the repetitive parts of network monitoring rather than checking dashboards manually all day. None of these are dealbreakers if missing, but a candidate who already brings one or two will spend less time getting the basics of this network under control and more time actually improving it.
Education and experience
A bachelor's degree is expected, generally in electronics, computer science, or a closely related field. Beyond the degree, 42 months of practical experience managing network infrastructure is the bar for this seat, ideally including direct responsibility for a production network rather than only supporting one under someone else's direction. The exact major matters less here than in some technical roles, since networking knowledge tends to come from hands-on work far more than coursework. A candidate who's only worked in a helpdesk-adjacent role and touches networking occasionally will likely need more ramp-up time than this position allows. The company is specifically looking for someone who's already carried end-to-end ownership of a network's uptime, not someone who's only ever escalated issues to a vendor or a more senior colleague.
How the role fits into the company
This is a standalone position rather than one slot on a larger infrastructure team, so the person hired reports directly to IT leadership and carries real autonomy over network decisions. One recent hire on the broader IT team came through Naukri Mitra and has since taken on a mentoring role for anyone new joining infrastructure, which is worth knowing since some cross-team support exists even though the network role itself is solo. That said, day-to-day decisions and uptime accountability rest squarely with whoever takes this seat, not a shared team consensus. Expect a mix of planned maintenance windows, usually scheduled for off-hours, and the occasional unplanned fire drill when something breaks during the workday. Neither follows a strict schedule, so flexibility for occasional early mornings or evenings for maintenance work is part of the deal.
Vijayawada's IT sector has grown steadily in recent years, and Gandhi Nagar specifically has seen an uptick in office openings, so network demands here tend to shift faster than in a more established tech hub. That pace is part of what makes the role interesting, and part of what makes solid documentation habits non-negotiable. A network that scales smoothly through the next round of headcount growth depends almost entirely on decisions made now, while things are still manageable.
Compensation and benefits
- Salary up to ₹71,500 per month
- Health insurance
- Paid time off
- Provident fund contributions
- Relocation assistance and accommodation support for candidates relocating to Vijayawada
Anyone tracking network administrator salary in Vijayawada per month figures will find this one on the stronger side for the local market, reflecting both the solo responsibility involved and the experience bar attached to it. There's no formal on-call stipend beyond the base salary, so factor that into how you weigh the occasional after-hours maintenance work mentioned earlier.
Applying
This is an on-site role in Gandhi Nagar, so relocation or a local commute is expected. Send a resume detailing the size and complexity of networks you've managed, including rough device counts and whether you were the sole administrator or part of a team. That context matters more than a generic list of tools, since managing a network alone requires different instincts than being one of several hands on the same infrastructure. Candidates checking network administrator job openings in Vijayawada regularly should know this process moves quickly, usually with one technical interview covering a real troubleshooting scenario, followed by a conversation with IT leadership. Most candidates hear back within a week of the final round. Come prepared to talk through a specific incident you've resolved, ideally one where the initial symptom didn't point directly at the actual cause.
