This sounds like an awesome job
After 16 years working at Encodo Systems AG, I’m currently between jobs. I’ve been asked a few times, “what do you really want to do?”, to which I usually answer, “what don’t I want to do?”
There are a lot of things I’d like to do that I think would be useful, but for which I’m currently unqualified, or only non-officially qualified. I’m a fast learner, but sometimes that’s not enough. You have to be able to hit the ground running. There’s other stuff for which I’m eminently qualified and for which I have a lot of experience. I’ve heard about a few of those already. Irons in the fire.
Anyway, I usually answer that I’d like to do something useful, something where I can leverage my years of experience and technical expertise to really help a company develop a product or project, where what I can offer is what they’re missing, be it in an organizational, architectural, or programming capacity (or all of them). I think there’s a huge benefit to knowing why you’re building something—and then making sure that it does those things in an automated, repeatable way.
Optimally, I’d like to help save the world or at least make it a better place. I’m currently teaching at a local university, which is a decent start, I guess.
A few days ago, I stumbled across this comment on an article on Ars Technica by Tofleru:
“Currently, I’m a lead engineer on an aviation software project certifying to DO-178C DAL A. (Translation: if our code is buggy, we can lose an aircraft and its occupants.) We document, review, and verify all of our software design and implementation. We test the hell out of it, from high-level integration testing to low-level testing, while achieving 100% statement, branch, complex condition coverage (MCDC). We have 5-20 lines of test code per line of flight code. Expensive, but that’s what good life-critical SW costs!”
That sounds wonderful.