What MongoDB Employees Should Know About Their 2026 Severance Package

When a company cuts hundreds of jobs at once, affected workers face an overwhelming stack of decisions in a compressed window. Federal law does not require private employers to pay severance at all. What it does require is advance notice of mass layoffs and, for workers 40 and older, specific review periods before any legal waiver can take effect. Knowing which protections are statutory (and therefore non-negotiable) versus which terms are discretionary (and therefore worth pushing on) is the difference between signing under pressure and signing with clarity.

To see what this looks like in practice, take Priya, a senior software engineer at MongoDB earning $185,000 per year. Priya is 43, based in New York, and received notice on June 9, 2026 that her role is being eliminated. She has a severance agreement sitting in her inbox. The rest of this guide walks through what Priya can verify, what she can negotiate, and what deadlines actually bind her.

What did MongoDB disclose about the June 2026 layoff?

MongoDB announced approximately 350 role cuts on June 9, 2026. The layoff was reported across industry trackers, and the company confirmed the reduction publicly. MongoDB has not disclosed the percentage of its workforce affected, the specific severance multiplier, or the sites where roles were eliminated.

Because MongoDB has not filed a public SEC Form 8-K Item 2.05 (or if one exists, it has not surfaced in public-record databases as of this writing), Low confidence the details below rely on what federal and state law guarantee rather than on company-specific filings. The public-record source for the layoff event is Crunchbase's tech-layoff tracker.

Does the federal WARN Act apply to a 350-person layoff?

The Worker Adjustment and Retraining Notification Act applies to employers with 100 or more full-time workers.[1] A "mass layoff" under the statute means a reduction of 500 or more employees at a single site, or a reduction of 50 to 499 employees if those employees make up at least 33% of the active workforce at that site.[1] A "plant closing" trigger is lower: 50 or more employees losing jobs at a single site within a 30-day window.[1]

MongoDB employs well over 100 full-time workers, so the company-level threshold is met. Whether the 350 cuts trigger WARN obligations depends on how many employees were cut at each individual site. If 50 to 499 roles were cut at any one site and those workers make up at least 33% of that site's active workforce, the 60-day notice requirement applies. It also applies at any site losing 500 or more workers, regardless of that percentage.[1]

When an employer fails to provide the required 60 calendar days of notice, affected employees are entitled to back pay and benefits for each day of the violation, up to 60 days.[2] Back pay is calculated at the higher of the employee's average regular rate or final regular rate over the preceding three years.[2]

Which state mini-WARN laws could give MongoDB workers extra protection?

Several states impose stricter layoff-notice requirements than the federal WARN Act. MongoDB's headquarters is in New York City, and the company has had offices in other states with mini-WARN statutes. The table below covers the states most commonly relevant to large tech employers. Note: MongoDB has not disclosed which sites were affected, so workers should check whether their own work location falls in a state with additional protections.

Low confidence The table above is compiled from state legislative texts. MongoDB's specific office locations and affected sites have not been publicly confirmed, so workers should verify their own state's rules by checking their state labor department website or consulting the DOL's WARN resource page.[3]

New Jersey's mini-WARN law is worth particular attention only if you worked at a New Jersey location. It is one of the few state statutes that mandates severance pay, but the obligation triggers only when specific conditions are met: the employer has 100 or more full-time employees and the layoff is a covered mass-layoff or termination event.[4] For a covered event, the statute requires one week of severance pay per full year of service. If the employer fails to give the required notice, it owes an additional week of severance on top of that.[4] If you worked at a New Jersey site that meets these thresholds, treat the statutory amount as a floor. You are entitled to the greater of the state minimum or what the company's agreement offers.

How does OWBPA affect the timeline for MongoDB workers 40 and older?

The Older Workers Benefit Protection Act, codified at 29 U.S.C. § 626(f), sets minimum requirements for any waiver of age-discrimination claims in a severance agreement.[5] Because this layoff involved a group termination (multiple employees), the OWBPA rules for group programs apply:

• 45-day consideration period. Employees 40 and older in a group layoff must receive at least 45 calendar days to review the severance agreement before signing.[5] An employer cannot shorten this window, even if the employee wants to sign sooner.
• 7-day revocation period. After signing, the employee has 7 calendar days to revoke the agreement. The waiver does not become effective until the revocation period expires.[5]
• Decisional unit disclosure. The employer must provide, in writing, the job titles and ages of all individuals in the "decisional unit" who were selected and not selected for the layoff.[5] Priya should verify that MongoDB's agreement includes this disclosure.

For individual (non-group) terminations, the consideration period is 21 days instead of 45.[5] Whether MongoDB classifies its 350-person reduction as a "group" program determines which timeline applies. A reduction of 350 roles almost certainly qualifies as a group termination, which means the 45-day window applies.

The EEOC's historical guidance on OWBPA confirms that a waiver must be "knowing and voluntary" and that the employee must be advised in writing to consult an attorney.[6]

How does severance pay interact with unemployment insurance?

Severance pay's effect on unemployment benefits varies by state. Two examples illustrate the range:

California: The California Employment Development Department generally does not reduce unemployment benefits because of a lump-sum severance payment, provided the payment is not allocated to a specific period of employment.[7] If Priya worked in California, she could file for unemployment immediately after her last day and collect benefits alongside her severance.

Rhode Island: Rhode Island regulations treat severance that is allocated week-by-week as disqualifying wages for the corresponding weeks.[8] A lump-sum payment that is not tied to specific weeks does not reduce benefits under the same regulation.[8]

The structure of the severance payment, whether lump sum or salary continuation, matters more than the dollar amount. MongoDB employees should check their state's unemployment agency website before choosing a payout structure. Workers in New York should consult the NY DOL's guidance on severance and UI eligibility, as New York treats continuing severance payments differently from lump-sum payouts.

