Ok, how much recruiters/interviewers ACTUALLY care about personal projects and github contributions...

Ok, how much recruiters/interviewers ACTUALLY care about personal projects and github contributions? Should I waste my time with this?

Attached: Ies6rm2.png (764x212, 15K)

The statistical likelihood of your application actually reaching the eyes of an HR rep is almost zero, but if for some cosmic coincidence, your application made it through their filters and managed to be one of the 20 they will spend time vetting for the next 2 weeks, then no, they're still not going to look at your github contributions.

Attached: tohru dumb.gif (500x463, 1.4M)

All recruiters/interviewers are different. Some care more if you're a nigger or a womyn, some care more if you have certificates and personal projects over degrees, some care more if you have no degree but years of employment experience. Just build up as much as you can to showcase yourself in a good light, because that's all you really can do.

It's something you can talk about at the interview if you have no previous work experience.

>Should I waste my time with this?
you've already lost

This. I’d say most Headhunters don’t look at them, and don’t even know what Github is all about.

What if I explicity tell about them on the resume? Like, a section for personal projects instead of just linking my github.

they won't look at it if they don't understand what it is
describe your projects in detail if you want to talk about personal projects and link it if you want, but they still won't follow the URL

I've avoided mentioning personal stuff on my resume because the projects I've actually finished and released all revolved around reverse engineering old games, I enjoyed the learning experience from working on those projects but I'm hesitant to mention it because I imagine most companies won't be comfortable with the legal gray area those projects fall under and it just seems like it would come off to a recruiter as the wrong "kind" of nerdy, thus hurting my chances more than anything else

well it's clear there's no way out for you
you've backed yourself into a rut where you believe your skills are useless because they're related to video games and no amount of me telling you you're wrong will change that

On the other hand they might also think that soemoen with revverse engineering skills is useful for finding out how the competition does things.

If it isn't that much important, what the fuck should I do to stand out from the rest for an employer after graduating

having an HR who's also your uncle, or a distrant friend from school, or a friend of your parents works wonders

>muh networking
I guess I'm fucked then, I never waste my time talking with anyone at uni

It's more that I'm just worried about recruiters viewing it negatively, as far as I'm aware those "no reverse engineering our product!" clauses you find in every EULA tend to get thrown out of court more often than not but I imagine most employers would still frown on a guy going and reverse engineering copyrighted games anyway

I'd love to change gears and do something more technically challenging than the typical CRUD full-stack app development I'm doing now but I just don't know how to move forward here

Might be worth making a personal website with a section for presenting each project and showing screenshots and such, that gets the point across better than them having to skim each project's README.md

What sort of job openings would specifically require those skills?

if you personally think it is a waste of time then don't do it. you don't *need* it to past a HR filter or get a whiteboard interview. just keep in mind interviews are also about probing you as an entire package, so it sounds like you are just in it for the $$$ and you are going to lose out to people who are passionate either way.

Knowing how to use a repository is more important than having 5 gay stupid school projects

Hopefully you're aware that socializing is a good thing and you should do more of it instead of relegating all socializing to some useless imageboard online.

No
Just say what they want to hear and solve any and all questions they give you.
If it's your first job take a lower salary wait a year or two and apply while employed.

It would be like explaining to a baby how to conjugate a verb. They are several levels of intellect below what is required to actually understand what you're trying to tell them.

Recruiters almost always know nothing about anything they're recruiting for. They only look for buzzwords and don't know what the fuck they're asking. I once saw a job listing requiring 5+ years of Swift programming experience. This was in 2016. Swift was created in 2014.

Give a baby the choice between a $100 bill and three $5 toys, and it will choose the toys.
Don't expect someone of their level to see the value in what you're offering them. Instead, conjure up their equivalent of 'toys' - use buzzwords and acronyms just like they do, banter about stupid normie shit like sports, and try to falsify a human connection with them so that they'll remember you when they go back to report their findings.

Worked for me.

>it sounds like you are just in it for the $$$ and you are going to lose out to people who are passionate either way
I AM passionate though, and I actually enjoy and have fun doing little projects of my own. But I also feel a bit guilty of wasting my time if it isn't really productive.

>They are several levels of intellect below what is required to actually understand what you're trying to tell them.
Why companies even hire those retards though? Why not just schedule someone from the dev team a few hous a week to do technical interviews?

I am a recruiter/interviewer.

If your github contributions are "correcting a spelling error" and "a new library to determine odd and even numbers in the range of 0-10", then you might as well not bother. But actual contribution to real projects... that is awesome!

So do not ask: "Should I put my github on my resume?" Ask instead: "Am I really contributing to programming projects?"

When I review applications I'll take a look, but they won't influence my hiring decision. Your experience, what's on your resume and how well the interview goes dictates that. If anything, the projects give us talking points, but nothing more.

anecdote, I was only hired at current company because I had personal projects on github. it was a smaller company at the time (about 12 devs).

i don't think you'll find recruiters at larger firms looking at your personal shit. pedigree is everything to them.

Fucking a. I always plan on contributing to actual projects, but I have no idea how to actually get started. My github is filled with green though for the last 3 years, with personal projects, tools, etc. It tells you one thing, for sure: I write code every single day.

Is having your own projects also good, or is it better to mostly be contributing to big-name existing projects? Where would fall?