How to Handle Developer Candidates with Non-Compete Agreements

Non-compete agreements are a reality in technical recruiting. Whether you're sourcing talent in California (where they're unenforceable) or Texas (where they're aggressively enforced), understanding how to navigate these agreements is critical to avoid legal liability, hiring delays, and damaged candidate relationships.

This guide walks you through the practical, legal, and strategic considerations recruiters face when targeting developers with non-competes—and how to move candidates forward confidently.

What is a Non-Compete Agreement?

A non-compete agreement (or covenant not to compete) is a legal contract that restricts an employee from working for competitors or starting competing businesses for a specified period after leaving their current job. The typical duration ranges from 6 months to 2 years.

Common Non-Compete Provisions

Non-competes typically include:

Restricted activities: Development for competing companies, freelancing in the same domain, or starting a competing business
Geographic scope: Local, regional, state, or national restrictions
Duration: How long the restriction lasts after employment ends
Compensation limitations: Whether the former employer pays "garden leave" or salary during the restriction
Severance conditions: Whether non-competes are enforced even if the company laid off the employee

Legal Landscape: State-by-State Considerations

The enforceability of non-competes varies dramatically across the U.S. This directly impacts your hiring strategy.

Non-Compete Enforceability by Region

Region	Enforceability	Recruiting Impact	Key Notes
California	Generally unenforceable	Low risk; candidates can move freely	Companies waste money enforcing them
Texas	Highly enforceable	High risk; candidates are cautious	Courts favor employers; reasonable restrictions upheld
New York	Moderately enforceable	Medium-high risk	Must be "reasonable" in scope, duration, geography
Florida	Highly enforceable	High risk	Courts presume enforceability; burden on employee to challenge
Massachusetts	Moderately enforceable	Medium risk	Requires legitimate business interests
Washington	Increasingly restricted	Medium-low risk	Recent laws limit scope and duration
Illinois	Moderately enforceable	Medium risk	Must protect legitimate business interests

Key takeaway for recruiters: Your candidate's current location and the location of their previous employer determine the actual risk level, not just where they'll work next.

Due Diligence: The Five Steps to Assess Non-Compete Risk

Before extending an offer or even scheduling interviews, implement a systematic approach to evaluating non-compete risk.

Step 1: Ask Directly During Initial Screening

This seems obvious, but many recruiters skip it. Ask candidates explicitly:

"Do you have a non-compete or non-solicitation agreement with your current or previous employer?"
"What's the duration and geographic scope?"
"Have you reviewed it recently, or do you have a copy?"

Why this matters: Candidates often aren't sure. Some don't realize they signed one. Others minimize its scope. Getting clarity early prevents surprises at the offer stage.

Step 2: Request Documentation

If a candidate confirms a non-compete, request a copy. This is non-negotiable. You need to see:

Exact language around restricted activities
Duration and effective dates
Geographic limitations
Any carve-outs or exceptions

Many candidates will say, "It's probably unenforceable anyway." Don't rely on their interpretation. You (or your legal team) need to review the actual document.

Step 3: Consult Legal Counsel

Before proceeding with any candidate subject to a non-compete, have an attorney review the agreement. This typically costs $300–$800 per review, which is far cheaper than litigation.

Your legal review should answer:

Is this enforceable in the candidate's current jurisdiction?
Does the new role violate the non-compete?
What's the realistic litigation risk?
Are there indemnification strategies available?

Pro tip: If you hire developers regularly in states with strong non-compete enforcement (Texas, Florida, New York), it's worth establishing a relationship with an employment attorney who can do quick reviews.

Step 4: Understand the Severity

Not all non-competes are equal. Evaluate:

Scope of prohibited activities: Is it narrowly tailored (e.g., "no work on enterprise SaaS solutions") or broad ("no software development work")?
Geographic scope: City-wide vs. national (national is more likely to be unenforceable)
Duration: 6 months is more reasonable than 3 years
Consideration: Did the employee get something in exchange for signing? (They often didn't; they just signed as a condition of employment)

A narrowly scoped, 6-month non-compete in the same city is far easier to work around than a 2-year, nationwide restriction on all software development work.

Step 5: Assess the Previous Employer's Litigation Risk

Finally, consider: How likely is the previous employer to enforce this?

Well-funded companies (FAANG, established startups): Higher enforcement likelihood
Startups struggling with cash: Lower enforcement likelihood
Companies with high turnover: Less likely to pursue enforcement
Highly proprietary industries (fintech, defense contractors): More likely to enforce

A non-compete from a startup in a non-enforcement jurisdiction that's barely staying afloat carries far less risk than one from a major tech company in Texas.

Strategic Options for Moving Forward

Once you've assessed the legal landscape, you have several strategies. Choose based on the severity of the risk.

Option 1: Wait Out the Non-Compete

When to use this: Moderate to high-risk agreements, but you have flexibility on start date.

If a non-compete has 12 months remaining, and the candidate is willing to wait, this is the cleanest path. No litigation risk, no legal fees, no tension.

Considerations: - Candidate may lose urgency or take another offer - Delayed start dates often fall through - Best for candidates who are highly motivated to join your team

Timeline: 3–12 months, depending on agreement duration.

Option 2: Obtain a Waiver from Previous Employer

When to use this: When the previous employer is reasonable, or the candidate has leverage.

Some companies will waive non-competes if: - The employee's departure is mutual/amicable - The new role doesn't directly compete - There's a relationship between the companies

Ask the candidate: "Would your previous employer be willing to waive the non-compete in writing?"

This is surprisingly effective for candidates on good terms with their previous employer.

Timeline: 1–3 weeks if the employer agrees; often they don't respond.

Option 3: Litigation Insurance or Indemnification

When to use this: You really want the candidate, and legal risk is acceptable.

Some companies carry employment practices liability insurance (EPLI) that covers litigation costs if a non-compete is challenged. If yours does, confirm your policy covers non-compete disputes.

Alternatively, you can indemnify the candidate in writing, agreeing to cover legal fees if the previous employer sues. This reassures the candidate and shows good faith.

Sample indemnification language:

"Company agrees to defend, indemnify, and hold harmless Employee from any claims, damages, or legal fees arising from disputes related to the non-compete agreement from [Previous Company], provided Employee acted in good faith."

Cost: $0 in most cases; litigation would only trigger if the previous employer actually sues (rare).

Option 4: Restructure the Role

When to use this: The non-compete prohibits the specific work the candidate would do.

If the non-compete restricts work on "enterprise SaaS development," but your company also does open-source or data infrastructure work, the candidate might take a different role.

Example: A developer with a non-compete preventing SaaS work could join as a data engineer, tools engineer, or infrastructure specialist.

This works best when: - Your company has diverse projects - The candidate has transferable skills - The role is genuinely distinct from the prohibited activities

Option 5: Geographic Relocation

When to use this: Non-compete has geographic limitations, and the candidate can move.

If a non-compete restricts work within "50 miles of New York City," and the candidate agrees to work remotely from Boston, the non-compete may not apply.

Important caveat: Remote work complicates this. Modern non-competes increasingly include remote work language, so don't assume geography saves you.

Option 6: Challenge the Non-Compete's Enforceability

When to use this: The agreement is clearly problematic, and you have time and legal budget.

If a non-compete is: - Overly broad (nationwide restriction on all software work) - Lacking consideration (employee didn't get anything for signing) - Unreasonably long (3+ years)

...it may be vulnerable to challenge.

A well-drafted opposition letter from an employment attorney can sometimes convince the previous employer to back down before litigation.

Cost: $1,500–$5,000 in legal fees; litigation is much more expensive.

Timeline: 2–4 weeks for initial response.

The Candidate Conversation: What to Say and How to Say It

Your communication with the candidate matters enormously. Handle this well, and you retain trust. Handle it poorly, and the candidate disappears to a competitor.

Early Conversation Script

When you first learn about a non-compete:

"Thanks for being transparent about the non-compete. I appreciate that. We take these seriously, and before we move forward, I want to do due diligence. Can you send me a copy so I can have our legal team review it? In the meantime, what's your understanding of what it restricts?"

This signals: - You're professional and thoughtful - You won't put the candidate at risk - You're not dismissing their concern

Mid-Process Communication

If legal review reveals risk:

"Our legal team reviewed your non-compete. There's some risk here, but it's manageable. Here's what we're thinking: [Option 1/2/3]. Which path works best for you?"

This gives the candidate agency and doesn't ambush them at offer stage.

Offer Letter Handling

If you move forward despite non-compete risk, your offer letter should:

Acknowledge the non-compete exists
State it's the candidate's responsibility to comply
Offer indemnification if you're providing it
Specify the candidate's start date, accounting for any restriction period

Example language:

"You represent and warrant that your employment with [Company] will not violate any non-compete, confidentiality, or similar agreements you have with your previous employer. We have reviewed your non-compete agreement and believe the risks are [minimal/manageable/acceptable]. Should any dispute arise, we agree to indemnify you for associated legal fees, provided you acted in good faith."

Salary and Offer Strategy for Non-Compete Candidates

Non-competes reduce candidate bargaining power (they have fewer options), but they also increase your risk. How should this affect compensation?

Consider a "Non-Compete Premium"

If you're asking a candidate to take legal risk, compensate them for it. This can include:

Signing bonus: $5,000–$20,000 to offset legal review costs or foregone severance
Accelerated equity vesting: Cliff vests after 6 months instead of 12
Higher base salary: 5–10% above market if risk is significant

This isn't legally necessary, but it's fair and makes the candidate feel valued despite the risk.

Timing of Offers

If a candidate has 6 months left on a non-compete, consider:

Offer conditional on non-compete expiration: "Offer contingent on non-compete no longer being in effect by [date]"
Delayed start date: "We'd love to have you start January 1, after your non-compete expires"
Immediate start with risk assumption: Pay the premium and move forward

Documentation: What to Keep

If you hire someone with a non-compete and it's later challenged, documentation becomes critical. Keep:

The signed agreement (copy provided by candidate)
Legal review memo (attorney's assessment of enforceability)
Indemnification clause in the offer letter (if applicable)
Communications with the candidate about the non-compete
Evidence of legitimate business decision (why you hired despite the risk)

This paper trail protects you if the previous employer sues.

Red Flags: When to Walk Away

Not every non-compete situation is worth pursuing. Consider passing if:

The non-compete is ironclad and the candidate is replaceable: It's not worth legal risk for easily replaceable talent
The candidate is dishonest about the agreement: If they claim it doesn't exist or minimize it after you ask directly, they're a liability
The previous employer has a history of aggressive litigation: Some companies sue routinely; the risk is real
The candidate hasn't fully disclosed: If you discover a non-compete they didn't mention, trust is broken
Your legal team advises against it: If your attorney says "no," listen

In these cases, it's better to move on to other candidates than carry unnecessary risk.

Toolkit: Resources and Best Practices

Recommended Actions

Build a legal relationship: Have an employment attorney on retainer for quick non-compete reviews ($500–$1,000/month)
Create a screening template: Add non-compete questions to your standard initial call script
Document everything: Use a checklist to ensure you're capturing all necessary info
Train your team: Ensure all recruiters understand non-compete basics
Leverage GitHub activity: Tools like Zumo help identify developer activity and skill progression, which can be useful context when evaluating a candidate's genuine technical fit (and thus whether they're worth the non-compete risk)

State-Specific Resources

California: Review the California Business and Professions Code § 16600 (non-competes are void)
Texas: Reference Texas Business and Commerce Code § 15.50 (non-competes are enforceable if reasonable)
New York: Review New York General Obligations Law § 5-322.1 (enforceability requires legitimate business interest)

Consult state-specific employment law resources for your key hiring markets.

FAQ

Can a company enforce a non-compete against a remote worker?

It depends on the agreement's language and the applicable state law. Many modern non-competes include "remote work" language specifying they apply regardless of location. If a non-compete predates widespread remote work, it may have geographic limitations that technically don't apply. However, don't assume this—have legal counsel review the specific agreement and jurisdiction.

What if the candidate claims they don't have a copy of the non-compete?

Request it from the previous employer. Many candidates don't retain copies, but the previous employer has the original. You can ask the candidate to request it from HR, or in some cases, your legal counsel can request it on the company's behalf. If the candidate refuses or if the previous employer won't provide it, that's a red flag.

Are non-solicitation agreements different from non-competes?

Yes, and it matters. Non-solicitation agreements prevent an employee from recruiting colleagues or soliciting clients, but allow them to work for competitors. They're generally easier to enforce and exist in almost every state, including California. Many candidates have both agreements. Review both separately, as they create different restrictions.

How much does it cost to litigate a non-compete dispute?

Litigation typically costs $50,000–$200,000+ depending on complexity and duration. A cease-and-desist letter from your attorney costs $500–$1,500. A motion to invalidate the agreement costs $2,000–$5,000. Full litigation is much more expensive. This is why prevention (legal review upfront) is far cheaper than defense.

Can we ask the candidate to sign a release or waiver of the non-compete?

Only with the previous employer's consent. You cannot unilaterally override another company's non-compete. However, you can ask the candidate to request a waiver from their previous employer, which sometimes works if the departure was amicable. A formal waiver letter from the previous employer, signed by an authorized representative, is the gold standard.

Take Control of Your Hiring Process

Non-compete agreements don't have to derail your technical recruiting. With proper due diligence, legal guidance, and clear communication, you can confidently hire developers despite these restrictions—or safely avoid the ones that aren't worth the risk.

The key is systematic evaluation: ask, document, get legal input, and make informed decisions. Your legal team becomes a partner in your sourcing strategy, not an obstacle.

Ready to build a sourcing process that's both legally sound and highly effective? Explore how Zumo helps you identify developers worth pursuing in the first place—reducing the risk of hiring someone with serious non-compete baggage by giving you deeper insight into candidate activity and background before you invest time in screening.