Twilio Layoffs 2026: Communications & AI Cuts
Twilio has not announced a new mass layoff in 2026. The cuts already happened. Between September 2022 and June 2025 the company shed roughly four thousand employees across four formal rounds, a Communications-versus-Data restructuring, and the wind-down of multiple acquired groups. Q1 2026 earnings confirmed headcount is flat, margins are up, and the company is half the size it was at peak in 2022. The talent that left is now at Bandwidth, Sinch, Vonage, Plivo, Bird, Bland.ai, Retell, Vapi, ElevenLabs, AWS Connect, Microsoft Teams Phone, and a long tail of voice-AI agent startups.
Last updated: May 26, 2026
Mike Carter, KORE1. I am writing this one from the buyer chair, not the recruiter chair. I have run Twilio SMS for promo drops at Skullcandy, Electric Visual, and Hostsinger. I sat through the SendGrid renewal cycle for transactional email at ComplexCon. I argued with finance about the Segment seat-and-event pricing model at a portfolio brand right around the time Twilio was trying to talk every consumer brand into the customer data platform story. So when I say the Twilio talent picture in 2026 is more interesting than the Twilio layoff picture, that is somebody who has cut purchase orders to this company for ten years saying it. KORE1 places communications-platform, voice-AI, and developer talent through our IT staffing practice, and we earn a placement fee when companies hire from that bench. So read this with that lens.
The headline. Twilio in 2026 is not a fresh layoff story. It is a post-layoff story. The bloodletting ran from late 2022 through mid-2025 and the company that came out the other side is leaner, more focused on the Communications API, more aggressive about voice AI, and quieter about Segment than at any point since the 2020 acquisition closed. The recent reset cohort we wrote up in our 2026 tech layoffs roundup includes Twilio as a finished chapter rather than an active one. The closest analogs in tone are Stripe for the developer-platform shape and Adobe for the slow-burn SaaS reset, though neither maps cleanly.

