Lockheed Martin Associate Software Engineer reviews

- My manager was not helpful, only had two one on ones each year and would often make verbal promises that he eventually forgot months later. - boring and broken tech; testing your code locally could even be a struggle and there were pointless Java updates - program clearance took way too long; I was at the company for three years not knowing what I was working before I couldn’t take it anymore - paradoxical optimizations; teammates would often talk endlessly on how to optimize the broken tech they’ve been assigned to. It all felt kind of pointless - confused management and lots of cancellations; 4/5 of the projects I worked on were cancelled which was very demoralizing - clocking in hours on spreadsheets is annoying; often found myself working late because I was lost on a assignment and didn’t want to mischarge. Ended up subtracting my vacation time frequently - teammates were often bad at explaining things (especially through writing). I recall my software architect explaining dependency injection in a condescending manner to insinuate it’s too difficult to explain. After learning it myself a year later, I’d say it’s not that complicated at all. - teammates were a bit backstabby during year end reviews

low salary idk what else