Lightspeed's Engineers Left in July, Not October. Search Toronto Too

If you're sourcing off the October "Lightspeed layoffs" headline, you're three months late and looking at the wrong teams. The 10% product and tech cut was disclosed on July 30. The roughly 250 roles that followed include openings that were never filled, and the people who posted about it publicly were in content and sales.

What did Lightspeed actually cut, and when?

Lightspeed made two separate cuts at two separate times. First it removed 10% of product and tech headcount during the July to September quarter. Then, after September 30, it removed about 250 roles, and that count includes vacancies that were never filled.

On the November 5 fiscal Q2 2027 call, CFO Asha Bakshani put it plainly. Lightspeed "removed 10% of headcount within Product and Tech," and that happened "within the quarter." Then, "after the quarter end we removed approximately 250 roles." She said both cuts were already built into guidance and that some of the savings will be reinvested.

The engineering cut wasn't news on November 5. On the July 30 Q1 call, management said "we recently reduced about 10% of our headcount in product and tech," and pointed to lower headcount needs "particularly in product development." So the cut was booked in Q2 and already called "recent" on July 30, which means most engineering exits probably landed in July.

This is the fifth publicly reported round of Lightspeed Commerce layoffs since early 2023, and BetaKit has covered every one:

One caveat. In July, CEO Dax Dasilva told BetaKit the cuts hit about 100 people and that Lightspeed was still hiring. It's very likely that the "about 100" and the "10% of product and tech" describe the same group. Lightspeed hasn't confirmed it, though, so treat them as overlapping rather than identical.

Why the October headline points at the wrong teams

The October layoff posts came from content and sales staff, and the 250 figure mixes real layoffs with jobs that were never filled. That makes it a poor signal for anyone sourcing technical talent.

BetaKit's report from around October 13 found that the people posting layoff news on LinkedIn were in "content and sales roles." Lightspeed didn't say how many of the 250 were people and how many were closed openings. When CBC asked, spokesperson Stephanie Princivil declined to say which areas were affected.

The bigger reason is the direction Lightspeed is moving. On the same July call where engineering shrank, management talked about hiring "a few hundred more salespeople." Lightspeed is shifting headcount from building to selling, so the 250 isn't a uniform cut across the company.

The engineers left in July. The October headline was about sales, and recruiters reading it are a quarter behind.

The Upserve sale matters here too. Lightspeed sold its US hospitality product to Skyview Equity in late April, and those engineers moved with the sale. They weren't laid off. Management tied the lower product-development needs to the divestiture and to productivity gains. The likely result is that the July cuts fell on deprioritized or duplicate stacks, not on the core retail and European hospitality payments teams.

Why searching "Lightspeed" in headlines finds the wrong people

A headline search for "Lightspeed" mostly turns up engineers who still work there. People who left usually rewrite their headline, so the company name disappears just when you need it.

15 of 17

Refolk's index shows this clearly. Only 17 software engineers in Canada (SWE, Senior, Staff, Backend, and Full-stack titles) mention "Lightspeed" in their headline. Fifteen of them still list Lightspeed as their current employer: 13 under Lightspeed Commerce, 1 under NuORDER by Lightspeed, and 1 under plain "Lightspeed." Fourteen of the 17, about 82%, are Senior or Staff level.

It happens because headlines describe the present. An engineer who left in July usually swaps their headline for "open to work" or a new employer. The current employees keep the brand in their headline, so a keyword search finds people who aren't available.

A tenure end date is the month and year a person's role at a company ended, as listed in their work history. That's the field to filter on. A working filter set looks like this:

1. Past employer is Lightspeed, Lightspeed Commerce, or an acquired brand (NuORDER, POSIOS, Gastrofix, iKentoo).
2. Tenure ended between July and September 2026.
3. Title was engineering: software, backend, full-stack, platform, mobile, or engineering manager.
4. Current employer is blank, or they joined a new one after August 2026 (worth a later approach, not an immediate one).

A keyword search can't express "left in July." Refolk handles this directly: you describe the person in plain English, including when they left, and get back a ranked shortlist drawn from GitHub, LinkedIn, and the open web.

Where are Lightspeed's engineers: Montreal or Toronto?

Montreal is headquarters, but in Refolk's index Ontario has more Lightspeed-tagged engineers than Greater Montreal, 7 to 5. If you only want to hire software engineers in Montreal, you're skipping 7 of the 17 in the pool.

Here's the breakdown of the 17 Lightspeed headline matches:

