Lightspeed's 250 Is Roles, Not People. Count the Real Leavers by Nov 5

If you're trying to hire out of the Lightspeed layoffs, the number everyone is quoting won't tell you how big your candidate pool is. On Oct 13, 2026, Lightspeed Commerce said 250 roles were affected, a mix of laid-off people and vacancies it won't fill, and it isn't giving the split before earnings on Nov 5. 250 people and 250 empty headcount slots are very different candidate pools. Here's how to estimate the real number, and find the people, before the company tells you.

What did Lightspeed announce on Oct 13, 2026?

Lightspeed said 250 roles were affected through a mix of layoffs and vacancies it won't fill. It gave no split between the two and no breakdown by team. Spokesperson Stéphanie Princivil wouldn't say which areas were hit and pointed to the next earnings report, expected Nov 5, 2026.

What's on the record so far:

• The Logic asked how many of the 250 were layoffs. Lightspeed hadn't answered by deadline.
• Leavers posted before the company said anything. Madison McLauchlan at BetaKit found "multiple former Lightspeed employees across content and sales roles" posting on LinkedIn the week before the announcement.
• This is the fifth disclosed round since January 2023. The running total is about 1,130 roles cut or closed, roughly 350 of them in 2026.
• The July 2026 round took about 100 jobs, or 3% of the company. CFO Asha Bakshani said 10% of product and tech jobs were cut. Founder and CEO Dax Dasilva said Lightspeed was still hiring, and has said AI reduced its staffing needs, especially in product development.

1,130

That history matters. The engineers you might want could have left in July. Judging by the early LinkedIn posts, the October round looks more like sales and content.

Why is "250 laid off, 7.4%" the wrong headline?

It's wrong in two ways. The 250 includes vacancies nobody was sitting in, and the 7.4% is measured against a base that counts contractors. Trackers like layoffhedge.com already list the event as "250 employees laid off, 7.4%," which gets both the people count and the base wrong.

The base problem comes from Lightspeed's own figures, which don't agree with each other:

Splitting the number is possible. Hamilton Health Sciences announced 413 positions cut and said 167 of them were vacancies. Lightspeed could do the same. It has chosen not to yet.

For a recruiter, the takeaway is simple. Your real pool is 250 minus the closed vacancies, and nobody outside the company knows that second number. You can estimate it.

Method 1: How do job-board snapshots reveal the vacancy half?

Postings that disappear between a snapshot taken before Oct 13 and one taken after give you a rough count of the closed vacancies. Subtract that from 250 and you have an upper bound on how many people were laid off.

Here's the workflow:

1. Pull old captures. Look up Lightspeed's careers page and its Greenhouse or Lever board in the Wayback Machine for September and early October 2026.
2. Capture the board as it is today. Save the full list of reqs with title, team, and location.
3. Diff on removals only. Dasilva said in July that Lightspeed was still hiring, so new postings may show up. Ignore them. You're counting reqs that vanished.
4. Tag the removed reqs by function. Engineering, sales, content, support. This gives you an early team breakdown that the company won't publish until November.
5. Subtract from 250. What's left is the most people who could have been laid off.

Where the diff misleads

The diff only sees jobs that were posted publicly, so it undercounts closed vacancies. That pushes your upper bound too high. Watch for:

• Reqs approved internally but never posted.
• Postings already pulled after the July round, which won't show up in a September-to-October diff.
• Evergreen postings that stay up whether or not anyone is hiring.
• Reqs pulled for reasons that have nothing to do with the cut.

Treat the result as a ceiling, not a count.

Method 2: What do the leavers' own LinkedIn posts tell you?

LinkedIn posts are the fastest way to see who left, and so far they come from content and sales staff. A count of posts gives you a floor on the number of people laid off, not the total.

A job-board diff tells you how many chairs vanished. Only the people tell you who stood up.

Don't read the early skew as the whole picture. Salespeople and marketers have an obvious reason to announce a layoff publicly, because their network is their pipeline. Engineers may simply update a headline or say nothing. So the post count likely overweights sales.

In Refolk's index of professional profiles, 367 profiles in Canada have "Lightspeed Commerce" in the headline. A 25-profile sample shows the spread of functions:

• Senior Software Developer
• Senior Manager FP&A
• Outbound Account Executive and Account Executive II
• Product Manager
• Staff Analyst (Security)
• Head of Golf

Three traps in headline searches

• Missing employers. Headline matching misses everyone who doesn't put their employer in their headline.
• Stale affiliations. Lightspeed sold Upserve to Skyview Equity in April 2026 for up to US$81M. Some profiles may still point to a business unit that has already changed hands.
• Name collisions. Tencent's Lightspeed LA studio laid off about 80 people in July 2026. A plain "Lightspeed" search will pull them in. They're game developers, not commerce staff.

Getting past these traps means searching the profile, the posts, and the open web together. You're looking for people who were at Lightspeed and whose status changed around October, not just current headline matches. That's the gap Refolk closes: you describe the person in plain English and get back a ranked list, not a keyword dump.

Method 3: Will a Quebec collective dismissal notice show the real number?

Possibly, but only for Quebec establishments. Quebec is the only province where a public count of affected people is likely to appear, because its threshold is low and it keeps a monthly list of notices. Ontario's threshold is higher and I found no public registry of its filings, a key difference from US WARN notices.

