Juniper Boston, meh
Juniper Boston, meh
Great opportunities to take courses, attend informational lunches, etc.
Flexible hours, work from home, depending on supervisor.
Good medical insurance, reasonable base salary.
Effort tends to be rewarded more often than not.
If you want to do great things within Juniper, you pretty much have to be in California.
Lab support for unusual equipment can be non-existent (okay) or inflexible (worse).
Lack of investment/direction for certain products.
Offshoring.
Meh.
Was this helpful?
Juniper Networks Interview Questions
Juniper Networks Interview Experiences
Software Engineer
Almost all interviews were on the phone. They scheduled them one by one. Almost everyone on my team interviewed me. Questions mainly focused on computer networking, scripting, and basic coding. There were no complex algorithms. All questions were si
Software Engineer
Five interviews total, consisting of coding and general background questions about work experience. They asked OS questions and questions about my background. Questions about memory, cache, networks, threads, etc., were very common.
Software Engineer
5 interviewer panel. Covering past experiences, domain expertise, and behavioral questions. 1 hour each. No coding questions. Focus on system design and a deep dive into protocol knowledge. Then, a final call with the recruiter to discuss numbers
Software Engineer
Boston, Massachusetts, United StatesFebruary 1, 2017Almost all interviews were on the phone. They scheduled them one by one. Almost everyone on my team interviewed me. Questions mainly focused on computer networking, scripting, and basic coding. There were no complex algorithms. All questions were si
Software Engineer
San Diego, California, United StatesOctober 14, 2025Five interviews total, consisting of coding and general background questions about work experience. They asked OS questions and questions about my background. Questions about memory, cache, networks, threads, etc., were very common.
Software Engineer
Sunnyvale, California, United StatesJune 9, 20255 interviewer panel. Covering past experiences, domain expertise, and behavioral questions. 1 hour each. No coding questions. Focus on system design and a deep dive into protocol knowledge. Then, a final call with the recruiter to discuss numbers