• Ontario: 7 (Toronto 4, plus Ottawa, Guelph, and Kitchener)
• Greater Montreal: 5 (Montreal 3, Greater Montreal 1, Longueuil 1)
• "Canada" only: 5 (location not given)

Lightspeed has a Toronto office and remote engineers in Ottawa, Kitchener, and Guelph. The wider payments market leans the same way. Refolk's index finds 103 Canadian software engineers with "payments" in their headline. In a 25-person sample of them, Toronto beat Montreal 6 to 2.

All counts match headline keywords only, so treat them as directional. Even so, the takeaway holds: if you have a Montreal req, the Montreal pool is real but thin, so widen to Ontario remote before you widen your criteria.

Which Lightspeed engineering pods are worth sourcing?

Go after the teams behind Lightspeed's two focus businesses: North American retail and European hospitality, with payments running through both. In fiscal Q2 2027 those two businesses brought in 77% of $323.8M in revenue, which grew 15% organically.

Payments and point of sale

Canadian employers already hiring payments engineers include Shift4, Paymentus, and AtoB, and AtoB already employs one of the Lightspeed-tagged engineers in Refolk's index. You won't be the only one calling.

Expect a mix, not a block. If the July cut fell mainly on deprioritized or duplicate stacks after the Upserve sale, many leavers will have worked near payments rather than on the core processing path. Check each person's actual work before you pitch them a payments role.

European hospitality

This is the rarest pool and the one most recruiters overlook. Lightspeed's restaurant-POS engineering came from three acquisitions:

• POSIOS in Ghent, bought in 2014
• Gastrofix in Berlin
• iKentoo in Lausanne

~34x

Only three Belgian software engineers in Refolk's index put "payments" in their headline: one at Keytrade Bank, one at m-Path Software, and a freelancer. Some of that is language, since Belgian headlines are often in Dutch or French, so treat 3 as a floor. Still, it makes Lightspeed's Ghent team one of very few local groups of restaurant-POS engineers. If you're filling a hospitality-tech or payments role in Flanders, a single Ghent departure matters far more than the same number would in Canada, and on a market this thin, waiting for one to post "open to work" is not a plan.

For Ghent, Berlin, and Lausanne, search by former employer in the local language as well as English, and include the pre-acquisition brand. An engineer who joined POSIOS before the 2014 acquisition may never have put "Lightspeed" in their title.

How should you time and write the outreach?

Approach the July cohort now, with a message that recognizes they left three months ago and offers something Lightspeed couldn't. Don't open with the October news. It wasn't about them, and opening with it tells them you're working from the headline.

A sequence that works for this group:

1. Filter by exit date first. July to September 2026 departures from Lightspeed or an acquired brand. Set aside anyone who started a new job after August, and save them for a six-month check-in.
2. Verify the stack. Look at public commits, talks, or project descriptions to tell core payments engineers from people on adjacent or sunset stacks.
3. Lead with stability. This is the company's fifth reported round of cuts since January 2023. Anyone who joined before 2023 lived through three earlier rounds before July, and will care more about a team's runway than about a title bump.
4. Name the competition honestly. Shift4, Paymentus, and AtoB are hiring the same people. Say why your role is different: the scope, the stack, or the fact that you're adding engineers while Lightspeed shifts headcount to sales.
5. Offer remote across Ontario and Quebec. With 5 of 17 profiles listing only "Canada," location flexibility is part of what they'll compare.

Step 2 is where most sourcing time goes. Refolk cuts that down by pulling GitHub activity and work history into one profile, so you can tell a payments-core engineer from a front-end generalist before you write the first line.

FAQ

When were Lightspeed's engineers laid off?

Lightspeed cut 10% of its product and tech headcount in its fiscal Q2 2027 quarter (July to September 2026). Management already called it "recent" on the July 30 earnings call, so most engineering exits probably landed in July. The roughly 250 roles announced in October came after the quarter ended, and according to BetaKit the people posting about them were in content and sales roles.

How many Lightspeed engineers are open to work?

Nobody outside the company knows. Lightspeed didn't break down the 250 roles between people and closed vacancies, and it didn't name the affected areas. In Refolk's index, 15 of the 17 Canadian engineers with "Lightspeed" in their headline still work there. That's why searching by past employer and tenure end date works far better than searching for "laid off" posts.

Were Upserve engineers part of the Lightspeed layoffs?

Mostly not. Lightspeed sold Upserve, its US hospitality product, to Skyview Equity in late April 2026, and those engineers moved with the business. Management did connect the lower product-development needs behind the July cut to that sale, so some Lightspeed engineers on overlapping stacks may have been affected indirectly.