Director of Analytics Engineering

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Must not include sections with filler like "commensurate with experience". Must include Pay and Benefits only if posting actually states them. The posting includes pay ranges and benefits list. So we need Pay section with salary ranges. Benefits section with list. We also need sections: About the role (maybe from "The Role" paragraph). Responsibilities? The posting includes responsibilities described in "The Role" paragraph: building, scaling, leading team, establishing operating model, etc. Could treat as Responsibilities. Requirements/Essentials: list of essentials. Qualifications? Might be same as Essentials. Skills? Could be separate but we can combine. The instruction: prefer few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements, Benefits, Pay. Possibly also Skills? But we can embed skills within Requirements. Let's decide. We need to extract substantive content: - About Scribd, Inc. mission, culture, Scribd Flex, occasional in-person attendance required. That's about company. Could be "About the role" or "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put company info under About the role? Might be better as "About the role" includes description of role and team. But we have separate "The Role" paragraph. We'll put that under About the role. - Responsibilities: from "The Role" paragraph: building, scaling, leading high performing Analytics Engineering team, turning strong individual contributors into cohesive team, establishing operating model, fostering culture, creating technical foundations, strengthening team dynamics, ensuring great work recognized, creating career pathways, helping individuals navigate obstacles, distributing ownership, developing leaders, creating trusted environment, pragmatic approach, thinking in sequences, communication early and often, connecting analytics engineering investments to company priorities, communicating tradeoffs, contributing to decisions about data modeling, architecture, governance, quality, tooling, developer experience, approaching AI technologies with curiosity and pragmatism, building people and strengthening discipline. We can list as bullet list. - Requirements/Essentials: list of essentials (10+ years experience, 5+ years leading teams, proven track record, depth in building governed canonical data models, experience designing data quality etc., advanced SQL skills, production experience with modern data stack, demonstrated ability to lead cross functional data initiatives, strong judgment balancing immediate stakeholder needs with long term investments, excellent written and verbal communication). We'll put as bullet list. - Nice to Haves could be under Skills or Qualifications but we can maybe include as Skills section. But we can also omit if we want few sections. However we have Nice to Haves content: Advanced Python, leading data cleanup efforts, implementing RBAC and data retention, designing canonical data models for financial analysis, leading on-call rotations, coordinating incident response, resolving production issues, driving follow-up improvements. That's substantive. Could be under Skills. - Benefits: list: Scribd Flex, comprehensive health/dental/vision, mental health support and disability coverage, generous PTO including vacation, sick time, holidays, winter break, volunteer time, sabbaticals, paid parental leave and family support benefits, retirement matching and employee equity, learning and development programs, wellness and home office stipends, complimentary access to Scribd suite, enterprise access to leading AI tools. - Pay: salary ranges for SF, California, US outside CA, Canada. Provide as bullet list. - Schedule: Not mentioned besides occasional in-person attendance required. Could be under Schedule? The posting mentions occasional in-person attendance required for all employees. That's schedule info. Could include Schedule section with that detail. But we need to avoid filler. It's real specific: occasional in-person attendance required. So we can include Schedule section with that. We must not include boilerplate like EEO, privacy policy, accommodations, etc. Also remove duplicated lines, navigation, legal, etc. We must output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Skills

• ...
...

Benefits

• ...
...

Pay

• ...
...

Schedule

Occasional in‑person attendance is required for all employees.

