3 ms·

Interesting. I’ve hired At least 100 developers in my career And have never seen coding challenges or boot camps as Red flags, rather I see them as someone goin

Interesting. I’ve hired At least 100 developers in my career And have never seen coding challenges or boot camps as Red flags, rather I see them as someone going out and trying to learn and improve. On the contrary certain universities and employers certainly are( too much indoctrination(and ego in some cases) to undo). I know a number of boot camp graduates working in FANG level companies. Coding challenges are very important, leetcode questions come up a lot in interviewing loops at most big companies and I think their use is expanding. As much as I hate LC, it’s still a good skill to have if wanting to become a software engineer. I’ve never once looked at a candidates GitHub. There is no proof they wrote anything there. Plus I’ve usually worked in domains that always required tools and knowledge you most likely wouldn’t have anyways, no point in testing, so I hire based on if your a good person with the propensity to learn, grow, and do good things.

jcpst 4y ago
I don’t have hiring authority, but I was on a lot of technical interviews at my company for a while. When people put their GH handle on their resume, I definitely checked it out. Sometimes I would even see if I could get it running on the first try. This has been an indicator of some of practices they have. But it’s only ever a small piece of the picture. Some people push their code to github when they are very junior, and it doesn’t represent where their skills are currently at. There is the issue of forgery, but I lump it in the same category as lying on a resume- the deception is equally as serious.
- mtnGoat 4y ago
  That’s what I see a lot too. Old code from when they were learning stuff, usually not reflective of their current levels. Most things you do for an employer can’t be shared, so that’s why I’ve always given it low credence.
throwaway675309 4y ago
I absolutely check out somebody's GitHub if they include it on their résumé. Usually I'll pick out some parts of the code during the interview and we'll discuss why they made certain decisions (both architectural and technical). I find that this weeds out forgeries relatively quickly.

jcpst 4y ago

I don’t have hiring authority, but I was on a lot of technical interviews at my company for a while. When people put their GH handle on their resume, I definitely checked it out. Sometimes I would even see if I could get it running on the first try. This has been an indicator of some of practices they have. But it’s only ever a small piece of the picture. Some people push their code to github when they are very junior, and it doesn’t represent where their skills are currently at. There is the issue of forgery, but I lump it in the same category as lying on a resume- the deception is equally as serious.

mtnGoat 4y ago
That’s what I see a lot too. Old code from when they were learning stuff, usually not reflective of their current levels. Most things you do for an employer can’t be shared, so that’s why I’ve always given it low credence.

throwaway675309 4y ago

I absolutely check out somebody's GitHub if they include it on their résumé. Usually I'll pick out some parts of the code during the interview and we'll discuss why they made certain decisions (both architectural and technical). I find that this weeds out forgeries relatively quickly.