There is relative freedom to choose teams (during bootcamp) and projects (during planning), but most projects/teams are pointless and/or dull. People always seem to be doing A as a stopgap while they wait to move into B.
Not many options in London except AR/VR, which is becoming difficult to get into. You don't want to work on Workplace, do you?
People are constantly looking for "impact," which means moving an arid and unimaginative metric someone else has defined. It's a crushingly sad show of very smart and insightful individuals running around begging for leftover projects that may move some metric by 0.05%, which will let them keep their job for another semester.
Nobody knows how things work. When you ask why something is done in a certain way, it's likely the person originally responsible for it has just joined (and doesn't know anything and is just doing things at random), or has left, or is about to leave (so he/she is not incentivized to help).
Largely an oral and office-based culture struggling to get into the habit of writing things down to communicate, after work got hybrid and teams became intercontinental.
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