General Dynamics Information Technology reviews

Constant Emails sent out about the team not doing this correctly or not doing this on time even if it has nothing to do with where you are. Constant emails from several different people about a system being down or something that needs done “ASAP!!!!!”. Contact with supervisor is the only contact you will have from the company unless you or someone else is screwing up. Constant demand with no incentive to do so. Company is uncoordinated in the OPM Contract and they change guidelines constantly. I feel like most of the time I spend on my email trying to stay on top of new guidelines in fear of being snowballed with Reopens on cases. All of their IT systems suck and are down constantly. You can go on vacation for a week and comeback to 100 emails about screw ups and demands from you when you’re not even there to perform the tasks they want. I can barely find the motivation to do the job anymore the only thing driving me is my paycheck and my bills. Company needs serious work and to ease up on some of their employees. I went from wanting to go above and beyond in the job to only doing the minimum while searching for a new job.

I felt I had a moral imperative to post this review. Just stay away if you are a Software Engineer. It is the worst job I have ever had. You have been warned. The previous group of developers have all left that should tell you something. They tell you they follow an Agile development process which is a lie. We have been in firefighting mode since I joined this organization. I don't expect anything to change. Software Engineers are basically fall guys. The deployment process is a crap shoot 70% of deployments fail and have to be fixed. You basically have to troubleshoot every deployment to see what they missed. The process is totally manual. The architecture team will change the API you are using and deploy it bringing down the server. The client blames you. The power goes out. The client blames you. The user's don't even look at the requirements when testing. They see something they want and they enter a bug. It doesn't matter that it wasn't in the requirements and is a enhancement. It is reported as a bug. They have said I quote "We expect zero bugs before we accept the software". Enhancements are counted as bugs so unless you can read minds you are doomed to failure. If they have a database problem, you are blamed. Developers have to fix database issues because DBAs won't come in on the weekends. When the production database was rolled back to the integration database so they would be in sync. The process broke the applications since the DBAs don't write migration scripts to run with the changes implemented during development. It was a train wreck. The development team got blamed of course and also had to fix it. No testing was done just roll the production database into integration and sift through the wreckage.