You are surrounded with a very smart group of people who are very eager to help out. Collaboration is something that is built into Tower's culture.
Some of the times you get to work on interesting problems.
Even though management lacks in experience they are receptive to feedback. They mostly listen and try to help you out with future goals.
The worst thing about this place is its siloed nature. This is true mostly for core engineering. It's almost impossible to get a view of why you are doing some stuff.
With time it has increasingly become "my way or the highway" sort of management.
As the firm is growing so is the bureaucracy. It's very hard to get things done without getting permission from 100 different people.
There is no way to grow up in the job. You just make more money and sit tight in hope that your superior resigns and they can't find someone external to replace them.
Be open about future ambitions.
Apart from just being receptive, people need to act on the feedback rather than dismissing it.
I have an onsite interview with three other candidates, it takes one day, and we have interviews with interviewers from three main engineering teams. They asked some coding questions but are generally easy, and a lot more questions about computer sys
First an on-campus interview, where the guy was very friendly and gave some brainteasers Then a phone interview, with some more math and computer science problems The final round, an on-site interview, consisted of a 2.5 hour written test, mostly o
It started with a code test and then moved to on site, which consisted of a few rounds. They were very thorough at each stage, running through my coding decisions, my projects, my background, and any research I had been involved with, as well as why
I have an onsite interview with three other candidates, it takes one day, and we have interviews with interviewers from three main engineering teams. They asked some coding questions but are generally easy, and a lot more questions about computer sys
First an on-campus interview, where the guy was very friendly and gave some brainteasers Then a phone interview, with some more math and computer science problems The final round, an on-site interview, consisted of a 2.5 hour written test, mostly o
It started with a code test and then moved to on site, which consisted of a few rounds. They were very thorough at each stage, running through my coding decisions, my projects, my background, and any research I had been involved with, as well as why