Why your employee poaching defense keeps losing to a recruiter call

The non-solicitation clause was in every employment agreement on your shared drive. You’d had your lawyer redraft it last spring, paid the four-figure invoice, and watched HR roll it into onboarding without so much as a question. Two engineers left in October to the same competitor. A third left in November. The pattern your team had started calling “employee poaching” was already on its third backfill in 90 days, and the clause was nowhere in the conversation.

Your first instinct was to call the lawyer back. Tighten the language. Add a longer cooldown. Add a non-compete, even though half the team is in California and you already know how that conversation ends. Your second instinct, the one that arrived around 3 p.m. that day, was harder to push down. The contract didn’t keep them. The recruiter call did. They weren’t tricked or stolen. They picked. If you’re honest with yourself, you can name what they picked over.

Here is the problem none of the poaching guides on the first page of Google will say out loud. Employee poaching is a retention problem dressed as a recruiting problem, and the contract layer can’t fix what compensation transparency and growth paths should. The legal answer and the operational answer live on different pages of the SERP. The bridge between them is where your three open backfills actually live.

A non-solicitation clause didn’t keep them

A non-solicitation clause does real work, just not the work most leaders assume. It restricts a departing employee, for a defined period, from actively recruiting their former colleagues to follow them out. That’s useful. It is not a retention mechanism. It does not stop your engineer from accepting a competitor’s offer. It does not stop the competitor from sending the offer. The clause activates after the person has already decided to leave.

Most teams discover this the same way you did. Three people leave in 90 days. The clause was in every contract. The clause never came up. The contract layer exists for cases where a departing employee walks out with your customer list, your six closest colleagues, and a working draft of your unreleased roadmap. That happens. It justifies a thoughtful non-solicit and a sensible IP assignment. It is not the volume of loss most TA leads are quietly tracking when they say the team is getting poached and the funnel keeps reopening.

What employee poaching is, and what’s actually illegal

Why most poaching is legal but no-poach pacts are not

In most United States jurisdictions, an employer reaching out to a competitor’s employee with an offer is legal commercial behavior. Recruiters do it every day. The illegal version is different. Two or more competitors agreeing among themselves not to recruit or hire each other’s employees is what antitrust regulators call a horizontal no-poach agreement. Since the DOJ Antitrust Division and the FTC published their joint Antitrust Guidance for Human Resource Professionals in October 2016, that kind of pact has been treated as a per se violation of Section 1 of the Sherman Act. Per se means prosecutors don’t have to prove the agreement was unreasonable or harmed any specific worker. The agreement itself is the violation.

The enforcement record has been bumpy. Several criminal cases brought by the DOJ ended in jury acquittals between 2022 and 2024, but courts have continued to confirm that naked no-poach and wage-fixing pacts are per se illegal. If you find yourself in a quiet conversation with a peer at a competing firm where someone says “let’s just agree not to call each other’s people,” walk out. There isn’t a workaround.

Non-solicitation is narrow, but legal in most places

A non-solicitation clause is a vertical agreement between an employer and an employee, not between two employers. It restricts the employee, post-departure, from soliciting clients or coworkers for a defined period. Courts evaluate them on reasonableness of scope, duration, and geography. Many jurisdictions enforce them. Some narrow them aggressively. They are a different legal animal from the horizontal no-poach pact above, and the pages that lump the two together are quietly making your job harder.

Non-competes are a different conversation

Non-compete clauses restrict the employee from working for a competitor at all. The legal landscape has shifted. The FTC issued a near-total ban on non-competes in April 2024, which has been challenged in court and remains in flux. State law varies widely. California voids most of them by statute. None of the above is legal advice, and the right move is to talk to counsel in your jurisdiction. For an HR conversation, the trend line is narrower, not broader, and a strategy that depends on non-competes is sitting on shifting ground.

Why “they got poached” is usually a story about your comp band

