Solving challenging technical problems (e.g., concurrency, networking, high availability).
A strong testing mindset.
High-quality C++.
Strong command of agile development.
Talented engineers.
Often using old/deprecated software. Quality of code, except C++, is pretty poor. Code duplicity and tech debt. Unreasonable work policies.
The technical interview consisted of two, one-hour long interviews out of a total of five. These interviews tested concurrency and algorithms. Interviewers encouraged pseudocode but would give poor feedback if it was actually used, and did not consid
An absolute waste of time. I should have read the reviews here before wasting my time on the interviews. While all the people I spoke to were friendly, I met one really arrogant and rude person.
This is an online assessment. There are 12 test questions in total. Two of the questions are coding problems, and 10 are multiple-choice questions. The overall test is not difficult, but answering them correctly does not guarantee a follow-up inter
The technical interview consisted of two, one-hour long interviews out of a total of five. These interviews tested concurrency and algorithms. Interviewers encouraged pseudocode but would give poor feedback if it was actually used, and did not consid
An absolute waste of time. I should have read the reviews here before wasting my time on the interviews. While all the people I spoke to were friendly, I met one really arrogant and rude person.
This is an online assessment. There are 12 test questions in total. Two of the questions are coding problems, and 10 are multiple-choice questions. The overall test is not difficult, but answering them correctly does not guarantee a follow-up inter