Please be aware that this is an expired job ad, so the details shown here may now be out of date.
Academic research is often closed off to anyone who cannot afford the high subscription fees from paywall publishers. Even though your tax dollars paid for it, you often cannot gain access to the research, and neither can universities, researchers, and patients. PeerJ is a new Open Access journal [1,2,3], with backing from Tim O'Reilly, that is trying to change that.
We already have hundreds of high-profile academics that have joined our Editorial board, including four Nobel Laureates, in anticipation of our Autumn opening for submissions. We have a lot of exciting work to do in preparation for that milestone.
Located close to the "Silicon Roundabout" in the Shoreditch area of London, we are looking for a seasoned professional to join one of the most exciting startups happening at the intersection of tech and science today. You’ll be helping to shape the future of PeerJ’s systems and define our architecture. As one of the first engineers on board, you’ll help set the tone for all future hires and how things are accomplished. If you enjoy setting up and configuring Redis instances just as much as debugging loggers, then this is the job for you. This is a fantastic opportunity to be part of an exciting time in the history of science as we rethink how science should be communicated. You’ll work side by side with a technical CEO who knows what it is like to be a developer and writes code daily.
The ideal candidate brings expert knowledge or experience in working with AWS, scaling management, Redis notification and activity feeds, database management (both SQL and no-SQL), and linux server management. Additional background in python or PHP frameworks is desired, so that you can help hack your way around tying our services together. Java experience is bonus++.
We are offering top salary, stock options, a "take-what-you-need" holiday/vacation policy, and minimum £1,500 for your dev setup to be spent however you want every other year.
Ideally, get an intro via one of the current developers. Failing that, please send a one-page resumé highlighting what you've done recently. Supplementary links to past projects, Github, and the like are more than encouraged. Email to email@example.com.