Mostly great colleges.
Good managers who care about their employees.
Transparency (anyone can find out what other employees are working on).
Opportunity to get training on the job.
Employees are encouraged to move around, and there are programs specifically set up for employees to find the right team.
Management is becoming more concerned about the needs of developers (everyone getting new computers and much bigger monitors).
Some good technical work is done depending on the team.
A lot of what you experience can vary drastically depending on your team.
Unfortunately, some teams may have to maintain applications written using outdated technology, but I think that is slowly changing for the better.
Some internal politics to deal with, but I think this is inevitable in a company of this size.
The company is going in the right direction; keep it that way.
Give employees more structure.
Focus on ways to improve the software code quality and methodology to retain and attract talented employees.
For the first phone interview, I didn't receive the call. The recruiter then scheduled another one for me. The phone interview took an hour. The compiling function of the online coding tool went down, so I had to talk through my code with the intervi
Start with whiteboard coding, then ask questions on C++ STL and Algorithms. Usually, two engineers are present. One asks technical questions, while the other asks general ones about your background and last project. If everything is going well, the
Start with a phone interview, possibly two. Then, an onsite interview typically takes a day or half. Questions are very traditional: * Data structures * Algorithms * Language details * System design * Low-level concepts * Operating systems * Knowle
For the first phone interview, I didn't receive the call. The recruiter then scheduled another one for me. The phone interview took an hour. The compiling function of the online coding tool went down, so I had to talk through my code with the intervi
Start with whiteboard coding, then ask questions on C++ STL and Algorithms. Usually, two engineers are present. One asks technical questions, while the other asks general ones about your background and last project. If everything is going well, the
Start with a phone interview, possibly two. Then, an onsite interview typically takes a day or half. Questions are very traditional: * Data structures * Algorithms * Language details * System design * Low-level concepts * Operating systems * Knowle