Release Automation Engineer

Parity’s Polkadot blockchain implementation has seen 107 releases so far. On top of that the list of our releasable artifacts ranges from mobile apps to html-based offline desktop apps (yes, this is a thing).

Parity is looking for an industrious Release Automation Engineer to help us stay on top of that rather extensive release roadmap, and adhering to our rather rigorous security standards while doing so. (Yes, there are cleanroom builds. Yes, those happen on dedicated hardware in our physical possession.)

You will be taking our freshest codebases and turning them into shiny signature-wrapped binaries ready for the final QA round and publishing — then upload the result to appropriate locations, updating release notes and posting the announcements. And hopefully you won’t be doing this by hand, no — but automatedly, with style.

We expect that you :

• have a prior exposure to any reasonable build system (ideally this would be cargo, since we’re a Rust shop — but make will do).
• are fluent in bash — but bonus points if your weapon of choice is some other, more sane scripting language.
• are familiar with desktop software packaging — ideally finding certain comfort in maintaining old-school deb and rpm repos in the modern world of red-green deployments and html5-based webapps.
• have seen enough Linux internals to reason about choice of the libc version to link our software with.
• can figure out how to build software for Mac and Windows if necessary.
• can show us some advanced GPG trickery. (Yes, GPG is considered harmful. But it’s inevitable evil when it comes to release signing; you *will* be exposed. Let’s say it’s an occupational hazard.)
• know how to Docker your way around.
• are able to maintain security of our build systems and supply chains, knowing that there are threats out there who are advanced, persistent and are after us in particular.
• are a kind of person who finds The Checklist Manifesto book by Atul Gawande really inspiring.

You might get some extra points for your prior work on FOSS software and experience with blockchain systems — but not much else matters; definitely not your gender or nationality.