High job satisfaction, good work-life balance, flexibility in work hours.
Lot of red tape, poorly paid, sub-par talent. Too many managers, BAs, and PMs. Funding challenges. They don't pay their key resources well, and they don't care if key resources leave; they would rather hire junior devs at low pay.
Focus less on operational excellence and more on initiative and innovation. Pay your resources that do the majority of the work well, and hire good talent.
One phone interview with basic core Java questions for 30 minutes. The second interview is one-on-one, and you need to solve a real-time problem by writing code. Then, an interview with the Hiring Manager, followed by HR.
Basic C++ phone screen covering classes, base classes, protected members, static members, polymorphism, friend classes, etc., followed a few days later by an extensive technical interview with multiple team members.
The process was good. The interviewers asked difficult questions, but they were fair and representative of the position. Overall, it was difficult but fair. No other feedback otherwise. They came to the university for interviews.
One phone interview with basic core Java questions for 30 minutes. The second interview is one-on-one, and you need to solve a real-time problem by writing code. Then, an interview with the Hiring Manager, followed by HR.
Basic C++ phone screen covering classes, base classes, protected members, static members, polymorphism, friend classes, etc., followed a few days later by an extensive technical interview with multiple team members.
The process was good. The interviewers asked difficult questions, but they were fair and representative of the position. Overall, it was difficult but fair. No other feedback otherwise. They came to the university for interviews.