I have a dream to create a robot making company. I have graduated in AI field and have some ideas about it, but as the robot making is a multi deciplinary work and needs Electrical and mechanical engineering knowledges as well, I don't know what can I do for those parts? I mean how can I hire proper electrical/mechanical engineers? How should I lead them when I don't have skills in their field? Even if I do hire CTO guys to lead them, how can I evaluate those CTO guys's work and understand if they are screwing?
There's two parts to this question.
First part: "I am afraid of dealing with people smarter and more skilled than me!"
Uh, no. Terrible way of looking at it. If you're a manager, your goal should be to hire as smart, as competent, and industrious of people as you can. If you don't do that? Oh, sure, you'll be smarter than your underlings... but your team will suck and your performance will suffer as a result.
If it helps, picture it this way: Alice Q Genius and Bob Mehville both are looking for a CTO job. You decide to hire Bob... and Alice goes to work for another company, quite likely a competitor. Which company fares better - the one that got the 'meh' CTO, or the one that got the whip-smart one? Clearly the company that hires Alice is going to be better off - which is doubly worse if that 'other company' is competing with yours. And imagine if Bob Mehville thinks the same as you, and it comes time to hire some developers/engineers/whatever, where everyone is 'not quite as smart' as Bob? Care to imagine what talent your company would be losing, simply because management doesn't want smart employees?
The second part is this: "how can I evaluate those CTO guys's work and understand if they are screwing?"
My boss doesn't know C#. He doesn't know SQL. He doesn't know the APIs of the vendors we work with. Or any of that.
But that doesn't mean he doesn't make sure I'm not goofing around all day. All he has to know is:
- What's Kevin generally working on?
- What's the timeframe of his current tasks?
- Are the clients happy?
That's the part that I think you're missing. You're viewing this as "I'm a AI expert and I want to run an robotics company - but I don't have the engineering knowledge!"
No, the skillset you're missing isn't engineering: it's management. If you're going to run a company, your important skillset isn't the nuts-and-bolts of AI: it's how to manage people and how to navigate the business world.
In general, you want to hire people who have a proven history of success in the role you hire them for and who share your vision for the company. It’s not expected that you have in-depth knowledge of every skill your subordinates/partners possess (though it helps to have at least a high level understanding of what they’re doing.)
Don’t confuse leadership with micromanagement. As Steve Jobs put it, "It doesn't make sense to hire smart people and tell them what to do; we hire smart people so they can tell us what to do."
I am afraid of dealing people smarter and more skilled than me!
You need to get over this fear right now if you want to be successful in business. First of all, different kinds of people are better in different areas. You can't possibly expect to be the best at everything. Secondly, the success of the company is more important than satisfying your own ego. The last thing you want is for the people you hire to not show their best work because the boss is afraid of getting outshined.
A business like that isn't going to be easy to setup. Not only will you need engineers but you will need legal, marketing etc...
The majority of your staff will be doing things you don't understand yourself. You hire people with proven experience (via portfolios and references) and trust them. You will know if they aren't performing by the results they produce.
As other answers have pointed out, you'll need management skills more than you'll need engineering skills.
But you'll still need engineering skills.
Even if you have great management knowledge, I'd bet the amount of competent managers in the IT space without tech experience are far less than those who have worked first in a technical role.
It's nice to dream big, but you also need to ground those dreams in reality. If robotics is really your dream, I don't think you should have any issue with working in industry (at least at first), hopefully alongside those interdisciplinary people. When you have a more complete grasp of things, you'll be able to better achieve your dream.