Senior Engineering Manager, Backend (Content Foundations)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose.
Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings.
We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate etc.
We need to decide which sections to include: About the role (we have About The Role). Responsibilities (What You'll Do). Requirements (You Have). Qualifications? Could combine Requirements and Qualifications? The posting includes "You Have" (requirements) and "Preferred Skills". Could treat "You Have" as Requirements, "Preferred Skills" as Skills. Also we have About The Team maybe not needed as heading? The instruction says use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't require About The Team but we could include as a section if we want but not required. Probably better to include About The Role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Also maybe About The Team could be omitted as not in list; but we could still include but risk adding extra heading not in list? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exclusive. So we could add other headings if appropriate. But better to stick to those.
We need to preserve all substantive information: include details about team, mission, culture, etc. That's in About The Team and Culture sections. Could be placed under About the role? Might be better to have an "About the Team" section. But not required. However we must preserve all substantive information; if we omit About The Team, we lose that info. So we should include a section for About the Team. Could use heading "About the Team". That's not in the e.g list but seems okay.
Similarly, we have culture description at start. Could be part of About the Team or separate "Culture". But we can incorporate.
We need to avoid boilerplate like EEO, accommodation, privacy policy, etc. Remove those.
We need to remove duplicated lines.
Let's extract substantive content:
- Mission: Scribd, Inc. mission to advance human understanding. Products: Scribd®, Slideshare®, Everand™, Fable. Help billions move beyond access into insight, application, expertise.
- Culture: support culture where employees can be real and bold; debate and commit; embrace plot twists; empowered to take action; prioritize customer; best work when individual flexibility balanced with meaningful community connection. Scribd Flex empowers employees to choose workstyle and location that support best performance, while committing to intentional in-person moments that strengthen collaboration and culture. Occasional in-person attendance required for all employees, regardless of location.
- GRIT hiring framework: passion and perseverance toward long-term goals; also framework: setting and achieving Goals, delivering Results, contributing Innovative ideas, strengthening broader Team through collaboration and attitude.
- About The Team: Content Foundations newly formed team at center of biggest strategic investment. Behind UGC brands (Scribd and Slideshare) sits one of largest corpora of human-created knowledge: hundreds of millions of documents and presentations. Every piece passes through one system: uploaded, understood, transformed, served to millions of customers, and agents that cite it, ground it, learn from it. Content Foundations owns that system, its work lands in two places: powers product roadmap (faster uploads, richer document experiences, growth of corpus); operates as platform for teams that build on it: trust & safety, content understanding, supply, AI platform teams consume its interfaces. What this team ships translates directly into product outcomes for users and velocity for every team downstream. Content sits at top of strategy: engine of consumer brands and foundation of growth; ingestion platform is where all begins.
- About The Role: hiring engineering manager for Content Foundations to build and lead team that owns how content enters Scribd. Leadership role at intersection of large-scale data infrastructure and applied AI, carries three responsibilities in equal measure: technical leader for platform (setting vision for real-time, AI-native ingestion, making architectural calls evolving live high-scale system, holding quality and reliability bar for system whole company depends on); people leader for team (hiring, growing, inspiring group of backend and AI data engineers, shaping its culture, standards, identity from first days); partner the content organization plans around (running team's roadmap as a product, making commitments other teams can build against, representing platform in decisions with product and engineering leaders across company). Industry redefining document ingestion: documents can be parsed, classified, safety-checked, enriched in real time at moment of upload, before they ever reach a reader, with vision-language models and intelligent chunking replacing OCR and batch pipelines. You'll bring those capabilities into one of world's largest document platforms, with corpus scale to make it matter.
- What You'll Do (Responsibilities):
* Own the vision and strategy for how content enters Scribd, and lead evolution of one of world's largest document platforms into a real-time, AI-native ingestion system.
* Build state-of-the-art AI into heart of platform, partnering with ML and AI teams so that every document is understood, trusted, and enriched by intelligent systems from moment it arrives, and is ready for both human readers and AI agents.
* Turn platform capability into product impact, partnering with product to deliver supply-side roadmap, make content discoverable by readers, groundable by AI assistants and create visible wins for 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 roadmap, priorities, and commitments that teams across content organization plan against, and building 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 organization, partnering with senior product and engineering leaders across trust & safety, content understanding, supply, and AI platform teams to sequence one shared content mission.
- You Have (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 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.
* Platform-product mindset: built systems other teams and product surfaces depend on, and know how to design interfaces, SLAs.
* Security-minded approach to building systems: design for safe handling of untrusted input, least-privilege access, and data protection from start.
* Operational excellence: reliability, observability, and on-call health are first-class engineering work.
* Clear, direct communication with product, engineering, and cross-functional partners.
- Preferred 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.
- Pay: At Scribd, Inc. your base pay is one part of total compensation package and is determined within a range. Pay ranges based on local cost of labor benchmarks for each specific role, level, and geographic location. San Francisco is highest geographic market in US. In California, 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]. Note there's a typo: $187,5000 (extra zero). We must preserve as is? Probably keep exactly as written. In United States, outside of California, range between $154,500 [minimum] to $267,500 [maximum]. In Canada, range between $198,000 CAD [minimum] to $252,500 CAD [maximum]. They mention consider wide range of factors. Also eligible for competitive equity ownership, comprehensive generous benefits package.
- 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
- Schedule: Scribd Flex (flexible work model) and occasional in-person attendance required for all employees, regardless of location. So we can put Schedule section with that.
We must not include boilerplate like EEO, accommodation, privacy policy, etc.
Now produce HTML fragment with headings and appropriate content.
We need to decide ordering: maybe About the Team, About the Role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule.
We must use - for any list of duties/requirements/benefits. For prose use
.
We must not repeat job title as heading.
We must not include Job ID/requisition numbers.
We must preserve all substantive information; do not invent or summarize away detail.
We need to be careful to not lose any details: e.g., mention of "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." Also "Occasional in-person attendance is required for all Scribd, Inc. employees, regardless of location."
Also mention of GRIT framework details.
Also mention of "This posting reflects an approved, open position within the organization."
Also mention of "At Scribd, Inc. your base pay is one part of your total compensation package and is determined within a range." etc.
Also mention of "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."
Also mention of "This position is also eligible for a competitive equity ownership, and a comprehensive and generous benefits package."
Also mention of "Working at Scribd, Inc. Are you currently based in a location where Scribd, Inc. can employ you? Employees must have their primary residence in or near one of the following cities." That's location eligibility; we might include that
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate etc. We need to decide which sections to include: About the role (we have About The Role). Responsibilities (What You'll Do). Requirements (You Have). Qualifications? Could combine Requirements and Qualifications? The posting includes "You Have" (requirements) and "Preferred Skills". Could treat "You Have" as Requirements, "Preferred Skills" as Skills. Also we have About The Team maybe not needed as heading? The instruction says use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't require About The Team but we could include as a section if we want but not required. Probably better to include About The Role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Also maybe About The Team could be omitted as not in list; but we could still include but risk adding extra heading not in list? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exclusive. So we could add other headings if appropriate. But better to stick to those.
We need to preserve all substantive information: include details about team, mission, culture, etc. That's in About The Team and Culture sections. Could be placed under About the role? Might be better to have an "About the Team" section. But not required. However we must preserve all substantive information; if we omit About The Team, we lose that info. So we should include a section for About the Team. Could use heading "About the Team". That's not in the e.g list but seems okay.
Similarly, we have culture description at start. Could be part of About the Team or separate "Culture". But we can incorporate.
We need to avoid boilerplate like EEO, accommodation, privacy policy, etc. Remove those.
We need to remove duplicated lines.
Let's extract substantive content:
- Mission: Scribd, Inc. mission to advance human understanding. Products: Scribd®, Slideshare®, Everand™, Fable. Help billions move beyond access into insight, application, expertise.
- Culture: support culture where employees can be real and bold; debate and commit; embrace plot twists; empowered to take action; prioritize customer; best work when individual flexibility balanced with meaningful community connection. Scribd Flex empowers employees to choose workstyle and location that support best performance, while committing to intentional in-person moments that strengthen collaboration and culture. Occasional in-person attendance required for all employees, regardless of location.
- GRIT hiring framework: passion and perseverance toward long-term goals; also framework: setting and achieving Goals, delivering Results, contributing Innovative ideas, strengthening broader Team through collaboration and attitude.
- About The Team: Content Foundations newly formed team at center of biggest strategic investment. Behind UGC brands (Scribd and Slideshare) sits one of largest corpora of human-created knowledge: hundreds of millions of documents and presentations. Every piece passes through one system: uploaded, understood, transformed, served to millions of customers, and agents that cite it, ground it, learn from it. Content Foundations owns that system, its work lands in two places: powers product roadmap (faster uploads, richer document experiences, growth of corpus); operates as platform for teams that build on it: trust & safety, content understanding, supply, AI platform teams consume its interfaces. What this team ships translates directly into product outcomes for users and velocity for every team downstream. Content sits at top of strategy: engine of consumer brands and foundation of growth; ingestion platform is where all begins.
- About The Role: hiring engineering manager for Content Foundations to build and lead team that owns how content enters Scribd. Leadership role at intersection of large-scale data infrastructure and applied AI, carries three responsibilities in equal measure: technical leader for platform (setting vision for real-time, AI-native ingestion, making architectural calls evolving live high-scale system, holding quality and reliability bar for system whole company depends on); people leader for team (hiring, growing, inspiring group of backend and AI data engineers, shaping its culture, standards, identity from first days); partner the content organization plans around (running team's roadmap as a product, making commitments other teams can build against, representing platform in decisions with product and engineering leaders across company). Industry redefining document ingestion: documents can be parsed, classified, safety-checked, enriched in real time at moment of upload, before they ever reach a reader, with vision-language models and intelligent chunking replacing OCR and batch pipelines. You'll bring those capabilities into one of world's largest document platforms, with corpus scale to make it matter.
- What You'll Do (Responsibilities):
* Own the vision and strategy for how content enters Scribd, and lead evolution of one of world's largest document platforms into a real-time, AI-native ingestion system.
* Build state-of-the-art AI into heart of platform, partnering with ML and AI teams so that every document is understood, trusted, and enriched by intelligent systems from moment it arrives, and is ready for both human readers and AI agents.
* Turn platform capability into product impact, partnering with product to deliver supply-side roadmap, make content discoverable by readers, groundable by AI assistants and create visible wins for 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 roadmap, priorities, and commitments that teams across content organization plan against, and building 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 organization, partnering with senior product and engineering leaders across trust & safety, content understanding, supply, and AI platform teams to sequence one shared content mission.
- You Have (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 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.
* Platform-product mindset: built systems other teams and product surfaces depend on, and know how to design interfaces, SLAs.
* Security-minded approach to building systems: design for safe handling of untrusted input, least-privilege access, and data protection from start.
* Operational excellence: reliability, observability, and on-call health are first-class engineering work.
* Clear, direct communication with product, engineering, and cross-functional partners.
- Preferred 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.
- Pay: At Scribd, Inc. your base pay is one part of total compensation package and is determined within a range. Pay ranges based on local cost of labor benchmarks for each specific role, level, and geographic location. San Francisco is highest geographic market in US. In California, 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]. Note there's a typo: $187,5000 (extra zero). We must preserve as is? Probably keep exactly as written. In United States, outside of California, range between $154,500 [minimum] to $267,500 [maximum]. In Canada, range between $198,000 CAD [minimum] to $252,500 CAD [maximum]. They mention consider wide range of factors. Also eligible for competitive equity ownership, comprehensive generous benefits package.
- 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
- Schedule: Scribd Flex (flexible work model) and occasional in-person attendance required for all employees, regardless of location. So we can put Schedule section with that.
We must not include boilerplate like EEO, accommodation, privacy policy, etc.
Now produce HTML fragment with headings and appropriate content.
We need to decide ordering: maybe About the Team, About the Role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule.
We must use - for any list of duties/requirements/benefits. For prose use
.
We must not repeat job title as heading.
We must not include Job ID/requisition numbers.
We must preserve all substantive information; do not invent or summarize away detail.
We need to be careful to not lose any details: e.g., mention of "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." Also "Occasional in-person attendance is required for all Scribd, Inc. employees, regardless of location."
Also mention of GRIT framework details.
Also mention of "This posting reflects an approved, open position within the organization."
Also mention of "At Scribd, Inc. your base pay is one part of your total compensation package and is determined within a range." etc.
Also mention of "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."
Also mention of "This position is also eligible for a competitive equity ownership, and a comprehensive and generous benefits package."
Also mention of "Working at Scribd, Inc. Are you currently based in a location where Scribd, Inc. can employ you? Employees must have their primary residence in or near one of the following cities." That's location eligibility; we might include that
- for any list of duties/requirements/benefits. For prose use
. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must preserve all substantive information; do not invent or summarize away detail. We need to be careful to not lose any details: e.g., mention of "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." Also "Occasional in-person attendance is required for all Scribd, Inc. employees, regardless of location." Also mention of GRIT framework details. Also mention of "This posting reflects an approved, open position within the organization." Also mention of "At Scribd, Inc. your base pay is one part of your total compensation package and is determined within a range." etc. Also mention of "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." Also mention of "This position is also eligible for a competitive equity ownership, and a comprehensive and generous benefits package." Also mention of "Working at Scribd, Inc. Are you currently based in a location where Scribd, Inc. can employ you? Employees must have their primary residence in or near one of the following cities." That's location eligibility; we might include that