Software Engineer III, Core Services & Libraries (Remote, AUS)

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. 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 also a mission-driven company. We cultivate a culture that gives every CrowdStriker both the flexibility and autonomy to own their careers. 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 this role : The Core Services & Libraries team builds and owns the shared Go libraries and platform capabilities that CrowdStrike's engineering organization runs on. If an engineer needs to talk to a data store, publish a message, make a service call, manage feature rollouts, or handle failures gracefully — they reach for something this team built. You'll own foundational software that has to be right: well-designed APIs that tens of teams adopt, resilience patterns that hold up under real-world failure, and cloud abstractions that let services deploy anywhere without caring where. The scope is broad and growing — spanning data access, messaging, service communication, multi-cloud portability, observability, and security — with plans to extend beyond Go into other language ecosystems. What You’ll Do: Build and own shared libraries that engineers across the company depend on for data access, messaging, service communication, observability, and resilience Design APIs that get adopted — your interfaces need to be good enough that teams choose them over building their own; that means thoughtful defaults, clean abstractions, backward compatibility, and strong documentation Build multi-cloud abstractions that let services run across cloud providers and on-premise environments without vendor-specific code Design and implement resilience patterns — retries, circuit breakers, load shedding, graceful degradation — as reusable primitives that become the default for every service Build platform capabilities — feature management, traffic control, disaster recovery, and sharding as composable libraries Own the security posture of shared dependencies — keep foundational libraries current, remediate vulnerabilities, and ship secure defaults Participate in architectural governance — propose, review, and shepherd RFCs that set direction for the services ecosystem Advocate and consult — be a trusted advisor to engineering teams adopting shared libraries; help them make the right architectural choices, unblock integration challenges, and feed their needs back into the platform Partner with Data Services, Infrastructure, SRE, and Observability — your libraries sit on top of their platforms; build strong working relationships that keep shared libraries aligned with operational reality Operate what you build — on-call rotations, production triage, and using operational insight to make the libraries better What You’ll Need: Strong Go expertise — you've built production libraries or frameworks, or have deep experience designing APIs and abstractions consumed by other engineering teams Distributed systems depth — hands-on experience with message brokers, data stores, service communication frameworks, and the failure modes that come with distributed architectures Library and API design sensibility — you understand backward compatibility, versioning, migration paths, and what makes an API that developers actually want to use Cloud infrastructure experience — meaningful experience with at least one major cloud provider, ideally including multi-region or multi-cloud patterns Operational maturity — you've owned production reliability for systems you've built, debugged incidents under pressure, and turned those experiences into improvements 5+ years of software engineering experience, with meaningful time in platform, infrastructure, or developer tools Bonus Qualifications: Experience building or contributing to widely-adopted open source libraries Background in developer experience — migration tooling, documentation, developer portals Cost-conscious engineering — understanding how library defaults affect infrastructure spend at scale Deep knowledge of messaging system internals — consumer groups, partition strategies, delivery guarantees Multi-cloud migration experience — abstracting vendor-specific APIs behind clean interfaces Observability expertise — distributed tracing, metrics pipelines, structured logging Experience designing resilience primitives — rate limiting, circuit breakers, load shedding, retry budgets Experience with large-scale SDK migrations or safe deprecation o