The Stack Overflow Developer Story: A New Technical Resume

#1

Post by sklivvz1971 » Tue, Oct 11, 2016, 4:08 PM UTC

The Stack Overflow Developer Story: A New Technical Resume
blog.stackoverflow.com

Re: The Stack Overflow Developer Story: A New Technical Resume

#2

Post by minimaxir » Tue, Oct 11, 2016, 4:58 PM UTC

Weren'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.

Re: The Stack Overflow Developer Story: A New Technical Resume

#3

Post by jofer » Tue, Oct 11, 2016, 4:58 PM UTC

I was skeptical of this when they first launched the earlier versions, but I actually quite like the way they've done it in the final version.

My favorite resume of all time is Matt Hall's stratigraphic column resume: https://static.squarespace.com/static/549dcda5e4b0a47d0ae1db... (His blog post about it is here: http://www.agilegeoscience.com/blog/2010/12/17/resume-20.htm...)

I'm a geologist, so I'm rather fond of the puns, etc that he's made here, but the point is that a straigraphic column is a great way to lay out a resume. It gives a vertical visual depiction of what the person has been doing from most recent to longest ago.

That's exactly what the developer story is. I really like that they've used that visual layout. It's a very effective way to convey activities and employment history.

Re: The Stack Overflow Developer Story: A New Technical Resume

#4

Post by JustSomeNobody » Tue, Oct 11, 2016, 4:59 PM UTC

Is it really now? That sucks as I don't really engage with SO that often; Hardly ever really. Sure, if I Google for something SO results come up, but normally I search YouTube for a talk/tutorial or search Github for snippets of code.

I guess I'm screwed...

Re: The Stack Overflow Developer Story: A New Technical Resume

#5

Post by tenpoundhammer » Tue, Oct 11, 2016, 5:04 PM UTC

I have seen numerous versions of the "New Resume" in the last ten years or so. It's really hard to replace something universal that everyone understands, even if it's antiquated. I doubt this will fair much better.

Re: The Stack Overflow Developer Story: A New Technical Resume

#6

Post by thecolorblue » Tue, Oct 11, 2016, 5:08 PM UTC

JustSomeNobody wrote: post #4

Is it really now? That sucks as I don't really engage with SO that often; Hardly ever really. Sure, if I Google for something SO results come up, but normally I search YouTube for a talk/tutorial or search Github for snippets of code. I guess I'm screwed...

That is why this is a good move on stack overflow's part. They wand developers to feel like they have to use SO.

Re: The Stack Overflow Developer Story: A New Technical Resume

#7

Post by minimaxir » Tue, Oct 11, 2016, 5:12 PM UTC

thecolorblue wrote: post #6

JustSomeNobody wrote: post #4

Is it really now? That sucks as I don't really engage with SO that often; Hardly ever really. Sure, if I Google for something SO results come up, but normally I search YouTube for a talk/tutorial or search Github for snippets of code. I guess I'm screwed...

That is why this is a good move on stack overflow's part. They wand developers to feel like they have to use SO.

In terms of vertical integration, this technical resume aligns more with SO's robust job platform than with the Q/A platform.

Re: The Stack Overflow Developer Story: A New Technical Resume

#8

Post by drivingmenuts » Tue, Oct 11, 2016, 5:18 PM UTC

JustSomeNobody wrote: post #4

Is it really now? That sucks as I don't really engage with SO that often; Hardly ever really. Sure, if I Google for something SO results come up, but normally I search YouTube for a talk/tutorial or search Github for snippets of code. I guess I'm screwed...

I barely even look at SO. It's pretty much like Quora, as far as I'm concerned.

Re: The Stack Overflow Developer Story: A New Technical Resume

#9

Post by Dzugaru » Tue, Oct 11, 2016, 5:22 PM UTC

minimaxir wrote: post #2

Weren'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 OK for a first step in recruitment, I don't understand the need for extra fanfare.

Re: The Stack Overflow Developer Story: A New Technical Resume

#10

Post by dasil003 » Tue, Oct 11, 2016, 5:22 PM UTC

drivingmenuts wrote: post #8

JustSomeNobody wrote: post #4

Is it really now? That sucks as I don't really engage with SO that often; Hardly ever really. Sure, if I Google for something SO results come up, but normally I search YouTube for a talk/tutorial or search Github for snippets of code. I guess I'm screwed...

I barely even look at SO. It's pretty much like Quora, as far as I'm concerned.

Yes it is like Quora, just with domain specificity. I guess you see this as a bad thing, but both sites are tremendous fonts of information. What is preferable to you? Academic papers? Books? Conference Talks? Random Blog Posts? Man pages?