Interesting projects, skilled teammates, and well-above-average conditions.
Unstable processes, quite a few crunches.
I had a video call with my future manager and another manager from the company, where I got to ask any questions I had about the company. Then I had two one-hour-long technical screening calls with engineers from the company.
The interview process was okay. The interviewer, a director, seemed out of his depth and lacked understanding of memory barriers, crash resiliency, and transactions. He repeatedly agreed with me, offering no opposition or counterarguments. I develop
Like another reviewer posted, I had the phone interview with C++. This was one of the most difficult C++ interview questions I had, and I nailed it. So, I was asked to come for an onsite interview. My first interview was with a guy who looked fres
I had a video call with my future manager and another manager from the company, where I got to ask any questions I had about the company. Then I had two one-hour-long technical screening calls with engineers from the company.
The interview process was okay. The interviewer, a director, seemed out of his depth and lacked understanding of memory barriers, crash resiliency, and transactions. He repeatedly agreed with me, offering no opposition or counterarguments. I develop
Like another reviewer posted, I had the phone interview with C++. This was one of the most difficult C++ interview questions I had, and I nailed it. So, I was asked to come for an onsite interview. My first interview was with a guy who looked fres