Ruby Infrastructure Engineer

San Francisco OR Remote US/Canada
Engineering – Core Platform
At Scribd (pronounced “scribbed”), we believe reading is more important than ever. Join our cast of unique characters as we build the world’s largest and most fascinating digital library: giving subscribers access to a growing collection of ebooks, audiobooks, magazines, documents, and more.
In addition to works from major publishers and top authors, we also create our own original content exclusively for Scribd users.
Our community includes over 1M subscribers in more than 190 countries. Join us in turning screen time into quality time!

What You'll Do

You and your peers on the Ruby Infrastructure team will help Scribd adopt major ecosystem improvements such as Sorbet, new Rails versions, and interpreter releases. Measure and optimize performance across the thousands of requests per second served by Ruby at Scribd. Create libraries that encapsulate common Ruby application patterns and approaches. Open high quality pull requests to improve upstream projects like Sidekiq, Rails, and Ruby itself.

You will not be cleaning up other teams' Ruby applications, but rather working to make Ruby delightful.

You have
• Excellent written (English) communication skills.
• Ruby/Rails internals or systems-level knowledge.
• Rather than just being proficient in Rails, developers should understand how Rails was designed and put together.
• Familiar enough to drive large upgrades of Ruby and/or Rails; should be able to own the upgrade and refactoring process for gems as a result.
• Not love of Rails, but not hate of Rails either.
• An understanding that Rails is not a panacea for all problems, but a good solution for some problems.
• Familiarity with how ruby gems work.
• Ability to describe how at least one gem works / was built in detail.
• Ideally you've read the source code for at least a gem or two and can teach us something about how it comes together.
• Interest in sharing and learning from others in the large-scale Ruby and Rails communities.

Ideally you have
• Opinions on what pieces of "stock" Rails should be swapped out for what other components that are better for certain things.
• e.g. CoffeeScript, asset pipeline, etc
• An understanding, or desire to learn how ActiveRecord works from the inside out.
• Opinions on whether Rails should be "just for APIs" or serving web frontend code.
• Thoughts on the trade-offs between object serialization approaches, for example: RPC or RESTful JSON over HTTP.