Senior Engineering Manager, Backend (Content Foundations)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. "About The Team" could be part of "About the role"? Probably we can put under "About the role" the description of team and role.
But we need to preserve all substantive info. Let's extract:
About the role: description of role, responsibilities, etc.
Responsibilities: list of duties (What You'll Do). That's a list.
Requirements: maybe "You Have" section (required qualifications). That's 8+ years etc.
Qualifications: maybe "Preferred Skills". Could be separate.
Skills: maybe also "Preferred Skills"? Actually they have "Preferred Skills". Could be under Skills.
Benefits: list of benefits.
Pay: salary ranges.
Schedule: maybe not present; they mention Scribd Flex flexible work model, occasional in-person attendance required. That's schedule info. So we can include Schedule section with details about flexible work model and occasional in-person attendance.
We must not create sections with filler like "commensurate with experience". Not present.
We need to ensure we don't include boilerplate like EEO, privacy policy, accommodations, etc.
We must not repeat job title.
We must not include Job ID.
We must output only HTML fragment.
Let's craft:
About the role
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 culture, standards, and identity from its first days. And you'll be the partner the content organization plans around: running the team's roadmap as a product, making commitments other teams can build against, and representing the platform in decisions with product and engineering leaders across the company.
Then Responsibilities (Responsibilities
) with- items from "What You'll Do". Let's list each bullet: - 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. - Build state-of-the-art AI into the heart of the platform, partnering with ML and AI teams so that every document is understood, trusted, and enriched by intelligent systems from the moment it arrives, and is ready for both human readers and AI agents. - Turn platform capability into product impact, partnering with product to deliver the supply-side roadmap, make our content discoverable by readers, groundable by AI assistants and create visible wins for the contributors who grow the corpus. - Lead, grow, and inspire a founding team of backend and AI data engineers, shaping its culture, hiring, technical standards, and career growth from day one. - Run the team as a product, defining the roadmap, priorities, and commitments that teams across the content organization plan against, and building the operational excellence of a system the whole company depends on. - Champion security as first-class design principles, building a platform that safely processes untrusted content at massive scale and safeguards the corpus. - Influence across the organization, partnering with senior product and engineering leaders across trust & safety, content understanding, supply, and AI platform teams to sequence one shared content mission. We'll put each as
- .
Requirements (
Requirements
) from "You Have": - 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. Qualifications (Qualifications
) maybe we could treat "Preferred Skills" as Qualifications? But they have separate "Preferred Skills". Could map Qualifications to "You Have" (requirements) and Skills to "Preferred Skills". However they asked for both Requirements and Qualifications sections. We can put "You Have" as Requirements, and "Preferred Skills" as Qualifications (or Skills). But they also have Skills section. Let's decide: - Requirements: mandatory qualifications (You Have). - Qualifications: maybe also mandatory? Could be duplicate. But we can put "Preferred Skills" under Qualifications? Actually they have "Preferred Skills" heading. Could map to Skills section. And Qualifications could be empty? But we must not emit empty sections. So we need to decide which content goes where. We have: "You Have" (mandatory). "Preferred Skills" (optional). Also there is "At Scribd, Inc. your base pay is one part..." that's Pay. We could treat: - Requirements: You Have. - Qualifications: maybe we could include "Experience with document processing at scale..." etc as Qualifications (these are preferred but still qualifications). But they'd be similar to Skills. Better: Use Qualifications for "Preferred Skills" and Skills for maybe something else? But there is no other distinct skills list. Could combine Preferred Skills into Skills section and leave Qualifications empty? Not allowed. Thus we need to allocate content to both Qualifications and Skills meaningfully. Perhaps Qualifications: "Preferred Skills" (the list). Skills: maybe we could extract from "You Have" some skill items like "Depth in high-throughput distributed systems", "Enthusiasm for applied AI", etc. But those are already in Requirements. Alternatively, we could treat Qualifications as the "You Have" (mandatory) and Skills as the "Preferred Skills". That seems logical: Qualifications = required qualifications; Skills = preferred skills. Then Requirements could be responsibilities? But they already have Responsibilities separate. But they listed both Requirements and Qualifications as possible headings. Usually Requirements = mandatory qualifications, Qualifications = preferred qualifications. Skills = maybe technical skills. However we can map: - Requirements: "You Have" (mandatory). - Qualifications: maybe we could include "Experience with document processing at scale..." etc as Qualifications (these are preferred but still qualifications). But they'd overlap with Skills. Better: Use Requirements for "You Have". Use Qualifications for "Preferred Skills". Use Skills for maybe we could list specific technical skills from both sections? But that would duplicate. Given the instruction: "Prefer a few substantive sections over many thin ones." So we might combine Qualifications and Skills into one section if they overlap. But they ask to use headings for those specific names if we include them. We could include only Requirements and Skills, omitting Qualifications if no distinct content. But we need to decide. Let's examine the text: After "You Have" there is a paragraph about pay, then "Preferred Skills" heading with bullet list. So we have two distinct lists: mandatory and preferred. So we can map: - Requirements: Mandatory (You Have). - Qualifications: Preferred Skills (maybe they consider these as qualifications). But they also have Skills heading; we could put the same list under Skills and omit Qualifications. But we need to decide which heading to use. The instruction: "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not mandatory to use all. So we can choose which sections to include based on content. Thus we can include: - About the role - Responsibilities - Requirements (mandatory) - Skills (preferred) - Benefits - Pay - Schedule We can omit Qualifications because we don't have distinct content beyond Skills. Or we could treat Preferred Skills as Qualifications and not include Skills. But they'd be similar. I'll include Skills for the preferred skills list, and omit Qualifications. Now Benefits: list from "Benefits At Scribd, Inc." bullet list. Pay: salary ranges. Schedule: Scribd Flex flexible work model, occasional in-person attendance required. Let's extract benefits list: - 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 Now Pay: The text includes salary ranges with some formatting errors: "$187,5000 [minimum salary in our lowest geographic market within California]" seems typo: extra zero. Should be $187,500? We'll preserve as written? Probably we should keep exactly as given but maybe correct obvious typo? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The typo is part of the posting; we should keep it as is? It says "$187,5000". That's likely a mistake but it's substantive. We'll keep it. Thus Pay section:
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[