Refolk
November 10, 2026·9 min read

Angi's Managers Ran Teams of Three. Hire Them as Tech Leads, Not Directors

Angi's November 2026 layoffs cut managers who averaged three reports. How to find them by employer, level them as tech leads, and time outreach to each wave.

Angi layoffs November 2026hiring laid off engineering managersspan of control engineering manager levelingmanager to tech lead transitionsourcing ex-Angi engineers
Angi's Managers Ran Teams of Three. Hire Them as Tech Leads, Not Directors

If you're hiring managers out of Angi's November 2026 layoffs, the title on the résumé is the least reliable thing about them. CEO Michael Steib explained the cuts with one number: the average Angi manager oversaw three people, against a target of six to 12. That number should shape the level you offer, how you search, and when you reach out.

What did Angi cut in November 2026?

Angi cut about 300 roles "primarily in middle management and support functions," with $18M to $30M in restructuring charges landing mostly in Q4 2026 and H1 2027. It's a flattening driven by a management-ratio target, not a performance cull.

Steib, the former TEGNA CEO, was appointed in September to succeed Jeff Kip and announced the cuts six weeks into the job. On the Q3 call he put it plainly: "Angi had become too layered." The company expects $40M to $50M in annualized opex savings plus about $10M in reduced capex.

The business context hints at which teams are most exposed. Revenue fell 9% to $242M as homeowner leads fell 18%. Revenue from large pros grew 20%, while revenue from smaller pros fell 13%. My guess is that teams built around small-pro products lose the most layers.

Two rounds, two different populations

The January and November cuts aren't the same kind of event, and you shouldn't source them the same way.

  • January 2026: tied explicitly to "AI-driven efficiency improvements" and expected to finish before March 2026, so about an 8-week rollout. Headcount went from 2,800 at the end of 2024 to about 2,000.
  • November 2026 (~300 roles): framed around layers and keeping "leaders close to the action," with charges spread over roughly 8 months. That leaves about 1,700 people, around 39% below the end-2024 headcount.

January was justified by automation. November is justified by how many people a manager managed, not by what they did, which is why the November pool is the one you need to level carefully.

Why does a span of three change the level you hire at?

A manager with three direct reports is usually doing a tech lead's job under a manager's title. Span of control is the number of people who report directly to one manager, and it's the best single signal for leveling candidates from over-layered orgs.

3
Average direct reports per Angi manager
Steib's stated target is six to 12, which means cutting 50% to 75% of the manager layer.

Here's the arithmetic. Take 30 ICs managed at a span of three: that's 10 managers. Move to a span of six and you need five managers. At 12 you need two or three. Holding ICs constant, going from 3 to the 6-12 range removes half to three-quarters of the managers. The people cut are most likely the ones running the smallest teams, which means teams the size of a tech lead's pod.

The likely cause is title inflation. In layered orgs, manager titles inflate in a way tech lead titles don't. "Senior Manager" at Angi and "Senior Manager" at a company with spans of eight are different jobs.

A leveling rubric for over-layered managers

When you screen an ex-Angi manager, ignore the title and ask these questions in this order:

  1. How many direct reports did you have? Three or fewer points to a tech lead or tech lead manager (TLM). A TLM manages a small team and still owns technical direction and some hands-on work.
  2. Were any of your reports managers themselves? If not, they weren't a director in any market-standard sense.
  3. Did you own a budget or headcount plan? Without that, a Director conversation is premature.
  4. How much code or design review did you do each week? A lot of review time is a strong tech-lead signal.

The default mapping: a "Senior Manager" with three reports, no manager reports, and no budget lands at EM I or TL/TLM. Save EM II or Director for the candidate who managed managers and owned spend. Those people exist, and the rubric is there to find them, not to level everyone down by default.

A Senior Manager with three reports is a tech lead with a bigger title. Level the job, not the label.

Why is tech lead the better slot for these candidates?

Tech lead is the scarcer title in US software, so hiring ex-Angi managers into tech lead roles fills the harder req. In Refolk's index of professional profiles, there are 7,470 Engineering Managers and 3,374 Tech Leads in US software and internet companies, a ratio of 2.2 to 1.

If you post an EM role, an ex-Angi manager competes against a big field, and that field just got bigger: Squarespace cut about 300 people, roughly 19% of its 1,800-person workforce, the same week. If you post a TL role, the same person is one of a much smaller group who has led people and still knows the system.

That matters if a tech lead req has been open for a quarter. Inbound brings mid-level ICs who want a title bump or managers who want to stop coding, and your existing leads cover the gap until they start to burn out.

Here's the full supply picture:

SegmentCountSource
Engineering Manager (US, software/internet)7,470Refolk's index
Tech Lead / Technical Lead (US, software/internet)3,374Refolk's index
EM-to-TL ratio2.2 : 1Derived
"Angi" headline matches, mgr/dir/TL titles (US)53 total; 11 of 25 sampled at Angi (44%)Refolk's index
Angi headcount: end 2024, post-Jan, post-Nov2,800, ~2,000, ~1,700IBJ; last figure derived
Manager layer cut to reach 6-12 reports50% to 75%Derived from Steib's numbers

Why does searching "Angi" plus "Manager" fail?

Keyword search on this company returns mostly noise. In Refolk's index, a headline search for "Angi" plus manager, director, or tech-lead titles in the US returned 53 profiles. In a 25-profile sample, only 11 actually worked at Angi.

The other 56% were string collisions: "Angie's Transportation," "ABGi USA," and "algi machine shop." A short brand name matches inside other words and other businesses, and headline search can't tell the difference.

