Interesting technical work at a healthy, relevant company in the middle of the Internet. Management seems to be pointed in the right direction. Flexible work hours, time off, and telecommute options are available.
Lots of legacy code, challenging to learn as documentation is often poor. Change comes slow relative to a smaller company, as there is a fear something will break.
Bite the bullet and let some of these old systems go.
Initial phone screen, followed by two rounds of interviews. Two non-technical, the rest (six) technical including coding questions and deep tech evaluation. Met with engineers within my organization as well as without, and talked to two different h
All my interviewers were super cool and allowed me enough time to express myself. In the end, they were happy and chose a different candidate based on stack ranking, as communicated to me. The only (hugely) disappointing part was poor as well as inf
Initial phone interview, then onsite. On-site started fine with the manager of the group. The panel interview is where it went off the rails. The panel was trying to flex on each other technically and was more focused on asking esoteric, irrelevant
Initial phone screen, followed by two rounds of interviews. Two non-technical, the rest (six) technical including coding questions and deep tech evaluation. Met with engineers within my organization as well as without, and talked to two different h
All my interviewers were super cool and allowed me enough time to express myself. In the end, they were happy and chose a different candidate based on stack ranking, as communicated to me. The only (hugely) disappointing part was poor as well as inf
Initial phone interview, then onsite. On-site started fine with the manager of the group. The panel interview is where it went off the rails. The panel was trying to flex on each other technically and was more focused on asking esoteric, irrelevant