No space for personal life. You might need to work 12-15 hours a day on average. If you forget your personal life, you can survive. I didn't use the word 'work-life balance' because there is no life at all.
Expectations are more. Since your peers are living to work, you also have to live to work.
No training for tasks. You have to dive and swim. You cannot expect proper guidance for everyone.
Change in location/teams is very tedious. The teams are not assigned based on skillset.
Policies favor the company, not the employees. HRs use the phrase, "as per the policy," whenever you are raising any concerns. Your concerns are often turned down.
You have to adjust to team timing. Even when you are leaving at 5 p.m. in the evening, you might need to email "Leaving Early Today."
Your employees are humans, not mere machines. They have personal lives too. Consider freshers with post-graduation as freshers, not as engineers by designation, and don't pressurize them due to higher expectations.
We received an internship offer on campus. The first round was an online test consisting of general aptitude, OS, and basic computer science-oriented questions. Twenty candidates were shortlisted. We then had two rounds of interviews. * The first
There were 3 rounds: 1. Resume-based and projects. 2. Stress round solving a coding problem. 3. General round about puzzles and coding. Questions about why dynamic programming is useful, algorithm time complexity, trees, stacks, and queues.
It was a three-round process, with two technical interviews followed by an HR interview. The technical interviews covered algorithms, operating systems, and systems architecture. The HR interview was standard and not impossible to crack.
We received an internship offer on campus. The first round was an online test consisting of general aptitude, OS, and basic computer science-oriented questions. Twenty candidates were shortlisted. We then had two rounds of interviews. * The first
There were 3 rounds: 1. Resume-based and projects. 2. Stress round solving a coding problem. 3. General round about puzzles and coding. Questions about why dynamic programming is useful, algorithm time complexity, trees, stacks, and queues.
It was a three-round process, with two technical interviews followed by an HR interview. The technical interviews covered algorithms, operating systems, and systems architecture. The HR interview was standard and not impossible to crack.