Flock's 270 Exits Oct 29. Only 10 of 561 Profiles Are Engineers

Flock Safety is losing about 270 people, roughly 18% of its 1,500 staff, and most of them leave on October 29. If you hire computer vision, embedded, hardware or gov-tech engineers, this looks like a gift. It's harder to work than a normal layoff list, though. Many of these people chose to leave a surveillance company in the middle of a privacy backlash, and the reporting gives you a headcount and a date, not names.

What is happening at Flock Safety on October 29?

About 270 Flock employees are expected to leave through a voluntary separation program, and most approved departures take effect October 29. Reuters (Krystal Hu and Helen Coster) reported the figure on October 8. Flock declined to confirm the percentages.

A voluntary separation program is a buyout: the company offers enhanced severance to people who apply, then decides which applications to approve. The dates:

• October 2: applications close
• October 9: decisions expected
• October 29: most approved departures take effect
• 1 to 3 months after October 29: Flock may ask some approved leavers to stay on

Flock spokesperson Paris Lewbel said it is "not a layoff." Whatever you call it, turning a headcount into actual people is a sourcing problem.

Who is on the list: volunteers, forced cuts, or both?

Nobody outside Flock has said how many of the ~270 are buyouts staff asked for and how many, if any, are cuts imposed after applications closed. Treat the group as a possible mix, not a known one.

Here's why the mix is possible. Before the program launched, Wired reported that without buyouts the company would "almost certainly" need to lay off some staff. Engadget later wrote that "it is unclear how many of the employees in these upcoming layoffs are leaving voluntarily." Neither source says the buyout missed a target. Both leave room for a second, involuntary group.

For sourcing, this means you can't treat everyone the same way. A person who applied to leave and a person who was told to leave want different things from your first message. You won't know which one you're talking to until you've read their public signals or asked them.

Why "we're stable" doesn't work on buyout takers

Buyout takers already have money and time, so a pitch built on stability and a fast start date answers a problem they don't have. What they need to hear is why your company fits the reason they left.

Look at what volunteers walk out with:

• Severance that reportedly reaches tens of thousands of dollars, roughly twice Flock's previous packages
• Several months of health coverage
• Up to two years to exercise stock options

The options term matters most. Flock's last round was a $275 million raise in March led by Andreessen Horowitz at a $7.5 billion valuation, according to Reuters. Wired reported a raise "north of $8 billion" in April. Either way, the options are worth thinking about carefully, and a two-year window means a volunteer doesn't have to rush that decision. They can run a slow, picky job search.

What they do have is a reason they chose to leave. CEO Garrett Langley told the All-In podcast that the backlash's "biggest damage" was to "internal morale." The backlash has been heavy:

• Secure Justice counts 214 cities that have dropped Flock since 2021, 90 of them in August 2026 alone
• DeFlock's tracker counts 341 US communities that canceled, rejected, shut off or banned Flock
• Cancellations kept coming: La Crosse, Wisconsin on October 23 and New Bedford, Massachusetts on October 24
• Sen. Josh Hawley wrote to Langley about surveillance without congressional authorization

A buyout taker already has the money and the time. Your pitch has to supply the reason.

Refolk's index: Flock's visible alumni are sellers, not engineers

Most people who publicly identify with Flock Safety work in sales and go-to-market, not engineering. In Refolk's index of professional profiles, 561 US profiles mention "Flock Safety" in their headline, and only 10 hold an engineering title.

1.8%

The top titles in the sample are VP Go-to-Market, VP Commercial Sales, Director Enterprise Sales, Revenue Enablement, and Director of DFR & Nova Sales. That fits a municipal-subscription business, which needs a lot of people selling to cities. Reuters described the cuts as "across the board," so the 270 probably contain far more sellers than engineers.

Some caveats on the count. It includes some former staff: 22 of 25 sampled profiles still list Flock (88%), and the others have moved to Gaia Robotics, Replit and Mastercard. It also only catches people who put the company in their headline.

The practical point: gov-tech and public-safety SaaS founders will probably get more from this group by hiring experienced public-sector sellers than by hunting for engineers. A seller who kept closing city contracts through 2026's cancellation wave has been tested in a way most haven't.

Why a title search won't find Flock's computer vision engineers

If you want to hire laid-off computer vision engineers from Flock, searching the job title won't get you there. Nine of the 10 Flock engineers in Refolk's index call themselves "Software Engineer," and one says "Machine Learning Engineer." None say computer vision, embedded or firmware.

9 of 10

Search the obvious title and you get a different crowd. Refolk's index has 427 US profiles titled "Computer Vision Engineer," and the top employers in the sample are Meta (12) and Apple (7). Those are good engineers, but they don't come from Flock and they aren't in the middle of a buyout.

This is why Flock Safety engineers hiring feels slow. The people who worked on Flock's ALPR (automatic license plate recognition), edge inference and camera firmware sit under a generic title on LinkedIn. Their real specialty shows up elsewhere, in code and on the open web. If you're the only person sourcing for a hard-to-fill CV or embedded req, that means days of cross-referencing.

