Head of Security

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: About Snorkel (two paragraphs repeated). Then "About The Role". Then "Key Responsibilities". Then "Who You Are" with subsections: Experience & Leadership, Technical Depth, Governance & Compliance, General. Then "Why This Role". Then "Be Your Best at Snorkel" repeated. Then salary range. We need to map to headings: About the role (maybe combine About Snorkel and About The Role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We have content for About the role: we can combine the "About Snorkel" and "About The Role" paragraphs. That's substantive. Responsibilities: we have "Key Responsibilities" with bullet-like paragraphs. We can turn each paragraph into

under

. Requirements: maybe we have "Who You Are" sections: Experience & Leadership, Technical Depth, Governance & Compliance, General. Those could be considered Requirements/Qualifications/Skills. We need to decide mapping. Qualifications: maybe the "General" bullet includes Bachelor's degree etc. Skills: maybe technical depth etc. We need to avoid filler like "commensurate with experience". Not present. We have Pay: salary range $252,000—$370,000 USD. So we can include Pay section with that. Schedule: not mentioned, so omit. Benefits: not explicitly mentioned; there is "Be Your Best at Snorkel" describing benefits like market proven solutions, robust funding, scaling rapidly, opportunities to shape priorities, etc. That could be considered benefits. But it's more about culture. However we have no explicit benefits like health insurance, etc. The instruction: only include section if posting has real specific content for it. The "Be Your Best at Snorkel" is somewhat generic but still describes benefits. Might be considered benefits. However it's repeated multiple times. Could include a Benefits section summarizing those points. But we must not invent or summarize away detail; we can preserve the substantive info. The text: "Joining Snorkel AI means becoming part of a company that has market proven solutions, robust funding, and is scaling rapidly—offering a unique combination of stability and the excitement of high growth. As a member of our team, you’ll have meaningful opportunities to shape priorities and initiatives, influence key strategic decisions, and directly impact our ongoing success. Whether you’re looking to deepen your technical expertise, explore leadership opportunities, or learn new skills across multiple functions, you’re fully supported in building your career in an environment designed for growth, learning, and shared success." That's descriptive of benefits. Could be included. But we also have "Why This Role" which is also descriptive. Might be considered part of About the role. We need to avoid duplication. We'll include About the role (combining About Snorkel and About The Role). Responsibilities (Key Responsibilities). Requirements (Experience & Leadership, Technical Depth, Governance & Compliance). Qualifications (General). Skills maybe we can merge into Requirements? But we need separate sections only if we have content. Could combine Technical Depth as Skills. Let's decide: - About the role: includes the two About Snorkel paragraphs and About The Role paragraph. - Responsibilities: Key Responsibilities paragraphs. - Requirements: Experience & Leadership paragraph. - Qualifications: General paragraph (Bachelor's degree etc). - Skills: Technical Depth paragraph (maybe also Governance & Compliance? but that is more qualifications). We'll put Technical Depth as Skills. - Benefits: "Be Your Best at Snorkel" paragraph (maybe include once). We'll include it. - Pay: Salary range. - Schedule: omit. We must not repeat job title as heading. Not include Job ID. We must remove boilerplate: EEO statements, accommodation requests, repeated equal opportunity lines, etc. We'll strip those. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact sentences? We can keep them as is, but we can format into

or

• . Must not omit any substantive detail. That is tricky: we must keep all info, but we can restructure into HTML. So we need to ensure we don't drop any sentences. Let's extract substantive paragraphs: From the posting: 1. About Snorkel (first paragraph): "About Snorkel At Snorkel, we believe meaningful AI doesn’t start with the model, it starts with the data. We’re on a mission to help enterprises transform expert knowledge into specialized AI at scale. The AI landscape has gone through incredible changes since 2015, when Snorkel started as a research project in the Stanford AI Lab, to the generative AI breakthroughs of today. But one thing has remained constant: the data you use to build AI is the key to achieving differentiation, high performance, and production-ready systems. We work with some of the world’s largest organizations to empower scientists, engineers, financial experts, product creators, journalists, and more to build custom AI with their data faster than ever before. Excited to help us redefine how AI is built? Apply to be the newest Snorkeler!" 2. About Snorkel (second duplicate): "About Snorkel Snorkel AI is the frontier AI data lab, helping teams build the data and environments behind high-performing frontier and agentic AI. We combine technology with research-driven AI data development to create datasets, benchmarks, evals, and custom solutions for real-world AI systems. Founded out of the Stanford AI Lab in 2019, Snorkel works with leading AI labs and enterprises to move from better data to better outcomes. Excited to help us redefine how AI is built? Apply to be the newest Snorkeler!" We can combine but need to keep both; we can just include both paragraphs. 3. About The Role: "About The Role Snorkel is hiring a Head of Security to build and lead our security function end-to-end — infrastructure security, application security, and governance, risk & compliance (GRC). You'll own the security function end-to-end — strategy, team, and execution — and operate as the primary security voice with customers, auditors, and the exec team. You'll report to the CTO. This is a builder's role: you'll take security from its current state to a mature, right-sized function as Snorkel scales, hiring and developing the team as needs grow." 4. Key Responsibilities (multiple paragraphs): - "Security Leadership & Team Building Define Snorkel's overall security strategy, goals, and roadmap across infrastructure, application, and compliance domainsBuild, hire, and lead a high-performing security organization — starting lean and scaling deliberately as the company and its risk surface growEstablish the operating cadence for security (metrics, reporting, incident response, risk register) and represent security posture to the executive team and board" But note there is no punctuation between sentences; we need to keep as is. Might be messy but we keep. - "Infrastructure & Cloud Security Own cloud security architecture and posture across AWS (and other cloud providers as adopted) — IAM, network segmentation, encryption, landing zone designDirect detection & response capabilities, threat modeling, and vulnerability management programsSet standards for secure infrastructure-as-code, CI/CD, and secrets management" - "Application Security Embed security into the product development lifecycle — secure design reviews, threat modeling for new features, and AI/ML-specific risks (data protection, model/prompt security, training pipeline integrity)Partner with Engineering and Product leadership to build security into the SDLC without blocking velocityOwn application security tooling and practices (SAST/DAST/SCA, pen testing, bug bounty)Design identity, access, and activity-monitoring controls that correctly handle Snorkel's non-employee marketplace workforce — external contractor (1099 or similar) experts accessing the platform. This population isn't in scope for standard employee compliance obligations, but provisioning, deprovisioning, access boundaries, and monitoring still need to work correctly for them" - "Governance, Risk & Compliance (GRC) Build and run Snorkel's compliance program (e.g., SOC 2, ISO 27001, and customer-driven frameworks) — own audits end-to-endEstablish enterprise risk management practices: risk register, third-party/vendor risk, policy frameworkServe as the primary security point of contact for customer security reviews and questionnaires" - "Executive & Cross-Functional Partnership Act as a trusted advisor to the CTO and executive team on security risk and investment tradeoffsPartner cross-functionally with Legal, Sales, Operations, and Engineering to unblock enterprise deals and support customer trust requirementsCommunicate security posture, incidents, and roadmap clearly to both technical and non-technical audiences" 5. Who You Are sections: - Experience & Leadership: "10+ years in technology security, including significant leadership experience; you've held director-level or above scopeTrack record building and scaling a security function from a founding stage (team of ~1) through a mature org (10–30+), ideally at a high-growth technology companyExperience owning security budget, vendor selection, and board/exec-level reporting" - Technical Depth: "Deep expertise across infrastructure/cloud security (AWS, IAM, network security, encryption) and application security (SDLC integration, threat modeling, AppSec tooling)Hands-on familiarity with modern security tooling: SIEM, EDR, CSPM, vulnerability managementExperience working with AI/ML-specific security risks (model security, data pipeline protection, prompt injection)" - Governance & Compliance: "Proven experience building and running compliance programs (SOC 2, ISO 27001, or equivalent) from the ground upComfortable as the face of security to customers during security reviews/audits, and to auditors during certification cycles" - General: "Bachelor's degree in Computer Science, Information Technology, or related field; advanced degree a plusExcellent written and verbal communication; able to flex between board-level summary and engineering-level depth" 6. Why This Role: "You'll have meaningful ownership over the infrastructure that determines how quickly Snorkel can experiment with, evaluate, and productionize new AI systems. This isn't a role focused on training a single model or maintaining traditional ML pipelines - you'll build the platform that makes large-scale AI experimentation possible. You'll work on some of the hardest emerging infrastructure problems in AI: operating non-deterministic systems reliably, reproducing agent behavior across environments, evaluating long-running trajectories, scaling simulations and experiments, and turning rapidly evolving research workflows into robust production systems. The architecture decisions made by this team will define how Snorkel builds and operates AI systems for years to come." 7. Be Your Best at Snorkel (first occurrence): "Joining Snorkel AI means becoming part of a company that has market proven solutions, robust funding, and is scaling rapidly—offering a unique combination of stability and the excitement of high growth. As a member of our team, you’ll have meaningful opportunities to shape priorities and initiatives, influence key strategic decisions, and directly impact our ongoing success. Whether you’re looking to deepen your technical expertise, explore leadership opportunities, or learn new skills across multiple functions, you’re fully supported in building your career in an environment designed for growth, learning, and shared success." Then there is EEO boilerplate etc which we remove. Then later another Be Your Best at Snorkel duplicate (same text). We'll include only once to avoid duplication but we must preserve all substantive info; duplicating is not substantive extra info, it's duplicate. We can drop duplicate as per instruction: remove duplicated lines. Then Salary range: "Actual compensation will be determined based on factors including skills, qualifications, experience, and geographic location. Salary range(s) for this role $252,000—$370,000 USD" We need