Problem: It is difficult for businesses to narrow down to the perfect candidate on their own.

Solution: Surface more relevant developers to the business.

Problem: Developers are penalized the longer they are on the platform because newer developers appear first.

Solution: Tweak sorting to expose higher quality profiles.

Step 1 - Sort developers based on selected filters.

Filtering already narrows down candidates but the results are always sorted by newest profiles first. Step 1 would boost profiles that match better than others to the top.

For example, if a business selects mid-level developers then folks who chose only mid-level will appear first. Followed by folks who chose both mid-level and senior.

This will apply especially well when specialty tags are in place.

For example, if a business selects Hotwire and Heroku then developers who match both of those tags will appear before one who only has one of them selected.

Step 2 - Then sort developers by a score out of 100.

After filtering sorting is applied, or right away if no filters are selected, developers will be sorted based on a score ranging from -100 to 100.

This score will be calculated based on a few criteria that a) seem to be associated with higher quality profiles on the platform and b) create a better experience for both parties.

• Response rate:
  • Over 90% → +40
  • Under 50% → -40
• Scheduling link:
  • Present → +25
• Source contributor:
  • Yes → +15
• Recently updated profile:
  • Within the last month → +5
  • More than 3 months ago → -5
  • More than 6 months ago → -25
• New profile:
  • Less than 1 week old → +10
• Bio length:
  • More than 200 characters → +5
  • Less than 50 characters → -35