# Fiserv Is Exiting 12+ Products. How to Put Killed Work on Your Resume

_Fiserv is exiting 12+ products and Dropbox wound down FormSwift. How to write resume bullets for a discontinued product so they read as results, not failure._

- Canonical URL: https://www.refolk.ai/candidates/blog/fiserv-product-exits-discontinued-product-on-resume
- Published: 2026-11-20
- Reading time: 11 min
- Keywords: discontinued product on resume, how to list cancelled project on resume, Fiserv layoffs 2026, resume bullets for sunset product, laid off after product shutdown resume

If your best recent work was on a product your employer just killed, your resume now has to explain a shutdown you didn't cause. Most people write that part like an apology, and it doesn't need one.

A lot of people are in that spot right now. On its Nov. 3 earnings call, Fiserv said it had cut 3,000 employee and contractor roles since June and plans to exit more than a dozen non-core products. Days earlier, on Oct. 28, Dropbox announced it would cut about 9% of its workforce, after finishing the FormSwift wind-down at the end of the third quarter.

## Why a killed product isn't a failed project

A killed product is usually a portfolio decision, not a verdict on the people who built it. Fiserv said it would exit products that don't meet its expectations for "performance, growth or margins," so a product can make money and still get cut.

A **non-core product** is one the company has decided doesn't fit where it wants to grow, whether or not it's profitable. Fiserv's own history shows how far apart those two questions are. Its former CEO described the education unit it sold as a "very good business, but not strategic to what we do overall."

The pressure behind this round is financial. Under Takis Georgakopoulos, CEO since June 2026, Fiserv's Project Elevate savings target doubled from $500M to $1B, after activist fund Jana Partners pushed for $1.25B. A bigger savings target leaves less room for products that are fine but not central. A product can miss the bar without anything about the product changing.

The scale is large:

- 3,000 employee and contractor roles cut since June
- More than 10% of senior management included in that number
- About 7.9% of Fiserv's 38,000+ employees at the end of 2025 (the 3,000 also counts contractors, so the real share of employees is somewhat lower)
- More than a dozen products marked for exit

These cuts are public and they're big. Don't write a bullet that suggests the product died because of you.

## How to list a cancelled project on your resume: the three-part bullet

Describe a discontinued product the way the company would: what the product delivered, what the wind-down delivered, and one short line on why the business stopped. The results go first, and the shutdown gets a few words at the end.

The three parts:

1. **What it delivered while it ran.** State results in absolute terms: users, transaction volume, uptime, revenue you're allowed to share.
2. **What you delivered as it closed.** Migrations, retained customers, retired infrastructure. (More on this below.)
3. **Why the business stopped, in one short phrase.** "Portfolio consolidation" or "product exited in 2026 restructuring." No adjectives, and no "unfortunately."

Here's the difference in practice (brackets are where your real numbers go):

| Version | Bullet |
|---|---|
| Apologetic | Worked on merchant gateway until it was sunset as part of company restructuring. |
| Three-part | Built and ran a merchant payment gateway serving [N] small businesses at [X]% uptime; moved [N]% of them to [replacement product] before the 2026 product exit (portfolio consolidation). |
| Over-explained | Led gateway that leadership deprioritized due to margin concerns despite strong growth. |

The first version spends the bullet on the ending. The third one argues with your old employer's strategy, and that's a red flag to anyone deciding whether to hire you. The middle one reports results and leaves the reader to draw the obvious conclusion.

A developer on DEV put it plainly: "The outcome was cancelled. The work was not undone."

> The product was cut on a spreadsheet. Your bullet should read like a results line on that same spreadsheet.

## The wind-down is a result you can claim

Shutting a product down cleanly is measurable work, and consolidation is what companies are paying for right now. If you moved customers off the product, turned off its systems, or retired its data, that's an accomplishment with numbers attached. It may also fit a current job posting better than the original build does.

Dropbox shows how closely the shutdown itself gets tracked. Its Q3 2026 earnings release names the quarter the FormSwift wind-down finished and the dollar impact:

> **$10.4M** Quarter-over-quarter ARR drop Dropbox attributed to finishing the FormSwift wind-down
>
> Dropbox's earnings release names the exact quarter the shutdown was completed: the end of Q3 2026.

