I attended 75+ product based company interviews and these are the interview rounds for 99% of them, read on.
1/ Data Structures & Algorithms (DSA)
- Typically 45-60 minutes discussion
- You're given 1-2 DSA problems to solve
- You need to write the optimal executable solutions
- Explain time & space complexity
- Your code should pass every single test case
2/ System design/ High level design (HLD)
- Typically 60-90 minutes discussion
- You're given an abstract problem statement
- You need to explain the architecture, database modelling, API contracts
- Typically open ended questions, and outcomes are conversation driven
- Coding is rarely involved in this round, but be prepared to code if needed
- No one right solution, multiple ways, multiple scenarios discussion driven
3/ Low level design (LLD)
- Typically 60-90 minutes discussion
- You're given a generic problem statement
- You need to explain classes, attributes in them, how data flow works
- Avoid data redundancy in your design, follow SOLID principles
- Can expect to write code based on interviewer and discussion
- Be mindful of design patterns that can be involved based on problem
4/ Machine coding (MC)
- Typically 90-180 minutes discussion
- You're given a straight forward problem statement
- You need to write proper executable code for at least 1 core functionality
- You have to follow SOLID principles, design patterns where ever necessary
- Your code be flexible enough to incorporate changes
5/ Managerial discussion
- Typically 45-60 minutes discussion
- Questions about your projects, deep dive into challenges faced
- Questions that make the other person know you better (in life too)
- Situation based questions that can be answered with STAR format
- You're assessed based on your experience in dealing with problems
- Don't even think about lying or cooking up situations
6/ Cultural fitment
- Typically 30-45 minutes discussion
- Questions on how well you relate their company culture code and values
- Situations where you displayed a particular value in life/career and outcome
- Don't lie/ make up stories to align with a particular value
There are very few companies who host other interview discussions like Concurrency, Pair coding etc. But most of the companies have the pattern I listed above.
:)
Follow me Revanth Murigipudi for more such reads.
#interviewpreparation #interview #interviewexperience #softwareengineer
#datastructures #systemdesign #career
1/ Data Structures & Algorithms (DSA)
- Typically 45-60 minutes discussion
- You're given 1-2 DSA problems to solve
- You need to write the optimal executable solutions
- Explain time & space complexity
- Your code should pass every single test case
2/ System design/ High level design (HLD)
- Typically 60-90 minutes discussion
- You're given an abstract problem statement
- You need to explain the architecture, database modelling, API contracts
- Typically open ended questions, and outcomes are conversation driven
- Coding is rarely involved in this round, but be prepared to code if needed
- No one right solution, multiple ways, multiple scenarios discussion driven
3/ Low level design (LLD)
- Typically 60-90 minutes discussion
- You're given a generic problem statement
- You need to explain classes, attributes in them, how data flow works
- Avoid data redundancy in your design, follow SOLID principles
- Can expect to write code based on interviewer and discussion
- Be mindful of design patterns that can be involved based on problem
4/ Machine coding (MC)
- Typically 90-180 minutes discussion
- You're given a straight forward problem statement
- You need to write proper executable code for at least 1 core functionality
- You have to follow SOLID principles, design patterns where ever necessary
- Your code be flexible enough to incorporate changes
5/ Managerial discussion
- Typically 45-60 minutes discussion
- Questions about your projects, deep dive into challenges faced
- Questions that make the other person know you better (in life too)
- Situation based questions that can be answered with STAR format
- You're assessed based on your experience in dealing with problems
- Don't even think about lying or cooking up situations
6/ Cultural fitment
- Typically 30-45 minutes discussion
- Questions on how well you relate their company culture code and values
- Situations where you displayed a particular value in life/career and outcome
- Don't lie/ make up stories to align with a particular value
There are very few companies who host other interview discussions like Concurrency, Pair coding etc. But most of the companies have the pattern I listed above.
:)
Follow me Revanth Murigipudi for more such reads.
#interviewpreparation #interview #interviewexperience #softwareengineer
#datastructures #systemdesign #career