Great people! Everyone is so kind and helpful, and you will never feel like the smartest person in the room. Someone will always be better than you, but you can always learn from them.
Free food and generally decent company culture and benefits.
Meaningful career development and a decent product.
Good learning opportunities.
Starting to lose sight of what made LinkedIn great and blindly chase profits.
Deteriorating culture. There is much more pressure from leadership, so we are doing things faster, but things are being built with worse quality. Adopting a "Fast and scrappy" mentality, which really hurts the overall system structures and engineering excellence.
Leadership is overly focused on chasing A.I. instead of developing impactful products that boost the value of Premium subscriptions.
Leadership needs to understand that breaking fast and developing fast isn't always a good thing. Our infrastructure has much more errors than before.
People are getting more burnt out because of layoffs and heavier work pressure. Morale is low, and employees are not as helpful to each other because no one has time or bandwidth to help.
If things keep going the way they do, LinkedIn will cheapen its brand and we might lose our position when a better competitor emerges.
I was referred by a friend. Firstly, I had a phone screen where I was asked about a string-related question and a question about reading logs. Then, I was scheduled for an onsite interview. The design question was hard because I had never encountere
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
LinkedIn's interview process was extensive; they really want to ensure you're the right person for the job. I had three phone interviews before being brought on-site, where I then had five one-on-one interviews. The technical difficulty of the inter
I was referred by a friend. Firstly, I had a phone screen where I was asked about a string-related question and a question about reading logs. Then, I was scheduled for an onsite interview. The design question was hard because I had never encountere
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
LinkedIn's interview process was extensive; they really want to ensure you're the right person for the job. I had three phone interviews before being brought on-site, where I then had five one-on-one interviews. The technical difficulty of the inter