Tip 1: Do not deep dive into one subject if you get bored. Immediately switch to another subject. For example, if you have completed four DSA problems on arrays and feel a mood swing, switch to questions on trees, stacks, or linked lists. If you get bored with DSA, switch to a development framework, and vice versa.
Tip 2: For DSA problems, always start with a brute force approach and then optimize the code.
Tip 3: Always dry-run the code by making diagrams and indexes. In interviews, do the same with an oral explanation for each step.
Tip 1: Include projects on your resume for which you are confident in your complete architectural knowledge.
Tip 2: Explain your roles and responsibilities in detail for your current projects.



Check if a pair with the given Sum exists in Array (Two Sum).
I started with a brute force approach using 2 For loops and dry run the same then used the hash map approach to have better time complexity followed by dry run and then also told binary search approach if array got sorted.



I started with a brute force approach using 2 For loops and dry run the same then used the stack approach to have better time complexity followed by dry run.
Explain about these Spring annotations like @Controller, @RestController, @Entity, @Id, @RequestMapping, @GetMapping, @Query, @PathVariable, @RequestParam
Explain the MVC design pattern.
SQL query to fetch highest salaried employees from each manager (Practice)
Explain Microservice architecture and its advantages over monolithic. (Learn)
Explain HTTP codes in rest like 404, 200, 500. (Learn)
Technical managerial round.
Minimum cuts required to divide the cake exactly into 8 pieces.
Explain complete architecture for current project.
How will you contribute initially if selected?
Why looking for a change?

Here's your problem of the day
Solving this problem will increase your chance to get selected in this company
How do you remove whitespace from the start of a string?