Back to library
TwilioTwilio

10-Day Take-Home with Published Rubric

Developer Relations

What it tests

Content quality, technical depth, communication — with maximum candidate respect

Format

  1. 1Give candidates 10 days to write a publishable technical blog post explaining how to build something with your API
  2. 2Include working code samples
  3. 3Publish the evaluation rubric in advance: Technical accuracy (25%), Writing quality (25%), Code quality (25%), Creativity/engagement (25%)
  4. 4Live presentation of the project (20 min)

What to look for

  • Prior DevRel experience is NOT predictive of success
  • Quality of the take-home output IS predictive
  • The long timeline tests consistency and self-management, not just speed

Full description

Format:

  1. Give candidates 10 days to complete a project:
    • Write a technical blog post explaining how to build [X] with your API
    • Include working code samples
    • The post should be publishable quality
  2. Publish the evaluation rubric in advance so candidates know exactly how they'll be graded:
    • Technical accuracy (25%)
    • Writing quality (25%)
    • Code quality (25%)
    • Creativity/engagement (25%)
  3. Live presentation of the project (20 min)

Time: 10 days (candidate chooses how much to invest)

What to look for:

  • Twilio discovered: prior DevRel experience is NOT predictive of success
  • What IS predictive: quality of the take-home output
  • The long timeline tests consistency and self-management, not just speed

Why the published rubric matters: Candidates know what "good" looks like. This eliminates guesswork and anxiety, producing more authentic work.