Requirements and Responsibilities
- 5+ years of technical experience in development, operations, or joint DevOps responsibilities.
- Multiple successful customer engagements providing continuous delivery solutions, preferably employing AWS.
- Embody the Stelligent core values of sharing, increasing software delivery speed, continuous improvement, and self-service.
- AWS Professional Certification (e.g. AWS Certified DevOps Engineer - Professional or AWS Certified Solutions Architect - Professional).
- Comfortable working solo or leading a team
- Have trained, groomed, or mentored 3+ other engineers in continuous delivery in the cloud on other active customer engagements.
- In-depth familiarity with complete suite of AWS Services, with particular depth in those that are heavily used when providing DevOps Automation solutions, including tools like CloudFormation, Code* Services, CloudTrail, CloudWatch, EC2, IAM, OpsWorks, Route 53, S3, RDS, SES and VPC.
- Experience establishing and employing Continuous Integration practices and execution platforms such as CodeBuild or Jenkins.
- Frequent and comfortable use of configuration management automation tools such as Chef (or other such tools) in creating continuous delivery systems.
- You will be expected to formally and informally lead and mentor other members of your team.
- You will expected to be able to assess risks and plan solutions for the entire team, and collaboratively work with other members to execute them to achieve successful continuous delivery solutions for Stelligent’s customers.
- You will be expected to continually assess successful and not so successful practices, and to collaboratively adapt team practices to improve the value we bring to our customers.
- Recognition and acknowledgment after an assessment by a Stelligent Engineering Panel.
We are seeking engineers who appreciate and have experience with both development as well as operations (hence the current cultural buzz word, DevOps). We prefer engineers who have come from the Development side first, though we value the opposite path, and expect that for every three Dev->Ops types, that we will hire one Ops->dev type. We have found that the former tend to embrace the software engineering and development best practices easier than many people who have come from the latter model. That being said, as we get more and more engaged with established customers, the credibility of the Ops->Dev (both their experience and the burden of production responsibility) tend to carry a LOT of weight and gravitas.
Our engineers need to be ready to invest themselves in hands-on keyboard activity. They will be committing code to the likes of Git repos every day. We do not need “hand waving architect-only” types, though we like engineers who can both knock out code and be comfortable sharing large-scale and abstract concepts to a crowded room. We want hardcore, full-stack-aware engineers who are not afraid to learn the wealth of tools we need to employ and who are comfortable with a constantly changing landscape of tools and techniques.
They absolutely need to be able to communicate both verbally and in writing. A great deal of our communication is done remotely, and requires super clear thought, enunciation, and articulation.
Some - though not all - customers require a richer introduction than others, so engineers bound to engage with them may require secondary levels of vetting (e.g., interviews, projects, and background checks). Since this is a customer facing role, you should be comfortable traveling to client locations and delivering DevOps consulting services when needed.
Our engineers can live anywhere in the USA. Most of our customers require that we perform deep background checks. You should be willing and able to work for both commercial and government customers.
Engineers tend to work in teams of 2-3 (vs. solo), though once comfortable with the Stelligent way, we are comfortable letting individual engineers be on their own. That being said, it has happened that circumstances have resulted in a new engineer being engaged with a customer in nearly a solo manner (e.g., 1.2 engineers). We “live” in Slack, and even though everyone is in different places, we have a culture of open communication and sharing that makes up for the geographic separation and lack of formal office.