Tip 1 : Get Familiar with basic data structures and do competitive coding using those data structures. if you are beginner and stuck from where to start then don't waste your precious time in finding it by yourself. I recommend you to take some popular Data Structure courses which will be your road map. You can also take Coding Ninja course it is really very helpful during the preparation.
Tip 2 : Have Patience, things will not change over night but yes it will improve gradually. Try to understand the concept and logic behind the problem statement. It doesn't matter how much how much questions you have solved, the only thing that matter is how well you have understand the concept.
Tip 3 : Even after solving try to explain the working and logic of your code to yourself, it will give you an extra confidence. Mostly in coding interview, interviewer will ask you to explain the working of code.
Tip 4 : Consistency and Hard Work is the key to crack any interview. Don't stop applying, usually people get frustrated after getting rejected from companies and end up switching the field. Always remember quitting is not the solution for the problem, give yourself some time as good things take time.
Tip 5 : Believe in yourself, Confidence will give you an upper edge over all other applicants. Company also look for confident people who are ready to learn new stuff and are humble in nature because after getting recruited you have to work in a team of developer.
Tip 6 : Prepare well for your projects and introduction part, it's the most common question which is asked in almost every interview.
Tip 1 : Resume is the most important part of your recruitment, don't make it so fancy. Keep it simple and concise.
Tip 2 : Follow the standard pattern, you can also refer to resume related blogs in coding ninja blogs section.
Tip 3 : Prepare well for all the skills you have mentioned in your resume. If you don't have strong command over the skills you have mentioned in your resume then don't mention them. Interviewer don't like bluff.
Tip 4 : If you have any internship then prepare well for your internship experience and the project on which you have worked during that internship
This round was conducted in two part, first part was based on quantitative aptitude and verbal skills and other part was having 2 coding question. First 60 minutes was dedicated for Aptitude and verbal part and rest 60 minutes was for coding. There were also negative marking for incorrect answers.



Given array/list can contain duplicate elements.
(arr[i],arr[j]) and (arr[j],arr[i]) are considered same.



The Interview panel was having 3 panelist, HR, MR and TR. HR had begin the round with the basic introduction and then asked me about my projects. Then MR asked me questions related to my projects and internship, there were many questions that were asked to me by MR. I will list them below one by one.
1. Event looping in Node.js
2. Middleware in Node.js and where they are use?
3. How a Node.js server handles then incoming request?
4. Create a demo server using express.js and express router?
5. Promises in JavaScript?
6. What is ORM?
7. what will be the difference between a normal project and a project with ORM?
8. Working of Async and Await keyword?
9. Master-Slave relationship in DBMS?
10. Views in DBMS?
11.Difference between Drop, Delete, Truncate?
12. What are stored procedure?
13. Use of normalization and de-normalization?
14. Joins and how it works?
15. How you will make an HTTP request from Node.js server?
16. What is NPM?
17. How to deploy a Node.js Server?
18. What are event handling?
TR also asked some question related to OOPS, they were very basic questions like Polymorphism, Inheritance, Diamond Problem, Pointer vs References, Garbage Collection, Function overloading vs overriding, Friend class, Friend function.
then at the end HR took the interview and asked me about my family details and then she explained me about TCS bond.

Here's your problem of the day
Solving this problem will increase your chance to get selected in this company
To make an AI less repetitive in a long paragraph, you should increase: