First round was with a recruiter who was very nice and the recruiting team was very responsive / supportive throughout the process. Second step was a phone screen with an engineer to talk about experience and projects. Third stage was a take home working with a proprietary API. Fourth stage was described as two hour long pair coding sessions. One would be 'algorithm based' and the other would be 'going over take home'. Received brief feedback notes from the take home and a very general idea of what the algorithm problem could look like. Spent some hours prepping for these. When hour long coding interviews started was where things went off the rails in my opinion.
In the 1st algorithm hour, I was thinking out loud and the interviewer would stop me and say 'no, that's not what we're supposed to do' and point me back to the directions. It was tough bc that shook my confidence, and I could read, so even though I maybe was going in the wrong direction, I would have figured that out. They also seemed to be impatient with me and it was clear they wanted me to go faster. I was originally told that interviews wouldn't focus on getting to the solution but see how I collaborate and think through problems. I felt immediately like I wasn't doing well and that got in my head. I could have done better if the interviewer were perhaps more patient and didn't focus on me getting to the solution.
They said at the end of the hour 'oh well we didn't get to test it', implying that we should have not only been able to get to the solution, but should have been able to write tests all in about 50 mins bc they also said they wanted to leave 10 min for questions at the end. The 2nd hour (50 min) tech was directly after the first and we were to refactor my take home to be more proficient. We came up with an overview in terms of a solution that I had thought of before the call. The interviewer was also not patient enough. At one point they even said 'let me do this part so we can get through it'.
Confidence shook once again, and my brain basically shut down while thinking ' oh crap, they don't think I'm good enough for xyz reason'. I hope the company reads this, bc it would be great, especially for internship-like roles that your interviewers focus more on collaboration and working through a solution together. At the end of the day, I was rejected because I didn't have enough experience...for a returnship (which is an internship, let's be real). Oh, and that wasn't the end of the interviews. I still had another hour the next day of cultural interviews. It was such a long process and was heartbreaking going through that many rounds to be rejected.
I wish they had rejected me after the tech round instead of making me go the final round. Also, it's worth mentioning that everyone was nice, but I think the tech interview outcome wasn't fair nor is that how junior people should be assessed.
Why do you want to work at Lattice? Tell me about your experience.
The following metrics were computed from 1 interview experience for the Lattice Full Stack Engineering Returnship role in United States.
Lattice's interview process for their Full Stack Engineering Returnship roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Lattice's Full Stack Engineering Returnship interview process in United States.