Refolk
10 min readMarkdown

Fiserv Is Killing a Dozen Products. Bullet the Shutdown, Not the Loss

Fiserv is exiting a dozen products after 3,000 job cuts. How to put a cancelled project on your resume with real numbers and explain it in interviews.

If you built one of the dozen products Fiserv is exiting, your best recent work now describes something that may be gone by the time a recruiter reads about it. The problem is how the work is framed. Your record is fine, and the bullet can fix it.

On Fiserv's Nov 3 earnings call, new CEO Takis Georgakopoulos said the company has cut 3,000 employee and contractor roles since June. It is also exiting smaller products that fall short on performance, growth, or margin profile.

Fiserv cut products for margin, not because the work failed

Fiserv's stated reason for the exits is portfolio math: performance, growth, or margin profile. Nothing in that reason says the teams shipped bad work, so your resume shouldn't suggest they did.

Here's what the company has disclosed so far about the Fiserv layoffs in 2026:

  • 3,000 employee and contractor roles cut since June, including more than 10% of senior management.
  • Project Elevate's savings target doubled from $500 million to $1 billion, after activist investor Jana Partners pushed for $1.25 billion.
  • A $6.45 billion non-cash goodwill impairment in Q3. Adjusted operating margin was 31.2%, down from 37.0% a year earlier.
  • A split inside the merchant business. Clover processing revenue grew 12% while non-Clover SMB revenue fell 6%.

When margin drops about six points and an activist investor is tracking the savings, every product gets measured against the winners. PYMNTS described the products on the way out as having "limited customer adoption." A product can be well built and stable and still lose that comparison to Clover. Your team's execution didn't decide this. Portfolio math did.

One rule before you write anything: Fiserv has not named the products it plans to discontinue. Don't guess in your resume or in interviews, and don't let anyone draw you into guessing. Talk about your own product and leave the company's list alone.

3,000
Fiserv employee and contractor roles cut since June

Roughly 7.9% of the 38,000+ people Fiserv employed at the end of 2025, though the 3,000 includes contractors.

The phantom metric trap: which numbers you can still use

Use only numbers that were true on or before the shutdown date. Any metric that depends on the product continuing, like next-year retention, projected ARR, or full-rollout reach, is made up if the product never got there.

ResumePlot puts it bluntly: if a feature was cancelled before rollout, "any customer retention claim is fabricated." I call this the phantom metric problem. A phantom metric is a number that describes a future the product never reached. Hiring managers catch these because the math stops working once they ask one follow-up question.

The fix is to date your numbers. "Peak of [N] active merchants (Q2 2026)" reads as honest because it says when it was true. "Serving [N] merchants" in the present tense reads as a claim you can't back up.

Metric typeSafe when it's...Phantom when it's...
Users or merchantsPeak count measured before sunsetProjected to full rollout
Transaction volumeActual processed volumeAnnualized from a pilot week
Uptime or latencyPulled from production monitoringFrom a test environment only
RetentionMeasured on clients you migratedClaimed for a feature that never launched
RevenueBooked while the product was livePipeline the product "would have" closed

Start pulling these numbers now, while you can still reach the dashboards, the ticket history, and the people who ran the reports. That access is the first thing to go after a sunset.

Treat the shutdown itself as a deliverable

A sunset is a project with its own scope, deadline, and success metric. Client migrations, retention through cutover, contract wind-downs, and data decommissioning are all work you can measure, and most resumes leave them out.

PYMNTS reports that Fiserv intends to "transition away from or potentially exit" these products. "Transition away" means someone has to move clients onto something else without losing them. If that someone was you, these all count as results:

  • Client migration: accounts moved to a successor product, and the date you finished.
  • Retention through cutover: the percentage of migrated clients still active afterward.
  • Support load: ticket volume during the deprecation, and how you kept it down.
  • Decommissioning: infrastructure retired, data archived under retention rules, and cost removed.
  • Partner wind-down: contracts, integrations, or resellers closed out cleanly.

