Senior Release Engineer | Mozilla corporation | One of our global offices or remote

Senior Release Engineer | Mozilla corporation | One of our global offices or remote

Senior Release Engineer

Apply for this job

Team:

Engineering

Locations:

One of our global offices or remote

Depending on who is doing the counting, Mozilla commands 20-30% of the desktop browser market share, and has grand ambitions in the mobile space with our Firefox browser for Android and, more recently, our own FirefoxOS-based smart phones. At Mozilla, release engineering is the force multiplier that allows our much smaller, open source community with a user-focused browser to compete with offerings from some of the largest, most dominant companies in the tech industry today.

Despite how mission critical release engineering is to most organizations, no one goes to school for release engineering. Release engineers seem to naturally assort themselves from more traditional developers by an emphasis on pipeline rather than product. The software delivery pipeline becomes *your* product.

Mozilla’s software delivery pipeline currently delivers feature releases to end users *every* 6 weeks on desktop and mobile. Beta builds get released more that once a week. Early access (Aurora) and developer (Nightly) builds get released every day. We average about 16 pushes/hour, or almost 8,000 pushes/month (March 2014). Every one of those pushes initiates a build-and-test cycle on our pool of over 4,700 machines, both real and virtual. All of the above needs to continue humming along in the face of increasing load while we work or systemic improvements or even replacements.

If you haven’t already run away screaming, you might be Mozilla release engineer material if you meet the following criteria:

* You’ve released a product for public consumption, preferably more than once.
* Your programming ability is above average. The particular language is irrelevant.
* You have a passion for open source, and have internalized the Mozilla mission.
* You understand configuration management for Windows, Mac, and/or Linux. You shuddered when you just read that requirement, but can keep it under control.
* You’ve worked with cloud providers, or are passionate about learning how to do so at scale.
* You’ve worked with REST APIs.
* You are an excellent communicator, and know how and when to use email, IRC, and video chat effectively.

We understand that technologies are tools, and that underlying concepts are larger than any single tool. In release engineering, we currently use a mix of python, buildbot, jenkins, shell scripting, hg, git and others, but this list is fluid and *will* change over time. You are expected to learn new tools as required, probably even on your first day.

The release engineering team at Mozilla is distributed across the world. Whether you happen to work in one of our many offices (multiple locations in Canada, China, France, Japan, New Zealand, Taiwan, the U.K., and the U.S.), or choose to work from your home, Mozilla *lives* online, and that is where all communication happens.


http://careers.mozilla.org/en-US/position/ohz2YfwA