How to write an Interview Experience?
This is a sample interview experience to show the format of writing an interview experience. It would take just about an hour to write your interview experience, and it’s quite easy.
Hey geek! It's time to become a success story instead of reading them. Check out our most renowned DSA Self Paced Course, now at a student-friendly price and become industry ready. And if you are looking for a more complete interview preparation resource, check out Complete Interview Preparation Course that will prepare you for the SDE role of your dreams!
Feeling prepared enough for your interview? Test your skills with our Test Series that will help you prepare for top companies like Amazon, Microsoft, TCS, Wipro, Google and many more!
Include necessary tips and search your asked question on Google or GeeksforGeeks and include its link with the question so that anyone else can refer to it to learn about the solution. If you are not able to find any relevant link to the question on GeeksforGeeks or any other website then you can mention it with the question otherwise you can skip it. On GeeksforGeeks, you can find interview experiences for jobs and internships in product and service-based companies.
How to Write an Interview Experience?
You can create an article on https://write.geeksforgeeks.org/. After creating the article, the author may use the preview button to see how it looks and submit it for review and the status of your article will become Pending. The team reviews your article and gives you feedback in comments under the article and saves your article status to Awaiting Author. Finally, after you have made all the required improvements, your article status becomes In Review, which means it has been approved and is going to get published soon. When your article gets published, the status of your article becomes Published.
Below is a sample interview experience and get an insight on how to write your Interview experience.
Sample Interview Experience
- The first round comprised of 50 MCQ questions including aptitude, logical, C output questions, and technical portions (Test Duration: 1 hour):
- Quantitative aptitude and Logical part were much more predominant, the questions were more intuitive and not typical paper pen/formula based. They were not very difficult but were very tricky.
Suggestion: I would suggest doing practice from sites like GeeksforGeeks, Indiabix, etc. as it will give the confidence to solve problems.
- The technical aptitude part covered questions from computer networks, operating systems, data structures (particularly tree), digital electronics, and questions from microprocessors & other electronics topics. C output questions were also there.
- Suggestion: I would suggest doing quizzes from GeeksforGeeks to get in touch with all concepts of C and other subjects.
Tips: Solve the questions with a calm mind. Don’t stress yourself during the test because you have to do 50 questions in 60 minutes. Don’t spend too much time on any question if you are not able to do it on the first attempt.
Round-2 (Technical Interview Round-1)
- Questions from the project. My project was on REST, so he asked various typical questions on REST (Why, How, etc). He later asked me to design a REST API for a part of my project.
- He asked me to design an Uber Cab service. He gave me an instant scenario that there are 5 lakh drivers, and they all are sending a request to the server & database at a particular time. He asked how can you manage these requests efficiently. I gave answers by using the concepts of Load Balancer, Sharding, Master-Slave, etc. and he was pretty much happy to listen to the concepts.
- Later he gave me an instant of the above-designed Uber where sorting was the answer. So I gave him an answer using Comparator of java and wrote code for the same.
- Discussions on MVC architecture. He said suppose you click weather.com on any browser what happens if you use MVC architecture behind and what happens if you haven’t used MVC. We had a good discussion over the use of a Controller in MVC.
Tips: Explain using more diagrams. (I used 4-5 total pages in this interview)
Round-3 (Technical Interview Round-2)
- Again discussion on all projects.
- Discussion over REST and SOAP.
- I have used eXist-db (Native XML Database) as a database in one of my projects and MySQL in another. From there we went to discussions over SQL vs NoSQL. He kept on giving me instances one after other and asked which suits best on each of them(SQL or NoSQL)
- What happens when one ajax call is still running, and you send another ajax call before the data of the first ajax call comes back?
Tips: You should know each and every word of your Resume.
Round-4 (Managerial Round)
- Basic questions about team management and team conflict.
- What problems did you face in doing projects technologically wise and managing wisely too?
- He gave me instants which can arise during working in a team and asked what will you do in them.
- Some discussions over what technologies I know.
- Which project do you like the most and why?
Round-5 (HR Round)
- Tell me something about yourself.
- What differentiates yourself from others.
- Little discussions over my extracurricular activities are written in my resume.
- Team Conflict questions.
- What are your future plans related to further studies?
- Do you have any Location constraints?
Tips: Know yourself before any interview. Be calm & answer politely.
You can also check out our Interview Experiences Archive to get more insights about how to write an interview experience.
If you like GeeksforGeeks and would like to contribute, you can also write an article using write.geeksforgeeks.org See your article appearing on the GeeksforGeeks main page and help other Geeks. Please write comments if you find anything incorrect, or you want to share more information about the topic discussed above.