4 ms·

It's funny because I have made sure to emphasize my personal projects on GitHub on my resume and in interviews, I'm pretty sure they've never looked at anything

It's funny because I have made sure to emphasize my personal projects on GitHub on my resume and in interviews, I'm pretty sure they've never looked at anything.

striking 7y ago
I've definitely had people look at my personal projects. As an example, I applied to a company doing computer vision and they sniffed out my CV projects. They definitely came up in the interview.
bluedino 7y ago
Ironically I've found the same thing. I linked to live demos of projects on my personal web server and never found traffic referred from Github.
hoorayimhelping 7y ago
How big is your sample size? What phase of the interview are you thinking of? Context changes the approach. If I'm doing phone screens (i.e. top of the funnel and looking at large numbers of people) I glance over github projects and links quickly - about a minute per resume to look over everything (this is is why formatting, styling, and ease of reading matter on resumes). If I'm doing in person interviews (i.e. bottom of the funnel, talking to small numbers of people) I look at almost every personal project, website, and link the candidate puts on their resume with the intent of asking the candidate about them.
madhadron 7y ago
Depends on the place. When I was hiring at a startup, trawling a provided GitHub account was the second thing I did after scanning over the resume.
jonfw 7y ago
When I was interviewing after I graduated college last December, all we ever talked about was my projects. We would skip over school (every other candidate they interviewed had a comp-sci degree, not a differentiator) very quickly. I even had an interview where one my interviewers pulled up my GitHub during the interview and asked me questions about design and tooling decisions on certain projects. From each company where I received an interview, I was told that it was because they were interested by my side projects. Of course- it may depend on what your side projects are! Mine were of interest for the cloud based roles I was looking for- RESTful APIs, Kubernetes, AWS, Linux SysAdmin stuff, etc.
nullc 7y ago
It's possible that they were missed because so many people list their GitHub where it contains absolutely zero work written by them (or even nothing at all).
Lunatic666 7y ago
Then you applied at the wrong companies. For people with a real GitHub repo with a project or contributions, I always skip all programming tests and jump on the real code. It's a real pleasure to have an excited candidate explaining reasons for architecture or choice of tools etc. compared to fizz buzz. I can only encourage everyone to bring a small side project, it will make your interviews easier.
- bradlys 7y ago
  You can say this as much as you want but it's an industry practice. Almost every company I interviewed with in the bay area never looked at any source code for projects I did. (Not even a project that had over 50,000 users - they just installed it and said, "Oh, yeah, that's sweet. Thanks! Now finish writing this sudoku checker and then doing a spiral matrix traversal.") They're using a standardized interview format and they don't care about anything else. I've interviewed with others where I did have projects up, they viewed the source code, and it went over well with them - but that was extremely rare (I can only recall 1 at the moment out of the 100+ companies I've interviewed at).

It's funny because I have made sure to emphasize my personal projects on GitHub on my resume and in interviews, I'm pretty sure they've never looked at anything.

striking 7y ago

I've definitely had people look at my personal projects. As an example, I applied to a company doing computer vision and they sniffed out my CV projects. They definitely came up in the interview.

bluedino 7y ago

Ironically I've found the same thing. I linked to live demos of projects on my personal web server and never found traffic referred from Github.

hoorayimhelping 7y ago

How big is your sample size? What phase of the interview are you thinking of? Context changes the approach. If I'm doing phone screens (i.e. top of the funnel and looking at large numbers of people) I glance over github projects and links quickly - about a minute per resume to look over everything (this is is why formatting, styling, and ease of reading matter on resumes). If I'm doing in person interviews (i.e. bottom of the funnel, talking to small numbers of people) I look at almost every personal project, website, and link the candidate puts on their resume with the intent of asking the candidate about them.

madhadron 7y ago

Depends on the place. When I was hiring at a startup, trawling a provided GitHub account was the second thing I did after scanning over the resume.

jonfw 7y ago

When I was interviewing after I graduated college last December, all we ever talked about was my projects. We would skip over school (every other candidate they interviewed had a comp-sci degree, not a differentiator) very quickly. I even had an interview where one my interviewers pulled up my GitHub during the interview and asked me questions about design and tooling decisions on certain projects. From each company where I received an interview, I was told that it was because they were interested by my side projects. Of course- it may depend on what your side projects are! Mine were of interest for the cloud based roles I was looking for- RESTful APIs, Kubernetes, AWS, Linux SysAdmin stuff, etc.

nullc 7y ago

It's possible that they were missed because so many people list their GitHub where it contains absolutely zero work written by them (or even nothing at all).

Lunatic666 7y ago

Then you applied at the wrong companies. For people with a real GitHub repo with a project or contributions, I always skip all programming tests and jump on the real code. It's a real pleasure to have an excited candidate explaining reasons for architecture or choice of tools etc. compared to fizz buzz. I can only encourage everyone to bring a small side project, it will make your interviews easier.

bradlys 7y ago
You can say this as much as you want but it's an industry practice. Almost every company I interviewed with in the bay area never looked at any source code for projects I did. (Not even a project that had over 50,000 users - they just installed it and said, "Oh, yeah, that's sweet. Thanks! Now finish writing this sudoku checker and then doing a spiral matrix traversal.") They're using a standardized interview format and they don't care about anything else. I've interviewed with others where I did have projects up, they viewed the source code, and it went over well with them - but that was extremely rare (I can only recall 1 at the moment out of the 100+ companies I've interviewed at).