The people you work with are competent, hard-working, kind, and motivated people. Their interview/hiring process is very selective, so the people that make it through are really smart folks.
50 hours a week or more seems to be the expectation.
This may depend a little on the area you work in; I know software developers specifically might be better off.
However, if you work in Install Support, Technical Support, or EDI, you won't survive at the company if you don't put in 50 hours a week for a few years.
I don't actually have much advice for management. The practice of hiring the best college grads and working them until they quit seems to come from the executives, not from management.
30-minute phone screen, then an OA around 4 hours long. The OA had mental math, but also a few LeetCode-type problems. They were not very difficult if you studied common patterns and implementation.
After I applied online, I got an email back the next day asking me to take a quick personality and skills test. After I took the test, I was asked to set up a quick phone screen interview. It was pretty casual and not much to worry about. It was a gr
I had a phone screen, took a skills test, and was invited onsite for an interview. We had a group orientation about the software before breaking off into role-specific introductions and interviews. 1:1 interviews followed with case studies on how t
30-minute phone screen, then an OA around 4 hours long. The OA had mental math, but also a few LeetCode-type problems. They were not very difficult if you studied common patterns and implementation.
After I applied online, I got an email back the next day asking me to take a quick personality and skills test. After I took the test, I was asked to set up a quick phone screen interview. It was pretty casual and not much to worry about. It was a gr
I had a phone screen, took a skills test, and was invited onsite for an interview. We had a group orientation about the software before breaking off into role-specific introductions and interviews. 1:1 interviews followed with case studies on how t