> Yet I was the only one who would create things (hard- and software) in their spare time.
I have found this to be a very good signal in the hiring process.
People who have technical side-projects (machining, 3d printing, electronics, game programming, open-source) tend to be really good at conceptualization, problem-solving, cost-benefit analysis, problem-solving, staying-power, which are critical elements to the success of a software project.
Trivia CS knowledge questions, such as the one presented here, have their place too: they test whether someone can think on their feet, which is not a bad skill to have. However, all things consider, who would you rather hire?
- someone who can do an O-time analysis, but has not finished any real project?
- someone who failed the O-time analysis, but has built something to the end?
I'd obviously prefer someone who can do both, but the person who has released an open-source project for their ultra-niche hobby (say, a sock knitting pattern designer, used by 5 very passionate individuals; or a climbing wall with LED lights showing you the path) gets my vote otherwise. They may not have come up with the trie solution, but what they've done is conceptualize, build and deliver something concrete to users.
Which means they have proven and refined the precise skills every software project needs.