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!
The Publisher Content Management team maintains all of the premium content - ebooks, audiobooks, magazines and articles, and sheet music, that is available to Scribd subscribers. The work includes:
• Verifiably-correct ingestion of all publisher content
• Augmenting publisher content with external metadata sources and internally-built metadata• Ensuring correct availability of publisher content based for time-based, region-based, and other publisher restrictions.
• Managing the data pipelines and generated reports that are used to pay publishers.Scribd's premium content has been incredibly popular with Scribd users and thus is critical to both maintain the current pipelines and services as well as plan for future growth, both in publisher content library size and user consumption.
The team is based in our new San Francisco office. We use tools that emphasize asynchronous communication (Slack, Gitlab, Jira, Google Docs) but will also pair program or jump into a meeting room when those are the best approaches. Regardless of the medium, solid communication skills are a must. We operate with autonomy (developers closest to the code will make the most well-informed decisions) while holding ourselves and each other accountable for using good judgement when faced with each day's unique challenges.
Our technical work is divided between our user-facing Rails application and our offline data warehouse (where much of our processing is done on top of Spark). Many of the systems we're responsible for span both environments, so engineers regularly work within both. The resulting systems are data pipelines and services that we own and operate.
As the Manager of the Publisher Content Management team, your job will be to build and develop a team of engineers capable of ensuring the operational excellence of our existing systems while building new systems to meet the needs of our growing user base and content libraries. The responsibilities include:
• Management of the existing team of engineers, including 1:1s, career development, and performance reviews.
• Ownership of the team's interviewing, hiring, and onboarding processes.
• Ownership of the team's sprint process, including working with a project manager and company stakeholders to prioritize work and establish a consistent team velocity.
• Ownership of the team's long term roadmap, including working with stakeholders to identify user, publisher, and internal needs, develop ideas into tangible team projects, and bring the highest impact projects into the development process.
• Leadership through the software development lifecycle by establishing and maintaining a culture of ownership and accountability.
This is not a hands-on, in-the-code technical role. Though you were a highly-proficient software engineer earlier in your career, these skills are now used primarily to understand the work of your team. Your primary involvement with technical work will be during the technical design process and assisting in operational concerns. You'll frequently do code reviews and may occasionally pick up a small coding task.
In this role you're regularly work with stakeholders from:
• Content Acquisition, supporting their needs around current and future content deals.
• Content Operations, supporting their work to ingest and modify content according to business needs.
• Product, developing new features and experiences for our users.
• Engineering, providing metadata for other teams to build new and enhanced functionality.
Office or remote?
In this unprecedented time this role will start as full-time remote, as all of our employees are working from home. When everyone is able to return to the office we plan for this role to be located at our new office in San Francisco. However, if you have experience managing a team remotely we'll happily consider a remote role as well.
• 8+ years of experience as a professional software engineer
• 1+ years of experience as a software engineering manager or equivalent leadership experience
• Experience or a strong interest in backend systems and data pipelines
• Experience working with systems at Scribd's current scale
• Bachelor’s in CS or equivalent professional experience
Benefits & Perks of Life at Scribd
• Health & Welfare Benefits: Scribd pays 100% of employee’s Medical, Vision, and Dental premiums and 60% of dependents.
• Leaves: Paid Parental leave, and 100% company paid short-term/long-term disability plans
• 401k plan through Fidelity, plus company matching with no vesting period
• Stock Options - every employee is an owner in Scribd!
• Performance bonuses and Spot bonuses
• Generous Paid Time Off, Paid Holidays, Volunteer Day + office closure between Christmas Eve and New Years Day
• Catered meals - breakfast, lunch & dinner catered 5 days/week
• Referral bonuses
• Tuition Reimbursement
• Diversity, Equity & Inclusion programs
• Learning & Development and Coaching programs
• Monthly Wellness benefit + free onsite gym
• Luma by Concern, our mental health digital platform
• Work Life Balance flexibility
• Company events + Scribdchats
• Free subscription to Scribd + gift memberships for friends & family
Scribd is committed to equal employment opportunity regardless of race, religion, color, national origin, gender, sexual orientation, age, marital status, veteran status, disability status, or any other characteristic protected by law.
We encourage people of all backgrounds to apply. We believe that a diversity of perspectives and experiences create a foundation for the best ideas. Come join us in building something meaningful.