Food, games, and work culture are good.
No downside till now, I think.
I recently went through an SDET interview process. Here's how it went: * Had a 30-minute call with a recruiter. Answered basic questions about my background. * Technical phone interview: 1 hour. Discussed testing concepts and did a simple coding
The questions were of medium to difficult levels. One question involved dynamic programming, and another required normal loop implementation. The coding platform used was InterviewBit. Everyone was provided with a different question, though all we
I got a call from Google and I attended an interview for an SDET role. The interviewer seemed to be in a bad mood, with no smile and no enthusiasm. Expectations for coding skills for a QA Engineer are higher than for a developer.
I recently went through an SDET interview process. Here's how it went: * Had a 30-minute call with a recruiter. Answered basic questions about my background. * Technical phone interview: 1 hour. Discussed testing concepts and did a simple coding
The questions were of medium to difficult levels. One question involved dynamic programming, and another required normal loop implementation. The coding platform used was InterviewBit. Everyone was provided with a different question, though all we
I got a call from Google and I attended an interview for an SDET role. The interviewer seemed to be in a bad mood, with no smile and no enthusiasm. Expectations for coding skills for a QA Engineer are higher than for a developer.