Our revenue has increased more than 10x in the last year, and we’re scaling Heap to meet the demand. Our backend supports an expressive set of queries that need to come back with sub-second latencies and reflect up-to-the-minute data. To make this possible, we’re working on a new distributed infrastructure.
We’re looking to bring on our first Infrastructure Engineer to lead the DevOps side of this challenge. Help us de-risk our stack, add more 9s to our availability, and incorporate open source tooling.
You’ll own the design and development of our DevOps toolchain. You’ll build a deploy pipeline and manage configurations. You’ll set up performance metrics and act on them to scale a complex distributed system.
We’re looking for stronger software engineering skills than a typical DevOps role requires. You’ll need to be able to understand our codebase and debug issues as they come up. Some example projects:
- Select a service discovery tool and incorporate it into a codebase that assumes static locations for services.
- Set up centralized logging and tools like Kibana for making use of the data.
- Standardize our VPC configuration, which has a number of bad warts.
- Set up Terraform or CloudFormation and use it to manage the complicated aspects of our AWS configuration.
- Determine how we’ll monitor, backup, and otherwise operate our ZooKeeper cluster.
- Much, much more.
We’d like to get to know you if:
- You communicate with clarity and precision. We care about this almost as much as your technical ability.
- You’re self-directed with a strong sense for relative priority. There is low-hanging fruit everywhere. We need someone who has a good sense for which projects will have the most impact.
- You have experience with AWS, especially EC2, VPC, and ELB.
- (Bonus) You have experience with our stack. Heap runs on Kafka, ZooKeeper, PostgreSQL, Redis, and Node.js.
We work in San Francisco but we welcome remote engineers. We'd love to hear from you! Email us at email@example.com if you think you'd make a great fit.