Every Fall I give a presentation to the incoming freshman Computer Science class at C.U. There is a lot of interest in start-ups among the students. Some want to intern at them, some want to work at them when they graduate, and some are just curious.
I first try to give them an accurate picture of working at a startup. It's not for everyone and I don't want to sell it as the ultimate to everyone. I try to provide an accurate picture of the environment so each student can decide if it's for them.
And I then discuss what they need to do to prepare for working at a start-up, and what to do to get a job at one. Which really comes down to one key piece of advice - go intern at them. Several over the 4 years of school if possible.
Who's This Old Guy
On the advice of some of our interns, I start off with my background so that they pay some attention to what I'm saying. As I've learned from my daughters, people my age tend to be invisible to millennials.
To make it more real, rather than listing off my job history, I talk about what it was like at each. What I learned. What I got to do.
At Microsoft I discuss the joy and challenge of working with a group of brilliant people. With Enemy Nations I discuss how hard it is to make something playable and enticing. I talk about how when I first started programming it was with punch cards.
And I wrap up this part talking about the joy I've had creating software products. Making something people find useful, that helps them get through their job or their day better.
General Advice
Before getting into the start-up specific advice, I talk with them about two fundamentals that matter regardless of where they go work. These are items rarely discussed, yet key for people getting started on their career.
First is that they should do what they're good at. When you find something comes easy, that doesn't mean it's not a worthy job, it means that is what your brain is wired for. I was marginal at Physics while I rock at programming. That doesn't mean Physics is harder per-se, it means my brain sees programming solutions, often times just giving me the solution.
Doing what your brain is wired for means you can accomplish extraordinary things in that field. Whereas doing what your brain is merely good at means you can be competent with great effort. Do what you're good at.
Second is to take the more interesting path. Programming will pay you well regardless of where you work. Getting the most money tends to suck the passion out of you work. You're doing it for the dollars, not for the creative effort.
I discuss the adventures I have had. The joy of creating some incredible products. The thrill of being on the bleeding edge of new technology. The thrill from taking on impossible challenges and mostly accomplishing them.
If you ignore the common path. If you don't follow the conventional wisdom. If instead you go after jobs and projects - based on how interesting they are, how challenging they are, how much you will learn. Then you will find that you have lived a life in full.