This. I'd suggest making his own stuff instead of getting into an internship, maybe building some small apps he could even charge for and make some side money. Start at 13 and build enough of those, and he might never need a job. I wish I'd done something like that in college, when I had plenty of free time.

Plus, that was what always impressed the most during job interviews. I was generally one of the top prospects in the interviews I did -- not because of my GPA, or the school I went to, or past job experience, but because of some of the interesting projects I'd done either on my own or to help out my father with his businesses. It shows not just skill (which lots of other people have, even if it might be a bit less than you) but ambition and drive (which, it seems, not many others have).

> It's just very different to work on your own stuff at your own pace vs. working for a boss. I also suspect completing more of his own projects would actually be better for his career than whatever a company would allow him to do.

Which is exactly why I'd suggest working for someone if that's what he's into. Working with other engineers will give you a real sense of engineering standards, give you a sense of how to work on teams, help you set a reasonable pace etc. In a lot of ways at that stage in life your boss is much closer to a mentor/coach.

I would not suggest he does contract work, but instead finds a group of people who are interested in teaching and mentoring. I think we are comparing different outcomes in that sense.