Takes great care of engineers, doesn't kick older ones to the curb, and usually has challenging work to do.
Great for ancient-technology spelunkers.
We used to rush new features out too quickly, leading to decades' worth of weird legacy systems that few understand, with no real automated testing. Now, we're focused more on stability and making better choices, but the pace of improvements is slower, and the overall risk hasn't really been balanced out yet. Some problems with managers who did things the old way are still in charge, but we're trying to adjust.
Put people with expertise in testing, architecture, stability, and design in charge of that sort of thing. Have legacy managers focus on cleaning up their legacy systems while learning new skills.
I went through interview day, which consisted of an online exam and in-person interviews. The online exam changes regularly, but in my case, the task was to simply create an event-based notification system for notifying analysts of price changes. A
The interview consisted of a telephonic first round, followed by an in-person technical round. It was a fairly run-of-the-mill interview process. Be prepared to write code on pen and paper for fairly straightforward problems. The interview focused o
We had a phone interview two weeks ago. They asked me some basic questions on C++: * Constructor (ctor) * Destructor (dtor) * Static keyword * How to call C code Algorithm: * Big O notation * Hash tables * Bubble sort Database (DB):
I went through interview day, which consisted of an online exam and in-person interviews. The online exam changes regularly, but in my case, the task was to simply create an event-based notification system for notifying analysts of price changes. A
The interview consisted of a telephonic first round, followed by an in-person technical round. It was a fairly run-of-the-mill interview process. Be prepared to write code on pen and paper for fairly straightforward problems. The interview focused o
We had a phone interview two weeks ago. They asked me some basic questions on C++: * Constructor (ctor) * Destructor (dtor) * Static keyword * How to call C code Algorithm: * Big O notation * Hash tables * Bubble sort Database (DB):