Bronto Software reviews

Unprofessional, stupid ra ra things, basically everything you read in the negative reviews is true. Benefits are terrible for example they tell you they have 401k but don't tell you it's a 2% match OVER 5 years. % year vesting for a measly 2%? Really? Medical is very basic and expensive, raises are minimal and as was always said in other reviews, Bonuses were NEVER paid out even close to what was promised, yet they had money for beer and community programs and spending a fortune on things the 2 owners liked . They treat employees like 20 year olds who don't know any better, and that's the only people that could be happy there. Those or washed up people who don't think the economy came back and are still working for crappy pay and benefits.Any entry level job at a Cisco or ANYWHERE else would pay $10-20k more and have benefits that make Bronto's look as poor as they are And yes, as other reviewers said, the politics are brutal. If you're one of the ones that are liked and ra ra everything the incompetent owners and managers say, then you're fine. By now there is no chance they will sell as the issues with their quality and software and one dimensional nature of their products is well known and they have been eclipsed by every other competitor in their area, so don't count on making money from being bought or going public. They've been promising that for 5 years. Who ever is saying positive things must be people that have never been to a well run company that cares for it's employees or it's HR trying to outweigh the bad honest reviews.

In short, I think communication within and around Engineering could be improved. There are benefits to not bogging down a department with process and the department currently holds a great practical balance around documentation, but I feel Bronto could benefit greatly by defining some standards and applying some small processes within the Engineering department to radiate information and to decrease misconceptions about the current development process. Specifically, I think the relationship between software engineers and QA would greatly improve in addition to increasing external visibility into the development progress. For example, if what triggers deployments to staging and to production were more clearly defined, all teams within the company would have a shared understanding of the reason for each type of deployment and would be able to speak the same language when discussing them .