Location: Dallas, TX | remote, local, or relocate to [Austin/Houston/San Antonio, TX - Atlanta, GA - anywhere in Florida - Chicago, IL - DC metro - Research Triangle, NC - Seattle, WA - Boston, MA] | full-time, contract (for the right opportunity)
Stack: C, Java, Python, Matlab
Stack [rusty]: Fortran, C++, Verilog, VHDL
Non-stack: electronics troubleshooting, electronics test, requirements analysis, design or experiments, manufacturing support, real-time software, digital signal processing, systems engineering[1], natural language processing
Resume: <a href="
Contact: see resume
I would like to get back to hardware-focused development, but I realize at this point I am more attractive as a Java backend/systems developer.  I think my ideal role would be "big" embedded (real-time, non-GUI code running on a full hardware platform with either an RTOS or soft-real-time server OS).  Failing that, my next preference would be something oriented towards distributed Java applications (Hadoop, plain ol' sockets and REST, etc.)  I'm open to any type of company; I mainly want good tools, flexible scheduling, a quiet environment, and no government contracting/security bullshit (after 14 years I'm tired of it).
I have a variety of experience acquired on my slightly winding career.  I like variety and being a multidisciplined engineer.  In addition to the electrical, systems, and software engineering experience I have some basic-level mechanical engineering knowledge.
I have a couple irons in the fire at the moment, but I have some bandwidth left at the moment.
[1] This requires explanation.  My experience is in systems engineering by the INCOSE definition[2], not IT systems engineering.  Adding to the title/skill confusion, I'm a decent sysadmin and know my way around Linux.  I am not, IMO, good enough to get paid to be a sysadmin/devops/IT systems engineer.  I don't really have a desire to be, either.
[2] <a href="