The company is filled with good people who strive to do a good job.
Your experience will depend almost entirely on the team you're on. My experience was that their management style is very hands-off and respectful of your own process, until they see that you're going in the wrong direction.
They're not going out of business anytime soon. Prospects look good and they have resources aplenty. A good career choice for the average socially-unconscious geek with no other interests other than the suburban dream.
Each project in the company has its own tech stack and processes. You will only experience what your team is directly working with, but you will hear about teams using ancient technologies that should have been put to rest years ago. If you are there long enough, you will eventually have to collaborate with another team, and you'll find out how hard it is for people to effectively communicate given the way things are set up. Also, you might get attached to the project you're working with and the people involved – don't! Because at any time they might decide to move people around to address some 'need'. Also, if you're at all conscious about what you eat (most tech people are not, but if you are), then get used to cooking for yourself because the cafeteria food doesn't cut it.
Keep meetings to a minimum for engineers. Do not declare that something is "unacceptable" without understanding how and why it got there. Tech debt is a reality; do not focus so much on new dev efforts so long that you miss addressing this debt.
I had a call with HR who scheduled a call with a senior engineer. HR mentioned it would be a technical interview, so I prepared accordingly. However, the interview focused more on what I am currently doing at my present company. I received a call fr
I had two phone interviews first: one for a Senior Software Engineer position and one for an Architect position. The first phone interview asked about my background and my projects. I don't remember exact technical questions. The second phone inter
The first round was a tech screen with a typical DSA question. The onsite was a full day, where I was asked to solve a full project in 90 minutes. The rest of the rounds involved answering questions about it.
I had a call with HR who scheduled a call with a senior engineer. HR mentioned it would be a technical interview, so I prepared accordingly. However, the interview focused more on what I am currently doing at my present company. I received a call fr
I had two phone interviews first: one for a Senior Software Engineer position and one for an Architect position. The first phone interview asked about my background and my projects. I don't remember exact technical questions. The second phone inter
The first round was a tech screen with a typical DSA question. The onsite was a full day, where I was asked to solve a full project in 90 minutes. The rest of the rounds involved answering questions about it.