Lead Software Developer - L2/L3 Networking Protocols

Responsibilities

Assess requirements, design, develop, and deliver high-quality software in partnership with functional teams.

Participate in SW design reviews and clearly communicate system software requirements.

Experiment with and evaluate performance and scale enhancements, ensuring optimal use of Board HW devices and SW resources.

Demonstrate cross-functional collaboration with Product Marketing, SQA, and other development teams to ensure the software satisfies performance, scalability, interoperability, and security requirements.

Lead the control plane team and coordinate cross-functionally on initiatives that require alignment across organizational boundaries.

Produce functional and design specification documents, drive sign-off, and interface with developers, QA, documentation, customer support, and program management teams.

Contribute to full product life cycle development.

Skills

Must have

Minimum of B.S./B.E./B.Tech in CS/EE/ECE/IT

12+ years of relevant industry experience in Networking/Telecom

Embedded/Network Management

Strong understanding of routing algorithms, data structures, and open-source integration.

Strong understanding of control plane and data networking concepts

Excellent knowledge of Layer-2 Bridging protocols

STP/MSTP/RSTP, LACP, MLAG & LLDP

Strong knowledge of Layer-3 Routing protocols

BGP, MPLS, EVPN-VxLAN

In-depth understanding of Linux operating systems and embedded software development

Excellent programming knowledge in C/C++

Experience in troubleshooting and debugging memory leaks and performance bottlenecks

Experience working with multi-site project teams

Ability to learn on the job and take on new challenges

Should be able to implement and manage the complete delivery of the component/modules owned

Strong analytical and problem-solving skills

Ability to stay productive in flexible and dynamic work environments

Excellent oral/written communication and interpersonal skills

Nice to have

Exposure to GO and microservices architecture