Staff Software Engineer
Obsidian SecurityObsidian Security | Staff Software Engineer | Philadelphia or Palo Alto | Full-time | $176k-$196k + equity + 401k | https://job-boards.greenhouse.io/obsidiansecurity/jobs/51527...
We secure the SaaS apps companies actually run on: M365, Salesforce, and hundreds more. You’d be on the Threat product team working full-stack. That means browser extension code (content/background scripts, manifest v3, message passing), backend services chewing through millions of events, and the data pipelines feeding our detection engine. One day you’re in TypeScript debugging why a content script won’t capture form submissions on some vendor’s weird SPA. The next you’re in Python fixing a Kafka consumer that’s falling behind. Sometimes you’re in Rust optimizing a hot path in the telemetry collector.
Big current focus is shadow AI, i.e. catching when employees paste sensitive data into ChatGPT, Claude, or whatever LLM showed up this week. You’d build the systems that detect it.
Looking for ~8+ yrs experience, real browser knowledge (DOM, event loop, SPA routing, CORS, not just “I used React”), prior browser extension work, strong TypeScript, comfortable in Python, willing to write Rust, plus data-at-scale chops (event streaming, Postgres, Elasticsearch, Kafka). Bonus: AI security (prompt injection, exfiltration), detection engineering/SIEM, or security tooling.
Apply via the link above, or see all our open roles at https://www.obsidiansecurity.com/careers
Opens the company's application page
Listed via
hackernews_hiring
Similar roles
Design & Tech
Related reads from TCHNX
The Quiet Revolution in Local-First Software
As major platforms face outages and data breaches, a new generation of developers is building applications that prioritise local data storage and peer-to-peer sync, challenging the cloud-first orthodoxy that's dominated tech for two decades.
The Quiet Revolution in Edge AI: Why Your Next Computer Might Not Need the Cloud
As neural processing units become standard in consumer devices, we're witnessing a fundamental shift in how AI applications work. Local processing is no longer a fallback; it's becoming the preferred architecture.
The Rise of AI-Assisted Code Generation 2: Are Developers Becoming Prompt Engineers?
As AI coding assistants reshape software development, the industry grapples with a fundamental question: is writing code giving way to writing prompts? We examine how London's tech scene is adapting to this seismic shift.