Almost every LinkedIn-built internal tool has a terrible user experience: it's slow, unreliable (crashes, errors), and has a terrible user interface.
There are constant service outages that stand in the way of work and hurt productivity.
Most repos' trunks are constantly broken.
Platform and framework teams are understaffed. Oftentimes, you depend on their help to get yourself and your team unblocked, but they "don't have bandwidth." They ask you to create a ticket for them, but it might take 1-2 months for them to look at it.
Many people lack communication skills (in part due to severe English unfamiliarity). We are supposed to speak English at work, but the hiring criteria don't seem to prioritize English skills. In meetings, it's almost impossible to understand some people, and even using audio transcription doesn't work.
There is no culture of timeliness. People are constantly late for meetings, and meetings always run over the allotted time. People tend to interrupt speakers in the middle of a presentation to ask a question or to raise a concern instead of waiting until the end.
The SVP of engineering is a joke. He is so awkward, especially after watching his all-hands meeting where he used the F-word just to sound cool.
I was contacted through LinkedIn InMail for a 30-minute conversation with a recruiter. Afterwards, I had a 1-hour technical interview with a software engineer. The final interview was also a 1-hour technical interview, but with a different software
After submitting my resume, the recruiter contacted me and gave me an interview. I actually had two phone interviews. The interviewers were very nice, and the problems were not difficult. They asked about my experience, my past projects, and some sof
I had one technical phone screen, which was easy. Then I was called onsite for a set of five rounds. It was a long day of interviews. The interviewer in the first algorithm round had a fixed solution in his head and could not accept any other approa
I was contacted through LinkedIn InMail for a 30-minute conversation with a recruiter. Afterwards, I had a 1-hour technical interview with a software engineer. The final interview was also a 1-hour technical interview, but with a different software
After submitting my resume, the recruiter contacted me and gave me an interview. I actually had two phone interviews. The interviewers were very nice, and the problems were not difficult. They asked about my experience, my past projects, and some sof
I had one technical phone screen, which was easy. Then I was called onsite for a set of five rounds. It was a long day of interviews. The interviewer in the first algorithm round had a fixed solution in his head and could not accept any other approa