Skip to content

Instantly share code, notes, and snippets.

@drewr
Last active March 8, 2021 18:13
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save drewr/8113cd9817e457f9227739bcbe2fffeb to your computer and use it in GitHub Desktop.
Save drewr/8113cd9817e457f9227739bcbe2fffeb to your computer and use it in GitHub Desktop.
Software Engineer, Infrastructure

Software Engineer, Infrastructure

[recruiting preamble text here]

The Infrastructure team in Elastic Engineering sits underneath the Elastic product stack and support many efforts in the company at large. Primarily we’re software developers that handle state — CI specifications, cloud resources, integrations between teams. The Elastic Stack is built on our infrastructure and we touch everything needed to get it there. We also do software consulting around the organization to put our products to use for our own business.

What you’d be responsible for

  • Develop tooling to facilitate the building and shipping of the Elastic Stack
  • Develop and support production services related to all aspects of the Elastic business, including our downloads, Docker registry, maps service, and much more.
  • Support internal use of the Elastic Stack for software development and analytics.

Possible experience

  • Software Developer: You probably have a broad software development background (we use Python, JavaScript, Clojure, Rust, but across the company is everything else from Java to Go). Being deep in some language is a requirement, but it doesn’t have to be one of the above.
  • Site-Reliability Engineering: We are an operations team. We solve problems with code, but fundamentally we keep things working. You may have worked as an SRE.
  • Service-Oriented: Multiple years hands-on experience administering Linux, preferably with distributed systems with some scale. You’ve maybe help run a SaaS platform.
  • Infrastructure-as-code: You may have experience automating production Linux systems collaboratively, deriving configuration through version control, and are proficient in some of Docker, Puppet, Chef, Ansible, Salt, Habitat, Dhall, Terraform, Packer, your own shell scripts. Maybe you’ve thrown half of that away and use Kubernetes. We do that too.

About you

  • You have a strong desire to automate and monitor.
  • You have a desire to build reusable software components. You’ve likely created an open source library for your favorite language, or at least made a meaningful contribution to one.
  • You enjoy a versioned workflow, representing your work in git, motivated by a GitHub workflow through issues and pull requests.
  • You have a healthy knowledge of Linux (have compiled your own kernel at some point, know how to trace syscalls, understand TCP, care about the difference between sysvinit/runit/systemd, etc.) You don’t have to know everything, but you’re motivated to solve problems in this arena.
  • You love open source development, and have committed to some project somewhere (doesn’t have to be ours), whether mailing lists, patches, documentation, etc.
  • You enjoy working with a distributed company and the active, asynchronous communication it requires.
  • You believe that a diverse company is a better company, and want to work with men and women all over the world.
  • You are willing to listen and give everyone at the table a voice.

Additional information

[recruiting postamble text here]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment