Daily Harvest Software Engineer Interview Questions
& Process

It was a remote interview with a phone screen where I talked to an engineer about my past experiences. Then there was a coding challenge, followed by an "onsite" where I spoke with more engineers and a product manager. The process focused more on solving real problems with engineers, covering database knowledge and architecture, rather than just algorithms. There were also many questions about how I'd collaborate with non-engineering teams. It was an enjoyable and thought-provoking experience, though I declined the offer due to salary.

The process took a while, it had a home assignment. When I visited their office, it kept going with seven interviews in one day. One person seemed like they were just going through the motions, but besides that, I felt I got along well with everyone. I didn't get an offer and there was no feedback, just a generic statement about needing to be careful with hiring. Given the situation, it seemed they urgently needed more engineers, so it feels less sincere when 'being careful' is the only feedback. No job and no useful insight, just a lot of wasted time. If companies are worried about their hiring reasoning getting out, you have to wonder what they are hiding.

It was a typical interview process. Started with an HR screen, then a technical interview, and finally a last round. Everything moved pretty fast, finishing in under two weeks. The questions were pretty open-ended but related to the job. The team was nice and answered questions well.