Across the automated searches and layoff-tracker queries I ran, I did not find reliable public reporting, press releases, or tracker entries that document layoffs or a quantified headcount reduction at Netguru during 2025. Important: absence of public reporting is not proof that no reductions occurred — it only means I could not verify any number or official statement from publicly accessible sources. To produce a definitive report with counts and categories (roles, departments, locations, reasons), I need either internal HR headcount/change data or a verifiable public source (company statement, filing, reliable news coverage, or a layoff-tracker entry).

• Company resolver: confirmed canonical company handle and domain (Netguru — netguru.com).
• Layoff trackers: queried layoffs.fyi for company entries (no records returned).
• News search: attempted news queries for 2024–2025 layoffs (no matching news items found in the searches performed).
• People Data Labs (PDL) company enrich: attempted call failed due to missing API key (PDL API not configured), so I could not obtain headcount history or 1-year delta from that source.

All queries were automated; see citations section for the resolved company domain. The specific queries targeted public reporting and common layoff trackers — because those returned nothing, there are no public numbers to cite in this report.

1. No public layoff tracker entry or press coverage located for "Netguru" documenting a 2025 layoff event in the searches performed here.

2. I could not obtain company headcount deltas from People Data Labs because the PDL API key was not available to this toolchain; therefore no PDL-derived headcount change or 1-year growth/decline figures are included.

3. Because there are no verifiable public sources returned by the searches, I cannot provide numbers (how many employees were fired), categories (roles/departments affected), or the company-provided reasons (e.g., restructuring, cost-cutting, performance, market conditions). Any such figures would be ungrounded and therefore were intentionally omitted.

Conclusion: Based solely on publicly accessible sources searched here, there is no verifiable evidence to report on layoffs at Netguru in 2025. To move from "no public evidence" to a validated account, one of the following is required: a company announcement or press release, a reliable news story, a layoff-tracker entry, or internal HR data.

Limitations and risks:

• Public silence does not equal absence of events. Smaller or regionally covered reductions (especially at private companies) sometimes do not appear in global trackers or English-language press.
• The PDL enrich call failed due to missing API credentials, so external headcount tracking that could indicate a delta (e.g., year-over-year headcount) was unavailable.

Recommended next steps to produce a definitive report with counts and reasoning:

1. Provide internal HR data: the fastest, most reliable route is to supply an internal headcount-change export (employees terminated/resigned by date, role, location, and termination reason). With that I can produce a full sectioned report with counts, categories, and timeline.
2. Share any company communications: if Netguru issued an internal memo, blog post, or press release about workforce changes, share the URL or text.
3. Authorize a PDL (or similar) enrich call: if you can provide a PDL API key or allow the workspace to run company-enrichment, I can fetch historical headcount and growth/decline metrics to estimate public-facing deltas.
4. Expand media search scope: if you want, I can broaden searches to Polish-language tech press, local business registries, LinkedIn company posts, or social channels (Reddit, Twitter/X). Please confirm language and geographic scope.
5. Check hiring pages and job postings: comparative analyses of careers pages and job openings over time can sometimes indicate contraction (mass removal of openings) or growth.

If you want me to continue searching external sources, tell me which of the above steps to run next (enable PDL with a key, provide internal HR data, expand searches to Polish-language outlets, or allow deeper scraping of the company's site and LinkedIn).