Stack OverflowCreating the new developer resume (CV).
You're more than a resume, show off
what you've built.
Create the new developer CV on Stack Overflow: resumes are outdated and don't address developers' needs, this antiquated system hurts developers.
Finding what's wrong
Defining developers' needs.
I spent the first months looking for ideas and trying to understand what's wrong with the traditional CV. To do so, I met with a lot of developers asking them to introduce themselves to me or to each other: I wanted to know what matter the most to them.
Code came always first, whether it's code shipped or technologies used. Some other topics found in the traditional CV were also de-emphasized. The Developer Story had to represent all of this.
New design & content.
Design & product decisions.
All decisions were tested during many hallway testing sessions with developers.
Entries that meet developers needs.
Developers should see their story as they build it.
Guide users through an inline tour.
New users are guided through an inline tour to talk (again) about the unique selling point and help them set up their story.
The big picture
Redesigning the signup.
Once the product tested, we needed to update the signup to ask more information and redirect them to the Developer Story when necessary. We decided to ask for information that could benefit each features of Stack Overflow and not just the Developer Story. And as always, everything had to be optional. To do so, we did several rounds of A/B testing to be sure that we wouldn't hurt too much the current signup conversion.
Old signup view.
New signup view.
A/B testings results.
The product is currently in beta so unfortunately I can't talk about KPIs changes yet.