Pros
Well the pay wasn't bad....
Cons
Where to begin...setup for failure by merit of zero training. My training was "the guy who had the job for 7 years made 4 videos--everything about the job should be in there"--spoiler alert, it wasn't. It wasn't the same as having that person there to question and train me firsthand, and when I found out their method of coding was entirely doing everything in C# outside the tool the system was supposed to be running on, I had to reverse engineer anything I had to work on instead of opening it in the system and knowing in 10 minutes how it worked. They were behind on deadlines but never let me just code, rather expecting me to field support questions and still manage to code at the same time. When I offered to work outside the 40 hours so I could have dedicated time to focus on coding I was told "the job is only budgeted for 40 hours a week--you should be able to do everything in 40 hours". I still worked beyond that time to make sure I was able to deliver projects, on my dime, never getting to bill for the extra time, and never received recognition from the manager. When we were looking at why something worked in UAT and not Prod, when we opened the code up she saw a file named differently and wanted to delete it based on the name--not knowing what it did (which was to initiate the whole process). It turned out it was a critical piece to the process working, but again no recognition for resisting the "one of these things is not like the other--let's delete it" method. Mind you I have over 14 years experience in my field but never was given any kind of recognition for that qualification.