Hermes González's profile

Devpost UX - How developers search for new jobs

Project Overview
While being part of the Startup Institute's 8 week program i had the opportunity to collaborate with Devpost and giving a hand with one of their projects, Team Pages, that could meant a pivot in their focus as a company. On top of being "the home of hackathons" Devpost was exploring being a place where developers could find jobs, have a portfolio and find best fits with other companies.

My Contributions
I was in charge of research and coming up with solutions that addressed any findings of said research. My primary goal was to conduct interviews to get insight into developer frustrations, motivations, and priorities during their job search. To achieve that first i had to understand various stages of careers to define the differences between Junior, Mid-Level, and Senior developers.

Description
The research pipeline was designed like this: First, gather all the information relevant about developers salaries in the US. Then send some surveys and schedule interviews. After that identify trends, create user personas, and make a presentation to the product manager with our finds
The first survey was meant to get a sense of the priorities of developers looking for new jobs and to spot people open to be interviewed. It was just 7 questions in order to maximize the response and paint a first picture of the dev job hunting scene. After that i sent some follow up mails to try to get some one on one calls to show the current state of the product and finding some areas of improvement.

Then we started to map the concerns and interests of the people we had interviewed. We used some post-its in the wall and got this big picture, differentiating senior, mid-level and junior developers.
This led us to rethink some of the aspects of the current state of the Team Pages.
First, trying to achieve a cleaner look in the landing page. Most of the developers we interview had a pretty clear sense of what they were looking for. So instead of showing some of the companies listed looking for hires, we gave more importance to the search process.
We moved from a pop-up window to a more streamlined process of answering questions about location, the positions they were interested in, what level of experience they had, their tech stack and finally the company size. At the moment of this presentation we weren't sure if it was best to input salary expectative so we initially left it out.
And finally the results page. We decided to give a direct overview of the company with the best match. Showing the positions available, then a quick view of the company's interview process, internships, benefits, among other things. Also a section specifically for the Tech stack, something during interviews was particularlly important to more senior developers. We also added a section where members of the company share what they thought of working there, and lastly other results that had fewer matches in the search.

Final thoughts
This project was significant to me because it was my first experience doing UX, and the fact that it was within a New York based startup made it pretty exciting. It was for a brief period but i could get a taste of what it meant to be a UX researcher, and how i could contribute to a team from that role going throug a whole iteration. I wish i had the time to make test over the presentation we made, but already i had some improvements i'd like to make after seing the mockups, like giving more opportunity to navigate other companies before giving a full overview of the best match. Also some branding suggestions that i thought i could help a better postinioning of Devpost.

But i ended up pretty satisfied with the results, and had a great time working with the folks at Devpost who were all super nice.

Check out more about them at https://devpost.com/
Devpost UX - How developers search for new jobs
Published:

Owner

Devpost UX - How developers search for new jobs

Published: