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 Content Understanding team's mission is to build metadata from and produce insights into the subject matter of, topics and categorization of, inter-corpus relations of each individual piece of content on Scribd. The work includes:

• Maintaining metadata extraction pipelines, storage of document metadata, and APIs exposing metadata to other Scribd systems.

• Analyzing uploaded documents for copyright infringement, spam, and other quality checks. 

• Maintaining systems that link documents to Scribd’s taxonomy and other classification systems. 

• Exposing all documents to search indexers through sitemaps. 

Scribd's ability to surface more relevant, topical, and personalized content to our users hinges on our ability to understand the content of each book, audiobook, article, and uploaded document. The output and success of the Content Understanding team is a strategic pillar of Scribd's continued and accelerating growth.

The team is split between our San Francisco headquarters and our Toronto 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. Though the tech stacks differ between environments, the engineering work in both is the same - create data pipelines to ingest, process, clean, and layout the metadata coming from publishers and other external sources, as well as create new metadata from our vast content base.

As the Tech Lead of the Content Understanding team, your job will be to provide hands-on technical leadership across all of the team's in-progress work as well as the team's technical roadmap. The responsibilities include:

• Leading the design, implementation, and delivery of your primary project.

• Consulting on and approving the technical design, project plan, and delivery schedule of all other team projects.

• Ensuring consistency of design, adherence to Scribd engineering principles and practices, and operational excellence across all team work.

• Working closely with the team's Engineering Manager to prioritize technical projects and improvements relative to requested feature work.

• Developing a long term roadmap for evolving team systems to support orders of magnitude growth of Scribd's subscribers, user uploads, and publisher content.

• Being a presence that makes every engineer on the team better.

As the responsibilities demonstrate, the Tech Lead role is more than just an advanced IC role. It is a hands-on leadership role, where you will balance the responsibilities of project work with team technical leadership. Your years of experience allow you to give guidance on projects you aren't deeply familiar with and quickly diagnose the root causes of bugs. You and the Engineering Manager will be a team, whereby your expertise and ability to handle daily technical blockers enables the Engineering Manager to focus on interviewing and hiring, people management, and project planning.

If these responsibilities match your interests (and excludes responsibilities you have no desire to perform) then you should apply!

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 this role is available at our new office in San Francisco or in our Toronto office. This position can also be fully remote for candidates with experience leading development remotely.

• 10+ years of experience as a professional software engineer

• 3+ years experience working with data pipelines

• Deep knowledge of common data architectures and industry technologies

• Bachelor’s in CS or equivalent professional experience

Core Infrastructure plays a fundamental role in both our on-premise infrastructure and our efforts to upgrade infrastructure towards AWS. As an infrastructure engineer you will be part of implementing the infrastructure to support the continued growth of Scribd's foundation. You will be part of the team which manages our existing on-premise datacenter, while helping service owners move into a newer AWS-centric model. You will help in this shift from a traditional operations organization into a services-organization which provides key components to our backend technology stack such as: container orchestration infrastructure, logging services, monitoring and alerting patterns, caching layers, and relational/non-relational clustered data storage. You and your team will educate developers and help delegate traditional operational responsibilities to teams which are already taking an increased level of ownership of their production environment. Sharing your experience and good judgement will be crucial to helping these teams scale their services operationally for years to come.

/skribbed/ (n).

1. a tech company changing the way the world reads

2. a membership that gives users access to the world’s largest online library of books, audiobooks, sheet music, news, and magazines

We value trying new things, craftsmanship, being an open book, and the people that make our team great.

Join us and build something meaningful.

The Content Engineering team is broadly responsible for catalog management and content metadata at Scribd. Supplying supplementary data to ebook and audiobook pages? That's us. Ensuring that all user-uploaded documents are useful, accessible, and legally available? That's us. Creating pipelines that build clean and well-structured data for Search, Recommendations, and Data Science to build amazing features from? That's us. Analyzing user reading activity and translating them into publisher payouts? That's us. We're a spoke within Scribd, connecting many engineering, product, and publisher-focused teams through data.

The majority of the team is based in San Francisco but there's a strong and growing remote contingent as well (much like Scribd overall). We use tools that emphasize asynchronous communication (Slack, Gitlab, Jira, Google Docs) and are ready and able to jump on a video call when text doesn't cut it. 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 - document spam detection, document copyright detection, topic extraction and classification, sitemap generation, and translating user activity into publisher payouts, just to name a few - span both environments, so engineers regularly work within both. Though the tech stacks differ between environments, the engineering work in both is the same - create data pipelines to ingest, process, clean, and layout the metadata coming from publishers and other external sources, as well as create new metadata from our vast content base.

As a Senior Backend Engineer, you've probably seen quite a bit in your career, and we want to leverage all of it. Software development will be your primary function, but we'll expect you to contribute in a number of ways, including advising on technical design, reviewing code, participating in interviews, and mentoring less experienced engineers

When you are doing software development, you'll be doing more than just coding a ticket handed to you. You'll own the implementation, delivery, and operation of systems, end-to-end. You'll consider testability, upgradeability, scale, and observability throughout the development process. You'll regularly have one or two engineers following your lead, whose output you will be responsible for. On Content Engineering, a Senior Backend Engineer is a leader.

If you've been a senior engineer for a while and have been more focused on architectural concerns, cross-team initiatives, and other strategic endeavors, we have a place for you as well. Just know that this is a code-heavy role

We have a wonderful new office in San Francisco, as well as smaller offices in Toronto and New York. If you live close to one of those you'll find great people and a nice work environment.

If you don't live near one of those offices, we'd still love to have you! Scribd is expanding its remote workforce with the goal of finding the best employees regardless of location. Being a remote employee means providing your own productive work environment. Being a remote employee means providing your own productive work environment, and everything else is pretty similar to being an office employee. We expect remote employees to have solid communication skills, good judgement, and demonstrable personal responsibility. We also expect the same from our in-office employees, so you'll be in good company.

Backend Engineers on Content Engineering typically have:

• 8+ years of experience as a professional software engineer

• 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

We present these in order to detail the picture of what we're looking for. Of course, every engineer brings something unique to the table, and we like nothing more than finding a diamond in the rough.

• What’s your favorite book that you’ve read recently?

• In one sentence, why does this role appeal to you?

• We are located in downtown San Francisco, within walking distance of Caltrain and BART

• Health benefits: 100% employer covered Medical/Dental/Vision for regular, full-time employees

• Generous PTO policy plus we close for the last week in December

• 401k matching

• Paid Parental leave

• Monthly wellness budget and fully paid membership to our onsite fitness facility

• Professional development: generous annual budget for our employees to attend conferences, classes, and other events

• Three meals a day, catered from local restaurants

• Apple laptops and any equipment you want to customize your work station

• Free Scribd membership and a yearly reading stipend!

• Company events that include monthly happy hours and offsites (past events include Santa Cruz, bowling, arcades, geocaching, ropes courses, etc.)

In the meantime, check out our office and meet some of the team at https://www.scribd.com/about

/skribbed/ (n).

1. a tech company changing the way the world reads

2. a membership that gives users access to the world’s largest online library of books, audiobooks, sheet music, news, and magazines

We value trying new things, craftsmanship, being an open book, and the people that make our team great.

Join us and build something meaningful.

The Content Engineering team is broadly responsible for catalog management and content metadata at Scribd. Supplying supplementary data to ebook and audiobook pages? That's us. Ensuring that all user-uploaded documents are useful, accessible, and legally available? That's us. Creating pipelines that build clean and well-structured data for Search, Recommendations, and Data Science to build amazing features from? That's us. Analyzing user reading activity and translating them into publisher payouts? That's us. We're a spoke within Scribd, connecting many engineering, product, and publisher-focused teams through data.

The majority of the team is based in San Francisco but there's a strong and growing remote contingent as well (much like Scribd overall). We use tools that emphasize asynchronous communication (Slack, Gitlab, Jira, Google Docs) and are ready and able to jump on a video call when text doesn't cut it. 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 - document spam detection, document copyright detection, topic extraction and classification, sitemap generation, and translating user activity into publisher payouts, just to name a few - span both environments, so engineers regularly work within both. Though the tech stacks differ between environments, the engineering work in both is the same - create data pipelines to ingest, process, clean, and layout the metadata coming from publishers and other external sources, as well as create new metadata from our vast content base.

A Backend Engineer on Content Engineering can take many forms:

You may be a relatively new college or boot camp graduate, looking for your first job where you can learn the ropes from a team of experienced professionals. You have a place here. 

You may have a few years of experience and are looking for your next challenge. You have a place here. 

You may have built out a few systems alongside senior engineers and are ready to take on ownership of feature delivery. You have a place here. 

We look for engineers that aspire to learn and grow, that thrive on constructive feedback, and know they’ll be ready to step up when the opportunity presents itself. 

We have a wonderful new office in San Francisco, as well as smaller offices in Toronto and New York. If you live close to one of those you'll find great people and a nice work environment.

If you don't live near one of those offices, we'd still love to have you! Scribd is expanding its remote workforce with the goal of finding the best employees regardless of location. Being a remote employee means providing your own productive work environment. Being a remote employee means providing your own productive work environment, and everything else is pretty similar to being an office employee. We expect remote employees to have solid communication skills, good judgement, and demonstrable personal responsibility. We also expect the same from our in-office employees, so you'll be in good company.

Backend Engineers on Content Engineering typically have:

• 0-6+ years of experience as a professional software engineer

• Experience or a strong interest in backend systems and data pipelines

• Bachelor’s in CS or equivalent professional experience

We present these in order to detail the picture of what we're looking for. Of course, every engineer brings something unique to the table, and we like nothing more than finding a diamond in the rough.

• What’s your favorite book that you’ve read recently?

• In one sentence, why does this role appeal to you?

• We are located in downtown San Francisco, within walking distance of Caltrain and BART

• Health benefits: 100% employer covered Medical/Dental/Vision for regular, full-time employees

• Generous PTO policy plus we close for the last week in December

• 401k matching

• Paid Parental leave

• Monthly wellness budget and fully paid membership to our onsite fitness facility

• Professional development: generous annual budget for our employees to attend conferences, classes, and other events

• Three meals a day, catered from local restaurants

• Apple laptops and any equipment you want to customize your work station

• Free Scribd membership and a yearly reading stipend!

• Company events that include monthly happy hours and offsites (past events include Santa Cruz, bowling, arcades, geocaching, ropes courses, etc.)

In the meantime, check out our office and meet some of the team at https://www.scribd.com/about