Problem of the day
Tip 1 : Do not rush into things. Learning takes time. Focus should be on the concepts and not just on leaving topics half-prepared. Devote 70% of both time and effort to DSA. I solved a total of around 500 questions on sites like GFG and Leetcode. Do not repeat similar questions just to increase the count of the number of questions
Tip 2 : Competitive Programming is a bonus and not a necessity, rather focus on core DSA based problems before trying CP. Do not pursue CP if you do not like it. Devote that extra time to core CS subjects and aptitude preparation.
Tip 3 : Projects play an important role too, do no ignore them. Try to get your hands dirty with a little bit of every field i.e., frontend, backend, and database.
Tip 1 : Try to make a single-page resume. Highlight skills, projects, and work experience more than CGPA. Ensure proper spacing and font to maintain professionalism.
Tip 2 : Does not lie on a resume. Everything written on your resume must be known by you in and out.
The test was in the morning from 10:00 to 12:00. It was a two-round test. There was a 45-minute MCQ-based Technical and Cognitive Assessment Round. Only those candidates who cleared this round could sit in the next round, a 45-minute coding test. There was a sectional cutoff that needed to be cleared in order to proceed to the coding round. The CoCubes test platform was fairly easy to understand and user-friendly.
The coding round was fairly simple. It had two very easy array-based questions.
I used the Sieve of Eratosthenes. Created a sieve array whose size was equal to the maximum number in the array given. Then filled the sieve using the algorithm.
I wrote a simple O(n) solution
This was basically a communication test, basically designed to test the English skills of the candidate. It was not an elimination round. There were several sections in this test where candidate would hear phrases/questions and had to repeat/answer them by properly pronouncing the text.
This was a Technical + HR interview. It was in the afternoon around 12 pm. As the role was Data Engineer intern, the interviewer wanted to know whether or not I had built some projects related to this field. Most of the interview went by him asking questions based on my projects. First I was asked to explain about a project then a lot of follow-up questions were asked.
Told him about my tech-stack.
Suggested some improvement on my projects.
Told him how interested I am in this field and this company. Also told him how passionate.
I was not able to answer this question.