A lot of bright people working with you or near you. Agile is growing in the company. Good work environment. Nice desks. There is the pantry, which is really nice. View to St Paul's. Nice perks. Many courses to learn new things. In most teams, a relaxed environment. You work for someone much better than Trump.
Not a good place to cause an impact. Few opportunities to do that there.
There is some micromanagement, not as bad as in many other places I worked, but it's at least "mili-management." They don't monitor what you're doing all the time, but many decisions about products come top-down without anyone asking your opinion.
Also, there is little proximity between R&D and business areas. I think only high management has a good vision of how the company is placed in the market.
Career progression is many times a political decision, not tied at all to results.
I see many people in management areas who are really good, but others that you really ask yourself: "Why? What's that person doing as a manager? How did that happen?"
The best thing you can do is finish the Linux migration and give more credibility to agile worldwide. However, to make it really perfect, it would be nice to change completely how problems reach engineers, allowing them to solve business problems and not just implement what's in the CTO's mind. You might get impressed by how much innovation you are probably blocking with the way you make decisions.
If you read this and you say either "yes, but this is complicated to change, we can't be perfect" or "but there are good reasons the company should be like that" – think again. You can do better, and I wish from the bottom of my heart you will someday.
I applied through a recruiter. The process took 2 weeks. Recruiter LinkedIn messaged me. We had a 30 min screening call. Followed by 3 technical rounds. * The first one was Leetcode- DP problem (Fibonacci number variation). * The second one was Cod
It's a classical interview process. It started with an HR round, in which they wanted to know you. After that, there was R1, a coding interview, where they asked one LeetCode medium question. In R2, they asked another LeetCode medium question for cod
HR contacted me two weeks after applying online. The interview process involved: * A one-hour technical Webex interview. * Four to five hours of on-site interviews, each lasting one hour. During the on-site interviews, two team members per ses
I applied through a recruiter. The process took 2 weeks. Recruiter LinkedIn messaged me. We had a 30 min screening call. Followed by 3 technical rounds. * The first one was Leetcode- DP problem (Fibonacci number variation). * The second one was Cod
It's a classical interview process. It started with an HR round, in which they wanted to know you. After that, there was R1, a coding interview, where they asked one LeetCode medium question. In R2, they asked another LeetCode medium question for cod
HR contacted me two weeks after applying online. The interview process involved: * A one-hour technical Webex interview. * Four to five hours of on-site interviews, each lasting one hour. During the on-site interviews, two team members per ses