At the end of this section, you’ll have embedded the Paircast button in your readme.

This is part 3 of a 3 part series on testing your developer experience with Paircast.
Start from part 1, or go back to part 2.

Share your Invite Link

On your project page, you’ll see some information about how you can invite developers to your Paircast project.

There are plenty of ways to recruit developers to your test (stay tuned!). Here are some common options:

  • Embed the “Record Paircast” button in your repository docs
  • Embed the “Record Paircast” button in your documentation website
  • Send your Invite Link to co-workers
  • Blast your Invite Link out to your developer community
  • Hire developers on Upwork
  • Haxor can recruit developers for you

For this guide, we’ll imagine we’re embedding the test into the Tesseract.js docs. This is a great option if you already have a stream of developers getting started with your product.

If you need some extra incentive to get developers excited, consider putting a coupon code in your Final Message or try hiring developers on a freelancing site. At Haxor we’ve found that the number one reason developers participate is to have an influence on product development.

Navigate to your Readme and click the Edit icon.

Copy the Markdown button code and paste it into your Readme. We reccomend using messaging like “help us improve these docs” or “we want your feedback.”

Make sure to put this button right before your installation instructions.

Review Developer Sessions

As developers complete your test, you’ll get emails and they’ll show up on your project page.