Search for the work instead of the title. Useful signals:

• Employer history: Flock Safety anywhere in experience, not only the current role
• Skills and domain terms: edge inference, ALPR, camera firmware
• GitHub activity: contributions to vision, embedded or on-device ML repos
• Open-web traces: talks, blog posts and old job descriptions that name the actual systems

Matching this by hand across LinkedIn, GitHub and the web is the gap Refolk closes. You describe the engineer in plain English and get back a ranked shortlist drawn from all three sources, so a "Software Engineer at Flock" with edge-inference commits gets surfaced and a Meta CV researcher doesn't.

Where do Flock's engineers live?

They're spread across the country, so don't source Atlanta only. The 10 engineers in Refolk's index are in 10 different metros, and only one is in the Atlanta area:

• New York City
• Arlington, Virginia
• Denver
• Los Angeles
• Kennesaw, Georgia
• Champaign, Illinois
• Auburn, Alabama
• Arvada, Colorado
• Washougal, Washington
• Rutledge, Tennessee

None are in the Bay Area. That gives remote-first companies an advantage: the Champaign or Washougal engineer probably isn't moving for a hybrid role. If your req requires relocation to San Francisco, expect a small pool from this list and plan your pitch around that.

How should you segment the Flock list before reaching out?

Sort people into "likely volunteer," "possibly cut," and "unknown" from public signals before you write a word, then sort by function and timing. This saves you from sending a stability pitch to someone who left on principle.

1. Tenure. Long-tenured staff with vested options got the most out of a two-year exercise window, so they had the most reason to apply. Recent hires had less.
2. Team. Separate engineering (CV, embedded, hardware, platform) from go-to-market and operations. The table above says sales will be most of what you find.
3. Public signals. Look for posts about the backlash, privacy or "taking time off." A profile marked "open to work" in the first week of November reads differently from a quiet one.
4. Timing. Note who is gone October 29 and who may be held 1 to 3 more months. The second group won't be free until late November through January.
5. Destination fit. Someone who left over ethics will rule out some employers right away. Check that before you pitch.

The fifth point applies to Axon in particular. Axon replaced Denver's Flock cameras and is the obvious competitor-hirer, but a volunteer who left because of surveillance concerns may find Axon a hard sell. Competitors still have a real shot with the involuntary group and with sellers who liked the work and disliked the headlines.

What should the pitch say to each group?

Pitch volunteers on mission, product ethics and data governance. Pitch the people who were cut on stability and speed.

For likely volunteers

• Say plainly what your product does with data and who can access it
• Name your data governance: retention limits, audit logs, who signs off on law enforcement requests (or say that you don't serve them)
• Describe the problem you're solving in one sentence that doesn't need defending at a dinner party
• Offer a slow process: an informal call now and a formal loop in December is fine, since their options window runs two years

For people who were cut

• Here the stability pitch works: runway, revenue, team tenure
• Move fast and give a concrete timeline
• Explain how their Flock domain experience (ALPR, edge inference, municipal sales) carries over directly

For anyone you can't classify

Ask a neutral opener: "I saw Flock's restructuring. What are you hoping the next thing looks like?" Let them sort themselves. Voluntary separation program candidates often say what they want in the first reply if you leave them space. Before you send anything, read what they've posted publicly about the backlash. It's the cheapest way to pick the right pitch.

When will the second wave of Flock departures arrive?

Expect at least two exit waves: the October 29 group, and a held-over group available from late November through January. Flock may keep some approved leavers for one to three months past the 29th, and any involuntary cuts could add to that later group.

The second wave is likely to be more urgent and more open to a stability pitch, especially if it includes people who didn't choose to leave. The backlash isn't over either. With La Crosse and New Bedford canceling in the final week of October, customer losses could keep pushing on the ~1,230 who stay. Put a follow-up on your calendar for the last week of November and again in early January, and keep your Flock shortlist warm instead of rebuilding it.

FAQ

Is Flock Safety's restructuring a layoff or a buyout?

Flock calls it a voluntary separation program, and spokesperson Paris Lewbel said it is "not a layoff." Reuters reported about 270 departures, roughly 18% of staff. Engadget noted it is unclear how many are leaving voluntarily, and Wired had earlier reported layoffs were "almost certainly" needed without buyouts, so treat the group as a possible mix.

How do I find Flock Safety's computer vision engineers?

Search by employer history and skills rather than job title. In Refolk's index, 9 of the 10 Flock engineers list their title as "Software Engineer," so a "Computer Vision Engineer" search mostly returns people from Meta and Apple. Look for edge inference, ALPR and camera firmware signals on GitHub and the open web.

When are Flock's departing employees available?

Most approved departures take effect October 29, 2026. Flock may ask some employees to stay one to three additional months, so a second group becomes available between late November and January. Reach out to the first wave now and plan follow-ups for both windows.