Spiceworks – New York, NY
Who you are: Do you have an aggressive-meets-approachable sales DNA and Web 2.0 media savvy? Are you a hunter who strives to close deals? Then you’ll… Spiceworks
3 people found this helpful
- Comp & Benefits
- Work/Life Balance
- Senior Management
- Culture & Values
- Career Opportunities
I worked at Spiceworks full-time for more than a yearPros
Lots of perks: free food, fun company events, lots of hype around nerdy stuff.
The "culture" seemed super exciting upon arriving. I often called it the "Disneyland" work place - hell, even our users would visit and were paraded around the office as they told them things about us, as if it were the "Small World" ride. Not sure if this is REALLY a con, as at times it felt weird.
There really are a ton of cool people there. Met some of the nicest, most nerdy people there and I love it!
I also really liked the idea that they wanted to pay down technical debt with "Fix-it Fridays" and improve learning with "Lunch and Learn" events. But... These has issues as well (listed in cons).
The intern project was great. I got to see how a lot of schools are training their students these days, and hopefully imparted some knowledge on those I interacted with.
The products are extremely interesting, and their business model is pretty interesting. They are making bank, and some of the people are having a freakin blast doing it.Cons
Uber-cliquey. The people that have been there from the early days are self-entitled, and are hypocritical. They use phrases like "culture" and "own your project" as cop-outs whenever it suits them. At first it was too cliquey because there were the "originals," and the "n00bs." I was a n00b. Then it became cliquey because it got so big, you couldn't possibly meet everyone, and you wanted to get to work to feel important.
The number of employees is TOO DAMN HIGH! Too many chefs in the pot for SURE! Everyone goes off and does their own thing though, so working together to solve problems is impossible. The few people that will do it, eventually give up due to needing to get their work done by the enforced deadlines. Then, when you try to integrate your pieces together last second (after you missed the deadline twice) nothing works, and everyone is high strung and tense, and REALLY defensive about their work (which likely was built incorrectly or over-using some crazy Rails magic 1/2 stuff that's not relevant anymore). I felt like the only one that wanted to build products as a TEAM.
Oh yeah... You don't get a say when things will be accomplished, or what should or could get done by said deadline. You just have to do it.
Problem is, deadlines are this immense pressure, that only a handful of people actual strive for - even if they didn't get a say. Meaning the "culture" was divided in some were hard workers, and some were "life balance" workers... Meaning they didn't work and often found ways out of it (extra long lunches, repeated "office visits" for the same thing that SHOULDN'T be done twice, like a root canal on the same tooth, etc).
Titles meant nothing when I started, and at some point they too became cop-outs. You didn't need a manager to be your point of contact, but the growth we went under certainly required it. However, in some cases, going out on your own meant you stepped on toes - but then again asking for resources from the manager would mean you were not owning the project.
The product is a mess. Super old technology (12+ years) mixed with brand new tech (< 24mo), and tons of duct tape, bubble gum, and string in between. As a senior engineer, job satisfaction was at an ALL TIME LOW. I've worked on products that were poorly implemented, hell - even used the wrong technology.... But the cluster-bomb their apps are, it's difficult to take pride or conjure excitement to work with the likes of a Rails 1/2 frankenstein, Prototype JS, etc.
Fix it Fridays were poorly implemented. A single day to remove an entire library that was used for the last 8 years? OK, that should be easy to fix in a day... NOT! Oh, so I can spend the next 3 months of every other Friday to fix it? Cool... Except when I'm finally done, the merge conflicts always totally screw stuff up for a few more weeks, and new features were implemented in the old library, meanwhile some of the conflicts you've been fixing have been refactored and now are bigger conflicts.... It's literally a never-ending job of cleaning up something you just fixed.
Lunch and Learns.... Not sure I ever learned a single thing. At first, I went every Wednesday and was the first one there to get a front row seat. I was excited at this idea - it took almost a year for it to wear off. Eventually I'd often go to just get the free food, mingle for a few minutes while I scarfed it down before the meeting, and then would head back down to be productive. The general feeling was that "it was pointless, but hey - free food!"
No future? I might be wrong here, but I'm certain the goal of the founders is to sell out. Constant talk of IPO, preparing for it, even though "we're not sure we want to do that" and constant claims of "what it would take to buy us out."Advice to ManagementAdvice
You should have listened to the few of us wanting to better things. Everyone feels it, but too chicken to say anything.
Nothing I said here should be a surprise to anyone there, plenty of people were saying these things, yet no one wanted to do anything about it or talk to the executive team.
Scott, Greg, Francis, You need to get more involved!!!! That is, if you want to KEEP your company.Doesn't RecommendPositive OutlookApproves of CEO