Here's a product discontinued resume bullet before and after:

  • Before: "Worked on [product], which was discontinued in 2026."
  • After: "Led migration of [N] merchant accounts from [product] to [successor] during Fiserv's 2026 non-core product exits, retaining [Y]% through cutover."

The second version is about something you finished, so it doesn't read as an apology.

The hard part is that one project now has two stories (what you built and how you wound it down), and different postings want different ones. A platform role wants the migration. A growth role wants the peak adoption. That rewriting is the work Refolk takes off you: it writes the resume from your own history, then tailors the bullets to each posting you paste in, so the right half of the story leads each time.

How to put a cancelled project on your resume

Keep it, name it, date it, and give the exit one short clause. If you leave it off, you get a gap, and a gap draws more questions than a dead product.

  1. Keep the real product name and dates. End the date range at the sunset or at your own exit, whichever came first.
  2. Lead with what you built and its as-of metric. The work comes first, the outcome second.
  3. State the exit reason in under ten words, using the company's words. "Product exited in 2026 portfolio review" is enough.
  4. Add a separate shutdown bullet if you ran or contributed to migration or wind-down work.
  5. Don't editorialize. Leave out "unfortunately," "despite strong results," and any suggestion that leadership got it wrong.

It also helps to know how ordinary this is. Cody Ogden's killedbygoogle.com tracks 299 products Google has retired since 2006, with an average lifespan of 5.2 years. A DEV Community post on cancelled projects makes the same point: describing a shutdown clearly and without blame "reads as maturity," while hiding it leaves a hole in your timeline that looks worse than the product dying.

The senior-seat math for laid-off fintech PMs

In Refolk's index of professional profiles, US financial-services companies employ 11,589 Product Managers and Senior PMs but only 597 product leaders at Director, VP, or Head of Product level. That's roughly 19 PMs for every leadership seat, which makes for a hard market for the more than 10% of Fiserv's senior managers who were cut.

19.4
US fintech PMs for every product-leadership seat

From Refolk's index of professional profiles, 11,589 PMs and Senior PMs against 597 Director, VP, and Head of Product titles.

SegmentCountWhat it means
US fintech PM + Sr PM11,589Baseline pool
India fintech PM + Sr PM8,819US pool is 1.31x India's
US fintech product leadership597About 4.9% of the PM pool
Fiserv cuts since June3,000~7.9% of year-end 2025 headcount (rough)
Fiserv senior management cut>10%Not broken out further

Treat the ratio as approximate. The leadership query used a different set of titles than the PM query, and the employer and title breakdowns below come from 25-profile samples, so they show direction, not exact shares.

That direction matters, though. In the US PM sample, the top current employers include Ramp, Brex, Capital One, Coinbase, and Nelnet. Fiserv isn't in the top 10. In the leadership sample, "Head of Product" accounts for 18 of 25 titles, at companies like Opto Investments, Early Warning, YNAB, and Parafin. Most of the senior seats are at smaller companies, not at large enterprises with layers of directors. The Indian pool clusters in Bengaluru and Mumbai, at employers like InCred, Dhan, Paytm, and Kotak Mahindra Bank.

So if you were a Fiserv director managing a large org, the role you can most realistically land is probably a Head of Product job at a company with one product and no VP layer. Your bullets need to show you can build from scratch, not that you've managed a large org.

Directors: frame the exit decision as capital allocation

If you recommended or carried out a product exit, that's the skill the market just rewarded. Fiserv's stock gained over 12% on Tuesday after the layoff news.

Part of the reason is who's running the company. Georgakopoulos was a partner at McKinsey & Company, according to Fiserv's 8-K, and investors are rewarding him for portfolio discipline: cutting what doesn't earn its keep and putting the money into what does, like Clover and Clover for Enterprise. Capital allocation is the decision about where a company's money and people go next. If you made one of those calls, write it in those terms.

  • Weak: "Managed portfolio of legacy merchant products."
  • Strong: "Recommended exit of [product] after [N]-quarter review of adoption and margin; reallocated [team size] engineers to [core product] and completed client transition by [date]."

