Problem
What tends to go wrong.
First DevRel hires go wrong when the company hires for charisma, follower count, or a vague advocacy title instead of practical responsibilities.
$
loading devrel-recruiting... ok
loading proof links... ok
loading contact path... ok
teds services --service devrel-recruiting
Hire DevRel for the work you actually need.
We help teams define, source, and evaluate technical advocates who can earn developer trust and support the business.
Solution
How we help.
We define the role, create the scorecard, evaluate practical work, and support interviews with stronger technical signal.
Who it is for
- Teams making their first DevRel hire
- Companies replacing vague advocacy titles with concrete responsibilities
- Leaders who need technical signal during the hiring process
What you get
- Role definition and scorecard
- Candidate review or sourcing support
- Interview and work-sample calibration
How it works
- Define the role and scorecard
- Review or source candidates against practical criteria
- Support interviews, work samples, and final calibration
Start a conversation
Tell us what you need to build, break, or explain.
teds proof --related
Proof lives in the work.
Related field notes show how we think through the problems behind this service.
Blog
Why Technical Content Is a Product Surface
Why tutorials, docs, demos, examples, and technical explainers should be treated as part of developer experience instead of marketing collateral.
BlogWhy DevRel Is Different for Research and ML Tools
Developer Relations changes when the audience is researchers, PhD scientists, machine learning engineers, and data scientists because adoption depends on evidence, reproducibility, workflow fit, and technical trust.
BlogWhen Your AI Product Needs DevRel and When It Doesn't
A decision guide for AI founders deciding whether they need DevRel now, technical content first, developer experience repair, or a clearer product strategy.