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

CrowdStrike is a global cybersecurity company that protects organizations through an AI-native security platform. The Senior Software Engineer, Vendor Semantics and Developer Experience will build systems to ingest, version, validate, and canonicalize vendor API specifications while maintaining developer tooling, SDKs, documentation, and validation guardrails for downstream teams.

Responsibilities:

• 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 teams to move quickly without requiring deep knowledge of the underlying semantic systems

Requirements:

• • A strong software engineering background with hands-on experience building systems that parse, validate, and transform structured specifications or schemas at scale
• • Proficiency in Go, Rust, and/or Python; comfort in polyglot environments
• • Deep experience with API specification formats -- OpenAPI/Swagger, Smithy, JSON Schema, or similar, including parsing, diffing, and reasoning about schema evolution
• • A practical understanding of graph data models and the downstream consequences of upstream schema decisions
• • A demonstrated instinct for developer experience , you have built internal tooling, SDKs, or frameworks that other engineers actually used, and you measure success by their productivity
• • A rigorous, correctness-first engineering mindset: you think in terms of invariants, edge cases, and what happens when a vendor silently changes something
• • Proven experience utilizing AI technologies to enhance decision-making, streamline workflows and processes, improve efficiency and drive business outcomes
• • Experience building systems that track and diff API specification changes over time (schema registries, changelog automation, breaking-change detection)
• • Familiarity with semantic web technologies (RDF, SHACL, OWL, SPARQL) or ontology engineering toolchains
• • A background in infrastructure, cloud platform engineering, or security tooling , you know how cloud providers think about their APIs
• • Experience with declarative configuration systems or code generation pipelines that translate high-level intent into low-level artifacts
• • A track record of making complex internal systems more approachable , you have been the person who writes the tool or guide that makes an entire team faster