First and foremost, you are a developer: you enjoy writing code. However, where others shrink back from optimizing builds, you dive in head first. You speed up tests, and fix intermittent false failures. Your peers crave fast and reliable feedback, so you shave 5 minutes off a compile or 10 minutes off a test run. You enjoy tuning build tools and learning how version control systems operate. You remove blockers that stand between implementation and delivery because code has no value until it is in a user’s hands.
In Pivotal Data, teams own the quality of what they produce. Developers write tests along with their code. There is no separate QA team, nor a group of people responsible for cleaning up others’ messes. The engineering effectiveness team works with other teams to improve the developer experience. We don’t clean up builds for other teams; we work with them to speed up the entire product cycle. And we build our pipelines to the same quality standards as the code flowing through them.
How we work
We’re looking for flexible generalists, so knowledge of specific technologies matters much less than the willingness and excitement to learn on the job and to stay focused on improving the effectiveness of your fellow engineers.
We pair and collaborate every day and you want to as well.
We have experience with a number of continuous integration systems. We know what they do well and what they don’t. We use Concourse ( http://concourse.ci/ ).
We understand the difference between a build and build pipeline.
We build docker images and are comfortable troubleshooting both containers and virtual machines.
We operate on a Amazon Web Services and Azure.
We are comfortable jumping between shell scripts, Ruby, Go, Python, JSON and YAML all in the same day.
We eagerly embrace and address whatever challenges we encounter -- from troubleshooting Docker Hub issues to writing Golang tools to make our lives better.
***Please answer application questions if they are not included in your cover letter****