I’ve held the role of Web Developer at Mozilla for a couple of years now, writing PHP and Python for various projects. But I haven’t written a single line of code in well over a month, which meant I had already transitioned into a new set of job responsibilities.
Many a Mozillian jokes that my new role is to unplug websites. While that is partially true, my real focus for the past couple months has been to interface with the various groups working on our websites to help drive each stage of website development for the Firefox 4 launch campaigns.
To make the transition official, I was gifted the job title of Web Production Manager and will have a team working with me to whip projects into shape: Mike Alexis, our web dev project manager, and 2 web production engineers, Austin King and Chris More. I can’t tell you how excited I am to work with all 3 of these guys.
Our initial task list looks something like this:
- Work with the Marketing, IT, QA, L10N, Security and Legal teams to document and fine-tune web development processes, as well as testing, launch and release procedures.
- Help product owners’ visions come to fruition by driving website development from instantiation, to launch, to release, to site retirement.
- Whiteboard, wireframe and prototype new features to help concepts become tangible.
- Ensure that all teams are involved in launch and campaign retrospectives, collectively celebrating our successes and learning from our mistakes.
- Wrangle the sprawl of over 170 Mozilla websites, ensuring that each has a product owner who monitors the success and validity of each website, and unplugging sites that no longer fit the Mozilla mission. Mwahaha.
- Re-engage the Mozilla community and enable them to better incubate solutions to problems facing the organization and its community, and celebrate them for doing so.
And of course, we’ll have the ever-present task of living, breathing and being the Mozilla mission, doing whatever it takes to do the right thing for the Mozilla Foundation and for the open web.