Python, Docker, problem solving

Docker and Containerization Tech Lead & Software Development Engineer @ Note: This position description was split into a separate entry due to wordcount limit on linkedin. I've been at Counsyl since Feb 2012. August 2015 - Present (Containerization Tech Lead & Software Engineer, Platform Team) Use of Docker inside Counsyl has picked up very rapidly, and in response I've stepped up to become the tech lead for docker and containerization in general. This gives me dedicated time and focus to continue to improve our Docker-based infrastructure, including writing better tools, helping teams integrate Docker into their workflow, and investigate alternatives to our Deis cluster. We have explored Kubernetes and Mesos as more stable and feature-rich replacements for our Deis cluster, and have chosen Kubernetes. I'm now leading the buildout of a k8s cluster and the tooling around it to make migrating seamless. This includes a python service framework and best practices to make the k8s layer unobtrusive (and can thus be ignored by the majority of teams). My Dockerization efforts have led to a shift in how we develop and deploy applications inside Counsyl. Until now we haven't been following a 12-factor approach to services, and even getting a new service running used to take several months. Now teams are able to launch a new service in under an hour. From August 2015 to Present (5 months) Software Development Engineer @ Note: This position description was split into a separate entry due to wordcount limit on linkedin. I've been at Counsyl since Feb 2012. February 2015 - August 2015 (Software Engineer, Platform team) The Platform team split from the techops team, with a shift in focus to writing software tools and maintaining a platform for the rest of our software developers. Our mandate is to make the development of software and launching of microservices enjoyable and easy. My first goal was setting up a puppet-based framework for deploying services inside Counsyl. Puppet proved to be a bad fit for this, since it's geared toward provisioning entire servers and not for easily deploying new services. As a side-project, I built out a deis cluster (a PaaS-type tool for deploying Docker containers) and started figuring out how to shift our infrastructure to a modern Docker-based system. I developed all of the initial tooling around this cluster, including deployment, making base images, a template for Django apps, and log collection and processing. This approach to service deployment quickly eclipsed the puppet approach and several teams and projects are now using it, with more coming every week. I've also written a bunch of docs and have given several internal talks on the benefits of a microservice architecture and how to do it well with Docker. From February 2015 to Present (11 months) Software Development Engineer @ Note: This position description was split into a separate entry due to wordcount limit on linkedin. I've been at Counsyl since Feb 2012. June 2014 - February 2015 (Software Engineer, Techops team) The techops team is in charge of building out key physical infrastructure, keeping servers online, and fighting fires! I chose this team because I only had experience writing software, but not with keeping an infrastructure running. I learned a lot about things I had never worked with while on this team. I implemented an LDAP-based heirarchical group structure with a simple API for protecting our internal views to a given team or sub-team. I took over a project (when the lead dev changed jobs) intended for large data storage with local caches, backed by S3. The files are encrypted during storage and transmission. This is being used by the lab and other teams to securely store files generated during normal operations. From June 2014 to Present (1 year 7 months) Software Development Engineer @ Note: This position description was split into a separate entry due to wordcount limit on linkedin. I've been at Counsyl since Feb 2012. Feb 2012 - June 2014 (Software Engineer, Billing Automation Team) I was the founding member of the insurance processing automation team. I had no prior knowledge of the insurance industry, but within three months I had built out our claim filing pipeline and automated handling the responses from the payers. On the initial launch it performed a man-month of insurance processing work in 20 minutes. We grew business an order of magnitude the year this launched, while only having to grow support staff by a few heads due to my automation efforts. I implemented a patient information auto-correction service which can automatically fix roughly 85% of bad patient insurance information without human intervention. I created optimal code set calculator which determines the best set of CPT Codes to bill insurance companies for the procedures performed. We don't need to bill for every service we provide (if we did our bills would be outrageous!), instead we target a particular price that is palatable to insurance companies and consumers, while still being profitable. Insurance companies pay different amounts for different procedures, so we automatically choose the optimal set of procedures to bill for. Towards the end of my tenure on the billing automation team we swapped in a new leader. I handed over the reigns well and the team is functioning exceedingly well. From February 2012 to Present (3 years 11 months)

Steven Buss is skilled in: Java, Python, SQL, REST, Distributed Systems, Software Development, Software Engineering, Git