Pros
Salary CEO - he’s never lied, and cares about his employees. but, he doesn’t understand software development. Perks Regular Events Seems like a 10 star place to work if you’re on the sales or CS Teams that the CEO actually understands.
Cons
CIO- Joe will tell you whatever he thinks will make you do what he wants to happen. If he wants you to do more prod support tickets he’ll give you a one on your review. If he wants you to quit, he’ll give you a one on your review. If he wants you to stay, he’ll tell you that your concerns are being addressed, but it will take time. Don’t expect any actual changes, because he doesn’t actually care. If he thinks you’re going to leave, but doesn’t want you to he’ll trash talk other employees who have left and say he won’t give them a positive review. When I was there, the Software Dev team members were third-class citizens. Every other role could veto your code from going to prod, but none of them would talk to each other. This meant that you were the bad guy to all the other teams for “holding up the release” even though it was out of your hands. Imagine the sales team telling you “I lied and told the giant customer that this was already done. This has to be done yesterday. Why aren't you working on this?” but the QA team telling you “I’m blocking this because on the Amazon Fire Phone one of the buttons has a border that’s one pixel thinner than some of the other buttons.” Or maybe it the architect saying “I’d really like this feature that has 200 calls a week to be more efficient. Would you rewrite everything to move it to pub/sub?” You’ll always be stuck in the middle until management decides on some priorities. Most of my team members would be assigned to multiple projects, and every one of them would be on a project without any target other than “Make company X stop complaining,” but no one could tell you what company X was asking for. Expect to be on multiple stand-ups a day where people ask you when the project will be done and you reply “Dev work will probably be done a week after you can give me any clarity on the feature that's being asked for; keep in mind that QA already has a 3 week backlog”. Working over-time was the only way to get recognized for your efforts, but having code that took 4 weeks to make 3 weeks out from even being seen by QA wasn't an excuse for taking a break. There's a lot of talk from Craig about work life balance and Forcura being a family, but don't you dare take some time to actually see your real family.
