Great company, high growth, and interest.
Long hours, no perks, and food.
General computer science questions. Included things about the command line, data structures, and basic C/C++ terminology.
Recruiter phone screen. Technical phone interview with two engineers. On-site technical coding interview with approximately eight interviewers. I thought most of it went pretty well. Only one or two of the engineers from adjacent teams weren't rea
I said hello, did the interview, and went home. It was hard, harder than most companies. I studied technical terms, but I still got popped. Hopefully, I'll come back stronger next year and get the job. Whatever, though. You live and learn, am I righ
General computer science questions. Included things about the command line, data structures, and basic C/C++ terminology.
Recruiter phone screen. Technical phone interview with two engineers. On-site technical coding interview with approximately eight interviewers. I thought most of it went pretty well. Only one or two of the engineers from adjacent teams weren't rea
I said hello, did the interview, and went home. It was hard, harder than most companies. I studied technical terms, but I still got popped. Hopefully, I'll come back stronger next year and get the job. Whatever, though. You live and learn, am I righ