Rajiv Gandhi Technology Park's IT corridor has an opening for a VoIP Engineer to work on-site in Chandigarh. The team runs voice traffic for a network that doesn't quietly tolerate dropped calls, and this hire will be one of the people responsible for keeping it that way. It's a full-time seat, not a contract or project-based arrangement, and it sits within the company's networking and telecom function rather than general IT support.
Skills You'll Bring
- Working fluency in VoIP protocols, SIP in particular, at a level where you can read a call trace and know what went wrong.
- Broad networking knowledge covering switching, routing, and how traffic actually moves across a corporate WAN.
- Direct experience with telephony systems, whether that's PBX platforms, SIP trunks, or call routing logic.
- Sharp troubleshooting instincts, since half the job is figuring out why something intermittent keeps happening rather than fixing something that's obviously broken.
Beyond that core set, familiarity with Cisco or Avaya voice platforms helps, as does prior exposure to quality of service tuning on congested links. A CCNA Voice or CCNP Collaboration credential isn't a requirement, though it does tell a hiring manager you've spent real time in this specific corner of networking. Comfort with packet capture tools such as Wireshark is useful too, mainly because most real VoIP problems only reveal themselves once you're looking at the actual packets. None of these extras will replace the core SIP and troubleshooting skills above, but they do considerably shorten the ramp-up time.
What the Role Covers Day to Day
- Set up and keep the voice network's hardware in working order, whether that's bringing a new switch online or staying on top of routine firmware upkeep across existing gear.
- When something breaks, run down why. That could mean a single user's one-way audio issue or an outage that takes down phones across an entire floor.
- Keep an eye on how the network is performing and where its security posture stands, catching early degradation before it becomes a visible problem.
- Look ahead to where the business is headed and make sure the voice network has room to grow into it, rather than hitting a wall just when it's needed most.
A typical week mixes planned maintenance windows with the occasional urgent ticket, the kind where a department head calls because their conference bridge keeps cutting out mid-meeting. Tracing that back to a misconfigured SIP trunk, rather than blaming the internet connection everyone assumes is at fault, is a fairly ordinary Tuesday in this seat. Capacity planning tends to get less attention than the reactive work, if only because a fire in front of you always feels more urgent than a chart projecting next quarter's call volume, but it's treated as a real part of the job rather than something squeezed in when time allows.
Requirements
The degree bar here is a bachelor's, and the fields that typically satisfy it are electronics or computer science, though anything with comparable technical grounding is also acceptable. This role also calls for four years of hands-on experience with network and VoIP infrastructure, gained in a live production environment rather than a lab setting.
That experience figure is a floor, not a hard cutoff. Someone with three strong years managing a busy voice network and a track record of solving hard problems under pressure will still get a look. What matters more than the exact year count is whether you've actually carried pager duty for a system people depend on, not just configured one in isolation.
Team and Escalation
The networking team here is mid-sized, big enough that no single engineer owns the entire voice stack alone, small enough that everyone knows which piece is whose. Escalations follow a tiered structure: first-line monitoring catches most issues before they reach a user, and this role sits at the second tier, called in once something needs a deeper look. Night and weekend on-call rotates across the team on a fixed schedule, and it's genuinely shared rather than falling disproportionately on the newest hire. New engineers typically shadow a senior team member through their first on-call rotation before taking one solo, which keeps that first late-night page from being someone's very first exposure to the escalation process.
Compensation and Benefits
- A monthly salary of ₹71,500, reflecting the seniority this role expects.
- Health insurance coverage for the employee.
- Paid time off, separate from public holidays.
- Provident fund contributions, handled per statutory requirements.
- Relocation assistance and accommodation support for candidates moving to Chandigarh, since this is an on-site posting.
The salary sits toward the higher end for network engineering roles in this part of Chandigarh, which tracks with the experience bar and the on-call responsibility that comes with the seat.
Where You'd Be Working
The role is based in IT Park, home to Rajiv Gandhi Technology Park, which puts it in the middle of Chandigarh's main tech corridor. This listing came to us via Naukri Mitra, and it's worth noting up front that this is not a remote or hybrid arrangement; the network hardware this role touches lives on-site, and so does the engineer maintaining it. Chandigarh's IT Park has grown significantly in recent years, and many engineers relocate here specifically for roles like this one, drawn by the concentration of network and telecom employers in a compact area.
Commuting within Chandigarh's sector layout is generally straightforward compared to larger metros, and several sectors near IT Park have seen a steady rise in rental housing aimed at exactly this kind of relocating professional. For someone weighing a move from outside Punjab or Haryana, that housing supply, combined with the relocation assistance listed above, tends to make the transition less of a logistical headache than it would be in a more sprawling city.
How to Apply
Submit a resume along with details of your hands-on experience with SIP-based systems and any voice platforms you've supported directly. Shortlisted candidates can expect a technical screening that covers call-routing scenarios and basic packet-level troubleshooting before a final round with the network team lead. Candidates already based in or near Chandigarh will likely move through the process faster, simply because scheduling an on-site interview is easier, but that's a logistics point rather than a preference on paper.
