Ask HN: What sort of side-projects are useful for getting jobs?
1–10 of 169 posts
Re: Ask HN: What sort of side-projects are useful for getting jobs?
#2Why would you think that? Anything that shows off your skills has value. Well, it would to me anyway. I mean, if I were evaluating your candidacy for a job, I wouldn't care if your projects were demos or "actual products".
Re: Ask HN: What sort of side-projects are useful for getting jobs?
#3The thing which is valuable is to show you can get things done. That's it. Nothing special, just do what you want to be doing then show it to be who need engineers to do that thing.
Re: Ask HN: What sort of side-projects are useful for getting jobs?
#4Re: Ask HN: What sort of side-projects are useful for getting jobs?
#5My references vary from simple image-upload site to a (more complex) link-hosting site that does a lot of magic behind the scenes. And a lot in between.
Even projects from hackathons. [Here's](http://helpmehelp.herokuapp.com/) a perfect example. The code is opensource (terrible though :D). The project is old, irrelevent and unused. But still no reason not to have it hosted somewhere.
Re: Ask HN: What sort of side-projects are useful for getting jobs?
#6Small demos, most of time time, keep you on the main, easy, default road while a bigger project let you see a lots of side scenarios which are more representative of what you will hit in job.
However, I would recommend, from my experience to always scope down features since at some point you may fell in the trap of adding feature and not learning the technologies, hence moving away of the primary goal. I am wrapping a 30 months project and will definitely not do any project that would take that long. I aim project between 4 to 12 months for the future (at about 40 hours per month).
Re: Ask HN: What sort of side-projects are useful for getting jobs?
#7Re: Ask HN: What sort of side-projects are useful for getting jobs?
#8The difference between a demo or prototype and an actual SaaS with paying users is significant. The former can land you a technical job if it's well done. The latter will getyou a C-level job for an upstart if it's well executed (read: shows important growth). But you haven't explained what kind of job you're applying for.
Could you expand on this? Are you referring to an acquisition?
Re: Ask HN: What sort of side-projects are useful for getting jobs?
#9This sounds trite, but honestly, finishing things is hard. If you can show off a couple of finished side projects, that reflects much better than a half-dozen abandoned halfway through.
Re: Ask HN: What sort of side-projects are useful for getting jobs?
#10Invest your time studying for interviews than wasting time building side projects if you're doing this purely for getting a job, period.
In my experience, companies don't care about your little side project when hiring--that is, unless your "little side project" had some huge impact or is something they have been aware of--the best you could get is "huh that's cool", and that's it, unless you created something really unique.
This whole process of job interview is broken because it's extremely easy to study for them and give the right answers if you invest a couple of weeks to a few months. But since we're talking about getting a job, I think you should take full advantage of this. If I were you, I would be doing this instead of doing side projects for the sake of getting a job.
Also, "side projects" should be something that you build because you think they're cool, not because you want to get a job. That's another reason why I say study for the interview instead of bothering to do side projects if the purpose is to get a job. It's neither meaningful for the employer nor for yourself.
If you still really want to do a side project, just pick a problem you want to solve, and apply some new technology you want to learn to build it. That's the best side project for yourself and the potential employer.