I applied in-person. The process took 5 weeks. I interviewed at Squelch (Redwood City, CA) in Jan 2019
Interview
My interviews at Squelch were scheduled easily, both phone and in-person. I was able to speak with a variety of stakeholders who were excited about Squelch and happy to have new blood join to help. The timeframe was perfect - no waiting for weeks to hear back. The recruiter stayed in touch regularly.
Interview questions [2]
Question 1
Because of my background in much larger companies (7,000 to 100,000 employees), the Squelch team wanted to make sure I would be able to handle a startup atmosphere where it's all-hands-on-deck. Would I feel frustrated with lack of super established structure?
I applied through a recruiter. The process took 2 weeks. I interviewed at Squelch (Redwood City, CA)
Interview
I had a 30 minute call with the recruiter followed by 45 minute call with the hiring manager. I then had an in person with the hiring manager. The last step was to meet the executive team. Fairly straightforward and fast.
Interview questions [1]
Question 1
They asked primarily about my previous jobs, my technical skill set, my ability to work with sales and customers, and about my ability to do demos and on-boarding. They also asked why I wanted to work at Squelch in particular.
I applied through an employee referral. The process took 2 weeks. I interviewed at Squelch in Mar 2018
Interview
After an informal conversation with the recruiter, I did a phone interview with an Engineering Lead. This led to an on-site interview with several Senior Engineers. Following the on-site I had a video interview with the VP of Engineering.
They followed up quickly and were easy to work with through the whole process.
Interview questions [1]
Question 1
The interviews mostly focused on past systems experience. They had me describe the architecture of a couple systems I'd previously built, and then dug into the details, tradeoffs, and lessons learned for a long time.
Additionally there were a couple of short whiteboarding questions, one that was all about probability and another that focused on algorithm design. It seemed like the most important part of these was actually thinking through them, asking good questions along the way, and collaborating with the interviewer.