Sr. Software Engineer, Vendor Semantics and Developer Experience (Remote)

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.

About the Role:

As the Senior Software Engineer, Vendor Semantics & Developer Experience, you will be the primary builder of a system that treats global infrastructure as a formal graph, where every node and edge is traced back to a versioned source of truth. Our Ontologists design the formal architecture of what truth looks like. Our Knowledge Engineers build the frameworks and transformation engines that make that truth computable. You are the engineer who keeps that system honest and keeps it usable.

Your domain is vendor semantic data: the OpenAPI, Swagger, and Smithy specifications that describe what cloud providers, security tools, and infrastructure platforms expose to the world. You build the systems that parse, track, validate, and canonicalize that information into a reliable source of truth. And you build the developer tooling that makes it possible for downstream product and ingest teams to work confidently against that truth.

This role is for someone who cares deeply about correctness, not just "does the code run" but "does the model mean what we think it means", and who understands that great internal tooling is a force multiplier for every team that touches this platform.

The Challenges You'll Solve

Hundreds of vendors publish API specifications, and they change constantly, inconsistently, and without warning. How do you build a system that tracks those changes, detects when a vendor's schema evolution breaks ontological assumptions, and surfaces that signal before downstream teams ship on a stale model? How do you give engineers a development experience that makes working with a complex knowledge graph feel tractable rather than treacherous? 

What You'll Do:

• Own the Vendor Schema Registry: You will build and maintain the systems that ingest, parse, and version vendor API specifications like OpenAPI, Swagger, Smithy, and others. You will track schema evolution across providers, detect breaking and semantic changes, and ensure that the canonical ontological model stays synchronized with the ground truth of what vendors actually expose.

• Build the Semantic Validation Pipeline: Correctness, not throughput, is your SLO. You will implement the validation systems that verify new and updated vendor schemas against the canonical ontology, catching mapping gaps, type conflicts, and semantic regressions before they propagate into the graph and mislead downstream consumers.

• Build the Developer Experience: You will design and maintain the internal tooling, SDKs, scaffolding, and documentation systems that make it fast and safe for product teams and ingest engineers to work with this knowledge platform. When a team needs to understand what a vendor resource maps to in the graph, or how to add support for a new provider, you are the reason they can do it with confidence and without lengthy onboarding.

• Close the Loop Between Schema and Graph: You will work closely with the Knowledge Engineers and Ontologists to translate real-world vendor schema constraints and edge cases into actionable input for the canonical model. When the messy reality of vendor APIs requires the ontology to flex, you are the one who surfaces that tension clearly.

• Raise the Floor for Downstream Teams: Product groups and ingest teams build on top of what you maintain. You will invest in the documentation, tooling, and validation guardrails that allow those t