As mentioned by, Lime's technical challenges are very interesting and span a wide breadth. They are consumer company with their own vehicle. So there's typically consumer facing problems, hardware problems and IoT problems. Lime is also heavily dependent on its operation, so there are interesting software challenges for those domain.
Company culture is impact driven and being a small place, you can rise very fast if you're effective in solving issues
Recently, Lime hired some very strong tech leadership which wasn't there before.
-Scooters have a bad rep and it's a big headwind for companies' financial success. The financial outcome of stocks is still very unclear.
Go public
After phone interview with the HR, Lime offered me an onsite opportunity, the office was pretty nice, in a very high building, all the people are nice, a typical energetic start up. There were 3 rounds of interviews. Two programming question and one
The interviewer was 30 minutes late to the call. There were 2 questions, which included 1 LeetCode level medium and 1 LeetCode level hard question in 50 minutes. The interviewer wanted a running code with correct syntax and we had to design our own
Typical recruiter outreach then a technical screen through CoderPad. The engineer didn't seem to like working there and said nothing the entire time. At the end the interviewer looked up and down the code pointed out some wrong assumptions and said w
After phone interview with the HR, Lime offered me an onsite opportunity, the office was pretty nice, in a very high building, all the people are nice, a typical energetic start up. There were 3 rounds of interviews. Two programming question and one
The interviewer was 30 minutes late to the call. There were 2 questions, which included 1 LeetCode level medium and 1 LeetCode level hard question in 50 minutes. The interviewer wanted a running code with correct syntax and we had to design our own
Typical recruiter outreach then a technical screen through CoderPad. The engineer didn't seem to like working there and said nothing the entire time. At the end the interviewer looked up and down the code pointed out some wrong assumptions and said w