Any job with legacy software involved highly values RE, in my experience. Either you have the source to the legacy application, in which case the reverse-engine

Any job with legacy software involved highly values RE, in my experience. Either you have the source to the legacy application, in which case the reverse-engineering thought process is still present while debugging, or you don't, in which case you've got a real RE job on your hands. For example, I worked at a company with a giant set of business processes running inside a minicomputer emulator, with no clear path to migrate the data. By reversing the database file format we were able to extract the data and build additional tools in a gradual-migration fashion, without disruption, data-loss, or the classic "rewriting software" problems.