My background is firmly in software engineer ing in the healthcare and related industries. I've always been a ”backend guy” focusing more on server side integrations and database (RDBMS, NoSQL, and Graph) design and other DBA tasks as well as data analysis. I've also worked on integration of search functionality and distributed processing. As the job of DevOps job definition started to solidify over the last several years I gravitated more into this role. I’ve worked a lot with Ansible to to automate and manage infrastructure. I’m a strong supporter and believer of infrastructure as code and configuration. Also was an early adopter and supporter of Docker and containerized infrastructure its use in local development environments. While I had initially done some work with mesosphere, I've moved more to using kubernetes. And though I've been leaning more towards terraform, I feel it in many ways compliments ansible and acts as a good balance. I often find my software engineering experience brings the discipline of test oriented development, a piece often overlooked in DevOps teams and yet to maintain stability and provide assurance and development velocity it is critical. I also tout what I term “infrastructure as product” which is that infrastructure is part of a company’s product. Infrastructure is often considered last or at worst itemized as “just needing a running server.” As with athletes and artists, their skill comes from the strength, stamina and/or fluidity of their bones and muscles; and so too with the software products, they are amplified by their infrastructures scalability, resilience, and adaptability.