Six weeks ago, I launched my first product: Key Values.
Three weeks ago, I wrote about my (long) journey leading up to that launch here in dev.to.
Today, I want to share some of the data I've collected from the 21,000+ users that have visited Key Values since I launched.
Key Values helps engineers find jobs based on shared values, and allows them to learn more about a team’s culture before applying. Job-seekers can visit the site and select from a list of 44 value tags including “Team is Diverse, “Light Meetings, and “Open Source Contributor (see full list here), which then filters the teams that have matching values.
I curated this values list after interviewing dozens of engineers who identify themselves as missionaries, not mercenaries. They believe that team culture and the people they work with are as important as (if not more important than) compensation or company reputation.
I then asked teams to pick the 8 values from this preset list that best describe their engineering culture, and qualify their selections in their profiles.
Whether people were actively looking for a job or not, these were the top 15 tags they selected when they visited Key Values:
Dev.to readers, like the other developers who came to Key Values, valued "Work/Life Balance" and "High Quality Code Base" above the other key values. In fact, these two values were consistently ranked in the #1 and #2 positions regardless of the community or country, (see more data here).
There are a lot of interesting discussions to be had about the top 15 values, but I find it most interesting where the dev.to community values differ.
Users referred from dev.to prioritized "Good for Junior Devs," "Ideal for Parents," and "Pair Programs" much more highly compared to all visitors on Key Values. The dev.to community values these things more than "Impressive Team Members," "Engages with Community," and "Safe Environment to Fail."
Dev.to sent 2,933 readers to Key Values, but here's where it gets interesting.
My article (How I stopped procrastinating, learned to code, and launched my first product) was posted on Hacker News and likely drove significant traffic because it made the front page! (Thanks @rbanffy for posting it!) As a result, it's hard to know how many readers were actually referred by Hacker News.
Despite the clear overlap between dev.to and Hacker News readers, there were still differences between each community’s value selections. Notably, “Good for Junior Devs and “Ideal for Parents are at the top of dev.to’s list but not on Hacker News' list.
Yes, posts about learning to code and launching a product for the first time appeal to green devs, but it’s not as obvious why these same readers would be looking for workplaces suited for parents. Perhaps both junior developers and parents are better represented in dev.to’s readership.
So far, Key Values has received the most traffic from Hacker News, which is why I published a story specifically for the HN audience appropriately titled: What Hacker News readers want in a job. You can read more about what members of the Hacker News, Product Hunt, and dev.to communities value most and how them compare with one another. I also discuss how value selections vary across countries, and what we might learn about engineering culture at the national level.
I appreciate how supportive the dev.to community has been ––Â thank you!
If you want to get in touch, you can email me (firstname.lastname@example.org) or find me on Twitter (@lynnetye, @keyvaluesio). Lastly, I haven't decided what I should write about next... so if you have any ideas or requests, comment below! ðŸ¤—