Smart Team, High Stress
Smart Team, High Stress
People here are really smart, passionate, and diligent. It's good to work and learn from them.
Stressful, constant sense of urgency. Directions can change very quickly, and scope is not protected at all. For example, I have to do frontend work even though I do not have frontend experience and was not hired for it.
Speed to build a feature is definitely important, but it is also important to consolidate things and make sure each feature delivered is solid, or you would end up with a lot of tech debt and get backfired, burning more time.
Additional Ratings
Was this helpful?
Applied Intuition Interview Questions
Applied Intuition Interview Experiences
Software Engineer
1 online tech round. Virtual onsite: 3 tech rounds + 1 hiring manager round. The coding questions are difficult. If you passed, it moved super fast, and you could ask for feedback when being rejected.
Software Engineer
The interviewer was very nice and helpful throughout the whole process. The question was hard to implement within 45 minutes, to be honest. Good experience overall, but I didn't get to move forward.
Software Engineer
Self-introduction and brief project introduction for 5 minutes, and then coding problems. The thought process was straightforward, but implementation details were hard. I did not make it all correct in the end; it had a sharp, abrupt ending.
Software Engineer
Mountain View, California, United StatesNovember 10, 20251 online tech round. Virtual onsite: 3 tech rounds + 1 hiring manager round. The coding questions are difficult. If you passed, it moved super fast, and you could ask for feedback when being rejected.
Software Engineer
United StatesNovember 8, 2025The interviewer was very nice and helpful throughout the whole process. The question was hard to implement within 45 minutes, to be honest. Good experience overall, but I didn't get to move forward.
Software Engineer
United StatesNovember 6, 2025Self-introduction and brief project introduction for 5 minutes, and then coding problems. The thought process was straightforward, but implementation details were hard. I did not make it all correct in the end; it had a sharp, abrupt ending.