The "Manager" part has its own problem. Steib said the cuts hit middle management and support, so a bare "Manager" title search pulls in support and ops managers along with engineering. In that sample, 11 of 25 were titled "Engineering Manager." Those are the ones you want, and you get them by searching on employer and function, not title.

A cleaner approach:

  • Filter by employer, current or past, using every brand name: Angi, HomeAdvisor, Angie's List, ANGI Homeservices. Some profiles will still carry the older names.
  • Add an engineering anchor: a title like engineer, tech lead, or engineering manager, or a skill from their stack.
  • Include past employer so you catch people who've already updated their profile after leaving.
  • Exclude support and operations titles unless you're hiring for those roles.

Writing that as a Boolean string across four brand names and three title families is slow and easy to get wrong. That's the gap Refolk closes: you describe the person in plain English and I search by employer, so "Angi" doesn't match "algi machine shop."

Where do Angi's engineers actually live?

Angi is based in Denver, with significant operations in Indianapolis and New York City, but its people are spread across the US, so use those cities to rank candidates, not to filter them out. A strict city filter will drop a large share of the pool.

The evidence that the footprint is distributed:

  • In August 2025, an Angi spokesperson said about 300 of its 2,800 employees lived in central Indiana. Everyone else was spread nationally.
  • The new Keystone office in Indianapolis has no in-office requirement.
  • In Refolk's "Angi" sample, the regions were Denver 2, NYC/Brooklyn 2, Kansas City 2, Houston/Katy 3, and Los Angeles 2. Indianapolis didn't appear at all.
  • In the tech-lead sample, New York led with 6 of 25, and Carmel, Indiana appeared once.

All of those come from 25-profile samples, so treat them as directional. The pattern still holds: Kansas City and Houston showed up as often as the headquarters city.

If you're hiring in Indianapolis specifically, the local numbers are a gap. Angi didn't answer IBJ's request for them, and Susan Orr at IBJ, who has covered both rounds from Indianapolis, is the reporter to watch for a breakdown. The 300 figure predates both 2026 rounds, so the current central Indiana population is smaller and unknown. And don't assume every ex-Angi engineer in the state lists Indianapolis: Carmel showed up in the sample on its own.

When should you reach out to each wave?

Re-check your employer-filtered search monthly from December 2026 through June 2027. This round is spread over about 8 months, not January's 8 weeks, so people will leave in waves rather than all at once.

Notice rules affect the timing. Federal WARN requires 60 calendar days' notice for covered layoffs, and New York's state WARN Act generally requires 90 days. In practice, NYC staff may hear earlier and leave later than colleagues in Denver or remote states. Check the current state rules before you build a calendar around them.

A practical cadence:

  1. November to December 2026: first notices. Reach out to people who post publicly, and to January-round leavers who are still looking.
  2. January to March 2027: the first notice periods end. Watch for "open to work" changes and profile updates that add an end date.
  3. April to June 2027: the final waves as charges finish in H1 2027.

Community signals help too. A thread on r/Layoffs, which has more than 145,000 subscribers, discussed the January cuts as they happened, and the same will probably happen as each November wave lands. Doing that monthly check by hand means rebuilding the same Boolean string every few weeks. With Refolk you rerun the same plain-English request each month instead.

FAQ

Should I hire ex-Angi managers as Directors?

Rarely. Steib said the average Angi manager had three direct reports, and reaching his six-to-12 target means removing half to three-quarters of the manager layer. Most people cut ran small teams with no manager reports. Ask about direct reports, manager reports, and budget ownership, and reserve Director for candidates who managed managers and owned spend.

When do the Angi layoffs from November 2026 finish?

Angi expects restructuring charges mainly in Q4 2026 and H1 2027, so departures should run through about June 2027. That's much slower than the January round, which was expected to finish before March 2026. Plan to re-run your sourcing search monthly over that period.

How do I find Angi engineers in Indianapolis specifically?

Search by employer first, including HomeAdvisor, Angie's List, and ANGI Homeservices, then rank by Indianapolis, Carmel, and nearby suburbs. Don't hard-filter on the city. As of August 2025 only about 300 of 2,800 employees lived in central Indiana, the Keystone office has no in-office requirement, and Indianapolis didn't appear at all in Refolk's 25-profile Angi sample.

Is a manager-to-tech-lead transition a step down?

Not when the scope is real. A manager with three reports and a tech lead running a small pod do similar work, but the tech lead usually has more technical ownership. Name the reason their role was cut - a ratio announced on an earnings call, not their performance - pay at the level, and offer a defined path to managing a team of six to 12, the span Angi's own CEO called normal.

The data behind this

Try it on the search you came here for

Stop building boolean strings. Just describe the person.

Type one sentence. I plan the search, read GitHub, public LinkedIn and Crunchbase records, and the open web as it is right now, and hand back a ranked list with the reason next to every name.

  1. 01Describe them

    One plain sentence. Role, city, stack, stage, whatever matters to you.

  2. 02I read the web live

    GitHub, public LinkedIn and Crunchbase records, the open web. Not a database that went stale last quarter.

  3. 03You read the shortlist

    Ranked, with the reasoning under every name. Open a profile, ask a follow-up, narrow it down.

  • No boolean, no filters, no seat to buy. One box.
  • Read at search time, so a profile updated yesterday counts today.
  • Every step visible as it runs, every name with its reason.

500 free credits on sign-up. No card, no demo call. See real searches.

Read next