Crypto Layoffs & No‑KYC Clampdown
Crypto firms are cutting hundreds of jobs—many in operations, support and compliance—as the industry pivots to AI automation and cost rationalization, while regulators are actively shutting down no‑KYC exchanges, forcing engineering teams to rework identity and compliance stacks. The twin pressure of layoffs and stronger enforcement is reshaping hiring priorities toward KYC/AML microservices and auditable pipelines. (pymnts.com, monaquatorium.org)
Crypto.com announced a 12% workforce reduction—about 180 roles—on March 19, 2026 as part of an enterprise-wide AI restructuring. (bloomberg.com) Gemini said it will exit the U.K., EU and Australia and cut roughly 25% of its global staff—about 200 positions—in a February 5, 2026 restructuring. (bloomberg.com) Industry tallies show more than 450 crypto-sector jobs removed across exchanges and infrastructure firms in early 2026, a wave outlets have linked to simultaneous cost-cuts and AI pivots. (opentools.ai) Multiple company statements and coverage specify layoffs concentrated in operations and customer‑support teams while hiring and investment continued in AI, data science, and core engineering roles. (coininsider.com) Regulators stepped up enforcement against no‑KYC platforms: the U.S. DOJ unsealed criminal charges against KuCoin in March 2024 for BSA/AML failures, and India’s FIU‑IND issued notices to 25 offshore exchanges in October 2025. (justice.gov) That enforcement and market pressure are driving engineering roadmaps toward unified, auditable compliance stacks and automated KYC/AML pipelines, a shift documented by RegTech and fintech trade analyses. (fintechoutlook.com) Job boards and talent trackers reflect the change: web3.career listed roughly 316 KYC-focused openings in March 2026 as firms recruit compliance engineers, AML specialists, and identity‑automation roles. (web3.career) Security and identity teams are being asked to rework identity flows for scalability and attestability—pen‑testing guides and architecture notes now recommend centralizing entity facts, versioned KYC artifacts, and auditable microservice pipelines. (keepsafe.cloud)
