How to hire on Toptal: real expectations 2026
How to hire on Toptal: real expectations 2026
To hire on Toptal in 2026, submit a project spec, pay the $500 refundable deposit, and a human matcher introduces 3 vetted candidates within 24 to 48 hours. You then run a 2-week no-risk trial at $60 to $200+ per hour before committing. Most clients sign within 1 to 2 weeks of first contact.
That is the headline. Most posts about hiring on Toptal stop at the deposit and the "top 3%" claim. This one walks the actual buyer playbook: how matching really feels, how the screen is structured, what the 2026 pricing line items look like in your invoice, how to write a spec the matcher can act on, what to grill candidates on in the intro call, and how to escalate when the match misses. We close with an honest comparison to weekly-booking models like Cadence.
How Toptal's matching process actually works in 2026
You fill out a project form on toptal.com, then a Toptal rep books a 20 to 30 minute intake call. They ask about your stack, engagement length, timezone overlap, and "must-haves" versus "nice-to-haves." This call matters more than the form. Spend it specifying outcomes, not just technologies.
After the intake, a human matcher (not an algorithm) reviews their bench and shortlists. In almost all cases you see 3 candidate profiles within 24 to 48 hours. You can ask for resumes, prior client references, and a 30-minute intro call with each. Toptal claims 90% of clients hire the first candidate they meet. That number is real, but it bakes in survivorship bias: clients who reject all 3 candidates often abandon the search rather than ask for round 2.
The $500 refundable deposit is collected before any matcher work begins. If you hire, it credits against the first invoice. If you walk away, you can request a refund. Some clients report friction here, so put the refund request in writing within the first 30 days.
The 2-week "no-risk trial" works like this: you and the engineer start work immediately, you get billed in real time, and if you are not satisfied at the end Toptal refunds those hours or finds a replacement. The catch: the work shipped during the trial is real work that lands in your codebase, and the engineer is real billable contractor time. It is not a free sample.
What the "top 3% of talent" claim really means
This is the line every Toptal page leads with. Here is the actual filter.
Applying engineers go through 4 gates: a language and personality screen, a 1-hour live technical interview with a senior Toptal engineer, a take-home project that takes 1 to 3 weeks, and a continuous evaluation phase after onboarding. Toptal says roughly 3% pass all 4 gates.
Two things to internalize. First, the screen tests engineering skill in a vacuum, not in your codebase. A senior Python engineer who passed the test project might still be a poor fit for your particular monolith, your particular team norms, or your particular release cadence. Second, the screen does not test for AI-native fluency. Toptal does not require Cursor, Claude Code, or Copilot proficiency, and the standard test project is solo-coded without those tools. In 2026 that gap matters more than it did in 2023, because the speed delta between an AI-native shipper and a non-AI-native shipper on a typical SaaS feature is now 2 to 4x. If you want that capability, you will need to screen for it yourself in the intro call.
Toptal screens hard for senior generalist software engineering. It does not screen for fit, stack-specific edge cases, timezone, or modern tooling discipline. Those are still your job.
Real Toptal pricing in 2026 (and the line items you miss)
The headline rate band is $60 to $200+ per hour. That covers most engineering roles. AI specialists, senior architects, and finance experts cluster at the top of the band; mid-level frontend or backend engineers cluster in the $80 to $130 range.
Toptal also publishes weekly bands for ongoing engagements:
| Engagement | Weekly band | Notes |
|---|---|---|
| Part-time (20 hrs/wk) | $1,000 to $3,200 | Most flexible, slower matchers respond |
| Full-time (40 hrs/wk) | $2,000 to $6,400 | Senior engineers prefer this |
| Hourly (ad hoc) | $60 to $200+/hr | Burns deposit faster, no commitment |
Two extra line items to budget for:
- $500 refundable deposit. Required before matching. Credits to your invoice if you hire.
- $79 monthly subscription fee. Recurring access fee for the platform. Usually not waived.
A common trap: the hourly plan technically has no minimum, but senior engineers prefer 20+ hour weekly blocks and matchers will steer your spec that way. Submit a 10-hour ask and you get 1 senior at the bottom of the band, or 3 mid-level candidates. The "top 3%" is gated on weekly-block availability.
The other thing nobody puts on the pricing page: Toptal applies a markup over what the engineer actually receives. Client reports put it at 40 to 50%, meaning a $120/hr billed rate may pay the engineer $70 to $80. Every marketplace does this, but Toptal does not disclose its markup. If you care about take-home rate (because you want the engineer motivated long-term), ask the candidate directly.
For grounding, Cadence prices the same engineering tiers at flat weekly rates: $500 for junior, $1,000 for mid, $1,500 for senior, $2,000 for lead. No deposit, no monthly fee, no markup mystery. That is one anchor point in the market; it is not the right answer for every situation, as we will get to.
How to write a Toptal job spec the matcher can actually act on
The single biggest predictor of a good match is the quality of the spec you submit. Matchers are skilled, but they are not mind readers. Most weak first introductions trace back to a vague spec.
A spec the matcher can act on has 6 fields:
- One outcome. "Ship the first cut of our customer-portal billing UI by end of June." Not "help with frontend stuff."
- Stack specifics. Next.js 15, React Server Components, Stripe billing API, Supabase Postgres. Name versions where they matter.
- Timezone overlap requirement. "Must overlap 4 hours with US Pacific" is a hard constraint. Saying "remote OK" gets you a Bangladesh-based engineer who is asleep during your standup.
- Engagement shape. 20 hours per week for 8 weeks. Or 40 hours per week for 12 weeks. Or "starts at 20, scales to 40 if it works." Be explicit.
- Must-haves versus nice-to-haves. 3 must-haves max. Everything else is nice-to-have. Matchers optimize against the must-haves.
- Codebase context. "We are a 4-person team, 30K LOC monorepo, GitHub Actions CI, deploys via Vercel." Helps matchers screen for engineers who have shipped at your scale.
If you have written a thorough developer-vetting spec for a B2B SaaS engineer, you already have most of these fields. Reuse the same template.
What to ask in the Toptal intro call (the 6-question script)
You get 30 minutes per candidate. Spend the first 3 on context, the next 22 on these 6 questions, and the last 5 on Q&A. Keep notes; you will compare across 3 candidates.
- Walk me through the last feature you shipped end-to-end. What was the spec, what did you actually build, what surprised you. Listen for specificity. Vague answers ("it was a dashboard for analytics") are a red flag.
- What does your daily AI tooling stack look like? Cursor, Claude Code, Copilot, ChatGPT. Ask which they reach for first, what they delegate to AI versus do themselves, and what their verification habit is when AI generates code. This is not on the Toptal screen, so you have to surface it yourself.
- What is your timezone, and what hours overlap with my team? Confirm the matcher's claim. Engineers sometimes overstate overlap.
- How many other engagements are you running concurrently? Senior engineers on Toptal often run 2 to 3 in parallel. That can be fine, but you want to know.
- Tell me about a project where the spec was wrong. What did you push back on, how did you handle it. Engineers who never push back ship what you ask for, not what you need.
- What would you want to know from us before week 1? Listen for whether they ask about your codebase, your release cadence, your test culture. Engineers who ask nothing are red-flag passive.
A version of this script also works for vetting any developer before hiring, not just on Toptal.
Common pitfalls and how to escalate
Three things go wrong most often.
Engineer not in your timezone. Most common cause: the spec said "remote-friendly" instead of specifying overlap hours. Most common fix: contact your matcher within the first 5 working days of the trial, ask for a re-match with hard timezone constraints, and flag the trial hours as eligible for refund. Document everything in email, not Slack.
Scope creep. The engineer takes your spec and starts solving adjacent problems. Sometimes welcome, often not. Counter with weekly written scope reviews. At end of week 1, write a 1-page "this is what is in scope, this is what is out of scope" doc and share it with the engineer. If scope creep continues into week 2, flag it on your weekly retro.
Trial-period invoice surprise. The trial is "no-risk" only if you formally end it within the trial window. Default behavior is that the trial converts to an ongoing engagement and Toptal bills normally. If you are unhappy at week 2, you must affirmatively end the engagement and request the trial-hours refund. Set a calendar reminder for day 12.
When the match is wrong, escalate in this order: 1) talk to the engineer directly (sometimes a misalignment is fixable in one call), 2) email the matcher with specific examples and ask for 2 to 3 fresh candidates, 3) escalate to Toptal client success if the matcher is unresponsive, 4) walk away and request the deposit refund. Steps 1 to 3 typically take 5 to 7 days. If you are still misaligned at week 3, walk.
If you are evaluating multiple platforms in parallel, the Toptal alternatives roundup covers the trade-offs across Lemon.io, Arc, Gun.io, and Cadence.
Toptal vs Cadence: when each model wins
Both work. They optimize for different buyers.
| Approach | Cost | Time to first candidate | Trial | Min commitment | Replacement |
|---|---|---|---|---|---|
| Toptal | $60 to $200+/hr + $500 deposit + $79/mo | 24 to 48 hours | 2-week no-risk (real billable hours) | 20+ hrs/week typical | Request re-match (5 to 14 days) |
| Cadence | $500 to $2,000/week, all-in | 2 minutes (auto-match) | 48-hour free trial | 1 week | Replace any week, no notice |
Toptal wins when: you have a 6+ month engagement, you need deep domain specialization (fintech, healthtech, ML research), you need to satisfy enterprise procurement that wants a known vendor on the master service agreement, or you specifically value the human-matcher conversation at intake.
Cadence wins when: you have a 2 to 12 week scope, you have not validated whether the role should exist long-term, you want flat transparent pricing with no deposit or markup mystery, you need AI-native tooling fluency as a baseline (every Cadence engineer is vetted on Cursor, Claude Code, and Copilot before they unlock the platform), or you want to swap engineers without a multi-week re-matching cycle. Cadence runs a 12,800-engineer pool with a 27-hour median time to first commit after booking.
For a 3-month feature build where you know the spec and want to ship by end of quarter, both work. For a 12-month staff-engineer hire where you need someone embedded in your codebase, Toptal is a better cultural fit. For "I think we need a backend engineer for the next 6 weeks but I am not sure," booking on Cadence is lower-risk: you pay one week, see the work, and decide. If you are weighing booking versus long-term placement, the Cadence founders page lays out the booking flow end-to-end.
A useful frame: Toptal is "hire a vetted contractor." Cadence is "book a week of vetted engineering capacity." Different verbs, different mental models.
What to do this week
If Toptal is on your shortlist, the action items are:
- Write the spec using the 6 fields above. 30 minutes well spent.
- Submit on toptal.com and pay the $500 deposit.
- When the matcher books your intake call, run through the spec field by field.
- Use the 6-question intro-call script with each of the 3 candidates.
- Set a day-12 calendar reminder for the trial-end decision.
If you want to compare against the booking model first, book a week with Cadence at $500 to $2,000 depending on tier and run it side-by-side with your first Toptal candidate during the trial. Two weeks, two engineers, real shipped work, then decide. The 48-hour trial on Cadence is genuinely free (no deposit, no markup), so the parallel comparison costs you only the Toptal trial hours.
Skip the loop entirely? If your scope is 2 to 12 weeks and you want to start Monday, see Cadence's hiring flow: every engineer is AI-native by default, weekly billing, replace any week, 48-hour free trial. One option among many; honest trade-offs spelled out above.
FAQ
How long does it take to hire on Toptal?
Most clients see 3 candidate intros within 24 to 48 hours after the intake call, with a typical 1 to 2 week stretch from first contact to a signed engagement that includes the trial period.
Is the Toptal $500 deposit refundable?
Yes, if you decide not to hire. If you do hire, it credits against your first invoice. Some clients have reported friction on refunds, so request it in writing within the first 30 days if you walk away.
What does Toptal really mean by "top 3%"?
It refers to the share of applying engineers who pass the live screen, technical interview, and test project. It does not vet for your specific stack, timezone, codebase taste, or AI-native tooling fluency. Those gates are still your job during the intro call.
Can I hire on Toptal for less than 20 hours per week?
Technically yes, but most senior Toptal engineers prefer 20+ hours weekly and matchers will steer you that way. Sub-20-hour engagements often get matched with mid-level talent only, or get longer matcher response times.
What if the Toptal match is wrong?
You can request a re-match during or after the 2-week trial without paying for the trial hours, provided you formally end the engagement within the trial window. Document the misfit in email within the first 5 working days and ask the matcher for 2 to 3 fresh candidates.