Sr. IP Network Engineer

About the role

Routing, peering, and capacity handle voice and data business delivery. You own the design and day-to-day operations of the IP core and access topologies that keep voice and data services performing to specification. This role requires you to translate network strategy into precise BGP, IGP, and MPLS configurations while maintaining strict alignment with policy. You will own the documentation that supports network designs, configurations, and operational audits. Collaboration with cross-functional partners ensures that capacity and peering decisions meet business needs. You will analyze complex problems and communicate technical tradeoffs in plain language to both technical and non-technical audiences. Your work directly impacts the reliability and efficiency of the services our clients depend on.

Key facts

What you'll do

Design and maintain IP core and access topologies to meet strict latency and capacity goals for voice and data services.

Develop and maintain BGP, IGP, and MPLS configurations that reflect network strategy, policy, and business requirements.

Perform detailed network analysis to identify bottlenecks, single points of failure, and optimization opportunities.

Create and update network documentation, including diagrams, address plans, and configuration templates for audits and operations.

Partner with peering and capacity teams to evaluate new connections and optimize existing paths for performance and cost.

Implement monitoring and alerting strategies for IP infrastructure to ensure rapid detection and resolution of issues.

Lead post-incident reviews and contribute to runbooks and playbooks that improve team operations.

Translate business requirements into technical specifications that guide the delivery of stable and scalable network services.

Support network technology evaluations and proof of concepts for new routing strategies or capacity upgrades.

Act as a technical owner for network changes from design through deployment and validation.

Requirements

Five to seven years of professional IP network engineering experience in carrier class environments.

Strong working knowledge of BGP, IGP, and MPLS in service provider or enterprise carrier settings.

Experience with network documentation practices that support designs, configurations, and operations audits.

Ability to interpret network requirements and translate them into stable configurations and topology designs.

Solid understanding of latency and capacity considerations for voice and data services.

Proven ability to analyze complex network problems and implement effective solutions under operational constraints.

Excellent written and verbal communication skills to convey technical details to both technical and non-technical stakeholders.

Willingness to collaborate closely with cross-functional teams including peering, capacity, and product owners.

Nice to have

Experience with monitoring systems specific to IP infrastructure and performance metrics.

Background in telecommunications or other highly regulated industries.

Practical notes

Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

The role focuses on network engineering for voice and data services in carrier class settings. Common tools include routing protocols and monitoring systems for IP infrastructure. Clarity on specifications supports consistent service delivery.

Questions to ask

Useful questions for the interview: what a typical week looks like, how work is assigned, what tools the team uses, and how feedback works. Asking how the role has changed recently and what the team wishes it had known when joining is also reasonable. Questions about the manager's priorities are especially valued.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.

About the company

Company work involves data transfer rates and frequency measures. Daily tasks connect to bit flow concepts across network channels. Understanding spectral width supports system monitoring. Team members track throughput levels during operations. Range width calculations guide internal protocols. Communication paths rely on these measurements for stability. Ongoing projects assess performance metrics tied to transfer capacity. Focus remains on maintaining efficient information flow. Clients expect consistent service from skilled staff. Knowledge of frequency ranges supports technical goals.