| > 2. homework project
> 3. call with engineer to discuss said homework project How much time does it typically take (or should take) to complete a 'homework' project? > 4. two phone screens with engineers
> 5. onsite interview with 6 engineers This seems very 'camel is a horse by committee' to me. Reminds me a bit (know it's different) of dating where someone wants you to meet their family for approval. I immediately pass on those dates (and will add I am happily married to a woman who did not do that). I wonder about situations where it takes so many inputs to make a decision to me that speaks a great deal about the decision making process being faulty. Fwiw when I graduated college years ago I was rejected by a company (friend of the family no less) who said they couldn't hire me because 'yes you are smart but you don't know this business' (true I knew zero). So I started a company like theirs myself and now many years later they are gone and my company (which I sold) still survives. (Will add this was years before the internet and common practice for people who knew nothing to go into businesses they knew about). Now yes I do understand programming is not the same but my point still stands why so many chefs in the kitchen? Does anyone ever go back and track the people who were rejected what happened to them? |
I was still in college at the time but I maybe spent 5-10 hours over the course of a week or so. I do remember it took a very long time for them to respond after I had sent it in though. I believe the project was to implement a basic web crawler in Go.
> Now yes I do understand programming is not the same but my point still stands why so many chefs in the kitchen?
After the homework problem I think that's where they were defining the process as they went. They seemed to be growing quite a bit at the time (IIRC when I was onsite they had just rented two more floors of office space) and I had bounced between a few contacts that were brand new to the company. The real struggle is that I never knew how many more steps were to come, and I'm not sure they knew either.
Though after the onsite they e-mailed me almost immediately to setup the call with Ben so I think everything had gone well up to that point. I don't think the call with Ben went poorly so my best guess is that they went with someone that had experience rather than a new grad.
FWIW I'm not actually bitter about this. I just found it to be an interesting snapshot of a particularly chaotic point in the company's history.