Good food, good engineering, good office.
Layoffs sometimes, bad on-call, attrition.
The interview included two graphs, similar to a course schedule. It wasn't too bad. The style was a mix of technical and behavioral questions. Just be sure to study the graphs a lot and be able to express your experience, and you should be fine.
Two coding interviews on separate days, with a bit of light behavioral at the beginning. No OA. There might be an additional person on the call just watching you, which I thought was weird.
I had a one-hour session with an interviewer. They asked me a couple of background questions about myself and graphics. Then, there was a C++ coding round, which lasted only for the last 15 minutes. However, the interviewer generously gave me an ex
The interview included two graphs, similar to a course schedule. It wasn't too bad. The style was a mix of technical and behavioral questions. Just be sure to study the graphs a lot and be able to express your experience, and you should be fine.
Two coding interviews on separate days, with a bit of light behavioral at the beginning. No OA. There might be an additional person on the call just watching you, which I thought was weird.
I had a one-hour session with an interviewer. They asked me a couple of background questions about myself and graphics. Then, there was a C++ coding round, which lasted only for the last 15 minutes. However, the interviewer generously gave me an ex