Not a good company for entry-level
Not a good company for entry-level
some teams are good, work life balanced. free food(not as good as before), free snacks.
Some managers are pretty bad. Micromanagement a lot. And he acted like a king, and you should not obey him. He judged your work based on points, always keeping pressure on you. And he would do something really annoying: email you about your 'performance,' BCC someone higher level, making you look bad. This is not a good manager. He compared you with senior developers with many years of experience, asking why you cannot figure things out. Such a rude guy. Even if you found another good team to join, he warned you about low performance being bad, but did not let you go. Such a drama person.
You can either work with this person, or just find another company.
Additional Ratings
Was this helpful?
LinkedIn Interview Questions
LinkedIn Interview Experiences
Software Engineer
The phone screen was a combination of systems and coding. It was relatively straightforward, all things considered. The recruiters at LinkedIn were great and made me feel at ease. The process was overall very smooth.
Software Engineer
Contacted by a recruiter through a resume database. Completed a HackerRank coding challenge, a 30-minute phone screen with the recruiter, and then two one-hour technical phone interviews. The interview questions were pretty standard (algorithms/dat
Software Engineer
The interview process consisted of: * 1 round design * 2 rounds algo + data structure * 1 round tech communication * 1 round HM Technical questions were very common. I handled them quickly. The HM asked a very high-level question, such as h
Software Engineer
Mountain View, California, United StatesMay 23, 2025The phone screen was a combination of systems and coding. It was relatively straightforward, all things considered. The recruiters at LinkedIn were great and made me feel at ease. The process was overall very smooth.
Software Engineer
Sunnyvale, California, United StatesNovember 1, 2016Contacted by a recruiter through a resume database. Completed a HackerRank coding challenge, a 30-minute phone screen with the recruiter, and then two one-hour technical phone interviews. The interview questions were pretty standard (algorithms/dat
Software Engineer
Mountain View, California, United StatesNovember 1, 2015The interview process consisted of: * 1 round design * 2 rounds algo + data structure * 1 round tech communication * 1 round HM Technical questions were very common. I handled them quickly. The HM asked a very high-level question, such as h
