This isn't your typical infrastructure or technical operations position; Paperless Post is looking for someone to build tools to manage infrastructure and solve operational problems. You modularize, reuse, and version control your infrastructure as code. You know when to use the latest technologies and when to automate, but still value uptime, performance, and stability. You follow best practices but iterate over your projects quickly and smartly.
Over the last year, we’ve moved to Amazon Web Services as a more modern architecture that can keep up with our rapid application growth. We’re now looking to take things a step further to fully embrace containers and Kubernetes as the platform for our engineering teams - from local development environments through to production. We’re not quite at that nirvana yet though and are looking for people to join the team along that journey.
A little bit about us
We embrace DevOps as a philosophy for the entire engineering team, rather than any one team’s job role. We’re creating an environment where all engineers should be able to bring services and applications to production and maintain them going forwards without waiting on “Ops” engineers.
We care as much about the people as we do the systems. We’re all human and that’s important to us. We don’t have all the answers all of the time and appreciate people need time to learn, this is something that is actively encouraged. We focus on developing ourselves as well as our systems, encouraging a blameless culture allowing us to all grow and learn from our mistakes.
As a distributed infrastructure team, it's important that you feel comfortable working virtually across time zones. Since we can’t do team lunches in person, we have virtual monthly hangouts where we catch up on the non-work side of our lives.
What you'll do here
- Kubernetes clusters - and all the related tooling!
- Work with developers to maintain codebases, internal tools, and services (build/deploy, etc.)
- Enable developers to deploy systems and application code in a rapid and consistent fashion
- Maintain servers (CentOS and Ubuntu) and investigate newer OS such as Container Linux
- Create infrastructure as code with configuration management and version control
- Troubleshoot production and systems issues
- Design and tune systems for performance, load, and scalability
- Maintain Postgresql databases
- Systems/network security
- Documentation, documentation, documentation
- Participate in on-call rotation and have a strong desire to make on-call better for everyone (e.g. teaching the machines to heal themselves)
What you should bring to the table
- Willingness to learn and explore the “known unknowns”
- Advocate of configuration management: we're currently a Chef shop but this will change as we move to Kubernetes. We'd love to hear your experiences with Puppet, Ansible, or anything else
- Experience orchestrating infrastructure using Terraform, CloudFormation or other similar tooling
- Understanding that applications are not "production-ready” unless they're instrumented and monitored
- Remote experience - We are a remote infrastructure team, and our engineering team as a whole is distributed across both the New York office and remote
- Ruby on Rails or Golang development experience
- Working with CDNs or a varnish caching layer
- Extensive networking knowledge
- Understanding the issues related to inherited code bases
Tech we use:
- Containerisation - Kubernetes, Docker
- Web/application serving - AWS ELB/NLB/ALB, Nginx, HAproxy, Rails, Fastly
- Datastore Administration - Postgres, Redis, Memcached, MongoDB
- Metrics and monitoring - Sensu, Statsd, Graphite, Grafana
- Log aggregation - Elasticsearch, Kibana, Logstash
- Continuous integration/deployment - Jenkins, CircleCI
- Network administration - AWS VPC, DNS
- Application packaging - RPM/Yum, Ruby gems
- Authentication/authorization - LDAP, Zero Trust Concepts
Note: it’s not a requirement that you know all of the above from the start, but this is the stack you will be building and maintaining so an interest in learning more about these technologies is required.
Company-wide we enjoy an amazing ecosystem of an even gender split and a healthy balance of engineers and designers. Because Paperless Post isn’t supported by ad revenue, we can focus our efforts on building and improving on the ideal version of our platform, product, content, and partnerships for our users.
We are proud that Paperless Post helped over 70 million people connect in the real world last year. Our product is global, and we are committed to being a company where everyone belongs. We encourage people from all backgrounds, races, genders, and abilities to apply!