We value trying new things, craftsmanship, being an open book, and the people that make our team great.
Join us and build something meaningful.
About the Team
We’re responsible for keeping Scribd up, responsive, and secure. Our duties include configuration management with Chef, wrestling with tricky Rails bugs, big-data cluster wrangling with Hadoop, mitigating the logo-branded vulnerability du jour, wearing a DBA hat to the InnoDB rodeo, bomb-proofing the mad science lab that is our codebase and, very occasionally, sweeping up the pieces when everything blows up. (We don’t let that last happen often.)
We work on almost every part of our application stack, from the servers and storage through the databases and caches to the application itself. We write code ourselves, including deep in the guts of our product, and developers also come to us for technical guidance. You’ll not simply operate the systems, but be part of the system-building process from the start. We’ve all seen the “worked in dev, ops problem now” meme and reject that world-view.
We believe in continuously improving our skills and codebase, work/life balance, and doing things right over doing them fast. We’re looking for engineers who share these views and are interested in contributing their knowledge, skills, and sound technical judgement to a growing engineering organization. In return, we offer interesting problems, plenty of opportunity to influence key technical decisions, and the chance to top the office pinball high score table.
Our tools and technologies
Haven’t worked with precisely the same set of technologies we use, but you’ve used something broadly similar? No problem! We’re just as happy to talk FreeBSD or commiserate with your AIX and pains as we are to chat about CentOS.
About the Role
Why we work here