1.method overloading in depth questions used Google to ask all the questions.shame on team. 2.immutable class with mutable fields like Date 3.strings depth like compile time error or output. 4.nms different layers and protocols 5.enum depth. Almost all depth which were not asked in other company interviews.. they want who can find compile time errors which any have no use of finding the correct candidate. it's waste of my time
- Java basics - Multithreading - File system design - Cloud native App design (forgot which app) - Coding question based on Linkedlist and one based on graphs/trees
Here's a post-route congestion heat map. What are some things you could do to resolve this congestion?
1) Difference between def & lef files 2) Ways to fix the routing and cell congestion 3) PBA vs GBA, AOCV vs POCV etc.
They basically are very interested in how you approach and solve the technical problems.
Asked qns related to previous work
All questions were behavioral based. If you read the job description, you'll have an idea what the questions will be about.
Many coding and problem solving questions. Quite challenging but doable if you prepare well. I found the interview exciting and I really enjoyed.
1st round 1.5 hrs. with problem solving, system design, behavioral questions and current projects. 2nd round - craft round -> never developed fully working application because of its time consuming and less interested. Some 2-3 more round, who cares.
How would you redesign (showing mock-ups of UI components) to make it cleaner/faster/easier to use?
Viewing 4751 - 4760 interview questions