Interns Experience



From my perspective, GS believes more in testing one's thinking ability rather than the number of coding tools and techniques you know. I prepared by solving ad-hoc coding problems rather than simple straightforward topics.

GS comes under Fortune's top 100 companies to work with. It can give us an idea of the esteem quality of its work culture. During the internship they treated us as a full time employee and gave equal responsibilities. GS has a pretty diverse workforce. You get to learn and collaborate your work with people from different locations all over the world. Apart from usual stuff, various gaming competitions, inductions and celebrity networking sessions were conducted for the entertainment and personality development of the interns. I worked there on a web based trading application to add a rescue management tool. It provided me an awesome opportunity to learn a wide variety of technologies ranging from Hadoop and HBase in backend to AngularJS and Bootstrap in frontend. Along with the development part I dedicated a lot of time in learning new testing frameworks like Jasmine, Junit to test my code.

All interns at GS were assigned a 'Mentor' and a 'Buddy'. Both were quite friendly (they never let me refer them as 'Sir'). GS also follows an open door policy, you can walk in and share your ideas with anyone anytime. Besides, my mentor always guided me to learn as much as possible during my tenure as an intern rather than focusing on completion of my project.

During your internship, GS assigns you some meaningful work which is a part of their live projects hence it expects a reliable and quality development from your side. Also the company expects its interns to understand their business and work culture followed throughout the firm.

Getting a PPO is not at all an easy task. I always tried to give more than expected in the given time. I showed my excitement to learn new things, and used to ask a lot of questions. I also used to participate actively and came up with new ideas even when not asked.



My preparation for internship was mostly through the online competitive coding sites. I specially solved problems on GeeksforGeeks, InterviewBit and Hackerrank. I also looked some topics specific to companies on the internet which helped me to get a rough idea about the question asked.

Working at Samsung was a very nice experience. Apart from the project, we had many activities over there. They organised a Hackathon for us, celebrated the Interns' Day and we enjoyed a lot. The environment of Samsung is good. People are very helpful over there and you get a chance to learn and develop your skills. Samsung expects its interns to learn new things and learn about company's environment.

My project was on Internet of Things (IOT). I had to develop a sensing and recommendation engine for smart IOT. My mentor was really supportive. He used to guide me every time on what to do and what not. He cleared every single doubt and confusion I had and assisted me in every possible way.

When you are working as an intern, you need to be regular. You cannot procrastinate the work and have to complete it on or before the deadline. You need to interact with people and your attitude should be good because if they will find you annoying they are definitely going to throw you out. The PPO is majorly based on rating by your mentor. In Samsung, we had a coding round followed by two interviews – one HR and one technical.

Communication skills are important because during your internship, you have to present your projects and communicate with others. You have to be very fluent and confident about what you are saying. My advice to juniors would be, “Just do coding else you will not get anywhere”.

Ashish Kumar Ashish Kumar


I have done a lot of competitive programming which helped me get an intern in CodeNation. Besides that, I have read GeeksforGeeks and solved problems on Leetcode and InterviewBit. I also practiced to write code on paper and believe me it is tougher than writing on an IDE or a text editor.

Working at CodeNation was a nice experience and the environment was good. Since, I am new to development area it was a bit difficult for me to adjust in the culture. The best part was that they organized outing every week. One can work from home (not interns). Work hours are highly flexible. All employees are friendly and one can learn a lot from them.

Our project was based on Java rules which is a part of Aline: a product for increasing developer productivity. We had to analyze a lot of Java code of various products. I learnt a lot of concepts related to Java. We used Python for coding. In CodeNation, we used to directly report to our manager. Our mentor used to guide us and review our codes and we used to keep him updated about our current progress. The team at CodeNation is very small, so it was easier to communicate and clear our doubts.

Coding helps you to grab an internship but for surviving in the company you need to have good technical skills and development background. The company expects you to be sincere about your work and finish the project on time. They want their interns to be versatile. They are not going to teach you everything. So start developing anything that you like.
My advice to juniors is – switch to Linux environment from Windows and have a good command on data structures.

Vedika Loiya Vedika Loiya

Vedika Loiya(Microsoft)

