Skip to main content

For recruiters

Posting roles

Writing role descriptions that match well, the salary signals candidates respond to, and how role attributes flow into the matchmaker.

Last updated

A role on Jobby.dev isn't a long-form posting — it's structured matching input. The closer the role's required fields are to the actual job, the better the matchmaker pairs you. Here's how to write one that doesn't starve.

Required fields

  • Title.One line. Use the title you'd post publicly — "Senior backend engineer (Go)", not "BE-3 Tier-2 IC". Internal codenames don't score against seeker headlines.
  • Required skills (3-7 tags).The skills the seeker must have. Three is too few (you'll match anyone); ten is too many (you'll starve). Five is the sweet spot.
  • Compensation range.Two numbers. Real ones. The matchmaker hard-filters seekers whose range doesn't overlap; posting $80k-$300k to be safe defeats the filter.
  • Location and remote preference. City + country, plus on-site / hybrid / remote. Hybrid roles need a metro radius.
  • Visa sponsorship.Yes / no / case-by-case. Required so visa-sponsoring vs. non-sponsoring roles don't waste each other's time.

Optional but high-signal

  • Bonus skills.Tags that boost the score but aren't required. Useful for niche stacks ("Rust" for a Go role, "Kubernetes" for a backend role).
  • Years-of-experience band.Entry / mid / senior / staff / principal. Filters out way-off seekers; doesn't hard- filter close-but-different bands.
  • Free-text role description. The recruiter sees this mid-interview as reference; the seeker sees it on the role detail page. Use it for the actual work, the team shape, the stack — not for keyword stuffing.

Salary signals

Three things candidates respond to, in this order:

  1. The range itself.Tighter ranges (within 30%) feel more honest; wider ranges (60%+) signal "we don't know what this role is worth".
  2. Equity granularity.Decline to answer is fine; an honest "0.05% over 4 years" is better than a non-answer.
  3. Bonus structure. Mention it explicitly if part of comp. Hidden bonuses kill trust at offer time.

Why some roles starve

The usual culprits:

  • Required skills too specific. "React, Next.js 15 App Router, Tailwind 4, Drizzle, Bun, Zod 4, Vercel AI SDK" will starve. Trim to the truly required signals.
  • Comp band below market. The matchmaker happily matches you, but seekers self-decline. Check the comp band against a real source before listing.
  • On-site only in low-density market. Real, but slow. Pair with hybrid-acceptable roles when possible.

Driving from an agent

Use jobbydev_job_create to post, jobbydev_job_update to tweak, and jobbydev_job_get to read back the active surface. The agent surface mirrors the browser UI 1:1.

Related reading