Relaxed environment, room to grow and learn from other people, interesting work. My team was very independent, and we were making most decisions on the direction of the product.
I don't have any major cons.
The high-level direction and goals coming from upper management were often lacking, leaving it up to us to find impact and define our own version of impact. Sometimes this was good, but I think for our team, it was definitely overdone.
I was contacted by a recruiter for a London Software Engineer position. There were 4 interview stages. After a week, I received a rejection email from the recruiter. Conclusion: solve a ton of LeetCode problems, especially medium, and prepare to l
90-minute technical interview that consisted of 4-5 moderate to difficult questions. The recruiters I liaised with were very nice and encouraged me to apply again despite being unsuccessful the first time around, as they said this was very common.
For phone screening sessions, before the virtual onsite. Leetcode questions, about two questions at medium levels within 45 mins. The interviewer asked about time complexity and space complexity. The interviewer doesn’t give much hints but is calm an
I was contacted by a recruiter for a London Software Engineer position. There were 4 interview stages. After a week, I received a rejection email from the recruiter. Conclusion: solve a ton of LeetCode problems, especially medium, and prepare to l
90-minute technical interview that consisted of 4-5 moderate to difficult questions. The recruiters I liaised with were very nice and encouraged me to apply again despite being unsuccessful the first time around, as they said this was very common.
For phone screening sessions, before the virtual onsite. Leetcode questions, about two questions at medium levels within 45 mins. The interviewer asked about time complexity and space complexity. The interviewer doesn’t give much hints but is calm an