A recruiter calling your senior engineer on Tuesday is not what makes the senior engineer leave. The decision was already half made. The recruiter call is the moment it becomes legible. People who are well-paid relative to their internal band, can see where the next promotion goes, and have a manager doing real work on their growth, take the call and politely decline. People who are paid below band, can’t see the next role, and haven’t talked about a promotion in 14 months, take the call and listen. The companies that worry most about poaching are the ones running the second pattern at scale.

What an exit interview will tell you

Honest exit interviews from people who took an outside offer almost always include one of three sentences. “I haven’t had a real comp conversation in two years.” “I didn’t know what my next role looked like.” “Nobody told me the bands had moved.” The third is the most common and the easiest to fix. Companies adjust salary bands quietly, often without telling the people inside them. The competitor’s recruiter quotes the new market rate. Your engineer has nothing to compare it to except their own paycheck, which hasn’t changed.

The pattern across hiring teams we work with is leaders quietly admitting that their best people leave for a 15 to 25 percent comp bump the leader could have approved internally if anyone had asked.

The two levers that beat a recruiter calling on Tuesday

There are two structural levers worth pulling. Recognition programs, engagement surveys, and culture decks are tactics on top. They cannot substitute.

Compensation transparency

Compensation transparency means three things. People know what their current band is. People know what the next band starts at and what behavior moves you between bands. People know the bands themselves have moved this year, because they were told.

Together those three remove the information asymmetry that makes the recruiter call a shock. When an outside number lands, the engineer knows whether it’s genuinely above your band or just at par, and whether the right conversation is “I’m leaving” or “I’d like to revisit my comp.” Companies that publish bands internally see fewer surprise resignations because the surprise is gone.

A comp review every six months, where managers are required to actually have the conversation, does most of the rest of the work. You don’t need a fancy system. You need somebody on the calendar.

Growth-path visibility

Growth-path visibility means an engineer or a CSM or a recruiter, three months in, can answer two questions. What does the next role look like, and what does it pay? What specific work, demonstrated over what timeframe, gets me there?

Both are answerable. Most companies don’t answer them, partly because the answers feel like a commitment, and partly because nobody has defined the next role clearly enough to write down. The cost is the recruiter call your engineer takes because the recruiter has an answer and you don’t. “Senior to staff in 18 months at this comp range, given these specific projects” is a more powerful retention sentence than any mission statement on a careers page. The careers page work and the growth-path work are mirror images.

”But we can’t match what they’re offering”

This is the version of the objection most worth taking seriously. It’s also the one that gives the most cover to leaders who don’t want to do the structural work.

Where the objection is right

It is correct in narrow cases. A specialist hire in a thin market, a niche technical lead, a candidate with founder-level credibility can sometimes command an outsized premium a healthy internal band cannot match. Those cases exist. They are not most of your departures.

Where it stops being right

It stops being right everywhere else. It usually shows up as a 15 to 20 percent comp gap the leader claims is unfundable. That kind of gap is almost never unfundable. It is unsurfaced. The bands haven’t moved in 18 months because nobody made the case to move them, and the case wasn’t made because attrition cost wasn’t counted against the cost of the band increase. Three lost engineers is a six-figure recruiting and ramp cost. A five percent band adjustment is often less than that and retains the other twelve.

What candidates resent is not being told. They’ll accept being slightly below market if the band is honest about it and the path to market is clear. They won’t accept being below market and being told the band moved at the all-hands when their personal number didn’t.

A working quarter where nobody got poached

Back to the December conference room, three red squares on the org chart. Same team, same competitor, six months later.

The structural work

You published internal salary bands in January. Three levels for engineering, three for customer success, two for ops. The bands include base, target bonus, and equity. People know where they sit. Promotion paths got written next, role by role, with the specific demonstrated work that takes you up. None of it is binding the way a contract is. All of it is legible the way a contract is not.

Comp reviews now happen on a six-month rhythm, scheduled before the manager’s own performance review so the conversation runs the right direction. The cost of moving a band has a number next to it. The cost of replacing a senior engineer has a bigger number. Both are visible to the people deciding.

