Sr. Manager, Engineering - Semantic Data Modeling Framework (Hybrid)
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. No Job ID.
We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate (EEO, legal, etc). Also remove duplicated lines, application instructions.
We need to include all substantive content from the posting: About the role paragraph, responsibilities list (What You'll Do), requirements list (What You'll Need), benefits list (Benefits Of Working At CrowdStrike), pay info.
We need to format as HTML fragment.
Let's extract content.
About The Role paragraph: "CrowdStrike's Data Platform team is expanding on the foundational infrastructure that powers the world's most advanced cybersecurity platform. We are seeking a Sr. Engineering Manager to lead the team responsible for the development, evolution, and enterprise-wide adoption of our ontology-based semantic data modeling framework. This is a critical system that enables consistent, interoperable, and intelligence-rich data representations across CrowdStrike's product portfolio, 3rd party and customer data modeling. In addition to being a deeply technical leadership role, success will require more than strong engineering execution. We are looking for a leader who can build excitement, drive adoption, and form strong partnerships with internal product teams, data producers, data consumers, security researchers, AI/ML teams, and customer-facing stakeholders. You will help make semantic modeling a practical, scalable, and widely adopted capability across CrowdStrike’s data ecosystem."
That's the about role.
What You'll Do: list of bullet points. Let's extract each bullet:
- Lead and grow a high-performing engineering team responsible for designing, building, and maintaining CrowdStrike's ontology-based semantic data modeling framework
- Define and own the end-to-end architecture for semantic modeling capabilities, including ontology design, schema management, validation, versioning, and integration with downstream data systems
- Drive the development of scalable, production-grade tooling and services that enable teams to define, discover, extend, and govern semantic data models across CrowdStrike's data ecosystem
- Establish engineering best practices around ontology governance, model lifecycle management, data quality, interoperability, and extensibility
- Partner with Data Platform architecture leadership to ensure alignment with cloud-native infrastructure, graph databases, streaming systems, and data lake/lakehouse architectures
- Evaluate and integrate emerging technologies and standards with a pragmatic, value-driven approach
- Define and execute a roadmap that drives measurable adoption of the semantic data modeling framework across CrowdStrike engineering
- Serve as the primary advocate and trusted advisor for ontology-based data modeling across the organization by translating complex semantic concepts into clear value propositions for assorted technical and non-technical audiences
- Build deep, consultative relationships with internal customer teams to understand their data modeling challenges, identify high-value use cases, and co-develop solutions that demonstrate framework value
- Develop enablement programs including documentation, training, workshops, office hours, and reference implementations that lower the barrier to adoption
- Create and communicate success metrics, adoption dashboards, and impact narratives to senior leadership
- Proactively identify friction points in the developer experience and prioritize improvements that accelerate time-to-value for adopting teams
- Define and communicate a clear multi-quarter vision and roadmap for the ontology framework, balancing platform innovation with customer-driven priorities
- Partner with product management, data engineering, threat graph, detection engineering, and AI/ML teams to identify high-leverage integration opportunities
- Maintain awareness of industry developments in ontology engineering, semantic technology, knowledge graphs, data mesh/data products, and AI-ready data architectures
- Translate CrowdStrike's cybersecurity domain complexity into well-structured, reusable, and extensible ontological models that improve data consistency, discoverability, and analytical power
- Build, lead, mentor, and develop an international team of engineers and ontology/data modeling specialists
- Foster a team culture of technical rigor, customer empathy, collaboration, and continuous improvement
- Attract and retain top talent through compelling vision, strong engineering culture, and meaningful career development
- Set clear goals, provide regular feedback, and create accountability aligned with both technical delivery and adoption outcomes
That's a long list.
What You'll Need:
- 10+ years of progressive software engineering experience, with 4+ years in engineering management leading teams of 6+ engineers
- Proven expertise in data modeling, ontology design, semantic modeling, knowledge graphs, or domain-driven data architecture
- Demonstrated experience building and shipping platforms, frameworks, or developer tools that required driving adoption across an engineering organization
- Strong understanding about technologies and standards such as: graph databases (e.g., Neo4j, Neptune, JanusGraph), RDF/OWL/SHACL/SPARQL, schema registries, metadata platforms, or semantic layers
- Experience with modern cloud-native data ecosystems (e.g., Kafka, Spark, Flink, data lake/lakehouse architectures, distributed systems)
- Solid design and problem-solving skills, with a clear passion for engineering excellence, quality, security, and performance
- Proven ability to influence and partner across organizational boundaries. Building trust, articulating value, and driving alignment with teams you don't directly control
- Excellent communication skills with the ability to present complex technical concepts clearly to engineers, data scientists, product managers, and senior executives
- Proven experience utilizing AI technologies to enhance decision-making, streamline workflows and processes, improve efficiency and drive business outcomes.
Benefits Of Working At CrowdStrike:
- Market leader in compensation and equity awards
- Comprehensive physical and mental wellness programs
- Competitive vacation and holidays for recharge
- Paid parental and adoption leaves
- Professional development opportunities for all employees regardless of level or role
- Employee Networks, geographic neighborhood groups, and volunteer opportunities to build connections
- Vibrant office culture with world class amenities
- Great Place to Work Certified™ across the globe
Pay: "The base salary range for this position for all U.S. candidates is $160,000 - $250,000 per year, with eligibility for bonuses, equity grants and a comprehensive benefits package that includes health insurance, 401k and paid time off."
We can put that in a Pay section as a
.
We need to avoid duplication: The benefits already mention comprehensive benefits; pay section mentions eligibility for bonuses, equity grants and comprehensive benefits package that includes health insurance, 401k and paid time off. That's okay.
We must not include boilerplate like EEO, equal opportunity, veterans, etc. Also remove "CrowdStrike is proud to be an equal opportunity employer..." etc. Also remove "Find out more about your rights as an applicant." etc. Also remove "CrowdStrike participates in the E-Verify program." etc. Also remove "Notice of E-Verify Participation Right to Work". Also remove "Placement within the pay range is dependent on a variety of factors..." maybe that's part of pay but it's generic; we could keep? It's somewhat generic but still specific. However instruction: remove duplicated lines, and application instructions. The sentence about placement within pay range is generic but still part of pay description. Might keep but it's not boilerplate? It's still part of the posting. However we might consider it as filler? It's not placeholder like "commensurate with experience". It's specific about factors. I'd keep it.
But we already have base salary range; we could add that sentence as part of Pay section.
We need to output only HTML fragment, no /. Use
headings.
Structure:
About the Role
...
Responsibilities
- ...
...
Requirements
- ...
...
Benefits
- ...
...
Pay
The base salary range for this position for all U.S. candidates is $160,000 - $250,000 per year, with eligibility for bonuses, equity grants and a comprehensive benefits package that includes health insurance, 401k and paid time off. Placement within the pay range is dependent on a variety of factors including, but not limited to, relevant work experience, skills, certifications, job level, supervisory status, and location.
We need to ensure we didn't miss any substantive info: The "About The Role" also includes earlier marketing fluff about CrowdStrike mission etc. Should we include that? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The initial paragraphs about CrowdStrike being global leader etc. Are they substantive? They are generic marketing but still part of posting. However the instruction also says: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The marketing fluff is not boilerplate; it's about company. Might be considered substantive? Usually they'd want to keep the "About the role" section only, not the generic company overview. But the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The company overview is substantive? It's not about the role. However the "About The Role" heading is used for the role description. The earlier paragraphs are not under a heading; they are just introductory fluff. Should we keep them? The instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect we will have an About the role section. The earlier fluff could be placed there as prose. It's not duplicated. I'd include it in the About the role paragraph.
Thus About the role paragraph should include both the introductory fluff and the specific role description. Let's combine:
"As a global leader in cybersecurity, CrowdStrike protects the people, processes and technologies that drive modern organizations. Since 2011, our mission hasn’t changed — we’re here to stop breaches, and we’ve redefined modern security with the world’s most advanced AI-native platform. We work on large scale distributed systems, processing almost 3 trillion events per day and this traffic is growing daily. Our customers span all industries, and they count on CrowdStrike to keep their businesses running, their communities safe and their lives moving forward. We're proud to work for a mission-driven company leveraging AI to transform the way we work. CrowdStrikers drive their careers through flexibility and autonomy while also being expected to contribute to a culture of responsible AI adoption, experimentation, and innovation. We use an AI-first mindset as a force multiplier to proactively and continuously accelerate execution, build expertise, uncover insights, and solve complex problems. We’re always looking to add talented CrowdStrikers to the team who have limitless passion, a relentless focus on innovation and a fanatical commitment to our customers, our community and each other. Ready to join a mission that matters? The future of cybersecurity starts with you. CrowdStrike's Data Platform team is expanding on the foundational infrastructure that powers the world's most advanced cybersecurity platform. We are seeking a Sr. Engineering Manager to lead the team responsible for the development, evolution, and enterprise-wide adoption of our ontology-based semantic data modeling framework. This is a critical system that enables consistent, interoperable, and intelligence-rich
for prose. We must not repeat job title as heading. No Job ID. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate (EEO, legal, etc). Also remove duplicated lines, application instructions. We need to include all substantive content from the posting: About the role paragraph, responsibilities list (What You'll Do), requirements list (What You'll Need), benefits list (Benefits Of Working At CrowdStrike), pay info. We need to format as HTML fragment. Let's extract content. About The Role paragraph: "CrowdStrike's Data Platform team is expanding on the foundational infrastructure that powers the world's most advanced cybersecurity platform. We are seeking a Sr. Engineering Manager to lead the team responsible for the development, evolution, and enterprise-wide adoption of our ontology-based semantic data modeling framework. This is a critical system that enables consistent, interoperable, and intelligence-rich data representations across CrowdStrike's product portfolio, 3rd party and customer data modeling. In addition to being a deeply technical leadership role, success will require more than strong engineering execution. We are looking for a leader who can build excitement, drive adoption, and form strong partnerships with internal product teams, data producers, data consumers, security researchers, AI/ML teams, and customer-facing stakeholders. You will help make semantic modeling a practical, scalable, and widely adopted capability across CrowdStrike’s data ecosystem." That's the about role. What You'll Do: list of bullet points. Let's extract each bullet: - Lead and grow a high-performing engineering team responsible for designing, building, and maintaining CrowdStrike's ontology-based semantic data modeling framework - Define and own the end-to-end architecture for semantic modeling capabilities, including ontology design, schema management, validation, versioning, and integration with downstream data systems - Drive the development of scalable, production-grade tooling and services that enable teams to define, discover, extend, and govern semantic data models across CrowdStrike's data ecosystem - Establish engineering best practices around ontology governance, model lifecycle management, data quality, interoperability, and extensibility - Partner with Data Platform architecture leadership to ensure alignment with cloud-native infrastructure, graph databases, streaming systems, and data lake/lakehouse architectures - Evaluate and integrate emerging technologies and standards with a pragmatic, value-driven approach - Define and execute a roadmap that drives measurable adoption of the semantic data modeling framework across CrowdStrike engineering - Serve as the primary advocate and trusted advisor for ontology-based data modeling across the organization by translating complex semantic concepts into clear value propositions for assorted technical and non-technical audiences - Build deep, consultative relationships with internal customer teams to understand their data modeling challenges, identify high-value use cases, and co-develop solutions that demonstrate framework value - Develop enablement programs including documentation, training, workshops, office hours, and reference implementations that lower the barrier to adoption - Create and communicate success metrics, adoption dashboards, and impact narratives to senior leadership - Proactively identify friction points in the developer experience and prioritize improvements that accelerate time-to-value for adopting teams - Define and communicate a clear multi-quarter vision and roadmap for the ontology framework, balancing platform innovation with customer-driven priorities - Partner with product management, data engineering, threat graph, detection engineering, and AI/ML teams to identify high-leverage integration opportunities - Maintain awareness of industry developments in ontology engineering, semantic technology, knowledge graphs, data mesh/data products, and AI-ready data architectures - Translate CrowdStrike's cybersecurity domain complexity into well-structured, reusable, and extensible ontological models that improve data consistency, discoverability, and analytical power - Build, lead, mentor, and develop an international team of engineers and ontology/data modeling specialists - Foster a team culture of technical rigor, customer empathy, collaboration, and continuous improvement - Attract and retain top talent through compelling vision, strong engineering culture, and meaningful career development - Set clear goals, provide regular feedback, and create accountability aligned with both technical delivery and adoption outcomes That's a long list. What You'll Need: - 10+ years of progressive software engineering experience, with 4+ years in engineering management leading teams of 6+ engineers - Proven expertise in data modeling, ontology design, semantic modeling, knowledge graphs, or domain-driven data architecture - Demonstrated experience building and shipping platforms, frameworks, or developer tools that required driving adoption across an engineering organization - Strong understanding about technologies and standards such as: graph databases (e.g., Neo4j, Neptune, JanusGraph), RDF/OWL/SHACL/SPARQL, schema registries, metadata platforms, or semantic layers - Experience with modern cloud-native data ecosystems (e.g., Kafka, Spark, Flink, data lake/lakehouse architectures, distributed systems) - Solid design and problem-solving skills, with a clear passion for engineering excellence, quality, security, and performance - Proven ability to influence and partner across organizational boundaries. Building trust, articulating value, and driving alignment with teams you don't directly control - Excellent communication skills with the ability to present complex technical concepts clearly to engineers, data scientists, product managers, and senior executives - Proven experience utilizing AI technologies to enhance decision-making, streamline workflows and processes, improve efficiency and drive business outcomes. Benefits Of Working At CrowdStrike: - Market leader in compensation and equity awards - Comprehensive physical and mental wellness programs - Competitive vacation and holidays for recharge - Paid parental and adoption leaves - Professional development opportunities for all employees regardless of level or role - Employee Networks, geographic neighborhood groups, and volunteer opportunities to build connections - Vibrant office culture with world class amenities - Great Place to Work Certified™ across the globe Pay: "The base salary range for this position for all U.S. candidates is $160,000 - $250,000 per year, with eligibility for bonuses, equity grants and a comprehensive benefits package that includes health insurance, 401k and paid time off." We can put that in a Pay section as a
. We need to avoid duplication: The benefits already mention comprehensive benefits; pay section mentions eligibility for bonuses, equity grants and comprehensive benefits package that includes health insurance, 401k and paid time off. That's okay. We must not include boilerplate like EEO, equal opportunity, veterans, etc. Also remove "CrowdStrike is proud to be an equal opportunity employer..." etc. Also remove "Find out more about your rights as an applicant." etc. Also remove "CrowdStrike participates in the E-Verify program." etc. Also remove "Notice of E-Verify Participation Right to Work". Also remove "Placement within the pay range is dependent on a variety of factors..." maybe that's part of pay but it's generic; we could keep? It's somewhat generic but still specific. However instruction: remove duplicated lines, and application instructions. The sentence about placement within pay range is generic but still part of pay description. Might keep but it's not boilerplate? It's still part of the posting. However we might consider it as filler? It's not placeholder like "commensurate with experience". It's specific about factors. I'd keep it. But we already have base salary range; we could add that sentence as part of Pay section. We need to output only HTML fragment, no /. Use
headings.
Structure:
About the Role
...
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...
Pay
The base salary range for this position for all U.S. candidates is $160,000 - $250,000 per year, with eligibility for bonuses, equity grants and a comprehensive benefits package that includes health insurance, 401k and paid time off. Placement within the pay range is dependent on a variety of factors including, but not limited to, relevant work experience, skills, certifications, job level, supervisory status, and location.
We need to ensure we didn't miss any substantive info: The "About The Role" also includes earlier marketing fluff about CrowdStrike mission etc. Should we include that? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The initial paragraphs about CrowdStrike being global leader etc. Are they substantive? They are generic marketing but still part of posting. However the instruction also says: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The marketing fluff is not boilerplate; it's about company. Might be considered substantive? Usually they'd want to keep the "About the role" section only, not the generic company overview. But the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The company overview is substantive? It's not about the role. However the "About The Role" heading is used for the role description. The earlier paragraphs are not under a heading; they are just introductory fluff. Should we keep them? The instruction says "Use