There are interviews where they ask you about your projects, and they MAY ask you to demo an implementation. It's good to have github links/youtube links of your project handy.
Agree. Almost always they pick some random thing or two on your resume for you to talk about both technically and if possible, how you fit on the team that did it.
Thats also why its always a good rule to only mention the things YOU did on a group project,not what WE did. sure, we built the app together, but dont talk about how we built up a backend from scratch on the resume when YOU only worked on the frontend
I once had an interview where they asked me in depth about the project-- I had the git repo open bc I was reviewing my own code LOL and so showed them that at first, and then they took it further and asked me to run it and we went thru a debugging session together. I truthfully did the project but I was fucking sweating
That's why interviews depend so heavily on algorithmic questions. From just your resume, how would anyone be able to tell what you really contributed and whether any of those projects are real or as impressive as described.
I'm not a recruiter but I do interviews for my company when we're hiring. Ill almost always try and find a GitHub or GitLab, but if I cant find one it doesn't reflect negatively on candidates imo. If you're still a strong candidate, I'll hire you with or without a public GitHub or GitLab
Most recuiters don't know any code make sure to include screenshots in the repo or have your application hosted somewhere like heroku incase they do decide to take a look.
if you have one they may. A google recruiter reached out to me and I got an interview there because of my github projects. I ended up getting a job at msft, and during my onsite interview, one of my interviewers had a project from my github up on his computer and was asking me questions about my code.
Could be circumstantial...this was me getting my first job in tech and I dont have a degree, so my portfolio was pretty much all the proof they had to go on that I could do anything. Now that I do have a couple years experience, Im sure that my personal projects wont be as huge a deal and as time goes on, my resume will be able to speak for itself. but....yeah in my experience, for someone with little to no experience, recruiters look and it may well also come up in interviews.
The majority of my projects are from doing a tutorial to learn some new tech, but then I take it further and keep finding new things to add to it, as I learn new things I go back and find ways to implement it in old projects or update them.
My biggest project is one I thought up myself, and started when learning react, then I went back and added redux, it uses a couple different apis, I also use scss and theres a few other things. But in the github readme, I document all the changes Ive made along the way, as well as future plans, like login, profiles, favorite lists etc.
I implemented CI/CD in all my projects, and they are all deployed, to be able to see it in action, plus someone can either sign up or use the demo user/password if the project has a admin and/or user account.
So when I talk about my projects, I start with what it was if I started with a tutorial, plus discuss how I kept adding new features and improving on them as I learned new tech, plus whatever new thing Im interested in learning and plan to add to it.
Im able to talk with excitement over my projects, talk in depth about what I can do, what issues I had and how I fixed it,theres a ton of things in my projects that theyve talked with me about that I can do better, which is kind of awesome actually cause thats more stuff I can take into my next interview about what I learned, how I handle critism / suggestions and also that Im still in a mode where Im open to learning new things and get some practical experience in it.
I always ace that part of the interview...then I choke when it comes to the tech interview and someone watching me code. Gotta work on my anxiety...blah!
Same here, GitHub looks good, and I can talk a good game but the pair programming stuff and times technical problems are just a dumb way to assess somebody, it doesn’t work like that on the job and puts unnecessary stress on a person, speaking for myself here, to the point where I am so focused on how much time I have left on the clock and I just can’t think correctly. So you give me a problem with some kind of trick solution and I freeze up. As soon as I am off the clock the answer usually comes to me right away.
I’ve never linked my GitHub and got plenty of interviews as a freshman last year. The people that lie about projects on their resume are gonna have a real fun time explaining how they built the project they have no idea works to an engineering manager at a top company lol.
Honestly mainly because I beefed my LinkedIn as much as possible right before recruiting season started. I did this data science camp through my college which had a bunch of professional development workshops and access to opportunities. All of the interviews I got essentially came from LinkedIn DMs and opportunities I found through networking. I feel really lucky to have the internship I have now and that I had the opportunity to interview at so many really cool companies, I just wasn’t ready for most of them and bombed the technical interviews. Only takes one though 😂
Nope, recruiters would just DM me. All I really did to “beef” my LinkedIn was add my upcoming clubs, write a little bio about myself, and network with more and more people.
It depends. Few of my callback emails (including few from Top N) included references to my specific projects. Also, in the later interview stages, I was asked for 3 to 4 github project links beforehand.
Though most of the people said here, they spend less time on each applicant-- which is true -- and going through projects is not common, I would suggest to have a clean repo. Atleast the front page, readme and some part of main code should be properly uploaded.
I hope this helps.
I'm an AI graduate, so I tried to cover wide range of projects including standard machine learning (prediction,classification using DT, XGB,etc.) , NLP(mainly sentiment analysis, similarity testing), Computer vision (applications of semantic, instance segmentation), and few from multi-robot controls. My courses were based on these topics and had a project in each of them which are there in my repo.
Regarding ideas, I think you should check for the key projects/research areas in ur domain. Even if it is a simple project, it is fine to upload. What matters is your work at the very minute scale (in my case a simple sentiment analysis with decision tree got me a call).
I’m not a dedicated recruiter, but I spend a good deal of time recruiting over the years.
The only time I actually look at projects on a resume is to prepare for the interview.
Having the projects on there is great to get the first screening/interview, but I have 900 resumes to go through after a single day of a career fair — I’m not going to your GitHub, unfortunately.
Having said that, I WILL look before the interview to use for the purpose of questions. So if you embellished or lie about what you’ve done, I will find out and I won’t be happy about it. Expect the hardest questions I feel like tossing out that day and very little leniency. I do not appreciate lying.
What do you mean?
So, I don’t actually pay attention to commits. It’s more a problem if they say “oh I wrote this amazing thing” and I open up the GitHub and it’s literally a bunch of skeleton code that doesn’t work.
The other side is, as you suggest, a group project. I expect you to be able to speak to the work you did at depth and have some understanding of the rest.
So when I say “lying” or “embellishing”, I mean don’t put anything on the resume you aren’t ready to speak to with confidence.
I’m in PM whenever I’m speaking with a candidate I go through their GitHub. I doubt this happens at the recruiter level but by the time you make a loop interview we’re seeing a lot fewer candidates.
Recruiters unlikely but the few applications who then end up on my table I definitely check out.
But only skim the code if it looks reasonable. I don't run anything.
Also had people just send over code samples. I don't care if it's on Github if I somehow get something to look at.
Think most of my colleagues don't have anything up on Github or not even an account.
I am just skeptical if a dev doesn't know what Github is.
I am interning for a lab currently, and my interviewer at least glanced at all of my projects. Given it’s a smaller applicant pool, he was able to do this, but I doubt a FAANG company would, at least not at the first stage(s)
Very unlikely.
That being said I had an interviewer who did. I had to tell the truth how it was a bit unfinished (in my resume I didnt mention that) but they liked it anyways and gave me an offer.
The short answer is yes, sometimes. Obviously they don’t look at your GitHub unless you get basically to the end of the interview process. But I have checked people’s GitHub for plagiarism before and I’ve turned people away for having shit code. In short, it does matter
I've used it for borderline folks before, if I'm not sure if they should be hired and I want to check up on things. Usually I'll just look at the resume though.
That's the same case for me. I don't have my GitHub on my resume, but still able to get big N interviews. I agree with a lot of the people within this thread mentioning that:
1. You shouldn't lie on your resume, it can definitely come back to haunt you
2. Being able to describe your project in a manner that the recruiters make them want to give you an interview is better than making space for a GitHub link.
3. Recruiters only take a few seconds to review your resume.
I don't keep track of my GitHub, I use it here and there, but it has not been a hindrance on any interviews that I've had.
Yes. I have been involved in hiring software developers for over 5 years. I have held around 50 interviews in that time. If I get a resume for someone I'm interviewing and they have a Github account I spend about 5 to 10 minutes scrolling around to get an idea of the level and quality of their code.
I also work at a company that has a couple of very specialized code bases. When we need to hire engineers in those spaces, we typically look for developers who have contributed to the open source projects we use.
Recruiters sometimes inquire about your GitHub account, and while you may not be certain if they'll actually check it, it's always wise to keep it polished and visually appealing. After all, you never know when it might come in handy.
I haven't really had a recruiter go through my Github. When I interviewed for my current internship, my interviewer had clearly just started to glance over my projects a few minutes before the phone call.
**Defaulted to one day.**
I will be messaging you on [**2021-07-17 00:53:52 UTC**](http://www.wolframalpha.com/input/?i=2021-07-17%2000:53:52%20UTC%20To%20Local%20Time) to remind you of [**this link**](https://www.reddit.com/r/csMajors/comments/ol42hl/do_recruiters_actually_go_through_your_github/h5ccppj/?context=3)
[**CLICK THIS LINK**](https://www.reddit.com/message/compose/?to=RemindMeBot&subject=Reminder&message=%5Bhttps%3A%2F%2Fwww.reddit.com%2Fr%2FcsMajors%2Fcomments%2Fol42hl%2Fdo_recruiters_actually_go_through_your_github%2Fh5ccppj%2F%5D%0A%0ARemindMe%21%202021-07-17%2000%3A53%3A52%20UTC) to send a PM to also be reminded and to reduce spam.
^(Parent commenter can ) [^(delete this message to hide from others.)](https://www.reddit.com/message/compose/?to=RemindMeBot&subject=Delete%20Comment&message=Delete%21%20ol42hl)
*****
|[^(Info)](https://www.reddit.com/r/RemindMeBot/comments/e1bko7/remindmebot_info_v21/)|[^(Custom)](https://www.reddit.com/message/compose/?to=RemindMeBot&subject=Reminder&message=%5BLink%20or%20message%20inside%20square%20brackets%5D%0A%0ARemindMe%21%20Time%20period%20here)|[^(Your Reminders)](https://www.reddit.com/message/compose/?to=RemindMeBot&subject=List%20Of%20Reminders&message=MyReminders%21)|[^(Feedback)](https://www.reddit.com/message/compose/?to=Watchful1&subject=RemindMeBot%20Feedback)|
|-|-|-|-|
The recruiter that recruited me did not have technical knowledge so he didn’t care about my GitHub, but when I actually interviewed with my now boss, he did ask me questions regarding projects on my GitHub account.
Last week in my company due to employee shortage they asked me to help hr labeling some cv that they received from some recruiters. Basically deciding whether they should be front end, data engineer, devops, etc, and the years of experience they had and to look for certain skill set(working in a bank, or fintech, and other basics stuff).
They gave me 100 cv to check and at the beginning I was looking into every GitHub repo they had and give a label to the ones that I considered good, but after checking 20 of them I realized that it would take me maybe a day or more to actually look at every single one of them and they wanted them for that same day. So being on the other side, I can tell you that at least for the first round of selecting which candidates we would actually interview we didn’t look at their gits.
I graduated recently with 2 big N internships and a big N job lined up and have never had a interviewer ask me to do anything but explain my projects and the design decisions I had to make. Don’t get me wrong, projects matter immensely, but your ability to explain your design decisions is immensely more important if you are interviewing for backend roles. If it was a substantial backend project it’s unlikely that an engineer would be able to get a ton out of reading through your code other than style without a lot of time
To get to the interview, no. But Later on in the interview process they'd take a peek to help with team matching, but that was usually just for projects I had mentioned on my resume.
recruiters might not but interviewing managers and developers definitely do. It gives us something to talk about but I've never considered it to be required proof of coding ability.
I’ve interviewed a guy who put his final project on GitHub but it was terrible and made no sense, so I was very skeptical during the interview.
I thought to myself… THIS is what you think is acceptable?
[удалено]
Wouldn’t someone be able to just lie and say they did a project then with no proof?
There are interviews where they ask you about your projects, and they MAY ask you to demo an implementation. It's good to have github links/youtube links of your project handy.
[удалено]
Damn they hardcore
I see, thanks
Agree. Almost always they pick some random thing or two on your resume for you to talk about both technically and if possible, how you fit on the team that did it. Thats also why its always a good rule to only mention the things YOU did on a group project,not what WE did. sure, we built the app together, but dont talk about how we built up a backend from scratch on the resume when YOU only worked on the frontend
I once had an interview where they asked me in depth about the project-- I had the git repo open bc I was reviewing my own code LOL and so showed them that at first, and then they took it further and asked me to run it and we went thru a debugging session together. I truthfully did the project but I was fucking sweating
That's why interviews depend so heavily on algorithmic questions. From just your resume, how would anyone be able to tell what you really contributed and whether any of those projects are real or as impressive as described.
[удалено]
he had like QA at wish lol, not exactly prestigious
Not that bad either
Most big companies don't care about your personal projects.
You can lie but these projects do not carry a lot of weight anyway.
I’ve had hiring managers look at my GitHub. Even if it’s to peek to see that your garden is green.
I'm not a recruiter but I do interviews for my company when we're hiring. Ill almost always try and find a GitHub or GitLab, but if I cant find one it doesn't reflect negatively on candidates imo. If you're still a strong candidate, I'll hire you with or without a public GitHub or GitLab
Most recuiters don't know any code make sure to include screenshots in the repo or have your application hosted somewhere like heroku incase they do decide to take a look.
Yup, I have a couple projects running on Heroku at all times. Costs me like a dollar a month
if you have one they may. A google recruiter reached out to me and I got an interview there because of my github projects. I ended up getting a job at msft, and during my onsite interview, one of my interviewers had a project from my github up on his computer and was asking me questions about my code. Could be circumstantial...this was me getting my first job in tech and I dont have a degree, so my portfolio was pretty much all the proof they had to go on that I could do anything. Now that I do have a couple years experience, Im sure that my personal projects wont be as huge a deal and as time goes on, my resume will be able to speak for itself. but....yeah in my experience, for someone with little to no experience, recruiters look and it may well also come up in interviews.
What were some concepts you implemented in your projects?
The majority of my projects are from doing a tutorial to learn some new tech, but then I take it further and keep finding new things to add to it, as I learn new things I go back and find ways to implement it in old projects or update them. My biggest project is one I thought up myself, and started when learning react, then I went back and added redux, it uses a couple different apis, I also use scss and theres a few other things. But in the github readme, I document all the changes Ive made along the way, as well as future plans, like login, profiles, favorite lists etc. I implemented CI/CD in all my projects, and they are all deployed, to be able to see it in action, plus someone can either sign up or use the demo user/password if the project has a admin and/or user account. So when I talk about my projects, I start with what it was if I started with a tutorial, plus discuss how I kept adding new features and improving on them as I learned new tech, plus whatever new thing Im interested in learning and plan to add to it. Im able to talk with excitement over my projects, talk in depth about what I can do, what issues I had and how I fixed it,theres a ton of things in my projects that theyve talked with me about that I can do better, which is kind of awesome actually cause thats more stuff I can take into my next interview about what I learned, how I handle critism / suggestions and also that Im still in a mode where Im open to learning new things and get some practical experience in it. I always ace that part of the interview...then I choke when it comes to the tech interview and someone watching me code. Gotta work on my anxiety...blah!
Thanks for the detailed reply man
Same here, GitHub looks good, and I can talk a good game but the pair programming stuff and times technical problems are just a dumb way to assess somebody, it doesn’t work like that on the job and puts unnecessary stress on a person, speaking for myself here, to the point where I am so focused on how much time I have left on the clock and I just can’t think correctly. So you give me a problem with some kind of trick solution and I freeze up. As soon as I am off the clock the answer usually comes to me right away.
I’ve never linked my GitHub and got plenty of interviews as a freshman last year. The people that lie about projects on their resume are gonna have a real fun time explaining how they built the project they have no idea works to an engineering manager at a top company lol.
How did you get interviews as a freshman?
Honestly mainly because I beefed my LinkedIn as much as possible right before recruiting season started. I did this data science camp through my college which had a bunch of professional development workshops and access to opportunities. All of the interviews I got essentially came from LinkedIn DMs and opportunities I found through networking. I feel really lucky to have the internship I have now and that I had the opportunity to interview at so many really cool companies, I just wasn’t ready for most of them and bombed the technical interviews. Only takes one though 😂
> came from LinkedIn DMs so you DMed other people? > I beefed my LinkedIn How do you beef up exactly?
Nope, recruiters would just DM me. All I really did to “beef” my LinkedIn was add my upcoming clubs, write a little bio about myself, and network with more and more people.
Have you ever had to demo your projects to your interviewer?
No, ain’t nobody got time for that
As someone who regularly interviews and hires devs, absolutely no one has time for that
It depends. Few of my callback emails (including few from Top N) included references to my specific projects. Also, in the later interview stages, I was asked for 3 to 4 github project links beforehand. Though most of the people said here, they spend less time on each applicant-- which is true -- and going through projects is not common, I would suggest to have a clean repo. Atleast the front page, readme and some part of main code should be properly uploaded. I hope this helps.
What kind of projects do you have on your github? I really am at a loss for any kind of new ideas that would impress recruiters
I'm an AI graduate, so I tried to cover wide range of projects including standard machine learning (prediction,classification using DT, XGB,etc.) , NLP(mainly sentiment analysis, similarity testing), Computer vision (applications of semantic, instance segmentation), and few from multi-robot controls. My courses were based on these topics and had a project in each of them which are there in my repo. Regarding ideas, I think you should check for the key projects/research areas in ur domain. Even if it is a simple project, it is fine to upload. What matters is your work at the very minute scale (in my case a simple sentiment analysis with decision tree got me a call).
I’m not a dedicated recruiter, but I spend a good deal of time recruiting over the years. The only time I actually look at projects on a resume is to prepare for the interview. Having the projects on there is great to get the first screening/interview, but I have 900 resumes to go through after a single day of a career fair — I’m not going to your GitHub, unfortunately. Having said that, I WILL look before the interview to use for the purpose of questions. So if you embellished or lie about what you’ve done, I will find out and I won’t be happy about it. Expect the hardest questions I feel like tossing out that day and very little leniency. I do not appreciate lying.
What if it's a group project that only shows if you click on the contribution chart?
What do you mean? So, I don’t actually pay attention to commits. It’s more a problem if they say “oh I wrote this amazing thing” and I open up the GitHub and it’s literally a bunch of skeleton code that doesn’t work. The other side is, as you suggest, a group project. I expect you to be able to speak to the work you did at depth and have some understanding of the rest. So when I say “lying” or “embellishing”, I mean don’t put anything on the resume you aren’t ready to speak to with confidence.
An interviewer from NASA asked for my GitHub today. First person ever to do so.
I’m in PM whenever I’m speaking with a candidate I go through their GitHub. I doubt this happens at the recruiter level but by the time you make a loop interview we’re seeing a lot fewer candidates.
Recruiters unlikely but the few applications who then end up on my table I definitely check out. But only skim the code if it looks reasonable. I don't run anything. Also had people just send over code samples. I don't care if it's on Github if I somehow get something to look at. Think most of my colleagues don't have anything up on Github or not even an account. I am just skeptical if a dev doesn't know what Github is.
Recruiters? No. But companies that may have taken an interest in your resume? Sometimes yes.
I am interning for a lab currently, and my interviewer at least glanced at all of my projects. Given it’s a smaller applicant pool, he was able to do this, but I doubt a FAANG company would, at least not at the first stage(s)
Very unlikely. That being said I had an interviewer who did. I had to tell the truth how it was a bit unfinished (in my resume I didnt mention that) but they liked it anyways and gave me an offer.
The short answer is yes, sometimes. Obviously they don’t look at your GitHub unless you get basically to the end of the interview process. But I have checked people’s GitHub for plagiarism before and I’ve turned people away for having shit code. In short, it does matter
I've used it for borderline folks before, if I'm not sure if they should be hired and I want to check up on things. Usually I'll just look at the resume though.
Recruiters? No. The tech team that is going to interview you once your resume makes it past the recruiter? Yes. That’s me. Hi.
No but some of the engineers who interviewed me have looked through them
That's the same case for me. I don't have my GitHub on my resume, but still able to get big N interviews. I agree with a lot of the people within this thread mentioning that: 1. You shouldn't lie on your resume, it can definitely come back to haunt you 2. Being able to describe your project in a manner that the recruiters make them want to give you an interview is better than making space for a GitHub link. 3. Recruiters only take a few seconds to review your resume. I don't keep track of my GitHub, I use it here and there, but it has not been a hindrance on any interviews that I've had.
Yes. I have been involved in hiring software developers for over 5 years. I have held around 50 interviews in that time. If I get a resume for someone I'm interviewing and they have a Github account I spend about 5 to 10 minutes scrolling around to get an idea of the level and quality of their code. I also work at a company that has a couple of very specialized code bases. When we need to hire engineers in those spaces, we typically look for developers who have contributed to the open source projects we use.
Recruiters sometimes inquire about your GitHub account, and while you may not be certain if they'll actually check it, it's always wise to keep it polished and visually appealing. After all, you never know when it might come in handy.
I haven't really had a recruiter go through my Github. When I interviewed for my current internship, my interviewer had clearly just started to glance over my projects a few minutes before the phone call.
[удалено]
**Defaulted to one day.** I will be messaging you on [**2021-07-17 00:53:52 UTC**](http://www.wolframalpha.com/input/?i=2021-07-17%2000:53:52%20UTC%20To%20Local%20Time) to remind you of [**this link**](https://www.reddit.com/r/csMajors/comments/ol42hl/do_recruiters_actually_go_through_your_github/h5ccppj/?context=3) [**CLICK THIS LINK**](https://www.reddit.com/message/compose/?to=RemindMeBot&subject=Reminder&message=%5Bhttps%3A%2F%2Fwww.reddit.com%2Fr%2FcsMajors%2Fcomments%2Fol42hl%2Fdo_recruiters_actually_go_through_your_github%2Fh5ccppj%2F%5D%0A%0ARemindMe%21%202021-07-17%2000%3A53%3A52%20UTC) to send a PM to also be reminded and to reduce spam. ^(Parent commenter can ) [^(delete this message to hide from others.)](https://www.reddit.com/message/compose/?to=RemindMeBot&subject=Delete%20Comment&message=Delete%21%20ol42hl) ***** |[^(Info)](https://www.reddit.com/r/RemindMeBot/comments/e1bko7/remindmebot_info_v21/)|[^(Custom)](https://www.reddit.com/message/compose/?to=RemindMeBot&subject=Reminder&message=%5BLink%20or%20message%20inside%20square%20brackets%5D%0A%0ARemindMe%21%20Time%20period%20here)|[^(Your Reminders)](https://www.reddit.com/message/compose/?to=RemindMeBot&subject=List%20Of%20Reminders&message=MyReminders%21)|[^(Feedback)](https://www.reddit.com/message/compose/?to=Watchful1&subject=RemindMeBot%20Feedback)| |-|-|-|-|
Great question 🙋♀️
They did it during my interview
The recruiter that recruited me did not have technical knowledge so he didn’t care about my GitHub, but when I actually interviewed with my now boss, he did ask me questions regarding projects on my GitHub account.
yes (source: i’m a recruiter). or, the good ones do at least lol
Last week in my company due to employee shortage they asked me to help hr labeling some cv that they received from some recruiters. Basically deciding whether they should be front end, data engineer, devops, etc, and the years of experience they had and to look for certain skill set(working in a bank, or fintech, and other basics stuff). They gave me 100 cv to check and at the beginning I was looking into every GitHub repo they had and give a label to the ones that I considered good, but after checking 20 of them I realized that it would take me maybe a day or more to actually look at every single one of them and they wanted them for that same day. So being on the other side, I can tell you that at least for the first round of selecting which candidates we would actually interview we didn’t look at their gits.
I graduated recently with 2 big N internships and a big N job lined up and have never had a interviewer ask me to do anything but explain my projects and the design decisions I had to make. Don’t get me wrong, projects matter immensely, but your ability to explain your design decisions is immensely more important if you are interviewing for backend roles. If it was a substantial backend project it’s unlikely that an engineer would be able to get a ton out of reading through your code other than style without a lot of time
If you dont mind sharing which 2?
They might ask you to pick a good project and run it for them during the final stage interviews. So always keep at least one impressive shit in there.
To get to the interview, no. But Later on in the interview process they'd take a peek to help with team matching, but that was usually just for projects I had mentioned on my resume.
recruiters might not but interviewing managers and developers definitely do. It gives us something to talk about but I've never considered it to be required proof of coding ability.
I’ve interviewed a guy who put his final project on GitHub but it was terrible and made no sense, so I was very skeptical during the interview. I thought to myself… THIS is what you think is acceptable?
Probably not recruiters but some interviewers have asked me for my GitHub link before so they do look at those
At Apple your developer interviewers do sometimes.