If you turn a blind eye to all the cons and agree to sacrifice your life/work balance and work long hours in a very harsh atmosphere, then you can be promoted quite fast.
Good work-from-home policy.
The culture is very toxic and fear-driven. An employee might be fired without any meaningful explanations the next day after discussing plans for the next few months with his/her manager.
Due to high stress at work, from time to time I have sleep disturbances. The most severe one lasted a whole week and eventually resulted in me calling an ambulance.
Everyone's obsessed with KPIs, not the real quality of deliverables. Projects are often badly scoped. As an engineer, you're just a "resource" that might be deployed to any project at any time without even asking you.
Working long hours is encouraged by the company's culture, although not compulsory. If you're perfect at everything (speed, quality, etc.), you'll reach only the "Intermediate" level at a performance review. To get a higher score, you'll need to seriously sacrifice your life/work balance.
Not LeetCode-like, but questions that require knowledge in multithreading and a good understanding of design patterns, which is a breath of fresh air. Interviewers were nice and patient. Also, should have a general sense of how databases work.
Revolut approached me, and the process of booking the "introductory" interview was easy. That's where the "good" ends. The interviewer was a few minutes late, which I can understand, and spent some time explaining the process. This is one of the lon
The interview process involves a few stages. It starts with a live coding interview, followed by a technical conversation and system design. All stages are focused on solving a problem with given requirements. Before every stage, a recruiter sends
Not LeetCode-like, but questions that require knowledge in multithreading and a good understanding of design patterns, which is a breath of fresh air. Interviewers were nice and patient. Also, should have a general sense of how databases work.
Revolut approached me, and the process of booking the "introductory" interview was easy. That's where the "good" ends. The interviewer was a few minutes late, which I can understand, and spent some time explaining the process. This is one of the lon
The interview process involves a few stages. It starts with a live coding interview, followed by a technical conversation and system design. All stages are focused on solving a problem with given requirements. Before every stage, a recruiter sends