This role can be based out of our New York City office or remotely in the US.
What you’ll do
Continue to build on existing automation to simplify the release process
Collaborate with team members to maintain a global view of cases that have been escalated to the Server Development teams and drive them forward to resolution
Manage the release of MongoDB to deliver critical fixes and major feature improvements
Investigate and summarize significant issues for internal and external users
Recognize patterns in a sea of information and take action accordingly
Anticipate potential user impact from identified issues and ensure solutions are prioritized
What you’ll need to succeed
Excellent technical communication skills to facilitate sound decision making
Proclivity to identify inefficiencies and automate manual processes
Technical ability to:
Quickly grok and clearly synthesize implications of system behavior
Contribute readily to tools written in Javascript, Python, or Go
Read and understand the intent of code and stack traces in many languages, especially C++
Past experience that would be nice to have
5+ years of experience in the field (combination of software engineering experience and release management)
Experience as a release manager of a very technical product
Experience delegating and prioritizing work without direct authority
Experience implementing and iterating new processes that require organizational buy-in
Familiarity with Github, Jira, and continuous integration testing
Technical aptitude in one or more of the following areas:
Systems, network, database administration
Consulting, technical support, or site reliability engineering
Experience administering large-scale production environments, including hardware, operating systems (Linux/Unix), networks (including firewalls and load balancers)
Interest in challenging technical issues central to databases: distributed systems, consensus algorithms, data replication, query optimization, data storage, OS internals, concurrency and scheduling, networking, etc.
In 3 Months:
You have made small improvements to our existing release automation
You have released patch versions of MongoDB
You have identified inefficiencies in our current release process as you ramped
In 6 Months:
You have scoped projects to improve our release tools and processes
You can take any bug report (regarding the database or the release tools) and work it to completion, either by working it yourself or knowing how to pull in additional help.
You have prepared talks about the release process targeted for different audiences
In 12 Months:
You have shadowed a major release of MongoDB and are ready to lead the next one
You have significantly improved the release process and its artifacts
You have begun effectively advocating for improvements outside of your domain