Stack OverflowCreating the new developer resume (CV).

The challenge

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.


Define new developers and employers needs: the new CV should be more useful and perform better than the current one.


Support the current product (Stack Overflow traditional CV) and provide everything the job feature needs.


Project lead (for the first 6 months, then handed to a PM), senior product designer, front-end developer (css and html only).

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.


The product

New design & content.


Design & product decisions.

All decisions were tested during many hallway testing sessions with developers.

Technologies are emphasized, whether it's the tech stack or technologies used on projects or at specific jobs.

It's designed in a way where users look good even if they don't have any work experience or education, as long as they can code. That decision was made because we met a lot of great developers who were self-taught in programming.

The Developer Story is based on what you've built, therefore code shipped is as important as traditional entries.

Entries that meet developers needs.


Inline editing.

Developers should see their story as they build it.

Screen Shot 2016-06-15 at 12.56.09Screen Shot 2016-06-15 at 12.56.09
Screen Shot 2016-06-15 at 12.56.18Screen Shot 2016-06-15 at 12.56.18

On boarding

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.

old signupold signup

New signup view.


If users select a choice in the "Where do you code" section, they'll be asked if they're looking for a job.

A/B testings results.



The product is currently in beta so unfortunately I can't talk about KPIs changes yet.