Interesting problems Friendly coworkers
The interview process involved: * One phone screen with a recruiter. * Multiple phone screens with engineers, two of which included coding challenges. * One in-person interview with multiple people in-office. The entire experience was very pr
Average interview. Thought I did well and got the question correct, but they never provided feedback so I am unsure as to what I did wrong. The interviewer was relatively nice but not super helpful.
During an over-the-shoulder code challenge on a Zoom call with a mutual editor, I was told it would be purely vanilla JavaScript. However, it actually turned out to be using a framework. This frustrated the interviewer when I kept trying to solve the
The interview process involved: * One phone screen with a recruiter. * Multiple phone screens with engineers, two of which included coding challenges. * One in-person interview with multiple people in-office. The entire experience was very pr
Average interview. Thought I did well and got the question correct, but they never provided feedback so I am unsure as to what I did wrong. The interviewer was relatively nice but not super helpful.
During an over-the-shoulder code challenge on a Zoom call with a mutual editor, I was told it would be purely vanilla JavaScript. However, it actually turned out to be using a framework. This frustrated the interviewer when I kept trying to solve the