Nearly everyone I worked with was friendly and professional. I've had a few managers there, and they were all fantastic. The department I was in was exceptionally run, although our product struggled to get off the ground. Late nights were few and far between, and I felt that I had complete control over my schedule most of the time.
As an SDET, not all the work was interesting. We got stuck doing a lot of manual tests since vendors weren't budgeted for our department. Also, sometimes it felt like we were all waiting around for something to happen, which was boring.
Keep up the good work; my stocks depend on it.
Very difficult. HR would not say what subjects the programming interview would test. It turned into a white board ASI operation questions. Two other interviews with four other people followed. It was not a pleasant experience. "Why should I hire you
Standard programming questions about data structures, what makes good software test design, and the high-level design of an ATM machine for blind people. It made for okay conversation but was pretty dry, to be honest.
Applied online. Received a call from a recruiter and had an informal, light interview, then scheduled a phone interview with the hiring manager. * Five interviews, all 1 hour long; included a lunch interview. * Combination of testing, vendor ma
Very difficult. HR would not say what subjects the programming interview would test. It turned into a white board ASI operation questions. Two other interviews with four other people followed. It was not a pleasant experience. "Why should I hire you
Standard programming questions about data structures, what makes good software test design, and the high-level design of an ATM machine for blind people. It made for okay conversation but was pretty dry, to be honest.
Applied online. Received a call from a recruiter and had an informal, light interview, then scheduled a phone interview with the hiring manager. * Five interviews, all 1 hour long; included a lunch interview. * Combination of testing, vendor ma