To prepare for my interviews I mainly spent my time perusing through GeeksforGeeks, studying the data structure and algorithm tutorials. Specifically for my Microsoft interview, I spent some time looking over Operating Systems, as the company normally asks a few questions from this topic. I took competitive coding pretty seriously in my second year, so I was pretty confident in this aspect before the interview.

My time at Microsoft was amazing. We were individually assigned a mentor, who would guide us as we worked towards completing our respective projects. I think the memorable aspect of my time at Microsoft was probably the work culture. There were no fixed timings. We were allowed to come and go as we pleased as long as we met the deadlines that were set for us.

During my time at Microsoft I mainly worked on VSTS(Visual Studio Team Services). I was asked to improve the pre-existing contextual search algorithm, in the search engine. I mainly used Typescript(an improved version of Javascript), C# and JQuery for this task. My work on this project was both on the front-end as well as on the back-end, and I was asked to add extra features and functionality to the project. Initially, since I was unfamiliar with the languages, my mentor helped me in this regard. Since I was working on improving a pre-existing project, I normally had to consult with him at every juncture of the development process. He was really helpful, and his guidance was unparalleled.I completed the project to my mentor's satisfaction, and I think this was the vital factor that helped me clinch a PPO.
Advice for my juniors would be to utilise their time productively. They should work towards honing their coding skills and undertaking several projects, as these aspects are crucial during campus placements.

Kodali Bhargav Teja Kodali Bhargav Teja

Kodali Bhargav Teja(Arista):

Arista was always the company I was targeting. I was very interested in Operating Systems and Computer Networks, and these factors helped me decide that Arista was the company for me. To prepare for the interviews I mainly used Interview Bit. This website helped me develop an in-depth understanding of data structures and algorithms. I also made sure I was proficient in my knowledge of C and C++, before the interview rounds.

I had a fantastic time working at Arista. The work culture prevalent in the company is unparalleled. There was no dress code, and we were allowed to come and go as we please, as long as we kept to the assigned deadlines. My project was titled "GDB macros for IS-IS Routing Protocol". GDB is used to debug live processes or a dead process through its core file. We had to write scripts to walk through the IS-IS related data structures in the core file and dump their state so that the debugging process becomes easier. To proceed towards the project, we first had to understand the code of IS-IS protocol which was implemented in C and figure out the complex data structures which were used.

The people at Arista were really helpful. My mentor was really supportive. Whenever I hit a road-block in my work, he was always ready to help. He always encouraged me and my fellow interns to contact him if we ever faced a difficulty in completing the task that was assigned to us. I always worked diligently on the task that was assigned to me, and I made sure that all the code I wrote was free of bugs. This was the factor which helped me clinch a PPO at Arista.
I would advise my juniors to divide their time and master data structures and algorithms, as these topics are crucial. Coding skills cannot be developed in a short amount of time. So it is my advice to the juniors to utilise their time productively, and ensure that they make the most of it.

Vamsi Krishna Avula Vamsi Krishna Avula

Vamsi Krishna Avula(Google):

As the interviews approached, I didn't prepare specifically for them. I used to take part in programming competitions regularly, and this enabled me to perform well during the interviews. They help you improve your knowledge of data structures and algorithms.

My experience at Google was incredible. The work culture at Google is unparalleled. I especially enjoyed the food. During my time at Google, I mainly worked on two projects. I am currently not allowed to divulge the name of both these projects. My first project was a visualization service for a data/metrics monitoring library. My work was mostly on the back-end (Java). This project was launched during my internship. My second project was a dashboard on top of a Regression Analysis (and automated alerts), which our team has been doing. I had to write everything from scratch, using mainly Python and Javascript.

During my time at Google, I worked under a manager but I was assigned two mentors. Both of them were very helpful especially when I needed to ramp-up on internal tools and technologies.
I would advise my juniors to take mock interviews, either with their friends or seniors. This provides an impetus to your preparation. Anything you write in your resume is fair game for the interviewer. So do not write anything that you may not actually know completely about. Unless the question asked in the interview is very straight forward (like implement a Queue with 2 Stacks), don't give away the optimal solution immediately. Even if you do solve the question on the spot, they'll probably think you solved it before. Walk them through a brute force solution first. These were the points I kept in mind while preparing for my interviews.