What terms can a departing MongoDB employee negotiate?

Federal law does not require private employers to pay severance, so the package is a contractual offer and many terms in the agreement are open to negotiation. Low confidence Common terms worth discussing include:

• Cash multiple. Industry convention for tech companies is one to four weeks of base pay per year of service, but there is no legal floor. MongoDB has not disclosed its formula.
• COBRA subsidy. Employers can offer to pay the employee's COBRA premiums for a defined period. COBRA coverage itself lasts up to 18 months after a qualifying event, but the subsidy period is negotiable.
• Equity treatment. If Priya has unvested restricted stock units (RSUs), the agreement may address whether any additional vesting occurs. Acceleration of vesting beyond what the plan document already provides is entirely negotiable.
• Reference language. A neutral reference letter or agreed-upon language for future employers is a common ask that costs the company nothing.
• Non-compete and non-solicitation scope. Some agreements include restrictive covenants. The enforceability of non-competes varies by state. The NLRB has ruled that employers may not offer severance agreements that impose overly broad confidentiality or non-disparagement provisions that interfere with employee rights under the National Labor Relations Act.[10]
• Outplacement services. Companies sometimes offer career coaching or job-placement support. The value of these services varies widely.

Workers should also look for a severance tax calculator to estimate the after-tax value of any cash component before agreeing to a number.

What concrete steps should MongoDB employees take right now?

The consideration window is running. Here is a priority-ordered checklist:

1. Read the full agreement before anything else. Look for the OWBPA disclosures (decisional unit, ages, job titles). If they are missing, the waiver of age claims is likely unenforceable.[5]
2. Calendar your deadlines. Mark the 45th day and the 7-day revocation window. Do not let anyone pressure you to sign early.
3. Check your state's mini-WARN rules. If you worked at a site in New York, New Jersey, or California, state law may provide additional notice or severance requirements. The DOL's WARN guidance document explains how federal and state laws interact.[3]
4. File for unemployment early. Most states allow you to file on your last day of work. Filing early protects your claim date even if severance delays benefit payments.
5. Consult an employment attorney. OWBPA requires that the employer advise you, in writing, to consult an attorney before signing.[5] Take that advice. Many employment lawyers offer free initial consultations for severance review.
6. Run the numbers. Use the layoff calculator to estimate your total separation value, including WARN back pay, severance, unemployment benefits, and COBRA costs. Also review how severance is taxed and what WARN Act protections look like in practice.
7. Document everything. Save your offer letter, equity grant notices, performance reviews, and any communications about the layoff. These documents support both your negotiation position and any future legal claim.

For more context on negotiation tactics and common patterns across tech layoffs, see our guide on how to negotiate severance.

Frequently asked questions

Does MongoDB have to pay severance under federal law?

No federal statute requires private employers to pay severance. The WARN Act requires 60 days of advance notice for qualifying layoffs, and employers that fail to provide full notice owe back pay for each day of the shortfall.[2] New Jersey is a narrow exception: if you worked at a New Jersey location where the employer has 100 or more full-time employees and the layoff is a covered event, state law mandates one week of severance per full year of service, plus an extra week if required notice was not given.[4] Low confidence Outside of state-specific mandates like New Jersey's, every dollar of severance is a contractual offer that workers can negotiate before signing.

How long do MongoDB employees over 40 have to review the severance agreement?

Under the Older Workers Benefit Protection Act, employees 40 and older in a group termination must receive at least 45 calendar days to consider the agreement.[5] After signing, they have 7 additional calendar days to revoke.[5] The employer cannot shorten these periods. For individual terminations (not part of a group layoff), the consideration period is 21 days instead of 45.[5] MongoDB's 350-person reduction almost certainly qualifies as a group program, making the 45-day window applicable.

Can I collect unemployment benefits while receiving MongoDB severance?

The answer depends on your state and how the severance is structured. In California, a lump-sum severance payment generally does not reduce unemployment benefits.[7] In states like Rhode Island, severance allocated to specific weeks can delay or reduce benefits.[8] Workers should contact their state unemployment agency before choosing between a lump-sum payment and salary continuation. Use the severance tax calculator to model the after-tax impact of each option.

What happens if MongoDB did not provide 60 days of WARN Act notice?

If MongoDB failed to provide the required 60 calendar days of advance notice at a covered site, affected employees are entitled to back pay and benefits for each day of the shortfall, up to 60 days.[2] The employer also faces a civil penalty of up to $500 per day of violation, payable to the local government where the site is located.[1] Workers can enforce WARN Act rights through a federal lawsuit. The DOL's layoff guide explains how to assess coverage.[3]

Should I sign the severance agreement right away?

No. You are not required to sign immediately, and federal law (OWBPA) gives workers 40 and older at least 45 days for group layoffs.[5] Signing early does not increase the payout, and once you sign and the revocation period expires, you lose the ability to bring age-discrimination or other waived claims. Use the full consideration period to consult an attorney, estimate your total separation value, and research your state's unemployment rules. The NLRB has also clarified that severance agreements cannot impose overly broad confidentiality or non-disparagement terms that interfere with your rights under the National Labor Relations Act.[10]

What OWBPA disclosures should I look for in the MongoDB severance agreement?

The agreement must include the job titles and ages of all individuals in the "decisional unit" who were and were not selected for termination.[5] The agreement must also advise you, in writing, to consult an attorney before signing.[5] If these disclosures are missing, the waiver of your age-discrimination claims is likely invalid. The EEOC's OWBPA overview explains the full list of requirements for a knowing and voluntary waiver.[6]

Sources & verification