What Twilio Actually Said in 2026
April 30, 2026 was the Q1 earnings call. Revenue $1.39 billion, up 20 percent year over year on a reported basis and 16 percent organic. Voice channel revenue up 20 percent, the sixth consecutive quarter of accelerating growth. Messaging up 25 percent on the back of WhatsApp and RCS traction. Operating margins expanded again. Free cash flow grew. The Motley Fool transcript and the StockStory deep dive both used the phrase “best quarter in three years,” and the financial press more or less agreed.
On the headcount question, CEO Khozema Shipchandler was explicit. Flat. The Q1 prepared remarks and the analyst Q&A both landed on the same message: headcount has been flat for two to three years, will continue flat, and the operating leverage from here comes from product mix and pricing rather than additional reductions. Twilio is not telegraphing another round.
What the company also said, less directly. Segment is finally inflecting. AI is the carrier wave for the Communications business, with named customer wins that landed in the prepared remarks: Bland.ai signed a multi-year deal for Messaging, Voice, Recordings, and Branded Calling. Scorpion’s AI agent built on Twilio drove a 39 percent booking-rate lift and $8.4 million of customer revenue. A historic professional sports league signed a seven-figure Verify contract. The Verify and ConversationRelay product lines are being pushed as the cross-sell motion for the sales org going forward.
What the company did not say. No new layoff. No new restructuring charge. No PIP guidance. No commentary on the Segment carve-out chatter that has been recurring in the activist press since the Anson Funds and Legion Partners pressure in 2023 and 2024. The silence on Segment is itself a signal. Boards usually telegraph divestiture timing in advance to avoid surprising the analysts.
The 2022 to 2025 Cuts, In Order
Twilio’s modern layoff story is four rounds plus a restructure. The shape matters.
| Date | Headcount Action | Approximate Scale | Stated Reason |
|---|---|---|---|
| Sept 2022 | Round one. Jeff Lawson letter. | ~900, 11 percent | “We hired too many people during the pandemic.” Path to profitability. |
| Feb 2023 | Round two. Org split into Communications and Data & Applications BUs. | ~1,500, 17 percent | Operational restructure. Sales-org compression. Segment management changes. |
| Dec 2023 | Round three. Activist pressure phase. | ~290, 5 percent | Anson Funds and Legion Partners proxy pressure. Concentrated in Data & Applications. |
| Jan 2024 | Jeff Lawson exit. Shipchandler steps in as CEO. | Founder departure | Board transition. Lawson out of CEO role and off the board. |
| June 2025 | Restructure. Two business units formalized. Quiet reductions inside the change. | Undisclosed; estimated several hundred | “We had gotten too big, especially in Communications.” Org clarity. |
| 2026 YTD | No new announced reduction. | Headcount flat per Q1 earnings | Shipchandler confirms steady-state staffing. |
Net effect. Peak headcount in 2022 sat around nine thousand. Current headcount sits in the mid-five-thousands. Roughly a forty percent reduction over thirty-three months, achieved across four formal rounds and one restructure. That is more workforce action than most of the public SaaS cohort and meaningfully more than Adobe, Salesforce, or ServiceNow have admitted to over the same window.
Two patterns worth noticing about the Twilio rounds specifically. First, the rounds skewed harder against Data & Applications than against Communications. Segment, Engage, and Flex absorbed disproportionate cuts even though the company kept saying the data platform was the future. Second, the geographic concentration was the Bay Area and Dublin, with later rounds reaching into Bangalore and Bogotá. The Denver headquarters (Twilio moved HQ from San Francisco to Denver in 2022 as part of the remote-first transition) carried the more durable Communications product engineering and absorbed proportionally fewer cuts.
Where the Displaced Twilio Talent Is
This is the operating question. Here is the destination map for the talent that left between 2022 and mid-2025, plus the smaller flow still moving out of Twilio quietly in 2026.
The CPaaS competitors
Bandwidth, Sinch, Vonage (now part of Ericsson), Plivo, and Bird (formerly MessageBird) have absorbed a meaningful share of the senior Twilio messaging and voice platform engineering bench. Bandwidth especially. The Raleigh, North Carolina footprint has been hiring aggressively across SIP infrastructure, number management, and the messaging API stack, and Bandwidth pays competitively for senior Twilio alumni. Sinch’s North American operation has done the same. Plivo runs leaner but has picked up several senior Twilio Voice engineers who wanted the smaller-company surface area. Bird, post-rebrand, has been quieter on the talent side but is still in the mix on the European bench.
Voice AI agent platforms
This is where the 2026 movement is happening, not in 2022 to 2025 layoff cohorts. Bland.ai, Retell, Vapi, ElevenLabs Conversational AI, Synthflow, and the broader voice-agent infrastructure tier have been picking off senior Twilio Voice engineers, ML practitioners on the IVR and speech side, and conversational-design product managers. The Bland.ai signed-deal disclosure on the Q1 call is telling. Bland.ai runs on Twilio infrastructure and still poached senior Twilio engineers for the agent-orchestration layer. The hyperscaler equivalents (AWS Connect, Amazon Pinpoint, Microsoft Teams Phone, Google Contact Center AI) have also been absorbing the senior conversational-AI bench, with Microsoft’s Teams Phone org the most active US-side hirer.
Contact center as a service
Five9, NICE CXone, Genesys, and Talkdesk on the CCaaS side. The Twilio Flex contact center product never reached the install base of the major CCaaS incumbents, and the senior Flex product and engineering bench has spread across that cohort. Five9 has been the most consistent buyer, with NICE picking up the senior practitioners who wanted to work on a more mature platform with deeper analytics.
Segment alumni and the CDP destination map
The Segment story is its own thing. The senior CDP engineering and product talent that left Segment after the Twilio acquisition (and especially after the December 2023 round) has mostly landed at three places. Snowflake and Databricks have absorbed the data-warehouse-native CDP talent that bought into the composable CDP thesis. Hightouch, Census, and RudderStack have absorbed the senior practitioners who specifically wanted to keep working on reverse ETL and event collection rather than move into broader data platform engineering. A smaller but real slice has gone to BigQuery and Microsoft Fabric on the platform-vendor side.
SendGrid alumni and the email cohort
SendGrid (acquired 2019 for $2 billion, now folded into Communications) has been more stable than Segment but has still shed senior engineering and customer-success talent to the email-platform tier. Postmark, Mailgun, Resend, Customer.io, and Klaviyo (on the marketing-automation overlap) have absorbed most of the senior email-delivery and transactional-messaging practitioners. Resend in particular has hired a meaningful slice of the senior SendGrid bench in 2025 and 2026.
The unified communications and adjacent enterprise tier
RingCentral, Zoom Phone, 8×8, and Webex on the unified-comms side. Some senior Twilio practitioners with telecom-industry roots have landed in this tier, especially those who wanted to work closer to the BYOC and enterprise voice side of the market. It is a smaller flow than the CPaaS-direct or voice-AI destinations, but it shows up consistently in the candidate side.

