Indeed, had you asked me to rate myself as a developer 10 years ago and today, I would have rated myself substantially higher 10 years ago, simply because I had no idea how much I didn't know.
It wasn't until my first job that I started to grasp that I didn't know everything (or even very much) about the field I'd chosen to work in.
Thanks for this comment.
Many developers who don't study CS tend to not-know-what-they-don't-know. It's fantastic they can throw together some web apps, but they don't always seem aware of what they can't do. I'd like to see the OP be thrown into a situation where he has to, among other things: write a static analyzer, design a stable routing algorithm over a mobile ad-hoc network, or publish, defend and implement a novel cryptographic key distribution protocol.
Here's a bit of philosophy for the OP (since he seemed so keen on hiring a "philosopher"): Knowledge is being more cognizant of what you don't know.