Coding for over 20 years and have worked designing hardware, writing firmware, software, patents, web applications, devops, site reliability engineer, and done so from a lone independent consultant through CTO. Worked remotely through all of this.Got my start with tech at a very young age taking apart things (that I probably shouldn't have) and trying to understand how they work. This progressed until I got my first computer at home at age 13 where I immediately took the opportunity to start learning coding (TCL, Bash, C, x86 assembly, C++), hardware architectures, firmware, and reverse engineering software looking for vulnerabilities in various protection systems.Received a BSc in Computer Engineering with a minor in Mathematics from 2002 - 2005 (in less than the typical 4 full years). During this time, I had planned to enter a Ph.D program, so worked on academic research papers with the goal to get publication credits through submissions to journals and scholarly conferences. With interests too varied to pick a grad school (mathematics, computer hardware, computer software, geophysics, physics, and economics), I decided to wait until I could select field. 15 years later, I still don't know what to pick, but my desire to learn as much as I can and solve problems in creative ways remains.I do best where I can utilize my extensive experience, breadth, and depth of knowledge to find solutions to problems that can't be located via google. I enjoy architecture, planning, mentoring, improving processes and engineer/product team workflows, and otherwise helping to bring the best out of my coworkers. I want to work on problems I find fascinating for a company whose mission I believe in.Plays well with those who are passionate, committed, and have a strong desire to help each other learn and improve.Does not play well with time wasting recruiters.