Lots of people to learn from. Exposure to new and emerging tech.
Difficult to onboard. Very little documentation.
I received an opportunity from a recruiter. The process involved finishing a coding exercise, a phone interview, and then an onsite interview. The onsite interview lasted about 2.5 hours, with five people rotating in and out to ask questions.
Interviewed through internal referral. Applied through internal referral. Received an email from the recruiter the other day to arrange a phone screen. Was called by an engineer two weeks later. Talked about working experience and projects.
Interviews were not too challenging, possibly because it's a QA position. They focused on basic debugging questions that a QA would deal with daily, along with simple C programs and algorithms questions. No special preparation is required if you kno
I received an opportunity from a recruiter. The process involved finishing a coding exercise, a phone interview, and then an onsite interview. The onsite interview lasted about 2.5 hours, with five people rotating in and out to ask questions.
Interviewed through internal referral. Applied through internal referral. Received an email from the recruiter the other day to arrange a phone screen. Was called by an engineer two weeks later. Talked about working experience and projects.
Interviews were not too challenging, possibly because it's a QA position. They focused on basic debugging questions that a QA would deal with daily, along with simple C programs and algorithms questions. No special preparation is required if you kno