GRC and Security Compliance Lead

- Own audit evidence end to end for SOC 2, ISO 27001, and PCI DSS — what evidence is required, who produces it, where it lives, and whether it would actually satisfy a reviewer. Be the auditor's primary point of contact through fieldwork. - Own control mapping across frameworks. Build and maintain the crosswalk so one control and one piece of evidence satisfies SOC 2, ISO 27001, PCI DSS, and customer questionnaires — rather than running the same work three times. - Own the colocation and infrastructure vendor side of compliance: datacenter provider SOC reports and attestations, physical security and carve-out language, and how shared responsibility actually divides between us and each provider. - Own security questionnaires and the security sections of RFPs. Maintain the answer library, keep it current as the product changes, and know which answers to fight for and which to concede. - Author and own the lifecycle of our internal policies and standards: drafting, review and approval cycles, annual review, exceptions and carve-outs, and retiring what no longer reflects reality. - Own our public-facing posture documents — Trust Center content, the AI Safety statement, Model Cards (with Research), the Privacy Policy (with Legal), and the deployment-model and self-hosted documentation customers rely on during review. - Own the documentation system itself: where documents live, how they are versioned and reviewed, and how a customer-facing claim traces back to an internal source of truth. Nothing we say publicly should be unattributable. - Maintain accurate data flow maps and records of processing across hosted, dedicated, and self-hosted deployments — and own the process that keeps them accurate as the product changes. - Run compliance and security awareness training and enablement, including clear guidance to Sales Engineering on what they may and may not commit to on a customer call. - Partner with Security Engineering so evidence is generated once, by automation — from Ansible, GitHub, and our logging and monitoring stack — and reused, and flag where a manual evidence pull should become an automated one. - Support the privacy program: contribute to DPIAs and transfer impact assessments, subprocessor and vendor privacy reviews, and DSAR intake, in partnership with the Privacy Operations Lead.

- Substantial experience in GRC, security compliance, or technical compliance documentation — enough that you have carried at least one audit cycle end to end from the evidence side and owned the outcome. - Exceptional writer. This is the central requirement, not a soft skill. You can turn a messy technical reality into a document a skeptical auditor, customer, or engineer will accept. - Hands-on involvement in at least one formal audit — SOC 2, ISO 27001, or PCI DSS — as the person producing and defending evidence, not only as a reader of the report. - Experience mapping controls across more than one framework, and a real opinion about how to avoid duplicated compliance work. - Technically fluent and unintimidated: you can read an architecture diagram, follow a data flow through datacenter and cloud infrastructure, understand what a log line or a retention setting actually implies, and ask the question that exposes a gap — without needing someone to translate for you. - Startup-friendly judgment. You know which questionnaire answers are worth fighting for and which to concede, and when a policy needs a carve-out rather than a mandate. Controls and policies that ignore how the company actually ships get routed around, and we would rather you name the trade-off than write the ideal version. - Working knowledge of GDPR, CCPA/CPRA, and where AI regulation is heading — enough to write public posture documents that hold up. - Bias toward building systems and templates rather than becoming the person every request has to route through. - Comfortable with ambiguity and with making a defensible call when the standard is unsettled.