Twilio Compensation in 2026
If you are trying to hire Twilio-trained talent or figure out what to ask for, the bands matter. Levels.fyi data updated through May 2026, cross-checked against Blind and against what the desk sees on closed offers.
| Level | Role | Twilio Total Comp Range | Bandwidth Equivalent (reference) |
|---|---|---|---|
| IC1 (entry) | Software Engineer, 0–2 yrs | $145K – $175K | $120K – $155K |
| IC2 | Engineer II, 2–4 yrs | $195K – $235K | $155K – $195K |
| IC3 | Senior Engineer, 4–7 yrs | $255K – $345K (median ~$291K) | $210K – $280K |
| IC4 | Staff Engineer | $405K – $560K (median ~$482K) | $310K – $410K |
| IC5 | Senior Staff Engineer | $490K – $775K (median ~$686K) | $420K – $580K |
| IC6 | Principal / Distinguished | $700K – $900K+ | Limited public data |
Two things to pull from the table.
The IC3 senior delta against the CPaaS competitor cohort sits in the $40K to $80K total-comp range. That is meaningful but bridgeable on a base-and-bonus restructure for a senior who wants out. Bandwidth and Sinch typically close the cash gap on the base side and accept a smaller equity component because the public-market story for both companies has been thinner than Twilio’s. A senior who values cash predictability over equity upside ends up indifferent at the IC3 level.
At IC4 and above the math shifts. Twilio still pays at the high SaaS engineering level, and the CPaaS competitors have a hard ceiling that sits roughly $150K to $200K below Twilio for the equivalent staff-and-principal band. That is why the senior Twilio platform talent at IC5 and IC6 rarely lateral-moves to Bandwidth or Sinch. They go to voice-AI startups with equity asymmetry, to Stripe or Block or Datadog for the broader developer-platform compensation peer set, or to AWS and Microsoft for the predictable big-tech bands. For a deeper comp lookup across the broader senior engineering bench, our salary benchmark assistant covers the IC3 and IC4 ranges for senior platform engineer, senior backend engineer, and senior infrastructure engineer in the relevant US metros.
The BLS figure for software developers nationally sits around $132K median per the BLS May 2024 OES data. Twilio’s IC1 band runs above that. The IC3 senior median is more than double. SaaS and developer-platform compensation has its own gravity and the BLS numbers rarely catch the high end cleanly.
The Acquired-Company Pattern
Twilio has been an aggressive acquirer. The pattern across the major acquisitions is worth sitting with because most of the post-2022 attrition has concentrated in those groups.
Segment. Acquired November 2020 for $3.2 billion in all-stock. The biggest acquisition Twilio has ever done. Folded into what became the Data & Applications business unit. Activist Anson Funds called publicly for the carve-out in February 2024. Shipchandler in early 2024 acknowledged Segment was “not performing at the level it needs to” and put a Q2 2025 break-even target on the table. Segment hit that mark, but the broader composable CDP thesis (Snowflake, Databricks, plus reverse-ETL tools sitting on top) has continued to eat into the use case Segment was built for. The senior Segment product and engineering bench has thinned steadily through 2024 and 2025. The remaining Segment org has stabilized, but its strategic future inside Twilio is still genuinely an open question.
SendGrid. Acquired February 2019 for $2 billion in stock. Email API and transactional messaging. The integration has been one of the cleaner Twilio acquisitions. SendGrid sits inside Communications now and the product roadmap has continued. Some senior engineering talent has left for Resend and the newer email-platform cohort, but the wind-down dynamic that hit Segment has not hit SendGrid the same way. Most of the senior practitioners who are still inside are still building.
Zipwhip. Acquired July 2021 for $850 million. Toll-free messaging. Folded into Communications and quietly absorbed. Most of the senior Zipwhip product and engineering bench has cycled out by 2026, with a meaningful share going to Bandwidth (also Raleigh-area for the East Coast component) and to the broader CPaaS competitive set. Zipwhip is the acquired-company integration that worked technically but lost the original team almost entirely.
ValueFirst. Acquired 2021 for the India SMS aggregation business. Quieter still. The integration has been smoother on the India side and most of the senior ValueFirst bench has stayed inside Twilio India.
If you are looking at a candidate from one of these groups in 2026, especially Segment or Zipwhip, you are usually looking at a senior practitioner with deep platform expertise, real production experience at scale, and a sober view of what acquired-product integration actually looks like inside a public SaaS company. That last attribute is more valuable than the resume usually conveys.

