While it may seem appealing on their website, you don’t want to work there.
LI, as it is today, is a place where interns come to die.
It’s a place where you won’t learn anything valuable for your future career. You may learn how LI works, but it’s all in-house.
There’s no valuable knowledge that you can learn from working here.
After LI was acquired by MS, it’s no longer the same company it was a couple of years ago. It has its own - rather bad - in-house software, which they can’t afford to have good developers to work on. So they only hire contractors these days to make it function for the time being.
There’s no future for any intern who comes to work here. All you’ll learn is LI infrastructure, which is useless for you if you plan to have any future.
My suggestion: avoid at all costs!
P.S. I’ve been working for LI since 2015. It’s not a place where you want to work.
It was a smooth process. HR called me and scheduled an interview. There were two rounds: 1. Coding: They asked almost the same questions mentioned here by others. 2. Operational round: Three questions were asked related to the curl process, 3-tier
I had 2 stages in the interview process. The first interview round was about solving and implementing a DSA problem. The second round consisted of a discussion about projects in my resume.
Had the beginning of the call with OS fundamentals on thread vs process, process synchronization, and the screening. Two LeetCode questions were asked: one easy on Trees and one difficult on backtracking.
It was a smooth process. HR called me and scheduled an interview. There were two rounds: 1. Coding: They asked almost the same questions mentioned here by others. 2. Operational round: Three questions were asked related to the curl process, 3-tier
I had 2 stages in the interview process. The first interview round was about solving and implementing a DSA problem. The second round consisted of a discussion about projects in my resume.
Had the beginning of the call with OS fundamentals on thread vs process, process synchronization, and the screening. Two LeetCode questions were asked: one easy on Trees and one difficult on backtracking.