This guy got rejected by some automated system without even interview.
Yes, this. Sometimes I wonder if those coming up with the Homebrew example have any experience whatsoever with software development. I mean, sure the project is popular and surely doesn't hurt on a resume. But does it showcase any level of technical expertise or mastery? No, I'm afraid not. I would bet that the majority of software engineers would be able to put together an equivalent system in a week or so. Think about it, and pay attention to what are the system's usecases. It's hardly rocket science.
But it does show that he can develop and ship a popular product, something outside the capability of so many “great engineers”. Good luck generating any revenue on the backs of smart engineers that have no stomach for understanding the nuance of development over and above writing and checking in code.
Does it, though? I mean, the key differentiating factor is being able to stomach the cloud infrastructure costs. The vast majority of cloud engineers already work on far more complex systems as part of their day-to-day activities. What exactly do you think that putting together something a kin to a file hosting service places you above any other candidate?
_That_ guy (Howell) got several rounds of interviews, _this_ guy (OP) got rejected by an automated system.
"Him" is the creator of Homebrew. Seven interviews at Google.
"This guy" is the creator of enigo (discussed in this thread). Automatic rejection by Anthropic.
(Edit: upon page reload i saw the quicker answer.)
Silicon Valley lives in lalaland.
