It's probably not coincidence that the former environment I spoke of was also a government contract.
Government work is hard for the reasons you mentioned, and also because generally, contracting pays well enough to price you out of other markets.
My exit strategy was to find a government vendor (e.g., that makes products for government / enterprise consumption) vs. a government contractor. The services side of the house is still pretty much a suit-and-tie affair, though we pride ourselves on being much more meritocratic than our customers, but on the engineering side, pretty much anything goes.
The one thing I will say about gov contracting is that as a result, I interfaced with much more than would have been in my normal comfort zone, and I came away from it MUCH more knowledgeable than I would have had I not done it at all, and the work was very rewarding. My advice is to hold out for the good parts as long as you can while quietly looking for a way out that seems fulfilling.
Thanks for the advice. I've slowly been moving to the more technical side of the house since I graduated school, because I got hired on as an "Systems Engineer" that wrote power points. It was great in that I learned to deal with customers and push my comfort zone, but it also left my coding experience woefully insufficient for a time.
Luckily, I'm a step closer to what I want to do now, and I can fill my time with Udacity/Coursera classes when there is an abundant amount of downtime. I do have my eyes on the prize (which would be working in a faced paced and supportive environment) but I'm still building my skill set. It's just good to know that other people have been where I am and approached the problem logically to finally get somewhere that there was a better fit for them.
I plan on moving away from government contracting in general soon. I find that while they do pay well the constraints they put on the work just isn't worth it. If the company doesn't own the system that they work on then they don't tend to care about it in the same way.
Government work is hard for the reasons you mentioned, and also because generally, contracting pays well enough to price you out of other markets.
My exit strategy was to find a government vendor (e.g., that makes products for government / enterprise consumption) vs. a government contractor. The services side of the house is still pretty much a suit-and-tie affair, though we pride ourselves on being much more meritocratic than our customers, but on the engineering side, pretty much anything goes.
The one thing I will say about gov contracting is that as a result, I interfaced with much more than would have been in my normal comfort zone, and I came away from it MUCH more knowledgeable than I would have had I not done it at all, and the work was very rewarding. My advice is to hold out for the good parts as long as you can while quietly looking for a way out that seems fulfilling.