I applied online. I interviewed at Weave (Salt Lake City, UT)
Interview
Received a call from a recruiter within one day of applying. Gave them a run-down of experience. I was told their process is as follows: recruiter call, technical interview, multiple meetings jam packed which could take up to 5 hours for the last one since there is a possibility of interviewing with different teams.
Their interview process A) takes too long. B) The interview questions during the technical are more geared for fresh/recent graduates. And not someone that's been out of school for 5+ years. So word of advice study data structures and algorithms regardless of how long you have been out of school/experience.
I decided to stay with my current company as the next stage of the interview process is way too long, the interviewer seemed in a time crunch, and would require missing work for a possible shot at working at Weave.
Interview questions [1]
Question 1
A reverse engineered Caesar Cipher with twists on hacker rank.
Recruiter scheduled an interview with me. They were 15 mins late and then called me on the phone instead of the scheduled meeting. It was clear he was just in the car and forgot about the meeting or something. I cleared that interview and was told they were going to schedule the next interview.
About a week later, the recruiter emailed me to schedule that same introductory call again. They never wrote any notes or even remembered having the first interview with me. I reminded them we had already done that introductory call and they said they would get me scheduled on the following Monday.
On the following Wednesday, I hadn't heard anything and I backed out of the process. Please treat people's time with at least a tiny bit of respect.
I applied through a recruiter. I interviewed at Weave
Interview
Applied via their career portal, had a disucssion with TA team about interview process and what the company is, what it does.
First round was taken by the engineering manager
The interview was quite technical, focusing on questions about Go programming and its concurrency model. The interviewer also asked about the interviewee’s past projects, particularly their experience in implementing parallelism and concurrency across distributed systems.
