I don't see anything on here that I couldn't do with my LinkedIn profile, TBH. I do kinda wish I knew the secrets of how to get 2-3 recruiting emails a day though. Unless it's "have 5 more years of experience," I think my profile could use some help.
dice.com
The Stack Overflow Developer Story: A New Technical Resume
41–50 of 147 posts
Re: The Stack Overflow Developer Story: A New Technical Resume
#42So when the recent email hit my inbox, it was with a healthy dose of skepticism that I just immediately deleted it.
Re: The Stack Overflow Developer Story: A New Technical Resume
#43Weren't GitHub profiles the new technical resume? How well did that work in practice, and how would this Stack Overflow approach be different? I was under the impression (from reading HN/Reddit) that while engineers do read GitHub profiles if explicitly linked in a resume, nontechnical recruiters do not. And they are the gatekeeper to said engineers.
Not every programmer likes to share his side-project code on public places like GitHub - for many reasons. Or pullrequest to some opensource mess. Code you write and problems you solve at work usually can't be shown on GitHub either. So, this "show me your GitHub" thing for me is no different from "show me your Facebook, wait what, no FB account??" experience with non-technical HRs ;) Conventional resume is totally O…
I am often brought in on the hiring process to vet peoples technical skills. I used to just try to ask questions in the hour or two I got with the person, this seemed no better than flipping a coin. Even if the person was honest and we were both talking about the same skill, but how do I know that their experience with that skill is applicable? Now I insist on seeing a portfolio of some kind for coders. A Github, Bitbucket, Sourceforge or any other publicly viewable body of source will do.
15 minutes with someones code is a much better predictor of skill than even several hours of discussion. It costs a lot less too.
Re: The Stack Overflow Developer Story: A New Technical Resume
#44My recent job search lead me to the idea that the traditional resume is broken. Temporal view only gives recruiters and hiring managers the bullet points to qualify you in whatever bucket that they need. Instead of a traditional CV/Resume, I went with a single page narrative approach with a link to the temporal view on my LinkedIn profile. Initially there was some pushback as the recruiters were bellyaching over the…
Did you happen to post about this anywhere (on a blog maybe?). I'd love to see the narrative version and hopefully learn a thing or two.
Re: The Stack Overflow Developer Story: A New Technical Resume
#45Re: The Stack Overflow Developer Story: A New Technical Resume
#46Wait so hiring managers who didn't have more then 60 seconds to parse my resume now have the time to go through years of my stackoverflow activity? Sweet!
The SO story will allow them to scan the highlights quicker IMHO.
This is the only reason I created a logo for my open source project, so that it sticks out whenever someone posts about it.
Re: The Stack Overflow Developer Story: A New Technical Resume
#47Re: The Stack Overflow Developer Story: A New Technical Resume
#48Re: The Stack Overflow Developer Story: A New Technical Resume
#49https://news.ycombinator.com/item?id=12687415
https://news.ycombinator.com/item?id=12686741
But I don't think this is really aimed at supplanting that. It's really just trying to put a better face on the "passive" approach to things and I like it for that.
Re: The Stack Overflow Developer Story: A New Technical Resume
#50Unfortunately there is no way to opt out of this service right now. (edit: I don't want to email security to ask for an opt-out, it would just be nice to opt out until they fix the actual security issue.)
Edit: Found a web form they use on security.stackexchange.