Live data from Hacker News

Ask HN: Would you hire me (passionate hobbyist programmer) to a dev position?

news.ycombinator.com

41–50 of 105 posts

Re: Ask HN: Would you hire me (passionate hobbyist programmer) to a dev position?

#41
I like your idea of coding up your resume - it shows competence and a desire to learn and build. I recently did the same thing.

But there is a first-impression problem. Obviously design skill is not what you are trying to demonstrate, but it's the first thing people see! Some people might read the code (and appreciate it), but even they won't jump right into doing that in the first few seconds.

I'd suggest copying the heck out of a good-looking online resume, and then subtly tweaking it to your taste. Subtly.

I'd also suggest hosting this on it's own. It will look more professional. (Github pages is a slick, free way to go.)

Your question was about whether someone would hire you as a dev. Yes, I suspect they would! Especially if you find an employer that has at least a passing interest in your operations/systems experience. I would look for a software company that works in this area (maybe one of your frequently used vendors?) - they'll eat it up that you know the domain.

Re: Ask HN: Would you hire me (passionate hobbyist programmer) to a dev position?

#42
If you want to get a job as a programmer instead of saying that programming is your hobby, say that programming is a side project.

That was my main lesson in a (test) interview for a front-end position that I applied recently (I'm also an hobbyist).

Re: Ask HN: Would you hire me (passionate hobbyist programmer) to a dev position?

#44

I've wanted to ask something similar for a long time. I have a government job that has decent pay, but the schedule sucks, and I'm not challenged at all. I have freelance full-stack experience, just nothing black-and-white professional wise other than sysadmin & electronics experience in the military. I recently moved to what could be considered an "up-and-coming" startup city and I've been tossing around the idea of…

Based in the states I'd say you'd be hitting $80 within 1-2 years, perhaps quicker if you are a) good or b) using a tech that's hot right now.

I'd say work out timelines of how much you'd stand to lose if it took you 1,2,3 or 5 years to get past a certain point. I'd guess you end up recouping it in the long run but if you think it'd make you happier then you can't put a price on that.

Re: Ask HN: Would you hire me (passionate hobbyist programmer) to a dev position?

#45
A few (hopefully helpful) comments:

Resumes are sales documents; you're trying to convince someone to spend a lot of money paying you and hopefully investing in your skillset. Rather than think "is my resume good", reframe the question to, "who will be reading this, and what do they want to see?" There isn't one "right" resume.

Your word choice ("enterprise", "leverage", "medical applications", lots of talk about "projects"), certifications, and type of projects say "enterprise IT". If that's what you're going for, you might've hit it.

If you're writing a contractor resume (1099/freelance/etc.), you need to focus more specifically on skills and technologies, and how you've used them in the past. For a consultant resume, focus more on the business results of what you've accomplished (revenue/cost, customer satisfaction, retention, etc.) although frankly, you're probably too junior for that route.

If you want a job at a product company, figure out the age of the hiring manager. Most are 30-40 these days, if you want to get in front of those guys, talk more about "products shipped" and wins/successes you've had. For younger hiring managers/more progressive companies, a portfolio website would be nice. Also, the more code you can show/projects people know you can claim credit for/etc. the better, a big part of the hiring process for me is placing you on the social graph so I can try to find someone in my network who might vouch for you. It's surprising how easy it becomes to find someone who's worked with you after you've worked in the industry for 10+ years; help me do this.

Other general advice: "Good writing shows rather than tells". Rather than saying you're "passionate", talk more specifically about the projects you've done. SHOW.

Try to keep it plain; just make a PDF or if you really can do it well, a well-designed portfolio site. Formatting is table stakes, I don't think it would help much for a real dev/backend position, but it might hurt if you make it too hard to consume (esp. on a mobile device).

Get a copy editor. The writing is pretty bland, I think you could sell yourself better using more active language (focus on "what you did" vs. "what you are").

Put dates on things. I want to get the chronology of your career; this format makes that difficult.

Try to include links to websites. I want to see your github profile, what project's you've been working on, your blog, Twitter feed, etc. Again - trying to see who you are, what you do, and if we know anyone in common.

Try to use as simple language as reasonably possible. Say "use" rather than "leverage".

Be more specific about what you want. Full-time vs. hourly contractor vs. part time, if you want remote say which timezone you're in, talk more about what role you want (generalist/full stack, developer, designer, UX, manager, quality specialty, product management, ops, etc)

Finally, don't be afraid to let some personality show through. It's pretty bland, I don't know whether you're a wise-ass, what your sense of humor is like, more straight-laced, etc.; don't be afraid to be a little more funny/human with this.

Hope this helps. My email is in my profile if you want to talk further, I'm happy to chat more. I work in SF and regularly review resumes, so I see this stuff a lot.

Re: Ask HN: Would you hire me (passionate hobbyist programmer) to a dev position?

#46
No, I wouldn't hire you as-is. Probably not a first-choice intern either.

Some notes on why not:

+ Your web-sume looks rough. As pointed out by others, there are a number of typos (i.e: "and provide an opporunity") not to mention the design itself could use work. If you are GREAT at web design/UX you should spruce it up. Otherwise, kill it and move to a traditional resume. Knowing HTML5/CSS3 today is pretty meaningless, so showcasing that is sort of pointless.

+ There are tons of issues with your resume itself (i.e: "Excellent verbal and written communication skills." despite multiple typos and unclear flow) which need to be addressed. Cut the fluff, point to recent projects & address why they are cool/why anyone should care. Anything that you did 10+ years ago that isn't directly applicable to what you want to do in the near future has no place on the resume.

+ Your bitbucket projects are lackluster. You don't follow good git branching habits, your commits are non-atomic, your code is cumbersome and unfinished in many places. You also seem to use .py files as notes in non-standard ways, introducing weird artifacts and conventions to your projects.

Some notes on how to improve:

+ Learn how to use git productively in a team environment (this means no more working directly out of master). This is a good resource to that end: http://nvie.com/posts/a-successful-git-branching-model/

+ Learn better coding habits in whatever language(s) you are most comfortable with. Your bitbucket only has python code, so learn how to do things in more 'pythonic' ways. (i.e: Don't just stub notes inside .py files. Throw them inside a README.md or keep them in a secondary utility so you don't clutter the repo).

+ Sort of back to point #1 but deserves its own category: Learn how to use .gitignore. You have tons of artifacts in your repos that do not need to be/should not be there.

If you address all of the above, you'll be in a much better position to start qualifying for entry level dev openings.

Re: Ask HN: Would you hire me (passionate hobbyist programmer) to a dev position?

#48
I'm going to pick on one flaw of your CV and explain why it is problematic.

> Excellent verbal and written communication skills.

Prove it.

Anyone can write that. As a hirer I see that sort of statement all the time and it means nothing. I want you to prove it.

Eg.

> I regularly write reports for the CEO and board. I produce a monthly 200 word summary and 5,000 word detailed background on our team's accomplishments. This has lead to increased recognition of our team's performance.

I can immediately see what you mean by that. I want someone who can do that level of reporting and is trusted to talk to senior people. Of course, you might by lying - but that's what the interview and probation are for.

Let's also look at this:

> Backup reporting app that pulled results from a backup status DB and used a local database of admins and projects to present reports in various filtered formats.

So what? What did that achieve?

How about...

> I created a backup database app which sped up report by 35%. Using multiple output formats reduced support calls to the team by half.

I want my support calls reduced by half! We need to get this person in!!!11!

Ok, I exaggerate a bit - but in every single line of your CV, you should be showing not telling.

Post reply on HN