Paychecks are always deposited on time, and affinity groups are many. That's about all I can think of for pros.
GE in New Orleans claims to have a startup feel despite being a corporate operation, but this couldn't be farther from the truth. Honesty is rare, and decisions are motivated by political or individual reasons. Engineers are treated like numbers instead of people. Product work is reassigned often and rarely comes to completion with the same resources it started with, so pride in one's work is virtually impossible to attain. Financial difficulties pushed annual increases off indefinitely. Those selected for layoff and those who are underpaid often have many years of tenure over brand-new employees who are kept or compensated better. Loyalty and commitment mean nothing to leadership. Focus on career advancement is non-existent, and there are no roles available for moving up. Medical benefits for family are highly expensive, yet the annual deductible is ridiculously high.
Stop worrying about yourselves and put some thought into decisions that impact those you're responsible for. Also, put some energy into challenging antiquated HR policies that prevent you from compensating and valuing your employees.
One-hour phone interview with hiring manager describing the position and asking high-level questions about projects on resume and light technical questions (what is polymorphism, inversion of control). In-plant interview follows one week later and l
The interview process started with a quick phone call about expectations and other details about the profile. Then, we had two more sessions with team members. The first one was more conceptual than hands-on. Questions included: * Describe an acco
Team fit was the most important aspect, and the technical questions were more about process than architecture or standards. OOP wasn't discussed. Most of the topics were based on tools used.
One-hour phone interview with hiring manager describing the position and asking high-level questions about projects on resume and light technical questions (what is polymorphism, inversion of control). In-plant interview follows one week later and l
The interview process started with a quick phone call about expectations and other details about the profile. Then, we had two more sessions with team members. The first one was more conceptual than hands-on. Questions included: * Describe an acco
Team fit was the most important aspect, and the technical questions were more about process than architecture or standards. OOP wasn't discussed. Most of the topics were based on tools used.