Referred by a professional LinkedIn connection.

Recruiter Phone Screen: Standard.

Take-home assessment: CodeSignal, 4 questions. There have been many complaints about CodeSignal online; I'd recommend doing some research on others' experiences before starting.

TLDR (as of Jan 2022):

• Mix of approximately 2 easy LeetCode and 2 hard LeetCode problems.
• Do Q1, Q2, Q4, Q3 in that order.
• "Time spent" factors into the score, calculated from when the question is first viewed until it's last submitted. Moving on to the next question before finishing the previous one and submitting later would result in a score penalty.

The recruiter asked for feedback. I told them about CodeSignal and received the response: "We know, and I've been getting the same complaint from a lot of candidates. I've been trying to get them to change."

"Power Day" (virtual onsite): 2 Job Fit/technical, 1 Behavioral, 1 Case.

Technical Interviews: Both of my interviewers couldn't make it and had last-minute replacements. There was no coding, but lots of trivia and concept questions were asked, which was fairly standard. The last-minute arrangement may have caused some repeated questions between these two interviews. I had time to ask questions about the company, and my first interviewer gave me a lot of great answers and insights into the company and how things work (focus on AngularJS, cloud, and people within a team may not be working on the same project).

Behavioral: Standard questions (potentially phrased a little differently), but the interviewer's attitude wasn't the best. I did not feel they were very engaged, and the overall atmosphere was extremely cold. When they wanted me to elaborate on something, they would repeat the question word-for-word instead of asking me directly, leaving me to read between the lines.

Case: This was basically a systems design question. The first question, on product design, was deliberately very open-ended. I made a few assumptions and was quickly corrected. The second question involved light coding to ingest and manipulate log data streams. Many open-ended questions were asked, such as "What do you see from X that could be better?" Language choices were Java and Python, even though I was interviewing for a frontend position. Overall, it was a little unfriendly.

I received a call from the recruiter to tell me feedback/evaluation would be provided "soon." I did not receive any further response until I let them know I had reached the final stage with another company, and then I received a standard rejection.

• Manipulating log data streams for various pieces of information

• Product design