Comment by huntermeyer | Hacker News Reader

Comment by huntermeyer | Hacker News Reader

Parent Full thread

In 2013 I attended Epicodus in Portland, OR. At the time, it was a 17-week Ruby on Rails bootcamp.

I moved back to my home state of Florida following graduation.

Within two months I landed a Junior Rails Developer position at Listen360 - a badass company in Georgia. I relocated and have been with the company for over three years now.

In that time I've developed JrDevJobs.com, a job board for junior devs. Built several side-projects, and taken on contract work at a growing rate.

Bootcamps aren't for everyone, and they don't guarantee success. They are a spring-board and structure for those who are committed and able to learn the trade.

Software development is hard as hell. It challenges your abilities in every way: decision making, risk assessment, empathy, time management, and your ability to handle stress. But for those that love it know the rewards to be worth the struggle.

I'd like to say my bootcamp prepared me for the job I have, but I also know that I was going to become an engineer regardless. I saw the bootcamp as a way to get there faster than learning on my own.

I've toured and given speeches at several bootcamps across the country. I've seen patterns amongst the students: there are those that think they're "done" once they graduate, and those that think they're just getting started once they graduate. The latter tend to outperform the former. Full disclosure, this is totally anecdotal.

I think bootcamps are great for those who love to learn, are always challenging themselves, have a competitive nature, and love technology.

Good for you!

I ask all the interns that I interview to hire, "why do you want this job?" I can pretty much tell by the answer alone whether or not they are going to work out. Those that say, "I didn't know what to study" or "I heard there was a good career in this" I can pretty much write off. They almost never want to learn anything except what they learned for a grade. Often its over for them after school, they'll never have the drive to learn what they really need to advance. I always tell them that dollar for dollar, we are one of the poorest paid fields. The amount of time we spend learning vs how much we are paid is way out of proportion even with our technical salaries. They never believe me.

It's those that get kind of that geekish giggle about some theoretical concept (state machines, some language concept they discovered they think is cool, compilers, etc.) I know are going to be great. These are the ones that I really go after. With these people it doesn't matter how much they know at that moment, because when they're done, they'll know more. They'll keep doing it too.

There's another aspect to this though. Programmers have to be smart and get things done. In my experience of interviewing and hiring these qualities can entirely orthogonal. I've hired people who program enthusiastically on side projects and study advanced topics at the weekend but are pain in the workplace; overcomplicating tasks and working slowly while others deliver faster and with better quality. At the same time I've worked with people who express no interest in any realm of computing outside their direct area of expertise. They work hard from 9-5 being extremely productive and I know that they don't think about so much as a bit or a byte until they come into work the next day.

> There's another aspect to this though. Programmers have to be smart and get things done. In my experience of interviewing and hiring these qualities can entirely orthogonal. I've hired people who program enthusiastically on side projects and study advanced topics at the weekend but are pain in the workplace; overcomplicating tasks and working slowly while others deliver faster and with better quality. At the same time I've worked with people who express no interest in any realm of computing outside their direct area of expertise. They work hard from 9-5 being extremely productive and I know that they don't think about so much as a bit or a byte until they come into work the next day.

Speaking of teams, I'm usually the least productive member of any team I've been a part of because I often fall into the role of project servant: someone who bounces across team members as they get stuck with something or another. The best compliment I've gotten is that the role is that of the guy who gets ammo from person to person at the end of saving private Ryan: not the sexiest job but someone is doing it.

> someone who bounces across team members as they get stuck with something or another

Helping them see what they've missed or otherwise get over the hurdles? Sounds like a senior dev to me.

>Sounds like a senior dev to me.

That's what I'd call them.

I've always like troubleshooter, though: when there's trouble, they shoot it.

> I ask all the interns that I interview to hire, "why do you want this job?" I can pretty much tell by the answer alone whether or not they are going to work out. Those that say, "I didn't know what to study" or "I heard there was a good career in this" I can pretty much write off.

I would be careful about making that assumption - it was only 4 1/2 years ago when I landed my first job as a developer after 2 1/2 years of searching for any career track job after leaving my PhD program in mathematics. I was someone who was willing to do anything and was open to a wide variety of jobs. I put in long hours outside of work early in my career to learn and grow, with the mindset that I was behind and needed to accelerate my learning greatly - I had a work ethic that might be seldom seen in the industry, and a proven intelligence to match.

Fast forward to today, I am right now actively interviewing and being hotly contested by many companies for senior, lead, and management roles, including the likes of Google and Apple with multiple onsites scheduled or being scheduled (4 alone between Google and Apple over the next week or so).

IMO companies should try to tease out characteristics of people - how do they handle difficult situations, how open are they to feedback, how hard are they willing to work (especially earlier on), and how smart are they? Positive answers to these questions when interviewing inexperienced people are probably the biggest factors in determining the likelihood of someone being successful IMO (don't ask these questions directly of course, but the answers should be teased out).

Yes, it's the soft questions that really answer, "will this guy excel," for me. I'm on a sabbatical and I'm using the time to develop a product, because that's what I like to do. I want people like that.

this is a fantastic answer. Have you blogged about developing and launching JrDevJobs? (presumably this is a side project that brings in a small amount of income? how do you market something like this?)

Your presumption is correct :) I've thought about blogging, but I just haven't made it a priority. I'm so thankful for the people out there that do. - Especially when I find their post about an obscure problem that I'm needing help with!

well, you know where to post it when you get time to write :)

Your site looks good. It reminds of Seek.com.au. I wish more general job boards looked like this. I hate Indeed.

College for me was a bunch of theory, yes is good to have it but once I landed a job I realized I didn't know anything about developing a software from bottom up, therefore in the past 3 years I've learned considerable more that in my five years of college.

Reply on news.ycombinator.com