A Quebec collective dismissal notice is the filing an employer must send to the ministry when it lets go of 10 or more employees at the same establishment within two months. The notice has to state how many employees may be affected and the planned date.

Read the notice period as a size signal

In Quebec the minimum notice period depends on how many people are affected:

• 8 weeks for 10 to 99 employees
• 12 weeks for 100 to 299 employees
• 16 weeks for 300 or more

So if the planned date on a Lightspeed notice sits 12 weeks after filing, that suggests 100 to 299 people at that Quebec establishment. If 50 or more are affected, the employer must also help set up a reclassement (redeployment) committee, which is another sign of scale.

One practical catch: the latest monthly list I could find at the National Assembly library was for October 2025. Check whether newer lists have been posted. If not, plan on a records request, which may not come back before Nov 5.

Why Ontario will probably stay silent

Ontario's rule counts terminations per establishment. If the cuts were spread across Toronto, Ottawa, Calgary, and remote staff, no single Ontario office may reach 50 in four weeks, so no Form 1 is required. Even if one is filed, it goes to the Director, the workplace, and the affected employees. It doesn't go to you.

Are the Montreal leavers actually in Montreal?

Probably not, mostly. In Refolk's index sample of profiles with "Lightspeed Commerce" in the headline, Ontario outnumbers Quebec. A recruiter who only searches Montreal tech layoffs could miss most of the people who were let go.

From that 25-profile sample:

• Ontario: 8. Toronto 5, Kanata/Ottawa 2, Kitchener-Waterloo 1.
• Quebec: 6. Montreal 4, Greater Montreal 1, Laval 1.
• Calgary: 2.
• Vancouver: 1.

Monkhouse Law notes that Lightspeed has offices in Toronto and Ottawa. The headquarters city tells you where decisions are made. It doesn't tell you where the people sit. A sample of 25 shows direction, not exact shares, but the direction is clear enough to change where you search.

Run that search without a city filter first, then sort by province. You'll see right away whether a Montreal-only plan was aimed at a minority of the pool.

Can you hire laid-off payments engineers in Montreal?

Barely. The pool is tiny. In Refolk's index, only 114 people in Canada hold a software engineer or developer title with "payments" in the headline. In a 25-profile sample, just 1 is in Montreal, compared with 10 in the Toronto area (Toronto, Mississauga, Oakville).

114

Three things follow from that.

• You're competing for them. The top employers in the payments sample are Paymentus, AWS, Shift4, Interac, and 7shifts. Those are the likely competitors for any payments or POS engineer Lightspeed let go.
• October may not be the engineering round. July took 10% of product and tech. The October evidence points to content and sales, which would fit Dasilva's plan to grow outbound sales to 150 people in fiscal 2025 being cut back. If you want Lightspeed payments engineers, look at July leavers as well as October ones.
• City-plus-keyword filters won't find them. With roughly one payments engineer in 25 based in Montreal, filtering on the city plus "payments" returns close to nothing. Search Quebec and Ontario together, and remember that headline matching misses anyone who leaves the word out.

Postings with payments in the title show who else is competing for the same small group of engineers right now.

How do you combine the three methods before Nov 5?

Use each source for the part it measures well. The job-board diff gives you a ceiling, LinkedIn posts give you a floor, a Quebec notice (if one exists) gives you a regulated count for Quebec establishments, and Nov 5 earnings give you the company's own split.

1. Ceiling: 250 minus the reqs that vanished from the board.
2. Floor: the number of distinct leavers you can confirm from posts and headline changes.
3. Quebec check: the count and planned date on any collective dismissal notice, with the notice length as a size signal.
4. Reconcile on Nov 5: compare your estimate to the company's breakdown and update your shortlist.

By the time the earnings call confirms the split, the strongest Lightspeed leavers may already be talking to Paymentus and Shift4. The point of estimating early is to reach them first.

FAQ

How many people did Lightspeed actually lay off in October 2026?

Nobody outside the company knows yet. Lightspeed said 250 roles were affected through layoffs plus vacancies it won't fill, and didn't say how many were people. The Logic asked and got no answer by deadline. You can set an upper bound by subtracting the reqs that disappeared from its job board from 250. The official breakdown is expected with earnings on Nov 5, 2026.

Does Lightspeed have to file a Quebec collective dismissal notice?

Only if 10 or more employees at the same Quebec establishment are dismissed within two months. The notice must state how many employees may be affected and the planned date. The minimum notice is 8 weeks for 10 to 99 people, 12 weeks for 100 to 299, and 16 weeks for 300 or more. The ministry's monthly list is held by the National Assembly library, but recent months may need a records request.

Is there an Ontario equivalent of US WARN notices?

Partly. Ontario requires a Form 1 when 50 or more employees at one establishment are terminated within four weeks. It goes to the Director of Employment Standards, is posted in the workplace, and a copy goes to each affected employee. I found no public registry of these filings, and cuts spread across several offices may never reach the threshold.

Where are laid-off Lightspeed engineers most likely to be?

Probably Ontario as much as Quebec. In Refolk's index sample, profiles with "Lightspeed Commerce" in the headline were more often in Ontario (8 of 25) than Quebec (6 of 25). Payments engineers in Canada are clustered around the Toronto area, with 10 of 25 there against 1 in Montreal. Also check the July 2026 round, when 10% of product and tech jobs were cut.