Senior Engineering Manager, Backend (Content Foundations)

We need to output HTML fragment with sections: About the team? Actually headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real specific content. From posting: - About The Team (Content Foundations) – could be "About the team"? Not listed but we can use "About the team"? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings. We can also include "About the team"? Not in list; better to not include. So we need to map content to these headings. We have: - About the role: description of role, responsibilities etc. Could be "About the role" heading. - Responsibilities: list of what you'll do (bulleted). Could be under Responsibilities. - Requirements: "You Have" section (8+ years etc). Could be Requirements. - Qualifications: maybe "Preferred Skills" could be Qualifications or Skills. They have "Preferred Skills". Could be Skills. - Benefits: list of benefits. - Pay: salary ranges. - Schedule: maybe not present; there is Scribd Flex flexible work model, occasional in-person attendance required. That's schedule info. Could be Schedule. We need to avoid filler like "commensurate with experience". Not present. We must preserve all substantive info, not invent. We need to output only HTML fragment, no markdown fences. Let's extract content. About the role: The paragraph after "About The Role". We'll copy that text. Responsibilities: The bullet list under "What You'll Do". Each line starts with a verb. We'll put each as

. Requirements: The "You Have" bullet list (actually sentences). We'll list each requirement. Qualifications/Skills: The "Preferred Skills" bullet list. Benefits: The list under "Benefits At Scribd, Inc." includes items. Pay: Salary ranges paragraphs. Schedule: Scribd Flex description and occasional in-person attendance required. Also mention "Employees must have their primary residence in or near one of the following cities." That's location requirement maybe schedule? Could be schedule? Might be location. But schedule heading expects info about work hours, flexibility, remote etc. We have Scribd Flex flexible work model, occasional in-person attendance required. Also list of cities where employees must be based. That's location eligibility, not schedule. But we can put under Schedule: mention flexible work model, occasional in-person attendance required. Also maybe note location requirement? Might be better to put location under Schedule? Not ideal but we have no other heading. Could also put location under Requirements? But it's about eligibility. Might be considered part of Requirements? However we already have Requirements for experience. Could add a separate "Location" but not allowed. The instruction: include a section ONLY when posting has real, specific content for it. So we need Schedule section if there is schedule info. There is Scribd Flex (flexible work model) and occasional in-person attendance required. That's schedule. So we can include Schedule with that info. Location requirement maybe not schedule; but we could omit location info? Must preserve ALL substantive information. So we need to include location requirement somewhere. Could we put it under Requirements? It's a requirement for employment. Could be under Requirements as a bullet. That seems okay. So Requirements will include experience requirements plus location eligibility. Thus: - About the role: paragraph. - Responsibilities: bullet list of What You'll Do. - Requirements: bullet list of You Have + location eligibility (list of cities). Also maybe mention "Employees must have their primary residence in or near one of the following cities." plus list. - Qualifications: maybe we treat Preferred Skills as Skills. But we have both Skills and Qualifications headings. Could put Preferred Skills under Skills. Qualifications maybe we could put nothing? Better to avoid empty heading. So we will not include Qualifications heading if no specific content. We'll put Preferred Skills under Skills. - Benefits: bullet list. - Pay: paragraph(s) with salary ranges. - Schedule: paragraph about Scribd Flex and occasional in-person attendance. Now ensure we don't repeat job title. Let's craft HTML. We'll need to escape any special characters? Not needed. We'll produce:

About the role

...

Responsibilities

• Own the vision and strategy for how content enters Scribd, and lead the evolution of one of the world's largest document platforms into a real-time, AI-native ingestion system.
...

Requirements

• 8+ years in software engineering, including 3+ years leading backend, data-infrastructure, or platform engineering teams.
• Depth in high-throughput distributed systems and data pipelines: streaming and event-driven architectures, ingestion and transformation at scale, and the judgment to evolve a live, high-volume system toward real time while it keeps running.
• Enthusiasm for applied AI in production systems, with experience (or strong intent) integrating ML models, LLM-based document processing.
• A platform-product mindset: you've built systems other teams and product surfaces depend on, and you know how to design interfaces, SLAs.
• A security-minded approach to building systems: you design for safe handling of untrusted input, least-privilege access, and data protection from the start.
• Operational excellence: reliability, observability, and on-call health are first-class engineering work for you.
• Clear, direct communication with product, engineering, and cross-functional partners.
• Employees must have their primary residence in or near one of the following cities: United States Atlanta | Austin | Boston | Dallas | Denver | Chicago | Houston | Jacksonville | Los Angeles | Miami | New York City | Phoenix | Portland | Sacramento | Salt Lake City | San Diego | San Francisco | Seattle | Washington D.C. Canada Ottawa | Toronto | Vancouver Mexico Mexico City

