How a High School Valedictorian Chose Against College


Hey. I’m Paris Mitton. I’m a 19-year-old software engineer in Denver, Colorado. When people meet me nowadays, the first remark is always about my age. I’m probably the youngest person they’ve met in the professional field, and it’s a little strange. It’s made even stranger by the fact that just a few months ago, I was a senior in high school, straight A student, top of my class, and had applications out to the most well-known universities in the nation. How did I get here? If I could tell the senior-year Paris this story, I’m sure he would not have believed me.

This is the story of how everything that could go wrong, did go wrong — and how that ended up being the best thing that could have happened.

Like the majority of kids today, heading to a university had been on my life roadmap since I was very young. I knew for a fact that I was going to college. I can recall clearly the conversation I had with my mother one day in first grade. School had been boring me; the teacher was spending time on things I already knew and not enough on things I wanted to know. My mother consoled me by telling me that things would be better when (not if) I went to “college” and could study whatever I wanted. College, I asked her; what’s that?

“College is where people go to get smart and be successful,” she replied.

I don’t think my mother’s statement is out of line with the rest of society’s view; College enrollment is at an all time high, as is the cost, which would imply that we as a culture find a lot of value in higher education. The theory goes that the earnings you make over a lifetime outweigh the loans, and the connections you make with people can be for life. Being an industrious little 1st grader, I wanted to be 1. smart and 2. successful. So the choice was a no-brainer.

Here’s the ingenious plan 1st-grade Paris came up with:

  1. Get great grades in middle school to impress high school honors programs.

  2. Get great grades in high school to impress colleges.

  3. Go to a great college.

  4. Get a great degree.

  5. Get an internship at a great company.

  6. Get a job at a great company.

  7. Great.

As you can see it’s not really thought out. Frankly, very little of the college process is thought out — it’s just “what you do” as a middle class high school graduate. Even as I grew up, the simplicity of this plan never seemed to change. The last 10 years of my life have been pretty much a to-the-letter perfect execution of this plan. I was the traditional upscale college candidate — variety of extracurriculars, president of 2 clubs, straight As in every class, valedictorian, IB scholar, and with a passion for learning and my personal forté, computing. I wrote the essays, impressed the right people and aced standardized tests. In short, my life was the on-the-rails indicator of success. I was surrounded by people — teachers, advisors, parents, friends — who saw these metrics and reassured me that I was destined to do well. How could I not succeed?

Step 3, here I come!

I applied to CalTech, Stanford, and UC Berkeley. All out of state, mostly private, and highly competitive. Anyone who went to college in the last few years will notice that I did not apply to a safety school. Why not? My own mismanaged sense of pride, primarily. I am quick to note that literally every source I had was telling me the same thing: I’m going to get in. The admissions page sounds like all it takes is being the top of the class. My teachers and parents, impressed with my grades, said I was a shoo-in. Everyone, myself included, had a completely wrong idea of what college admissions really are (A lottery — more on that for another post).

So the results rolled in. I was rejected from Stanford and Caltech right off the bat. This was a surprise to me. Of course there is an element of chance in admissions — but I thought I was a lottery-winning sort of kid. Even if I didn’t get into one of those, I thought the chances were good I would get into the other. But two strikes out? Ouch. That’s ok, I told myself, Berkeley has a lower standard, since it’s a state school. I’ll get in there.

Can you guess what Berkeley said?

The night I was rejected to Berkeley was a very somber night. It was the first time I cried in several years. At the time, I felt betrayed by my teachers, my counselors, and my parents. I had been promised that if I wanted to be the best and proved I was willing to try, I would be accepted to the college of my choice. It was the educational equivalent of the American Dream, and it just failed me. So how did it come to this? This was all I could think: How did I try this hard for all my life, and yet, at the last moment, come up with nothing?

Despite all these questions swirling in my head, the real world doesn’t grind to a halt just because your personal one does. The most pressing question, of course, was “what happens now?” Admissions were closed. I was graduating in a few weeks. I’m not the kind of guy to sit around my parent’s basement. What did I have left? Only then was I was reminded of an experience I had a year prior that might offer a way out.

In the summer of my Junior year, I took an internship at a software development firm. The work was mostly trivial, but I did get to play around with the code and work with some real developers. I saw what they did on a day-to-day basis and realized that a lot of it was within reach of my own self-taught skills. I really wasn’t that far off in my capabilities from an actual working developer.

I was stalled at step 3 — but could I somehow leap over the missing steps and go straight to Step 6? Could I be an actual, working developer?

