DevOps Engineer

Our team of 9 engineers is curious, driven, friendly, and collaborative. We believe in an egoless approach to development and a blameless approach to problem solving. While we work independently, we support each other through frequent code and design reviews, daily stand-ups, and pair programming, facilitating learning and reducing friction in our regular release schedule of every 3 weeks.

In your first week, you will: * Commit to our puppet repository * Commit to our chatbot repository * Deploy updated chatbot code * Build and deploy AWS amis (via chatbot) * Deploy application code to production In your first month, you will: * Add meaningful functionality to our chatbot * Take primary ownership of at least two of the following: * testing/ci * configuration management * logs, metrics, alerting, and dashboards * asset management/pipe-lining * development environments * operations-level security/compliance * workers/job queues * Have identified pain-points in our application stack and/or infrastructure AND have suggestions around how to fix them By your third month, you will: * Help us make architectural decisions to increase availability/reliability * Improve system metrics visibility to Engineers and non-Engineers alike * Further optimize our deployment procedures so that we can get thoroughly-tested code into production even faster. * Want to grow the operations team more to accommodate your growing list of nice-to-have optimizations that aren't high priority, but would be so awesome to build/have.

We are seeking an experienced and motivated operations/back-end engineer to expand our (small) operations team and continue to promote DevOps at HelloSign. * Located in the US and are willing to work either remotely or in our San Francisco office * Will make meaningful decisions about our existing solutions and drive the software/services that support our growth. * Have strong opinions about how to do things, and continue molding those opinions based on your experiences. * Abhor performing repetitive tasks and/or stepping through inefficient processes * Do not take issue with attempting to script yourself out of necessity, nor with providing documentation to ensure that others can efficiently do what you do. * Find new technology interesting and often worth investigation, but exercise great caution before using immature solutions in production