Working in concert with our Data Engineers and UX Engineers as an Infrastructure Engineer, you will take ownership of Parse.ly’s distributed cloud environment.
This environment involves 300+ servers running in 7 availability zones and 2 regions in Amazon Web Services. It also includes AWS services such as RDS, ElastiCache, and Athena.
We practice true DevOps: infrastructure-as-code, reliance on automation/scripting, pervasive monitoring/alerting, and close collaboration with application engineering. In this role you will write application code and automate tasks in Python, other scripting languages, and other automation tools. You will master AWS services, security practices, and APIs.
You will ensure that one of the most important real-time analytics systems in the world, trusted daily by over 250 media companies, 2,000 website operators, and over 25,000 active dashboard users, is leveraging the best high-availability and rapid-recovery techniques.
Most of the product team is located in US/Eastern and US/Central timezones. We'll give preference to those timezones, because even though we operate on a distributed/async model, we like to have timezone overlap for f2f (video) collaboration and pairing. We prefer to hire US-based candidates, but we'll consider Canada, Mexico, and Argentina for this role.
What you'll do
- Own all code related to automated build-out of our cloud infrastructure. This includes code to build our EC2 boxes, monitoring/alerting scripts, cost reporting tools, and more.
- Evaluate new technologies that assist Parse.ly’s data engineering and user experience teams reduce toil through automation. Examples of technologies evaluated in the past: Datadog APM, Varnish, Docker, Vagrant, AWS ElastiCache, AWS RDS, Logstash/Kibana, PgBouncer.
- Assist in the rollout of critical services. For example, one of our Infrastructure Engineers recently assisted with the upgrade and migration of our central datastore, containing tens of terabytes and billions of records. This upgrade happened with no customer service interruptions and no server downtime.
- Gain operational expertise for core data infrastructure technologies, including Amazon S3, Kafka, Zookeeper, Storm, Cassandra, Elasticsearch, Redis, Postgres, and Spark.
- Report on improvement of key Service-Level Objectives (SLOs) within Parse.ly, such as API response times, service uptime, end-to-end data processing latency, and more.
And it’s a major bonus if you have:
- Past experience programming in Python
- Depth of experience with AWS
- Deep love of UNIX/Linux
- Comfort with shell scripting and server automation
- Experience with Terraform and Ansible
- Read all or part of “Site Reliability Engineering” book from Google/O’Reilly (available for free here)
- Past experience working remotely.
A Note About Diversity & Inclusion at Parse.ly
We’re improving diversity in the tech industry. At Parse.ly and our parent company, Automattic, we want people to love their work and show respect and empathy to all. We welcome differences and strive to increase participation from traditionally underrepresented groups.
Studies have shown that women and people of color tend not to apply for jobs unless they feel they meet exactly all items in the job description. We believe that high-performing teams include people from different backgrounds and experiences who can challenge each other’s assumptions with fresh perspectives. We encourage you to apply, even if you don’t match everything listed in the job description. Let us know why this role appeals to you, why you will be great, and which requirements will stretch you.
We are an equal opportunity employer who values and encourages diversity and belonging at our company. We do not discriminate on the basis of race, religion, color, national origin, gender, sexual orientation, age, marital status, veteran status, or disability status.
- Apply now by sending your CV and/or LinkedIn profile, Github link (or similar, if available) to firstname.lastname@example.org. Make sure to indicate you are applying for the "Infrastructure Engineer" role.
- Include a 1-3 paragraph intro to why you're interested in this role.
- Tell about us interesting project you worked on or point us toward a piece of code you wrote.