The hiring side of the same picture

You’re filling the three backfills the same way you fill any role. The careers page funnels into a single Position Link. Candidates record four screening questions in eight to twelve minutes. Resumes go through Truffle’s scoring against the criteria you set during intake. Candidate Shorts compress each candidate’s most revealing moments into about thirty seconds. AI Match shows how closely each response aligns with the role. You watch the top 12 Shorts on Tuesday morning over coffee, read AI Summaries on the next 8, and have four people you want to talk to by 10 a.m.

The hiring loop and the retention loop talk to each other. The intake that calibrated the screening questions also calibrated the band the role sits in and the path that leads out of it. The next person you hire knows what the next role looks like before they sign. The same loop is doing real work for high-volume hiring on the front-line roles where backfilling has been most expensive.

You haven’t changed the contract. You’ve changed the workplace.

What real poaching defense looks like

Horizontal no-poach pacts between competitors are per se illegal, and you should never propose one. Non-solicitation clauses do narrow, useful work. Non-competes are on a tightening leash. Each is worth getting right with counsel.

What the wrong response produces

Read poaching as a contract problem and the response is more contract. Tighter clauses. Longer cooldowns. A non-compete in jurisdictions where it might still hold. None of it changes the calculation your engineer is making on Tuesday afternoon when their phone buzzes. The recruiter has a number. Your team doesn’t. Two more leave in the next quarter because the underlying conditions didn’t change. The lawyer’s invoice clears, and three roles open in February. Your hiring velocity holds steady, but the same role keeps reopening.

What the right response produces

Read poaching as a retention problem and the response is structural. Bands published. Paths drawn. Reviews scheduled. The recruiter still calls on Tuesday. Your engineer still takes the call. The conversation now ends with the engineer telling the recruiter the comp is in band, the path is visible, and there isn’t a 25 percent gap to negotiate. The competitor’s recruiter calls a less prepared company next.

The companies that worry most about poaching are the ones who’ve under-invested in the only two levers that actually work. They’ve been spending the retention budget on engagement programs instead of comp bands and promotion paths. The contract perimeter is a comfort blanket. The workplace is the defense.

Frequently asked questions about employee poaching

Is employee poaching illegal?

In most United States jurisdictions, no. An employer reaching out to a competitor’s employee with an offer is legal commercial behavior. What is illegal is two or more competitors agreeing among themselves not to recruit, hire, or solicit each other’s employees. The DOJ and FTC have treated those horizontal no-poach pacts as per se violations of the Sherman Act since their joint 2016 guidance for HR professionals. This is not legal advice. Talk to counsel licensed in your jurisdiction.

What is a no-poach agreement?

A no-poach agreement is an arrangement between two or more employers, usually competitors, not to hire or actively recruit each other’s employees. It is different from a non-solicitation clause, which is between an employer and an employee. The horizontal version, between employers, is the one antitrust regulators have flagged as per se illegal under federal law.

What is a non-solicitation agreement?

A non-solicitation agreement is a clause in an employment contract that restricts a departing employee, for a defined period, from actively recruiting their former colleagues or soliciting clients. It is enforceable in many jurisdictions if the scope, duration, and geography are reasonable. It does not stop a former employee from accepting an outside offer, and it does not stop a competitor from making one.

How do you prevent employee poaching?

The durable defense is compensation transparency and growth-path visibility. Publish internal salary bands. Run comp reviews every six months. Write the next role for every current role, including what specific demonstrated work moves a person up and what the next band pays. People with that information take recruiter calls and politely decline. People without it listen.

Can a company sue another company for poaching its employees?

In rare cases involving trade secret misappropriation, breach of a specific non-solicitation clause, or tortious interference with contractual relations, yes. The bar is high and the cases are fact-specific. Most ordinary recruiting activity is legal commercial behavior and is not a basis for a suit.