The pay is pretty good and the problem is very interesting.
There are also a lot of great people who work there on the frontlines.
Leadership. There are probably other problems, but this is so much bigger than anything else, other stuff isn't worth mentioning.
In short, they don't know how to run a big organization well.
This mostly falls on the CTO who makes rash decisions without thinking them through. The CEO is to blame as well for enabling such bad leadership, as he seems to sit back and just let it happen.
The CTO seems to excuse chaos by saying this is how a production companies work. While production-focused organizations do sometimes change on a dime or have to force the organization to hyper focus on particular bare bone features, the CTO seems to feel that it excuses any type of chaos induced by him or others at his level upon everyone below.
That type of stuff slows development down and, in a production-focused organization, can kill it. But, instead, the CTO uses it as an excuse.
CTO also seems happy to let go groups of people that he feels have no value. I think leadership has that right, but some of the people let go were people that would have had value in other parts of the organization had he only asked. This is especially important, given he wants us to move faster than ever before.
This type of reactive leadership, including his personality, has led to an unfortunate toxicity at the top. Things have become much more political with a 'find someone to blame' culture.
I'd say more, but other commenters have brought up other aspects already.
New leadership, particularly the CTO, is needed. Or, he needs to have a "come to Jesus" moment realizing that his approach is hurting Torc, not helping it, and hopefully change it completely.
First step was a 105-minute HackerRank test with I think five problems that I was required to do in C++. I passed despite not getting anything for the shortest path problem. The next step was a CodePair interview with someone who does ML stuff at To
One round OA, one medium, one medium/hard, and one hard question. Second round zoom interview, HR emailed one day before asking for project presentation at the beginning of the interview, second half of the zoom interview is one coding question medi
The interview process was smooth and well-organized, starting with a screening call with the recruiter, followed by a 30-minute chat with the hiring manager. The virtual onsite interview, which took around 3-4 hours, delved deeper into software skil
First step was a 105-minute HackerRank test with I think five problems that I was required to do in C++. I passed despite not getting anything for the shortest path problem. The next step was a CodePair interview with someone who does ML stuff at To
One round OA, one medium, one medium/hard, and one hard question. Second round zoom interview, HR emailed one day before asking for project presentation at the beginning of the interview, second half of the zoom interview is one coding question medi
The interview process was smooth and well-organized, starting with a screening call with the recruiter, followed by a 30-minute chat with the hiring manager. The virtual onsite interview, which took around 3-4 hours, delved deeper into software skil