Software Engineer 4 – L2/L3 Protocols Test and Automation Engineer

About the Role:
 

Juniper Networks is seeking a talented Routing Protocols Test Engineer with a strong background in network protocols and test automation to join our growing team. As part of our cutting-edge networking solutions, you will be responsible for validating and debugging routing protocols including OSPF, BGP, MPLS, and Segment Routing. This role offers an exciting opportunity to work with world-class engineers on next-generation products that shape the future of networking.

Key Responsibilities:

• Create, execute, and maintain automated and manual test cases to validate the performance and functionality of routing protocols like OSPF, BGP, MPLS, and Segment Routing.
• Leverage Python to build and improve test automation frameworks, making testing more efficient and scalable.
• Investigate and debug network issues, performing root cause analysis and resolving complex networking problems.
• Work closely with cross-functional teams, including development, product management, and other QA engineers, to design test plans, environments, and tools.
• Document and communicate test results, including detailed bug reports and feedback to technical and non-technical stakeholders.
• Proactively identify opportunities for process improvements in testing and automation to improve efficiency and product quality.

Required Skills and Experience:

• Automation Expertise: Strong experience in automation, preferably with Python. Knowledge of automation frameworks (e.g., Robot Framework, Pytest) is a plus.
• Routing Protocols: Deep knowledge of Layer-2 and Layer-3 protocols, including OSPF, BGP, MPLS, and Segment Routing. Experience testing, validating, and debugging these protocols is essential.
• Debugging: Strong debugging skills and experience troubleshooting complex networking issues. Ability to quickly isolate issues in a multi-vendor environment.
• Communication: Excellent verbal and written communication skills. Ability to clearly explain technical issues and progress to both technical and non-technical teams.