Take home code interview, Recruiter, Technical Interview, Hiring Manager. Technical we talked about projects I built and added to my resume. Straightforward interview process, easy to talk to. Took about 1 week to finish.
Interview questions [1]
Question 1
Take home code interview was average, fix bug in react app, simple algorithm question.
I applied online. The process took 6 weeks. I interviewed at Limeade (Seattle, WA) in Apr 2019
Interview
Phone screening, technical phone interview, take home code pen challenge, on site. They were very slow to respond. Coding challenges you have to do on your own time are a waste of time. They should be putting as much effort into the process as you.
I applied online. The process took 2 weeks. I interviewed at Limeade (Bellevue, WA) in Oct 2017
Interview
First a call with the recruiter going over mostly behavioral questions. People have already pointed out to have an emphasis on why you want to work for Limeade so get that ready. The recruiter talked a great deal about how fast the process moved and while it was fast in general the last part rubbed me the wrong way.
After the first interview I had a technical phone screen. The developer one the other line had a terrible connection and made it difficult to understand him but he was very patient and was happy to see the solution progress. I found out just a day later that I would be going to the on-site. It was 3 sets of 2 interviewers. Almost all technical questions except probably 3 behavior questions asked by each group of 2.
I would say this was my least favorite part. I would say that 2/3 were absolutely great and were similar to the online technical assessment but the other one was absurd. It was basically a recipe program this guy came up with and wanted to know how I would do it with very little guidance. APPARENTLY he did it this one specific way and was looking just for that one way. Once I figured out what he wanted me to do I drew a data-flow diagram for it on the whiteboard and coded it up in just 5 minutes or so. It was a really specific question. I later asked a senior developer I know that has done tons of interviews and said that he would not have used that data structure for that problem.
I then got a standard rejection email 3 days later. That was probably the most disappointing aspect as they had been so communicative and friendly prior. In fact, I was told I would be told very specific reasons why they wouldn't proceed if it came to that but not so.
Overall the company seemed pretty great but was hampered by a few oddities.