But the city list is long; we could keep as is.

Skills

• Experience with document processing at scale: conversion pipelines, vision-language parsing, PDF and rich-document formats, media transcoding, or content-serving and streaming systems.
• Familiarity with RAG and retrieval infrastructure, such as chunking strategies, embedding pipelines, vector search, or grounding systems for LLMs and agents.
• Experience on UGC or marketplace platforms where content quality, trust, and scale intersect.
• Founding-manager experience: standing up a new team and its platform from a blank page.

Benefits

• Scribd Flex (flexible work model)
• Comprehensive health, dental, and vision coverage
• Mental health support and disability coverage
• Generous paid time off, including vacation, sick time, holidays, winter break, volunteer time, and sabbaticals
• Paid parental leave and family support benefits
• Retirement matching and employee equity
• Learning and development programs and professional growth opportunities
• Wellness and home office stipends
• Complimentary access to the Scribd, Inc. suite of products
• Enterprise access to leading AI tools

Pay

At Scribd, Inc. your base pay is one part of your total compensation package and is determined within a range. Our pay ranges are based on the local cost of labor benchmarks for each specific role, level, and geographic location. San Francisco is our highest geographic market in the United States. In the state of California, the reasonably expected salary range is between $187,5000 [minimum salary in our lowest geographic market within California] to $281,500 [maximum salary in our highest geographic market within California]. In the United States, outside of California, the reasonably expected salary range is between $154,500 [minimum salary in our lowest US geographic market outside of California] to $267,500 [maximum salary in our highest US geographic market outside of California]. In Canada, the reasonably expected salary range is between $198,000 CAD[minimum salary in our lowest geographic market] to $252,500 CAD[maximum salary in our highest geographic market]. We carefully consider a wide range of factors when determining compensation, including but not limited to experience; job-related skill sets; relevant education or training; and other business and organizational needs. The salary range listed is for the level at which this job has been scoped. In the event that you are considered for a different level, a higher or lower pay range would apply. This position is also eligible for a competitive equity ownership, and a comprehensive and generous benefits package.

Note there is a typo "$187,5000" (extra zero). We must preserve as is.

Schedule

Scribd Flex empowers employees to choose the workstyle and location that support their best performance, while committing to intentional in-person moments that strengthen collaboration and culture. Occasional in-person attendance is required for all Scribd, Inc. employees, regardless of location.

Check we didn't miss any substantive info: The "About The Team" content we omitted. That's substantive. We need to include it somewhere. Could be under About the role? But we already have About the role heading for role description. The About The Team content is about Content Foundations team. Could be included under About the role? Might be better to have a separate section but not allowed headings. Could we incorporate it into About the role paragraph? The About the role currently only includes the paragraph after "About The Role". We could expand About the role to also include the About The Team description as part of role context. That would preserve info. Let's do that: About the role heading will contain both the team description and role description. Thus About the role paragraph: combine the team description (starting "Content Foundations is a newly formed team...") and the role description ("We're hiring the engineering manager..."). We must ensure not to duplicate. Let's craft About the role paragraph:

Content Foundations is a newly formed team at the center of Scribd, Inc.'s biggest strategic investment. Behind our UGC brands (Scribd and Slideshare) sits one of the largest corpora of human-created knowledge anywhere: hundreds of millions of documents and presentations. Every piece of that knowledge passes through one system. It's uploaded, understood, transformed, and served to millions of customers, and agents that cite it, ground it, and learn from it. Content Foundations owns that system, and its work lands in two places at once. It powers the product roadmap: faster uploads, richer document experiences, and the growth of the corpus. And it operates as a platform for the teams that build on it: trust & safety, content understanding, supply, and AI platform teams all consume its interfaces. What this team ships translates directly into product outcomes for users and velocity for every team downstream. Content sits at the very top of Scribd, Inc.'s strategy: it's the engine of our consumer brands and the foundation of our growth, and the ingestion platform is where all of it begins. We're hiring the engineering manager for Content Foundations to build and lead the team that owns how content enters Scribd. This is a leadership role at the intersection of large-scale data infrastructure and applied AI, and it carries three responsibilities in equal measure. You'll be the technical leader for the platform: setting the vision for real-time, AI-native ingestion, making the architectural calls that evolve a live, high-scale system, and holding the quality and reliability bar for a system the whole company depends on. You'll be the people leader for the team: hiring, growing, and inspiring a group of backend and AI data engineers, and shaping its