The Design of a Rejected CodeSprint Landing Page

In late November, we at InterviewStreet looked at the number of projects that needed a re-design, realized that the volume of work justified hiring a full-time designer, and reached out to find one. We eventually chose three different designers to work on three different projects. With permission, here is the story of one of them.

Part 1: Wherein he finds us and gives us a lecture

Part 2: Wherein we decide to work on one project, and then change our minds

At this point, I give Stephen a call to discuss the particulars of the CodeSprint landing page.

Part 3: The First CodeSprint Landing Page

Part 4: Wherein I figure out what really bothers me


Epilogue:

As mentioned at the very, very beginning, Stephen was one of three designers that we worked with. They all turned out to have radically different modes of working, and yet were completely competent in their own way. If not for the fact that my interactions with the other two were mostly face-to-face, I would have also included their conversations, and this piece would have been much, much better.

As is self-evident, we went with the original landing page, but with the single page navigation that came out of this conversation, as opposed to a separate, second “Details” page. For that improvement alone, it was money well spent.

Stephen is currently working on the landing page for InterviewStreet’s Recruit product, which we hope to release later this month, after the end of CodeSprint.

One small note that should be mentioned: All our designer work is pre-paid up to agreed upon milestones. Spec work has it’s place, but not at this level.

This entry was posted in CodeSprint. Bookmark the permalink.
  • Anon

    the intro page sucks now, i like Stephen’s last idea much better… just letting u know