Data Engineering at Cisco

Cisco's Glassdoor rating of 4.1 sits among the highest of the companies we track, and pay lands above other Technology companies, so the material side of the bargain holds up. The tension is in the culture signals: mixed sentiment on Blind and a neutral happiness tier trending down suggest a workforce that sees the compensation but is less sold on the day-to-day. Big-company bureaucracy gets cited consistently, and the Splunk integration has added organizational complexity that tends to slow delivery cycles. What you get is a stable employer with meaningful data infrastructure problems and a comp package that competes; what you give up is the pace and autonomy of a leaner shop. Engineers who find meaning in scope and scale tend to stay; those who need fast shipping cycles tend to leave.

Cisco has had 1 tracked layoff in the past 12 months, the most recent in Oct 2025, and 4 executive departures in the past year point to ongoing structural reset as the Splunk acquisition gets digested. Hiring volume is moderate, with 10 open data engineering roles across 3 cities and Bangalore as the leading location, which reflects a deliberate offshore-heavy build-out rather than broad domestic expansion. The trending down happiness trend over recent quarters is the clearest signal: this is an organization in transition, not one that has settled into its post-acquisition shape. For someone joining now, the next 12 months will likely involve a period of reorganization and priority shuffling before the data platform strategy stabilizes. That is a real risk, and it is worth weighing against the platform-scale opportunity.

Cisco's core data problem is network telemetry at scale. The company processes billions of device events daily across enterprise and service-provider customers, which means the data engineering work skews toward high-throughput ingestion, real-time anomaly detection, and cross-product correlation across security, networking, and collaboration lines. The Snowflake, GCP and dbt stack visible in current listings points toward a modernized analytics layer sitting on top of a historically complex on-prem data estate, and Java remaining in Python, SQL and Java alongside Python signals legacy pipeline maintenance alongside net-new work. With acquisitions like Splunk folded in, engineers here are increasingly asked to unify disparate telemetry schemas rather than build greenfield. The job is less about elegant warehouse design and more about making sense of heterogeneous, high-volume operational data across a product surface that keeps widening.