For the Head of Product search, rewrite the scale bullets:

  • Swap "Led org of [N]" for the product you took from zero to its first [N] customers.
  • Swap "Owned $[X] portfolio" for one launch you scoped, priced, and shipped yourself.
  • Keep exactly one exit-decision bullet. It shows judgment, and startups need someone willing to kill a feature.
A product killed for margin is a capital decision. A bullet that hides it is a credibility decision.

Still inside Fiserv while your product's fate is unclear

If you're still employed and think your product could be on the exit list, start searching now, and do it quietly. Fiserv hasn't named the products, so nobody outside leadership knows how long their team has.

The context isn't reassuring. Fiserv employed more than 38,000 people at the end of 2025, and PYMNTS reports it's using AI to automate fraud reviews, customer service, and software development. The bind is familiar: you can't turn on an open-to-work banner when your VP is in your network, and every application that disappears into silence costs an evening you could have spent pulling metrics before the dashboards go dark.

How to explain a failed project in an interview

Tell it in three beats: the company's stated reason, what you shipped with dated numbers, and what you did during the wind-down. Keep the tone neutral and specific, and stop talking once you've covered the third beat.

  1. The reason, in the company's words. "Fiserv exited a set of smaller products that didn't fit its margin targets, and mine was one of them."
  2. What you shipped. "Before that, my team reached [N] merchants at peak and held [uptime] in production."
  3. What you did at the end. "I ran the migration to [successor] and kept [Y]% of clients."

What not to do:

  • Don't blame Georgakopoulos, Jana Partners, or the board.
  • Don't speculate about which other products are on the list.
  • Don't cite any metric dated after the shutdown.

The point the DEV Community post makes about the CV applies even more in conversation: a calm, blame-free account of a shutdown is a signal of seniority. Interviewers aren't checking whether your product survived. They're checking whether you can describe a bad outcome accurately.

Your cover letter needs the same one-sentence exit line you'll say out loud, and the two should match exactly, numbers included.

FAQ

What if the product was killed before it ever launched?

Then you can't claim adoption, retention, or revenue, because those numbers never existed. Use what did happen instead: the scope you defined, pilot or beta results with dates, technical milestones you hit, and any work you did to retire the code or reassign the team. ResumePlot's warning applies directly here: any retention claim for a feature that never rolled out is fabricated.

Can I say which Fiserv product I worked on?

Name your own product if you're allowed to, but don't connect it to Fiserv's exit list unless the company has publicly confirmed it. Fiserv hasn't disclosed which products it's discontinuing. Check your severance or separation agreement for confidentiality terms before you describe internal decisions in detail.

How do I mention being laid off after a product sunset?

In one plain sentence that uses the company's stated reason: your role was cut as part of Fiserv's 2026 restructuring, which included 3,000 roles and an exit from non-core products. Then move straight to what you shipped and what you did during the wind-down. Don't apologize. The more matter-of-fact you are, the less the interviewer focuses on it.

The data behind this

Put this to work

Paste your career in once. Every application after that is written for you.

Drop a resume or a LinkedIn URL. I rank the live openings against it, rewrite the resume and write a cover letter for the best of them, and fill in the employer's form when you press the button. You read, you decide what goes out.

  1. 01Drop your resume

    A PDF or a LinkedIn URL. About a minute, once.

  2. 02I rank the openings

    Every weekday morning, the live catalog scored against your history. Up to 20 worth your time, not two hundred links.

  3. 03Each one is written up

    Resume rewritten for the posting, a cover letter, a fit score. Press send, or let me fill in the form.

  • New matches ranked and written before you are up.
  • Every bullet stays inside what your history supports. Nothing invented.
  • Queued, submitted, interviewing, offer: one screen, not a spreadsheet.

Free, no card. Up to 25 applications sent a week, and nothing is sent until you say so.

Keep reading