If you work in IT in academia, then you make trade-offs that can sometimes be good. I just tried to start working remotely in a team where no one else does, and that has gone horribly and exacerbated any other issues I've had.
The biggest problem is inertia and waterfall style management, even if you "do agile". You'll likely work with outdated code that is maybe secure but no one uses it in 2018. So, you end up having to work nights and weekends on getting to a company that likes to learn new technologies so they can use the best tool for the job.
Oh yeah, don't forget about your coworkers. They will be propping their feet up on the table as you do work, because they are "classified" employees and can't be fired, essentially. If you can work on whatever you need to do to get out of your hellhole, then that is great...but most likely you will be fixing their bugs and working on legacy code.
If you are a junior developer, then maybe it is a great place to learn, but if you have more than 3+ years of experience you will most likely want to pull your hair out most days.
being lazy is encouraged, almost rewarded
no job security working with legacy code