Check that we didn't repeat job title. Good. Now need to ensure we preserve all substantive information. Let's extract details precisely. About the role: Should include description of team, mission, Scribd Flex, occasional in-person attendance? Actually that is schedule. But we can include company mission and culture in About the role. The posting starts: "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 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." That's about company. Then "So what are we looking for in new team members? At Scribd, Inc., we hire for “GRIT.” ..." That's about values. Then "This posting reflects an approved, open position within the organization. The Team Data & Analytics is building the DNA of an AI native Scribd, Inc. Bringing together Analytics Engineering, Data Science, and Data Analytics, D&A partners across product, technology, content, and the business to scale intelligence, advance understanding, shape strategy, and turn insight into lasting growth across our four brand portfolio. Making this ambition real at scale starts with Analytics Engineering. The team transforms fragmented data, inconsistent definitions, and dispersed analytical knowledge into trusted, reusable, production quality data foundations and products that enable intelligence to scale across the company. In partnership with Engineering, Analytics Engineers ensure critical data is captured, centralized, documented, secured, and governed. The team builds canonical datasets, shared metrics, and semantic layers, together with the quality, observability, lineage, and evaluation systems that make these assets trustworthy. On top of this foundation, Analytics Engineers develop AI agents and analytical tools that bring reliable intelligence directly into the decisions and workflows of teams across the company." That's about team and role. Then "The Role We’re hiring for a Director, Analytics Engineering to own scaling data for an AI native Scribd, Inc. You will build, scale, and lead a high performing Analytics Engineering team, turning strong individual contributors into a cohesive and highly effective team. This requires more than hiring and developing exceptional talent. It means establishing an operating model that creates structure without unnecessary bureaucracy, fostering culture and community that balances local priorities with the broader success of the company, and creating the technical foundations and standards of excellence that enable everyone to do their best work. Your leadership philosophy is grounded in service. A leader’s role is to provide clarity, create context, remove obstacles, and help others succeed. You will strengthen team dynamics, ensure great work is recognized, create meaningful career pathways, and help individuals navigate obstacles and opportunities throughout their careers. Durable teams are built by distributing ownership, developing leaders, and creating an environment where people feel trusted, supported, and accountable. Your pragmatic approach keeps the organization moving forward. Rather than waiting for an ideal end state, you will think in sequences and ask, “What is the right next version?” Communication happens early and often because transparency, thoughtful feedback, and visible decision making build trust and help teams move with confidence. Your strong strategic judgment is paired with enough proximity to the work to guide technical decisions credibly. You will connect analytics engineering investments to company priorities, communicate tradeoffs clearly to senior leaders, and contribute thoughtfully to decisions about data modeling, architecture, governance, quality, tooling, and developer experience. The transformation happening through AI is an opportunity to expand what talented teams can accomplish. Agentic coding, AI assisted development and analysis, and automated workflows can increase human judgment, creativity, and impact rather than replace them. You approach these technologies with curiosity and pragmatism, applying them where they create clear and measurable value. Above all, leadership is about building people and strengthening the discipline they share. Success is reflected in a team that grows more capable, confident, connected, and effective because of your leadership." That's responsibilities. Then "The Essentials" list. Then "The Nice to Haves" list. Then pay and benefits. Then "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. This includes surrounding metro areas or locations within a typical commuting distance: 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" That's location requirements; could be considered under Requirements or maybe separate but we can incorporate into Requirements as location eligibility. However the instruction says we can include Requirements section; we can add location as bullet. But we must not include boilerplate like "Get to Know Scribd, Inc. About Scribd, Inc. Life at Scribd, Inc. We want our interview process to be accessible..." etc. That's after benefits. We'll cut that. Now let's craft bullet points. About the role paragraph: combine mission, culture, Scribd Flex, occasional in-person attendance? Actually schedule separate. We'll include mission and culture and team description. Let's write:

Scribd, Inc. is on a mission to advance human understanding through its four products — Scribd®, Slideshare®, Everand™, and Fable — helping billions move beyond access into insight, application, and expertise. The company fosters a culture where employees can be real and bold, debate and commit, embrace plot twists, and are empowered to prioritize the customer. Scribd Flex gives employees flexibility to choose workstyle and location while committing to intentional in‑person moments that strengthen collaboration and culture. The Data & Analytics team is building the DNA of an AI‑native Scribd, uniting Analytics Engineering, Data Science, and Data Analytics to create trusted, reusable data foundations, canonical datasets, shared metrics, semantic layers, and AI‑driven tools that scale intelligence across the four brands.

That covers. Now Responsibilities bullet list: extract each responsibility sentence. - Build, scale, and lead a high‑performing Analytics Engineering team, turning strong individual contributors into a cohesive and highly effective team. - Establish an operating model that creates structure without unnecessary bureaucracy. - Foster culture and community that balances local priorities with the broader success of the company. - Create the technical foundations and standards of excellence that enable everyone to do their best work. - Strengthen team dynamics and ensure great work is recognized. - Create meaningful career pathways and help individuals navigate obstacles and opportunities throughout their careers. - Distribute ownership, develop leaders, and create an environment where people feel trusted, supported, and accountable. - Think in sequences and ask “What is the right next version?” rather than waiting for an ideal end state. - Communicate early and often, providing transparency, thoughtful feedback,