Mozilla

The team I’m on at Mozilla is preparing to hire more junior/mid and senior engineers in the USA, Canada, and Germany. We build and maintain the infrastructure that supports Firefox’s many features. This encompasses around 70 services, ranging in scale from 2 users to 20 million concurrent connections, which are created by about a dozen different developer teams. Python is the most common language, though Nodejs, Go, Rust, and even Perl are also represented. When you take a look at the source of these services (most are publicly available in https://github.com/mozilla-services/ and https://github.com/mozilla/), you’ll notice that all are dockerized following the standards at https://github.com/mozilla-services/dockerflow. Each service run by our team has a primary ops engineer as the main point of contact and a secondary to assist with engineering and on-call responsibilities, so no one person has to be familiar with every technology used in every service. Most services require on-call using pagerduty, but we regard pages as indicators of process problems and invest in the root cause analysis necessary changes to prevent failures from recurring. Although our top priority is keeping everything working well, you’ll often have the flexibility to balance your workload with services aligned with your skills and interests. We standardize our infrastructure code across projects, so that your work in adding a feature to your own services’ infrastructure can easily be reused by the rest of the team. In our infrastructure Git repos, you’ll design, maintain, improve, and review automation, Python scripts, and monitoring code.