Splunk Engineering Manager reviews

Of course everything isn't perfect, and we've got our share of not-perfect: * Commuting into Boulder can be aggravating. We set up Tuesdays and Thursdays for people to work from home and that seems to have helped a lot. * Some of our older systems have a lot of technical debt. We're quickly improving them, but it feels like we're not doing it quickly enough. * Some Splunk processes aren't very mature yet, and so it can sometimes be a challenge to get administrative work done. * Sometimes Splunk seems to overreach with standardization and we end up getting pressure to comply with a mediocre or poor standard rather than lead & excel with something better. The Boulder culture is very agile, devops and start-up oriented, and a lot of Splunk product and project oversight is waterfall and very dated. So far we're navigating this difference ok, but it's absolutely a challenge. * We also get a lot of pressure to "eat our own dogfood" - which is sometimes great. But it's bad when you're a cat and are pressured to eat dogfood.

- career ending technology in core enterprise - awful program management. no idea of how to do agile/scrum - re-org almost every year. new management comes in, screws up, gets fired, and the cycle continues. Extremely demoralizing. I think most experience Splunk now just kick back, do the bare minimum, and go home. Please wake us up when you have figured what you are trying to do.