A good team structure and business "family" structure were key in making this a good experience. I was part of a few teams on various projects, and all the people I got to meet were extremely good at what they did and had great personalities to work with.
Paperwork, paperwork, paperwork. So much that it may be more important than the product you develop in some cases. I understand the usefulness of documentation, but I'm not sure if every nuanced detail has to have a novel on it.
Nothing too bad as far as thoughts. Just listen to the lower-level engineers and floor workers a bit more. I feel that having the experience with the product directly should contribute much more heavily in the decisions made about it in management.
Pretty chill process, mostly behavioral. The first phone call was a screening and review of my resume. The second call was talking with the Engineering manager. We discussed some things I did in school and discussed the position itself. The on-sit
The interview went well. They had me talk with a few folks from the group that I would be hiring into. Then I talked to the hiring manager, then the section manager.
The interview was a classic format of three technical interviews with two employees, followed by a discussion with HR. In total, it took about three-quarters of a day. The interview took place on-site. All expenses were paid.
Pretty chill process, mostly behavioral. The first phone call was a screening and review of my resume. The second call was talking with the Engineering manager. We discussed some things I did in school and discussed the position itself. The on-sit
The interview went well. They had me talk with a few folks from the group that I would be hiring into. Then I talked to the hiring manager, then the section manager.
The interview was a classic format of three technical interviews with two employees, followed by a discussion with HR. In total, it took about three-quarters of a day. The interview took place on-site. All expenses were paid.