Senior Engineering Manager, Backend (Content Foundations)
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Must preserve all substantive info.
We need to parse the posting.
Key info:
- Location list: many cities (multiple). This is location info; maybe we can include as a short paragraph under something like "Locations" but not a required heading. Since we only output sections for headings defined, we could embed location info in a paragraph under About the role or maybe a separate section? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not limited to those, but we should use those headings when appropriate. We can also create other headings if needed? Probably stick to those.
We need to decide which sections have content.
- About the role: definitely content: description of role, responsibilities, etc. Could split into About the role (overview) and Responsibilities (list). The posting includes "What You'll Do" list of responsibilities. Also "You Have" list of requirements. Also "Preferred Skills". Also "Benefits". Also Pay info.
Thus we can have sections:
About the role
- paragraph summarizing role.
Responsibilities
- - items from "What You'll Do".
Requirements
- maybe combine "You Have" (mandatory) and maybe also "Preferred Skills" as separate? Could have Requirements (mandatory) and Qualifications (maybe same). But we have both Requirements and Qualifications headings possible. We could put mandatory under Requirements, preferred under Qualifications or Skills. The instruction says use headings like Requirements, Qualifications, Skills. So we can separate.
Thus:
- Requirements: mandatory experience (8+ years, 3+ years leading, depth in high-throughput distributed systems, enthusiasm for applied AI, platform-product mindset, security-minded approach, operational excellence, clear communication). Could be list.
- Qualifications: maybe education? Not specified. Could skip if no content. Better to not create empty heading.
- Skills: Preferred Skills list.
- Benefits: list from Benefits section.
- Pay: salary ranges.
- Schedule: maybe mention Scribd Flex and occasional in-person attendance required. That's schedule info. So we can have Schedule section.
We also need to include location info maybe as a paragraph under About the role or separate? Could add a short paragraph under About the role about locations.
We must not include boilerplate like "Apply now", "Posted on Sep 17, 2026", "See more open positions", etc. Also remove duplicated lines.
We must preserve all substantive information: need to keep the mission statement, culture description, Scribd Flex, occasional in-person attendance required, GRIT definition, About The Team content, About The Role description, responsibilities, requirements, preferred skills, pay ranges, benefits list, etc.
We must not invent or summarize away detail. Must keep specifics.
We need to be careful not to include navigation/legal/EEO etc. So remove lines about equal employment opportunity, privacy policy, accommodations, etc.
Also remove "Get to Know Scribd, Inc." etc.
Now craft HTML.
We'll start with About the role
then a containing overview: role as engineering manager for Content Foundations, mission, etc. Could also include location list.
Better to separate location maybe as its own paragraph.
But we must not create extra headings not in list unless needed. Could embed location in About the role paragraph.
Let's extract substantive paragraphs:
Mission: "Scribd, Inc. is on a mission to advance human understanding. Our four products — Scribd®, Slideshare®, Everand™, and Fable — help billions of people across the globe move beyond access and into insight, application, and expertise."
Culture: "Culture at Scribd, Inc. We support a culture where our employees can be real and be bold; where we debate and commit as we embrace plot twists; and where every employee is empowered to take action as we prioritize the customer. We believe the best work happens when individual flexibility is balanced with meaningful community connection. 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."
GRIT: "So what are we looking for in new team members? At Scribd, Inc., we hire for “GRIT.” Traditionally defined as the intersection of passion and perseverance toward long-term goals, GRIT reflects the mindset we expect from every employee. For us, it also serves as a practical framework for how we work: setting and achieving Goals, delivering Results within your role, contributing Innovative ideas and solutions, and strengthening the broader Team through collaboration and attitude."
About The Team: paragraph about Content Foundations.
About The Role: paragraph: "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 "The industry is redefining what document ingestion means...." Could be part of role description.
We could include that in About the role paragraph.
Now Responsibilities: list from "What You'll Do". Items:
- 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.
Now Requirements (mandatory): 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.
Now Preferred Skills: list:
- 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.
Now Benefits: list from "Benefits At Scribd, Inc.":
- 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: details:
- "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? Probably keep exactly as written. It says "$187,5000". We'll keep that.
Now Schedule: we have Scribd Flex and occasional in-person attendance required. Could put under Schedule.
Thus Schedule section:
Scribd Flex flexible work model allows employees to choose workstyle and location; occasional in-person attendance is required for all employees.
Now location list: many cities. Could embed in About the role paragraph or separate paragraph. Since we have no heading for Locations, we can add a short paragraph after About the role maybe.
We must not include boilerplate like "Posted on Sep 17, 2026", "Apply now", etc.
Now produce HTML fragment.
We'll need to ensure proper nesting: About the role
....
Responsibilities
... etc.
Make sure
About the role
- paragraph summarizing role.Responsibilities
-- items from "What You'll Do".
Requirements
- maybe combine "You Have" (mandatory) and maybe also "Preferred Skills" as separate? Could have Requirements (mandatory) and Qualifications (maybe same). But we have both Requirements and Qualifications headings possible. We could put mandatory under Requirements, preferred under Qualifications or Skills. The instruction says use headings like Requirements, Qualifications, Skills. So we can separate. Thus: - Requirements: mandatory experience (8+ years, 3+ years leading, depth in high-throughput distributed systems, enthusiasm for applied AI, platform-product mindset, security-minded approach, operational excellence, clear communication). Could be list. - Qualifications: maybe education? Not specified. Could skip if no content. Better to not create empty heading. - Skills: Preferred Skills list. - Benefits: list from Benefits section. - Pay: salary ranges. - Schedule: maybe mention Scribd Flex and occasional in-person attendance required. That's schedule info. So we can have Schedule section. We also need to include location info maybe as a paragraph under About the role or separate? Could add a short paragraph under About the role about locations. We must not include boilerplate like "Apply now", "Posted on Sep 17, 2026", "See more open positions", etc. Also remove duplicated lines. We must preserve all substantive information: need to keep the mission statement, culture description, Scribd Flex, occasional in-person attendance required, GRIT definition, About The Team content, About The Role description, responsibilities, requirements, preferred skills, pay ranges, benefits list, etc. We must not invent or summarize away detail. Must keep specifics. We need to be careful not to include navigation/legal/EEO etc. So remove lines about equal employment opportunity, privacy policy, accommodations, etc. Also remove "Get to Know Scribd, Inc." etc. Now craft HTML. We'll start withAbout the role
then acontaining overview: role as engineering manager for Content Foundations, mission, etc. Could also include location list. Better to separate location maybe as its own paragraph. But we must not create extra headings not in list unless needed. Could embed location in About the role paragraph. Let's extract substantive paragraphs: Mission: "Scribd, Inc. is on a mission to advance human understanding. Our four products — Scribd®, Slideshare®, Everand™, and Fable — help billions of people across the globe move beyond access and into insight, application, and expertise." Culture: "Culture at Scribd, Inc. We support a culture where our employees can be real and be bold; where we debate and commit as we embrace plot twists; and where every employee is empowered to take action as we prioritize the customer. We believe the best work happens when individual flexibility is balanced with meaningful community connection. 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." GRIT: "So what are we looking for in new team members? At Scribd, Inc., we hire for “GRIT.” Traditionally defined as the intersection of passion and perseverance toward long-term goals, GRIT reflects the mindset we expect from every employee. For us, it also serves as a practical framework for how we work: setting and achieving Goals, delivering Results within your role, contributing Innovative ideas and solutions, and strengthening the broader Team through collaboration and attitude." About The Team: paragraph about Content Foundations. About The Role: paragraph: "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 "The industry is redefining what document ingestion means...." Could be part of role description. We could include that in About the role paragraph. Now Responsibilities: list from "What You'll Do". Items: - 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. Now Requirements (mandatory): 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. Now Preferred Skills: list: - 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. Now Benefits: list from "Benefits At Scribd, Inc.": - 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: details: - "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? Probably keep exactly as written. It says "$187,5000". We'll keep that. Now Schedule: we have Scribd Flex and occasional in-person attendance required. Could put under Schedule. Thus Schedule section:
Scribd Flex flexible work model allows employees to choose workstyle and location; occasional in-person attendance is required for all employees.
Now location list: many cities. Could embed in About the role paragraph or separate paragraph. Since we have no heading for Locations, we can add a short paragraph after About the role maybe. We must not include boilerplate like "Posted on Sep 17, 2026", "Apply now", etc. Now produce HTML fragment. We'll need to ensure proper nesting:About the role
....
Responsibilities
- ... etc.
Make sure