Interview experience at "Infinera Bangalore India
Question Details
Interview process took 3 to 4 hours and it was done.It was good interview.It was on Java, Data structures and algorithm.1st round was written roundGiven a square image wri...
Full Details
Interview process took 3 to 4 hours and it was done. It was good interview. It was on Java, Data structures and algorithm. 1st round was written round Given a square image write a code to rotate this image by 90 degree. 2nd round Questions on Java Threading, what is static synchronization and normal synchronization on method. Gave one problem and asked to solve that I have been given with library called add.jar, which does addition job.This jar has many other methods too.All these methods are used at various places in our applications.This library has exposed some interfaces to client. If I want to print the time taken by all the methods used in my application. How can we do that?? 3rd round Explain how Collections.synchronizedMap() method works. Write some Restfull apis for telephone functionality and some questions on my project. 4th round Director took the interview. Simple behavioural questions and some java questions. Thanks and Regards
About This Question
This is a reported interview question from a infinera interview for a swe role (director level) during the phone screen round reported in 2015.
Difficulty rating: Easy
More Infinera Interview Questions
About Infinera Interview Reports
This question was reported by a candidate who interviewed at Infinera. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Infinera are the higher-signal extractions to take from this report.
For broader preparation context, the Infinera interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Infinera reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Infinera Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Infinera reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.