I might be biased since I recently joined, but I am using my fake name, so I have no reason to make stuff up:
If you are looking for a stable job for the next 5-10 years, are in your late 40s, and don't constantly want to learn something new, and you want to work 9-5, this might not be the job for you. But everyone at the company is very transparent about it ahead of time.
Keep the innovation. Since the company is so great, make sure they are not afraid to innovate and not afraid to make mistakes and lose the amazing job as a result.
I don't know if it's the case, but I can see how it could possibly be when people really like to keep their jobs, no matter what.
I suspect they weren't serious about hiring and were merely browsing the job market to gauge compensation trends. The initial phone screen was straightforward, primarily focusing on HashMaps, their Java implementation, and the necessity of `equals()`
A recruiter contacted me through LinkedIn. They asked some basic engineering questions to weed out any mismatches. Then I had a technical phone screen with the hiring manager. If that went well, there was an onsite where I met the hiring manager,
step 1 - 2 telephonic step 2 - 4 onsite step 3 - 2 onsite interviews
I suspect they weren't serious about hiring and were merely browsing the job market to gauge compensation trends. The initial phone screen was straightforward, primarily focusing on HashMaps, their Java implementation, and the necessity of `equals()`
A recruiter contacted me through LinkedIn. They asked some basic engineering questions to weed out any mismatches. Then I had a technical phone screen with the hiring manager. If that went well, there was an onsite where I met the hiring manager,
step 1 - 2 telephonic step 2 - 4 onsite step 3 - 2 onsite interviews