COMPANY OVERVIEW Deepgram is the leading platform underpinning the emerging trillion-dollar Voice AI economy, providing real-time APIs for speech-to-text (STT), text-to-speech (TTS), and building production-grade voice agents at scale. More than 200,000 developers and 1,300+ organizations build voice offerings that are ‘Powered by Deepgram’, including Twilio, Cloudflare, Sierra, Decagon, Vapi, Daily, Cresta, Granola, and Jack in the Box. Deepgram’s voice-native foundation models are accessed through cloud APIs or as self-hosted and on-premises software, with unmatched accuracy, low latency, and cost efficiency. Backed by a recent Series C led by leading global investors and strategic partners, Deepgram has processed over 50,000 years of audio and transcribed more than 1 trillion words. There is no organization in the world that understands voice better than Deepgram. COMPANY OPERATING RHYTHM At Deepgram, we expect an AI-first mindset—AI use and comfort aren’t optional, they’re core to how we operate, innovate, and measure performance. Every team member who works at Deepgram is expected to actively use and experiment with advanced AI tools, and even build your own into your everyday work. We measure how effectively AI is applied to deliver results, and consistent, creative use of the latest AI capabilities is key to success here. Candidates should be comfortable adopting new models and modes quickly, integrating AI into their workflows, and continuously pushing the boundaries of what these technologies can do. Additionally, we move at the pace of AI. Change is rapid, and you can expect your day-to-day work to evolve just as quickly. This may not be the right role if you’re not excited to experiment, adapt, think on your feet, and learn constantly, or if you’re seeking something highly prescriptive with a traditional 9-to-5. THE OPPORTUNITY Deepgram is looking for a GRC and Security Compliance Lead to own the written and evidentiary backbone of our security and privacy program — the documents and evidence that auditors, enterprise customers, and our own engineers rely on to know what we actually do. We hold SOC 2, ISO 27001, and PCI DSS obligations, we answer a steady stream of enterprise security questionnaires, and we publish public commitments about how we handle data and how our models are built. Today that work is spread across too few people. You will own it: the evidence, the policies, the public posture documents, and the system that keeps all three consistent with each other. Context matters here, because the claims you will be writing are unusually specific. Most of our infrastructure is bare metal in colocation datacenters — containerized on Docker, managed with Ansible, and deployed through GitHub Actions — with AWS used for overflow capacity and a small set of services. That means our control environment spans physical and colocation controls, on-premise hosts, and cloud, not a single cloud provider's shared-responsibility model. Deepgram also processes audio — often some of the most sensitive data our customers hold — across several 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, and fully self-hosted deployments running in the customer's own environment. Getting a public statement right means understanding which of those a given claim applies to. Writing is the core skill in this role, and we mean writing that survives a skeptical reader — an auditor, a Fortune 500 security reviewer, an engineer who knows the system better than you do. Where a claim needs technical verification, you define what has to be proven and partner with Security Engineering to prove it; you are not expected to do that engineering work yourself. This role reports to the Director of Information Security and works closely with Security Engineering, Legal, Research, and Solutions/Sales Engineering. We are open on level. Strong analyst-level and senior candidates are both in scope, and we will calibrate title, scope, and compensation to demonstrated experience. RESPONSIBILITIES - Own audit evidence end to end for SOC 2, ISO 27001, and PCI DSS — what evidence is required, who produces it, where it lives, and whether it would actually satisfy a reviewer. Be the auditor's primary point of contact through fieldwork. - Own control mapping across frameworks. Build and maintain the crosswalk so one control and one piece of evidence satisfies SOC 2, ISO 27001, PCI DSS, and customer questionnaires — rather than running the same work three times. - Own the colocation and infrastructure vendor side of compliance: datacenter provider SOC reports and attestations, physical security and carve-out language, and how shared responsibility actually divides between us and each provider. - Own security questionnaires and the security sections of RFPs. Maintain the answer library, keep it current as the product changes, and know which answers to fight for and which to concede. - Author and own the lifecycle of our internal policies and standards: drafting, review and approval cycles, annual review, exceptions and carve-outs, and retiring what no longer reflects reality. - Own our public-facing posture documents — Trust Center content, the AI Safety statement, Model Cards (with Research), the Privacy Policy (with Legal), and the deployment-model and self-hosted documentation customers rely on during review. - Own the documentation system itself: where documents live, how they are versioned and reviewed, and how a customer-facing claim traces back to an internal source of truth. Nothing we say publicly should be unattributable. - Maintain accurate data flow maps and records of processing across hosted, dedicated, and self-hosted deployments — and own the process that keeps them accurate as the product changes. - Run com