If investors track the shutdown that closely, the people who carried it out should put it on their resumes. Wind-down work gives you numbers like these:

- **Customers migrated or kept**, moved to another plan or a replacement product
- **Support volume handled** during the shutdown period, and how fast tickets were resolved
- **Infrastructure cost removed** by shutting off services, contracts, and environments
- **Data retired on schedule**, including retention and compliance deadlines met
- **People and knowledge transferred**, such as runbooks written and teams onboarded onto other systems

Fiserv's consolidation is this same kind of work on a bigger scale. The company has reduced its core banking platforms from 16 to five. Flagstar Bank, with $88 billion in assets, is moving to Finxact, replacing both a Fiserv legacy core and a competitor's core. Each of those moves is a migration project with a start date, an end date, and a count of accounts moved. If you worked on one, you have a consolidation bullet that fits core-modernization roles directly.

Get those numbers before you lose access. Dashboards and ticket queues often go away along with your laptop, even when the severance is generous (Dropbox is offering 16 weeks of pay plus one week for each completed year). Note the figures you'll be allowed to use, such as counts, percentages, and dates, while you can still check them.

## Report your results "excluding FormSwift"

Put the skill and system that transfer to the next job first, and mention the discontinued product in parentheses. That's how companies report their own numbers after cutting something.

Every quarter, Dropbox reports its numbers with the dead product removed: excluding FormSwift, ARR grew $4.7M in Q3 2026. Investors get the underlying trend without the shutdown in the way. Your resume can do the same. Lead with "payments reconciliation at [N] transactions a day" or "core banking data migration" and put "(FormSwift, wound down 2026)" or "(Fiserv product, exited 2026)" at the end.

Which skill goes first depends on the job you're applying for:

- For a **payments engineering** role, lead with transaction volume and reliability.
- For a **platform or migration** role, lead with the wind-down and cutover.
- For a **product management** role, lead with the adoption you drove and the decision you made about retiring the product.

