Hiring isn&#x27;t broken, dude. You just don&#x27;t interview well, and you seem antagonistic even to the idea that your cachet and skills, insofar as they exist, aren&#x27;t useful to the market. That&#x27;s a problem -- for you.<p>Interviews exist because employers need a way to quantify and qualify your ability. Typical computer science problems are a (flawed, but concrete) way of doing that. No reasonable interviewer expects you to recollect breadth-first search flawlessly, on demand, onto a whiteboard. But they do expect you to be able to reason from a problem statement to something approximating a solution. That&#x27;s fundamentally what programmers <i>do</i>. You should have the chops to think in this way, and you should be eager to try. Emoting &quot;what the fuck?!&quot; and claiming you can&#x27;t, or won&#x27;t, because you&#x27;re not a recent graduate is an excuse and a cop-out.<p>A few popular open-source projects don&#x27;t necessarily speak to your talent as a programmer. A 960 day GitHub streak is trivia, not a signal of anything useful. (If anything, it marks you as a target for burnout!) A few Hackathon wins and a couple hundred GH stars are the artifacts of a successful hobbyist, not a proxy for professional ability, or a gateway to employment.