Geographic Picture
Twilio moved its corporate headquarters from San Francisco to Denver in 2022 as part of the remote-first transition. That move mattered for the talent map.
Denver is the durable Twilio engineering center now. The Communications platform engineering bench, the core Voice and Messaging product orgs, and the Verify and Branded Calling product engineering all carry the Denver center of gravity. Denver also absorbed less of the 2022-2025 layoff impact than San Francisco or Dublin. The senior Twilio engineers we have placed out of Denver in the last twelve months have mostly stayed local, moving to Splunk’s local engineering org, to Comcast Advertising, to the small Bay-Area-transplant cohort of cloud-native startups in the Denver and Boulder corridor, and back into the local enterprise IT bench. Our IT staffing practice covers the Denver-Boulder corridor through the same recruiter team that handles the broader West region.
San Francisco still carries a meaningful Twilio engineering footprint, but the Bay Area absorbed the heaviest cuts across all four rounds. The displaced senior bench from SF has mostly stayed in the Bay (Stripe, Block, Databricks, Snowflake, Datadog, the voice-AI startup cohort centered around the Mission and SOMA) or moved south to Mountain View and Sunnyvale at AWS, Google, and Microsoft. A smaller flow has left the Bay entirely for Seattle and Austin.
Dublin was hit harder than most North American sites and has been quieter to recover. Twilio’s Dublin engineering and customer-operations footprint shed proportionally more in the 2022 and 2023 rounds. Some of that bench moved to the local Stripe and Intercom offices, some to Workday Dublin, and some to the messaging-platform competitors with European footprints.
Bogotá has been a quieter buildout in the last three years. The Latin American engineering footprint absorbed work as the Bay Area shrank, and senior Spanish-bilingual platform engineers in Bogotá have been a real cost arbitrage advantage for Twilio against the US-only CPaaS competitors. The senior bench there is mostly still inside the company.
Bangalore. The India footprint is large enough that the 2023 and 2025 rounds were visible but did not gut the office. Most of the displaced India bench cycled into Salesforce India, Microsoft India, Google, and into the Indian voice-AI agent startup tier (which is growing faster than the press coverage suggests).
If You’re Hiring CPaaS or Voice AI Talent in 2026
A few operating notes the desk has been running with on this category. Argue if you disagree.
The senior Twilio platform engineering bench (Communications API, Voice, Messaging, Verify, Number Management) is the most underpriced developer-infrastructure talent in 2026. Most of the senior engineers who built the core Communications stack have either stayed inside Twilio through all four rounds (and earn their loyalty premium) or have already moved to Bandwidth, Sinch, Stripe, or the voice-AI cohort. The middle band, IC3 to IC4 with three-to-six years at Twilio, is the gettable senior tier. They know the SIP, RTC, and PSTN integration territory deeply, have worked through real reliability incidents in production, and the cash gap against most enterprise SaaS buyers in 2026 is bridgeable. For the broader senior backend bench, our software engineer staffing and DevOps engineer staffing teams work this cohort across Denver, the Bay Area, Austin, and Atlanta.
For voice-AI agent companies specifically, the Twilio Voice and Verify engineering bench is the right target. Conversational design product managers from the Twilio Flex and Studio orgs are also in the mix. The skill set translates directly. Most of the candidates already understand SIP trunking, real-time media routing, and the call-state-machine reliability problem in a way that voice-AI startups need but rarely hire directly. If you are running a Bland.ai or Retell or Vapi competitor, this is the bench. Our AI and ML staffing team works the conversational AI and voice AI engineering bench through the same Bay Area, Denver, and Austin pipelines.
For data and CDP roles specifically, Segment alumni are still in market and most are willing to talk. The Segment senior engineering and product bench knows event collection, identity resolution, and the reverse-ETL integration territory at production scale. Most of them have re-anchored at Snowflake, Databricks, Hightouch, Census, or RudderStack already, but a meaningful share are still inside Twilio waiting for the right exit, and another slice landed in roles that are not turning out the way they hoped. Move on those candidates within four to eight weeks of first contact. The window closes fast once they re-anchor.
If you are hiring SendGrid alumni specifically for transactional email, the senior delivery and deliverability practitioner bench is small, valuable, and concentrated in Denver and Atlanta. The same goes for the senior abuse and compliance practitioners. This is one of the smaller talent pools in developer infrastructure and the practitioners who know it well are hard to replace once you let one go.
For broader cloud-native and developer-platform hiring, our cloud engineer staffing page covers the senior AWS and GCP bench that overlaps with the Twilio platform engineering profile. Most senior Twilio platform engineers have meaningful AWS expertise from the production side of the Communications platform.

