Very good and smart people (developers), a lot of money (for a regular developer), snacks, food, perks.
Management - the only reason management exists is to control your behavior and punish you. They have no clue about the project, no clue about roadmaps, no idea about technology, and so on. The entire culture is poisoned because it is built on constant competition between people who are supposed to work together. People behave like they are mining gold in Alaska. The more you mine, the more you get. Zero teamwork.
The corporate culture encourages individualism and ignores teamwork.
Code - it is a separate sad story. I've never seen such a huge and bad code repository. Basically, the entire codebase is written using static function calls and ignores the existence of design patterns.
Interviews - the interview process looks like you will be fighting with dragons every day, but in reality, you will most probably be struggling, surfing through posts and lame docs, trying to figure out how to implement one more trivial thing in PHP.
I applied online. The process took two weeks. The onsite consists of four rounds: - One traditional coding round - One AI-enabled coding round where you have access to an AI assistant - One system design or product architecture round - One behaviora
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
Generic LeetCode-style questions, many tagged as Meta, mean that extensive preparation is required to perform well in the technical interview. The experience varies significantly, as some interviewers provide hints and guidance, while others expect c
I applied online. The process took two weeks. The onsite consists of four rounds: - One traditional coding round - One AI-enabled coding round where you have access to an AI assistant - One system design or product architecture round - One behaviora
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
Generic LeetCode-style questions, many tagged as Meta, mean that extensive preparation is required to perform well in the technical interview. The experience varies significantly, as some interviewers provide hints and guidance, while others expect c