Working for Fullbay was the most miserable development job I’ve ever had. The two main reasons were the management you’ll have to work with and the terrible quality of the code. When you first start with Fullbay, you will sit through a week of training on how to use the Fullbay application itself. It takes a week because the application is that poorly structured.
Once you finally see the code, you will be horrified. It’s easily the worse code I’ve worked with. It’s the type of PHP application that gives PHP a bad name. The code is both sloppy and riddled with bugs and bad practices, an endless stream of PHP + SQL + JavaScript + HTML, all intermixed with each other. There is no framework, just a complete mess.
Every ticket has an estimate as to how long it should take to complete. If/when you go over that time allotment, you’ll likely be called out in the standup meeting in front of the entire team. You could attempt to ask one of the other developers, team leads, or your manager for help, but nine out of 10 times, you’ll hear nothing back. Communication is a real problem. In addition to time estimates, you’re asked to log your time on every ticket, down to the minute via Jira.
Once you’ve completed your task, QA reviews the work. Because the application is so poorly designed, QA often has an environment that’s slightly different than yours. This leads to endless bugs and tickets being sent back to you for reasons outside of your control.
There are little if any opportunities for career advancement. The best option is to become a team lead which just adds additional responsibilities with zero benefits.
The company has a real problem with management and overall direction. I honestly can’t see them keeping up with or surpassing their competitors at this rate. Features take way too long to develop and are often buggy because of the problems mentioned. I saw at least three failed deployments where rollbacks where necessary…
