Pipedrive Cut 267 in Estonia. Its Veterans Are the Last Ones Free
Pipedrive layoffs 2026: who was cut in Tallinn, Tartu, Lisbon and Berlin, how Estonian notice periods set start dates, and which stack terms to search.
If you hire engineers in Europe, your first move after Pipedrive's Oct 29, 2026 announcement will be to search "Pipedrive" and send messages this week. That gets the timing wrong. ERR puts the Estonian count at 267 jobs, and under Estonian law the people you most want to hire are the last ones who can start.
What did Pipedrive cut, and where?
ERR reports that Pipedrive is cutting about 70% of its Estonian staff (219 in Tallinn, 48 in Tartu). It is also closing its Lisbon office, and some of its Berlin developers are affected. In CEO Paulo Cunha's Oct 29 letter, the company told staff it will shrink in every location, with fewer teams, fewer management layers and fewer offices.
Here is what the press reports say, office by office:
- Tallinn: 219 roles (ERR)
- Tartu: 48 roles (ERR)
- Lisbon: the office of about 220 people is set to close (Estonian World)
- Berlin: developers affected (Estonian World)
- Prague: Estonian World says a smaller operation there is closing too, but ERR still lists Prague as an active office. Treat it as unconfirmed.
Pipedrive declined to confirm the local figures. ERR's numbers mean roughly 380 Estonian staff out of nearly 800 worldwide. To see the scale, go back to 2022. That year Pipedrive cut 143 jobs worldwide, 79 of them in Estonia, and it still had more than 1,000 employees, 557 of them in Estonia. After this round, roughly 113 people would be left in Estonia.
The company said it would speak to every employee one by one over the next two days to tell them whether their job was at risk. So by the end of October, affected people should have known. That doesn't mean they were free to start somewhere else, and the rest of this article is about that gap.
Who is in the 267, according to Refolk's index?
In Refolk's index of professional profiles, 365 profiles in Estonia mention Pipedrive in their headline. Portugal has 152 and Germany 54. In each country's sample, the people do a different kind of job.
| Country | Profiles mentioning Pipedrive | Currently at Pipedrive (sample of 25) | Dominant title cluster | Reported local staff |
|---|---|---|---|---|
| Estonia | 365 | 14 (56%) | Senior PM, Software Engineer, Data Platform Engineer, Product Designer | ~380 |
| Portugal | 152 | 21 (84%) | SDR, Account Executive, Customer Success Manager, Support Engineer | ~220 |
| Germany | 54 | 18 (72%) | SVP Growth, SEO Lead, Head of Web, Director Data Platform Engineering | not reported |
The table shows two things.
First, Portugal's 152 profiles cover about 69% of the roughly 220 Lisbon staff, and most of them still work at Pipedrive. Lisbon is well labelled and easy to find.
Second, Estonia's 365 is close to the reported 380 staff, but only 56% of the sample currently works at Pipedrive. The rest are alumni from earlier years. The count looks like full coverage, but much of it isn't.
Location data is also thin. In the 25-profile Estonian sample, 13 list Tallinn and only 1 lists Tartu, even though 48 of the cuts are in Tartu. Tartu looks under-labelled, so a location filter alone will likely miss people.
Where should an engineering hire start: Tallinn, Lisbon or Berlin?
If you're hiring engineers, start in Tallinn and Tartu, not Lisbon. Lisbon is the office closing completely, but its people are mostly in sales and customer success.
Here is what each location mostly holds, based on the index samples:
- Tallinn and Tartu: product managers, software engineers, data platform engineers, product designers. This is where the backend and frontend engineers are.
- Lisbon: SDRs, account executives, customer success managers, support engineers. This is the best pool if you're building a European sales team.
- Berlin: growth, SEO and web leadership, plus some data platform leaders. When Pipedrive opened Berlin in 2021, it called it the company's global marketing hub and home to design, sales and support engineering teams. The "developers in Berlin" in the reports probably skew toward web and support engineering rather than core platform work.
One warning before you plan around Lisbon or Berlin. Pipedrive CMO Mariliis Beger said she couldn't confirm the status of each office because "different countries have different labor laws." Lisbon follows Portuguese law and Berlin follows German law. Their timelines are not the Estonian timeline below, so don't apply the Estonian table to them.
Why is "Pipedrive" a bad search keyword?
Searching "Pipedrive" returns current staff, a long tail of alumni and outside consultants all mixed together. Search by stack and team name instead.
The Estonian alumni tail includes co-founders, former CTOs, board members, and people who now work at companies like Planhat and Creditstar. They are interesting people, but none of them were affected by this cut. In Germany, the keyword also pulls in Pipedrive consultancies such as PD Experts, which sells Pipedrive Beratung (consulting) services. These people put the product name in their headline because they sell it, not because they worked there.
The practical cost is real. Going through 365 Estonian headlines by hand to separate current staff from alumni, and engineers from PMs, eats hours before you send a single message. If you have a hard-to-fill backend role and no sourcer to spare, that sorting is the bottleneck.
Search for what these people actually worked on. Stack terms from Pipedrive's engineering job ads:
- TypeScript and JavaScript, Node.js on the backend
- React on the frontend
- MySQL, Redis, Apache Kafka
- Docker and Kubernetes
- Older ads also list Fastify, Go and PHP
Team terms. A tribe, in Pipedrive's org language, is a group of teams that owns one product area. The tribe names show up in people's experience sections:
- Monetization tribe: owns conversion, upsell and contraction flows
- Billing and Spark tribes, inside the EBS department
- Backend platform tribe: common data access layer, full-text search, entity filtering
- Product names: LeadBooster, Deals
"Node.js, Kafka, Monetization" finds someone who built conversion and upsell flows. "Pipedrive" finds someone who once had a login.
How long is the notice period for redundancy in Estonia?
Under §97 of Estonia's Employment Contracts Act, the notice period for redundancy depends on tenure. It is 15 calendar days for under one year of service, 30 days for one to five years, 60 days for five to ten years, and 90 days for ten years or more. Severance also grows with tenure.
| Tenure | Notice | Employer severance | Extra from the Fund |
|---|---|---|---|
| Under 1 year | 15 days | 1 month | none |
| 1 to 5 years | 30 days | 1 month | none |
| 5 to 10 years | 60 days | 1 month | +1 month |
| 10+ years | 90 days | 1 month | +2 months |
There is a second clock. A collective redundancy is a layoff large enough that the employer has to notify the Estonian Unemployment Insurance Fund (Töötukassa) first. The redundancy takes effect no earlier than 30 calendar days after the Fund receives that notice, and the Fund can extend this to 60 days.
The employer can shorten things by paying in lieu of notice. Under that rule, it pays the average daily wage for each working day the notice period fell short.
Put the two clocks together and the timing reverses what most recruiters expect. People hired in the last year or two can move first. My estimate is that staff with five or more years probably can't start until early 2027, unless Pipedrive pays them in lieu of notice. Pipedrive hasn't said whether it will. Ask each candidate directly. It takes one question and saves a month of guessing.
Sort your outreach by start year, not by title
Group your Pipedrive shortlist by the year each person joined. The start year tells you their notice period, their severance and how urgent their search is better than their title does. Use three groups:
- Joined 2022 or later (15 to 30 days' notice). These people can start first and have the smallest cushion. Contact them now.
- Joined 2017 to 2021 (5 to 10 years, 60 days' notice). This is the core of the people who built the platform. They also lived through the 2022 cut, when Estonia lost 79 roles. Make contact now, but plan for a start date in the new year.
- Joined 2016 or earlier (10+ years, 90 days' notice). These are the original builders. They get the longest notice and two extra months of Fund money. Treat these as relationship conversations, not pipeline fill.
Keep the groups in separate sequences. If a ten-year veteran gets the same "can you start in two weeks?" message as a 2024 hire, you look like you didn't read their profile.
Working tenure out from each LinkedIn timeline one by one is slow. Refolk returns start years with each profile, so you can ask for veterans by tenure directly.
Why the veterans can afford to wait
Pipedrive's longest-serving Estonian staff have 60 to 90 days of paid notice, plus one month of employer severance, plus one or two extra months from the Fund. A speed pitch won't work on them.
That adds up to several months of income with no pressure to take the first offer. Someone who joined before 2017 has watched Pipedrive's Estonian headcount fall from 557 to roughly 113. They are deciding what the next five years look like, not where to go next month.
A ten-year Pipedrive engineer isn't looking for a job next month. They're choosing what to build for the next five years.
So pitch the work: the system they would own, the team they would join, the problem nobody has solved yet. Name the specific work from their profile ("you built contraction flows in Monetization") and connect it to a specific problem you have. Compensation comes later. Being specific gets the first reply.
Why did Pipedrive cut, and who else wants these people?
Pipedrive's stated reason is about how customers find it, not about AI replacing its staff. More small businesses now ask AI tools which software to buy, so the free web traffic that drove Pipedrive's growth has dropped sharply, and the paid advertising bought to replace it costs more.
This matters when you assess candidates. The engineers weren't automated away. They lost their jobs because the company's customer acquisition broke. Their skills are as current as they were in September.
Former CTO Sergei Anikin gave Äripäev another reading. He said the scale of the cut may reflect the wish of Vista Equity Partners, majority owner since 2020, to exit its investment. Estonian World notes that no sale has been publicly confirmed.
You won't be the only one recruiting. Pipedrive's founders (Ragnar Sass, Timo Rein, Martin Henk, Urmas Purde and Martin Tajur) are a natural network for rehiring. A "Pipedrive Talent Index - Hire former Pipedrive colleagues" alumni post is already circulating on LinkedIn, and a Prague-based engineer has engaged with it. The alumni network may reach the best people first unless you have already started the conversation with a specific role. That means moving now on the 2022-and-later group and starting patient, work-first conversations with everyone who joined before then.
FAQ
How many people did Pipedrive lay off in 2026?
ERR reports 267 jobs cut in Estonia (219 in Tallinn and 48 in Tartu), about 70% of roughly 380 local staff. The Lisbon office of about 220 people is set to close, and developers in Berlin are affected. Pipedrive declined to confirm the local figures. It had nearly 800 employees worldwide before the cut.
When can laid-off Pipedrive engineers in Estonia start a new job?
It depends on tenure. Estonian notice periods are 15, 30, 60 or 90 calendar days for under one year, one to five years, five to ten years, and ten or more years of service. A collective redundancy also can't take effect until at least 30 days after the Unemployment Insurance Fund is notified. Recent hires can move first. Staff with five or more years will likely be free in early 2027, unless Pipedrive pays them in lieu of notice.
Is Pipedrive's Lisbon office closing?
Yes, according to Estonian World, which says the Lisbon office of about 220 people is set to close. In Refolk's index sample, most Lisbon profiles are in sales and customer success roles: SDRs, account executives, CSMs and support engineers. The timing follows Portuguese labour law, not Estonian law.
What should I search instead of "Pipedrive" to find its engineers?
Search for the stack and team names. For the stack, try TypeScript, Node.js, React, MySQL, Redis, Kafka, Docker and Kubernetes. For teams, try the Monetization, Billing, Spark and backend platform tribes, plus products like LeadBooster. In Refolk's index, only 56% of the Estonian profiles that mention Pipedrive currently work there, so the company name alone returns a lot of alumni and consultants.
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.
01Describe them
One plain sentence. Role, city, stack, stage, whatever matters to you.
02I read the web live
GitHub, public LinkedIn and Crunchbase records, the open web. Not a database that went stale last quarter.
03You read the shortlist
Ranked, with the reasoning under every name. Open a profile, ask a follow-up, narrow it down.
- Staff backend engineers in NYC who shipped Rust in production
- Series A fintechs in SF under 50 people, growing headcount this year
- Maintainers of fast-growing Rust web frameworks on GitHub
- 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.