That means one killed product can produce three different bullets for three different applications, and rewriting them every time is tedious. [Refolk](https://www.refolk.ai/candidates) does that rewriting for you: paste the posting and get your own resume back with the relevant part of your history first, and the shutdown kept as context, not the headline.

## Spell out the product: what Refolk's index shows about keyword matching

Write out your employer's full name and describe what the product did in plain words. Keyword search is looser than most people expect, and internal product names mean nothing to anyone outside the company.

I searched Refolk's index of professional profiles for "fiserv" in the headline. Here's what came back:

| Slice (headline contains "fiserv") | Profiles |
|---|---|
| United States, all industries | 16,186 |
| United States, Financial Services only | 1,096 |
| Share of US matches in Financial Services | 6.8% |
| India, all industries | 27,409 (mostly "Finserv" firms) |

> **6.8%** Share of US "fiserv" headline matches that fall in Financial Services
>
> In Refolk's index, only 1,096 of 16,186 US matches survive an industry filter. The unfiltered result mixes in unrelated companies.

Fiserv was still the most common current employer in both US results, at 7 and 6 of the top 10 entries. But the India result was dominated by Bajaj Finserv, Wise Finserv, Satin Finserv and InPrime Finserv, and the unfiltered US result included companies that have nothing to do with Fiserv. The matching is just comparing letters. If a keyword search can confuse Fiserv with Finserv, it can just as easily miss you when your resume uses an internal name.

What that means for your resume:

- **Write the full company name.** Don't abbreviate it, and don't count on a logo to identify it.
- **Say what the product did in plain words.** "Merchant payment gateway" or "student loan servicing platform" gets matched. An internal codename gets matched to nothing.
- **Add the category term used in job postings**, such as "core banking," "card issuing," or "e-signature." A recruiter who never heard of FormSwift still knows what document automation is.

## Sold is not shut down

If your product was sold, say so and name the buyer. A sale shows someone else paid for what you built. Not every exit is a shutdown, and the wording should match what actually happened.

Fiserv's exits before November show the range. In Q2 it decided to divest its student loan servicing and managed ATM businesses, and to exit the unprofitable SMB and fuel segments of its merchant business in India. Each kind of exit gets its own phrasing:

| What happened | Example | How to phrase it |
|---|---|---|
| Shut down | FormSwift at Dropbox | "Product wound down in Q3 2026; led customer migration" |
| Sold to another company | Fiserv student loan servicing, managed ATM | "Business divested to [buyer]" |
| Market segment exited | Fiserv merchant SMB and fuel in India | "Segment exited in 2026 market refocus" |
| Merged into fewer platforms | Fiserv cores, 16 to five | "Consolidated onto [platform]; retired legacy system" |

"Divested to [buyer]" is about the best ending a product can have on a resume. It means the product still runs, under a new owner who paid for it. If you worked on a sold business, don't describe it as discontinued.

## What to leave off when writing about a cancelled project

Describe what you built and what it achieved, and leave out the internal financials and strategy behind the decision to cut it. The fastest way to lose an offer over a killed product is to share too much about it.

On Blind, a Microsoft PM asked how to list a scrapped project. One reply was blunt: "nothing would disqualify you faster than sharing previous employer's confidential information." A cancelled product is especially tempting here because it feels like nobody needs the secrets anymore. Your former employer doesn't see it that way.

Don't include:

- **Non-public revenue or margin figures.** Use percentages, ranges, or operating metrics like volume and uptime when the dollar figures weren't published.
- **Unreleased roadmaps** or features that never shipped
- **Your theory of why leadership killed it.** The company's public reason is enough.
- **Customer names** covered by contracts or NDAs
- **Anything that criticizes the decision.** Hiring managers assume you'll say the same about them someday.

The harder problem is that many people reading this are still employed, working on a product that might be on the exit list, with no announcement date. Fiserv has said more than a dozen products are going. Putting "open to work" on your profile in that situation tells your current manager you're leaving, and every cold application you send goes into the same pile as thousands of people who just lost their jobs.

## Where killed-product experience lands next

Aim your killed-product experience at the products companies are putting money into now. The clearest sign of where that money is going comes from Fiserv itself.

While it cuts more than a dozen products, Fiserv is investing in Finxact and Clover. What you learned running a legacy core, a merchant gateway, or an ATM network carries over to the teams modernizing those same systems, at Fiserv and at its competitors. Experience retiring a platform is just as useful to a bank like Flagstar, which is moving off two cores at once.

Dropbox's cuts point the same way. About 200 roles went across Engineering, Product, Design, and G&A, so the people looking for work now include designers and operators along with engineers. A designer who built the exit flow for departing customers has a retention story. An operator who closed out vendor contracts has a cost story. Neither one depends on the product still existing.

Before you send fifty applications, check which postings actually match what you did. Refolk scores how well you fit each posting against your real history, so you can spend your best applications on the core-modernization or payments roles where your experience is clearly relevant, instead of stretching it to fit everything.

## FAQ

### Should I put a discontinued product on my resume at all?

Yes, if it's where your best recent work happened. Leaving it out creates an unexplained gap or a thin bullet, and it throws away your strongest evidence. List the product's results, add what you did during the wind-down if you were involved, and end with a short note on the shutdown. "Product exited in 2026 portfolio consolidation" is enough context.

### How do I write resume bullets for a cancelled project that never launched?

Write about what you shipped inside the company and what the work made possible: prototypes tested, integrations built, research that changed the roadmap, infrastructure other teams adopted. Stick to things you could describe in an interview without giving away confidential details. Avoid unreleased feature names, and describe the product by its category ("document automation tool") rather than its codename.

### Can I use revenue numbers from a product that was shut down?

Only if they were public or your employer has cleared them. Dropbox publishing the $10.4M FormSwift ARR impact makes that figure public. An internal dashboard number doesn't become public just because the product is gone. When you're unsure, use operating metrics like transaction volume, customer counts, uptime, or percentage growth.

### How do I explain being laid off after a product shutdown in an interview?

Give the company's public reason in one sentence, then move on to what you built and how you handled the exit. Something like: "Fiserv exited more than a dozen products in its 2026 restructuring, and mine was one of them. I spent the last quarter migrating our customers onto the replacement platform." That answer is accurate, puts the decision on the business, and spends most of its words on your results.

---

_From the Refolk job search blog. More posts: https://www.refolk.ai/candidates/blog/index.md_
