Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Stack Overflow Developer Story: A New Technical Resume

blog.stackoverflow.com

Post reply on HN
Print view View original

101–110 of 147 posts

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

#101

Post by fecak »

emodendroket wrote: post #97
fecak wrote: post #52

As someone who reads and writes thousands of developer resumes a year, the major problem I see is that people have a difficult time separating what is important from what isn't, and separating day-to-day responsibilities (which are typically understood from a job title) from unique and novel achievements. I don't know if this kind of tool solves that problem. Much of my work with resume clients is extracting what the…

That sounds like issues of content more than form.

Right. My point was that a new form of delivery doesn't help if the content isn't "right".

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

#102

Post by viraptor »

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.

There are company/country combinations where publishing your own work done in your free time is possible -> but it takes weeks/months of stupid bureaucracy to be officially accepted. At some point it's just not worth it. So while it's an interesting data point when someone does have the GH profile, it doesn't really mean much if they don't.

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

#103

Post by gamedna »

gentleteblor wrote: post #44
gamedna wrote: post #36

My 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…

I'm always excited when alternatives to the resume work. Glad it did for you. 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.

My email is listed in my profile, drop me an email and I am happy to shoot you a slightly redacted copy of what I wrote up.

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

#104

Post by bootload »

"your Developer Story is the best way to share whatever it is that you take pride in. It’s your story; tell it your way."

Are people still relying on third party companies marketing to both sides of the market, to attract employees? You don't really need them. The Internet and contributions to open source [0] is your developer story, use it. [1]

reference:

[0] I realise not everyone can/will want do this.

[1] offer from google engineering (SRE) on basis of newsgroup questions and code.

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

#106

Post by solipsism »

3pt14159 wrote: post #91
thaumasiotes wrote: post #69

Earlier quoted context omitted.

> the rest of it is just making sure you aren't a conartist, which an interview can easily handle I would have thought that if there was one thing an interview was not suited to do, it would be detecting con artists. Isn't passing interviews their only core skill?

Not for a useful interview. If you tell me you founded and sold a machine learning company but can't explain the pros and cons of using variance versus standard deviation then you didn't sell a machine learning company.

One (stddev) is in the same units as the quantity being measured, while the other isn't. I know nothing about machine learning and suck at math and statistics. Did I pass?

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

#107

Post by greggman »

So I got the notice this morning that my info had been changed to this new developer story on SO. I go check, it's literally > 10 screens before a single useful piece of info appears. 70 or so open source projects I contributed to or run followed by my job experience

> "your Developer Story is the best way to share whatever it is that you take pride in. It’s your story; tell it your way."

Um, no, that's not my way. My way would be to list my professional accomplishments first and then list my open source projects just to show how much of a geek I am.

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

#108

Post by initram »

greggman wrote: post #107

So I got the notice this morning that my info had been changed to this new developer story on SO. I go check, it's literally > 10 screens before a single useful piece of info appears. 70 or so open source projects I contributed to or run followed by my job experience > "your Developer Story is the best way to share whatever it is that you take pride in. It’s your story; tell it your way." Um, no, that's not my way. M…

FWIW, there's a tab to switch to the old view which is probably what most recruiters will know to do. I hope they track what recruiters actually click on when checking your resume.

I honestly don't know which they'd prefer. As someone who occasionally interviews people, I do tend to find the cookie cutter descriptions of jobs to be moderately unhelpful. I would be interested in seeing more "what you take pride in," in many cases.

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

#109

Post by csabeer »

Surprisingly, not many people know just how to write a good developer resume. The Developer Story is a good approach but even that is missing the key element that makes a resume work _when you are looking for a job_.

Imagine this scenario:

    - Farmer looking for horse to plough my fields and inspect my farm
    - Horse 1: "I am a stallion! My coat shines in the sun, my mane is dark and glossy, and the very earth trembles as I run. I have come from the stables of Arabia, have been in the armies of Alexander, the greeks, and the mighty Theseus! I have ploughed the fields of Asphodel, and won 'prettiest horse' in the Reading village fair"
    - Farmer: "Wow! You're...impressive"
    - Horse 2: "I enjoy ploughing fields and I'm pretty strong"
    - Farmer: "Great! I can offer you two apples, four sugar cubes, a nice warm barn..."
To be effective, Resume's shouldn't be all about how great we are (unless we are _really_ someone standout). Rather they should be tailored to the job we want.

The resume needs to get through the "hiring funnel". This means they must contain the keywords that the ATS and Recruiter need in addition to our technical accomplishments that the Hiring Manager and Interviewing Panel will want. This really is pretty simple but we get caught up looking inward and not paying attention to the actual audience of the resume. So most resume's end up hit or miss.

For anyone interested, I've written a book on how to do this. The book's description on Amazon contains the entire process so you don't need to buy it unless you want to. https://www.amazon.com/dp/B01KVVY9OA

Post reply on HN