Skip to content
CompanyBenchCompanyBench

How to evaluate a contract developer before you sign

A hiring manager's checklist for vetting a contract developer before you sign: availability, technical depth, a skills test, references and contract terms.

You have three contract developers on your shortlist. The resumes look solid and the rates are reasonable. What you do next decides whether the engagement goes well or whether you are rewriting bad code six weeks into the project.

A full-time hire is partly about culture and long-term potential. A contract hire comes down to one question: can this person deliver what you need, on time, within the scope you have set? That makes the evaluation tighter and more technical, and mistakes cost more. The checklist below works whether you are covering a two-week gap or staffing a six-month build.

1. Verify the fundamentals first

These are pass or fail checks. If any of them fails, stop, however good the portfolio looks.

  • Availability: confirmed for your exact dates and hours, with at least 4 hours of overlap with your core working hours.
  • Legal standing: right to work and to contract in their jurisdiction, and no active non-compete covering your industry or stack.
  • Billing model: hourly, milestone-based or retainer, agreed before the engagement starts.

2. Assess technical depth, not breadth

Most resumes list 15–20 technologies. Your job is to find out which ones the candidate really knows and which they touched once in a side project. Anchor the conversation in your own stack.

Project walkthrough

  • Ask them to walk through a recent project that is close to yours and describe the hardest technical problem they hit.
  • Probe trade-offs: "Why did you choose X over Y here?" Ask about performance, security and scalability decisions.

Warning signs

  • Answers that explain what a technology does rather than how they used it in production.
  • No recall of specifics such as file sizes, query times or API call volumes. This is a strong red flag.
  • Claimed expertise in tools that were released after their last role ended.

3. Run a short, relevant skills test

This is the most predictive tool you have. A 15–30 minute exercise does not need to be clever; it needs to look like the real work. Judge the process as well as the result. Do they ask clarifying questions, handle edge cases and write readable code?

RoleExample test
React developerA small component with one API call and one stateful interaction
Backend developerAn endpoint for a basic CRUD operation, with validation
Salesforce developerExplain how you would approach a custom Apex trigger for a given business scenario
Keep tests under an hour. A fair, focused test respects the candidate's time and shows you run a professional engagement.

4. Evaluate communication and collaboration

A strong developer who communicates badly can do more damage to a project than a mid-level developer who keeps everyone informed. In the interview or screening call, check three things.

  • Responsiveness: do they reply promptly at every stage? Someone who goes quiet for two days before the contract has even started is a risk.
  • Clarity: can they explain a technical decision to a non-technical stakeholder without falling back on jargon?
  • Mindset: ask what they would do if requirements changed mid-sprint. Good questions about scope, not only pay, are a good sign.

5. Review the portfolio and past work

Much contract work sits under NDA, so a strong portfolio is not always public. You can still look at commit history, open-source contributions in your stack and case studies with measurable outcomes.

  • Code history: on GitHub or GitLab, commit frequency, code quality and commit messages show how someone works.
  • Outcomes: look for case studies that state results, such as "reduced load time by 40%" or "migrated X users to a new system".
  • Ask them to share a piece of code they are proud of and walk you through the decisions. How well they explain it tells you as much as the code.

6. Check references with specific questions

Done properly, reference checks are one of your most useful inputs. One specific reference from a recent client is worth more than three generic ones from years ago. Ask:

  • "What was the project, and what exactly did they own?"
  • "Did they deliver on time and within scope? If not, what happened?"
  • "How did they handle feedback or technical disagreement?"
  • "Would you hire them again for similar work?" If the answer is hesitant, ask why.

7. Settle contract terms before you get attached

It is easy to get excited about a candidate and skim the contract. Don't. These terms protect your project and your budget. When we are the contracting party, standard terms are built into the contract, but you should still read them.

  • IP ownership: make sure code ownership passes to your company on delivery.
  • Confidentiality: have an NDA signed or agreed before granting access to any proprietary system or data.
  • Terms of change: confirm the revision policy, the termination notice period and whether the rate is fixed or can change.

Pre-signature checklist

AreaWhat good looks like
Availability and time zoneAt least 4 hours of overlap with your core hours confirmed
FundamentalsRight to work, billing model and rate confirmed before the engagement
Technical depthExplains decisions, trade-offs and real project specifics
Skills testCompleted a relevant, scoped test and explained the approach
PortfolioShows outcomes, not just a list of technologies
ResponsivenessReplied promptly at every stage and asked clarifying questions
CommunicationExplains technical decisions to non-technical stakeholders
ReferencesAt least one specific, recent reference that talks about outcomes
IP ownershipCode ownership assigned to your company after delivery
NDASigned or agreed before access to proprietary systems
Contract termsBoth sides clear on scope, revisions and exit conditions

Red flags

  • Cannot recall specifics from past projects: file sizes, timelines, volumes.
  • Long silences before the contract has even started.
  • Claims expertise they cannot show in a practical test.

Hire for the project, not the resume

The right contract developer is not always the one with the most impressive CV. It is the one whose skills, communication and availability match what your team needs now. We send a vetted shortlist of at least 3 candidates within 48 hours, which removes most of the early filtering, but applying the checks above consistently is what gets you from a shortlist to a confident decision. For more, see questions to ask before hiring a remote developer and how contract hiring works with us.