I thought about how my resume would look compared to any other entry-level candidate, straight out of college.

  • 19: those few years between 19 and, say, 23 mean a lot in the tech world. It could easily mean “less mature and responsible” to an interviewer.
  • No fantastic scholarships to speak of, and no recommendations from colleagues/professors: a bit of a wild card.
  • I had some experience, possibly more than most college candidates: that was an asset or at least an even playing field.
  • No college diploma: isn’t that a straight out disadvantage? So much so that many companies would not even allow me to apply to a job without that piece of paper. The job postings are discouraging. Required: 4-year-degree in computer science. Well, that wasn’t me. How do I play those weaknesses as strengths instead?

  • 19, and yet had enough knowledge to be an engineer. That says a willingness to learn.

  • Young and passionate, which means I work hard and contribute to the company environment.

  • I had minimal experience where new grads sometimes have none. I am familiar with the engineering workflow and standards like Scrum, Git, and continuous integration — practical, not theoretical, knowledge.

  • No diploma proves that I can teach myself and learn on the job. It can be a position of strength — leave the “safe” college approach and strike out on your own. I realized that my greatest asset was my youth, my enthusiasm, and my personality — and resumes do a very poor job of advertising any of these.

So, online job applications were out of the question. Instead, I started going to meetups. I found a few interesting ones in areas that seemed interesting. I met face to face with professionals (potentially colleagues) and exposed myself to cutting-edge ideas. Most importantly, potential employers saw me and not my resume. Much to my surprise and benefit, I found that the way I thought about myself is the same way that much of the tech world has taken to thinking as well. Many startups recognize the power of a unique company culture, and that great skills can come from everywhere. When I set out on my job search, I expected to, just maybe, find a team that was open-minded enough to appreciate my unique profile.

To my delight, I received interest from almost everyone I talked to. I didn’t just find AN opportunity — I found many. This was extremely validating for me. My computer skills hadn’t been rewarded (or even acknowledged) at school, and by my senior year, I began to question just how much a 5th year of english or a year of rehashed programming basics at college were going to help me. At the very least, the debt would be a serious financial setback. I felt like I had a valuable skill, and it would take me 4 years, several thousand dollars, and even more time spent in a traditional, static educational setting to prove it. So to hear that there were companies out there who recognized that, even degreeless, I was worthy of their time — that was magical. Maybe, there is a place out there for me.

The interview process was daunting at first. I have heard a lot of horror stories about cranky interviewers and oblique questions. I was definitely nervous, but I never felt unfairly treated or out of my element. The interviews I had mostly consisted of a rigorous technical overview, time chatting with employees, and then some sort of project. The projects usually involved implementing some aspect of the developer’s day to day work.

For each project, I tried to come up with something that was interested in but also displayed a variety of technical skills. My favorite was a project where I had 2 days to build a lightweight web service that aggregated data from different sources. When I was assigned this, I had just finished a long winded argument with a friend who suggested that the recent live action Teenage Mutant Ninja Turtles movie was actually good. Despite my most fervent arguments, he would not see reason — so I made “Taste Tester,” a “how good is your taste” web service. You give it a set of music, movies, and video games that you enjoyed and your ratings of each. Then, it would look up what the critics rated it and would snidely inform you how good your taste in media was. That way, whenever my friends said something stupid like “Avatar was a cinematic masterpiece,” I could give them scientific evidence that they had no idea what they were talking about. Projects like this made the interview process more interesting and were also fun to build.

When the dust settled, I was beyond flattered to be able to choose between two great job offers. This was a dream come true. Where universities had ignored my hard work and passion, the tech world seemed not just tolerant but welcoming. It’s been a sign of good things to come. Today, I work for FullContact, which unifies, cleans up, and saves customer’s address book information in the cloud. I work on tools for developers, and the technology that adds publicly-available information to people’s limited information on contacts. I’m learning a ton, collaborating with a great team, and feel invested in the work. This is the first time in my life I can wake up in the morning and think to myself, “Is today monday? Game on.”

March through October 2014 was one the scariest and most stressful times of my life. Looking back on it, I am nothing but glad that it’s happened. I love where I am and I wouldn’t have wanted to get here any other way.

What now?

I made it to Step 7 in 1st-grade-Paris’s plan, several years early. For now, I’m enjoying the ride and learning all I can. I’ve got a few business ideas cooking. Who knows? After planning my life for 15 years, I’m ready to go with the flow for a little while.

I’m going to be posting more about my experience — what I learned, and how I feel about university in America (guess what: negative!) here on my blog. You can chat with me on Twitter — @parismitton.