Common Questions
Did Twilio lay off employees in 2026?
No new announced layoff in 2026 year to date. Q1 2026 earnings on April 30 confirmed flat headcount and the CEO commentary signaled steady-state staffing going forward.
The cuts already happened. Four formal rounds between September 2022 and December 2023 plus a June 2025 restructure took Twilio from roughly nine thousand employees at peak to the mid-five-thousands today. That is a forty percent reduction over thirty-three months, completed before 2026 started.
Why did Jeff Lawson step down?
Activist pressure plus board-level disagreement on the Segment investment. Lawson exited the CEO role in January 2024 after the December 2023 round of layoffs and shortly after Anson Funds and Legion Partners filed proxy materials calling for strategic changes.
Khozema Shipchandler, the CFO at the time, stepped in as CEO. The transition turned out to be the right move from a market perspective. The “Kho Effect” framing in the financial press is doing a lot of work, but it is also fair. Operating discipline, margin expansion, and the AI carrier-wave story for Communications have all landed under Shipchandler in a way that was harder to read when Lawson was still in seat.
What is happening with Segment in 2026?
Segment hit its Q2 2025 non-GAAP break-even target and has stabilized inside the Data & Applications business unit. The strategic question of whether Segment stays inside Twilio or eventually gets carved out is still genuinely open.
The composable CDP cohort (Snowflake and Databricks as data warehouses, plus Hightouch, Census, and RudderStack as the activation layer) has continued to eat at Segment’s original use case. Most large enterprise data teams in 2026 are not buying Segment as the central CDP anymore. The Twilio strategic line is that Segment plus the Communications platform is uniquely positioned for AI-era customer engagement. The market has not fully bought that story yet, and the Q4 2024 Segment revenue softness suggests there is more work ahead.
Where are Twilio voice engineers going?
Voice AI agent platforms first. Bland.ai, Retell, Vapi, ElevenLabs, Synthflow, plus the hyperscaler contact-center products at AWS and Microsoft. CPaaS competitors second, with Bandwidth and Sinch leading. CCaaS incumbents (Five9, NICE, Genesys) third.
The skill-set translation is cleanest into the voice-AI agent tier, because the production telephony reliability work transfers almost directly. The economic translation is best into the hyperscaler products, because AWS Connect and Microsoft Teams Phone pay competitively at the senior level without the equity volatility of an early-stage voice-AI startup.
How much does a senior Twilio engineer make in 2026?
IC3 senior engineers cluster around $291K total comp median, with a range of roughly $255K to $345K depending on level, location, and equity vest year. Staff (IC4) sits in the $405K to $560K band, median around $482K.
Senior staff (IC5) at Twilio reaches the $490K to $775K range with the median around $686K. Principal (IC6) clears $700K and runs north of $900K at the top of the band. The high end of the Twilio comp curve is meaningfully better than the CPaaS competitor set and roughly competitive with Stripe, Datadog, and the senior developer-platform tier.
Is Twilio still hiring in 2026?
Selectively. The careers site has been listing several hundred open roles throughout 2026, concentrated in Communications platform engineering, Verify, ConversationRelay, and AI-product roles tied to the voice-agent infrastructure narrative.
Headcount is flat at the company level, which means most external hires are net-of-attrition replacements rather than expansion. The growth roles are real but narrow. The Verify and ConversationRelay product orgs have been hiring most consistently, with the Segment side substantially quieter than the Communications side.
Should I take a Twilio offer in 2026?
Group-dependent. A Communications platform offer at IC3 or IC4 in Denver is one of the better landing spots in developer infrastructure in 2026, especially if the vest is fresh and the role is on the Voice, Verify, or Branded Calling roadmap.
Segment is harder to recommend, even though the org has stabilized, because the strategic future inside Twilio is still uncertain enough that the equity story carries real downside risk. A SendGrid offer in the email-platform engineering bench is reasonable but not exciting. A Flex offer is a hard sell because the contact-center business unit is the most exposed to the voice-AI disruption that Twilio is otherwise riding.
Is Twilio losing the voice AI agent market to Bland.ai and Retell?
Twilio is the infrastructure layer underneath most of them, including Bland.ai which signed a multi-year deal disclosed on the Q1 2026 call. The agent-orchestration layer above is where Bland.ai, Retell, Vapi, and the rest are competing, and Twilio does not have a fully credible orchestration product yet.
The honest read in 2026 is that Twilio is winning the telephony-infrastructure-for-AI-agents story and losing (or at least not winning) the AI-agent-platform story above it. ConversationRelay is the bet that the orchestration layer can be built natively on Twilio. The voice-AI startup cohort is the bet that an independent platform wins. It is too early to call either side. The talent flow suggests both bets have credible teams.
Working the Twilio-Adjacent Bench With KORE1
For hiring managers working a search adjacent to the Twilio stack (Communications API engineering, Voice, Messaging, Verify, SendGrid email, Flex, Segment CDP, or the voice-AI agent orchestration tier), the bench in 2026 is deeper, quieter, and better-trained than at any point in the last five years. Most of the senior candidates who are open to a conversation are not on a job board. They are inside Twilio, watching the Bland.ai and Retell deals close, doing the comp math against Stripe and the voice-AI startup tier, and waiting for the right reason to take a recruiter call. Talk to our team and we will walk you through which Twilio-adjacent profiles are actually movable this quarter versus what the LinkedIn signal and the Blind chatter imply.
If you are a Twilio employee reading this, the destinations we are placing this category into are listed above. A quiet message gets a quiet response. We work both sides of the desk and we do not market candidates without permission.
The 17-day average time-to-hire we publish across our practice runs about 22 days on the senior CPaaS and voice-AI engineering bench. That is the honest number for this category. The 17 average covers everything we place across IT, engineering, finance, healthcare IT, biomedical, creative, HR, and light industrial. Communications platform engineering is one of the slower categories because the candidates are passive, the loop usually includes a real systems-design exercise, and the senior practitioners are choosier about the next move after surviving four rounds of layoffs at the previous employer.
