GRC and Security Compliance Lead
Deepgram · USA - Remote
About this role
## Company Overview Deepgram is the leading platform underpinning the emerging Voice AI economy, providing real-time APIs for **speech-to-text (STT)**, **text-to-speech (TTS)**, and building production-grade voice agents at scale. With **200,000+ developers** and **1,300+ organizations**, Deepgram powers voice offerings from companies including Twilio, Cloudflare, Sierra, Decagon, Vapi, Daily, Cresta, Granola, and Jack in the Box. Deepgram’s voice-native foundation models are available via **cloud APIs** or **self-hosted/on-premises** software, delivering high accuracy, low latency, and cost efficiency. Backed by a recent **Series C**, Deepgram has processed **50,000+ years of audio** and transcribed **1T+ words**. --- ## Operating Rhythm At Deepgram, an **AI-first mindset** is core to how teams operate, innovate, and measure performance. Team members are expected to: - Actively use and experiment with advanced AI tools - Integrate AI into everyday workflows (and even build AI into their work) - Adapt quickly to new models and modes - Continuously push what these technologies can do The pace is fast—change evolves quickly, and the role may not be a fit if you prefer highly prescriptive, traditional 9-to-5 work. --- ## The Opportunity: GRC and Security Compliance Lead Deepgram is seeking a **GRC and Security Compliance Lead** to own the **written and evidentiary backbone** of the company’s **security and privacy program**—the documentation and evidence that auditors, enterprise customers, and internal engineers rely on. ### What you’ll own - **Evidence** and **policies** - **Public posture documents** - A system to keep documentation and evidence **consistent** with each other ### Compliance & customer requirements you’ll support - **SOC 2** - **ISO 27001** - **PCI DSS** - Enterprise security questionnaires - Public commitments on data handling and model building Today, this work is spread across too few people—this role consolidates ownership. --- ## Why this GRC work is unique You’ll need to write unusually specific claims accurately because Deepgram’s control environment spans multiple deployment realities: - **Most infrastructure is bare metal** in **colocation datacenters** - Containerized with **Docker**, managed with **Ansible**, deployed via **GitHub Actions** - **AWS** used for overflow capacity and a small set of services - Controls span **physical + colocation**, **on-premise hosts**, and **cloud** (not a single shared-responsibility model) Deepgram also processes **audio**, often highly sensitive customer data, across multiple deployment models: - Hosted with **model-improvement opted in** - Hosted with **model-improvement opted out** (effectively **zero data retention**) - **Single-tenant Deepgram Dedicated** deployments with **regional data residency** - **Fully self-hosted** deployments running in the customer’s environment Getting public statements right requires understanding **which claims apply to which deployment model**. --- *Note: The provided description appears truncated at the end (“Writing is the…”). If you share the remainder, I can format the full posting as well.*
Listing freshness
CronJobs last confirmed this listing 20h ago. If its source stops confirming the opening for seven days, this page is removed from active inventory.