Unofficial. A job application for Deepgram’s Senior Product Manager, Enterprise role, built from public pages. Not affiliated with Deepgram.

Frictionless enterprise procurement, in twelve weeks.

Deepgram’s posting for Senior Product Manager, Enterprise asks for someone who can take that goal and derive a 12-week plan without asking what to do first. This is mine. I built it in one day from Deepgram’s public pages, with AI agents doing the reading.

The bottom lineDeepgram already has more of the enterprise package than a buyer’s security reviewer can see.
So the order isShow what exists. Then close the login and access gaps. Then start the slow federal work.
Done meansA reviewer gets from first visit to approval without emailing anyone at Deepgram.

What a security reviewer finds

The posting says buyers judge readiness as a package: identity, security, compliance and the experience their teams touch. This is that package as a reviewer meets it on Deepgram’s public pages, read on November 22, 2026.

Identity

Who can get in, and how the buyer controls it.

Roles and permissions
ShownThree fixed roles with a published list of what each can do.
ShownUnchanged. An auditor role is the first I would add later.
Single sign-on
Not foundNo documentation, changelog entry or pricing line.
Self-serveweek 4Documented, priced, and set up by the customer’s own admin.
Multi-factor login
Not foundA staff reply in July 2025 said there were no plans.
Shownweek 8Enforceable for a whole organization.
Service accounts
Not foundKeys belong to a person. The docs suggest a shared mailbox.
Shownweek 9Keys that belong to the project and survive staff changes.
Admin audit log
Not foundOnly request logs, kept 90 days.
Shownweek 10Role changes, key events and sign-ins, exportable.
Automated provisioning
Not foundNot documented.
Not foundCut from these twelve weeks. It follows single sign-on.

Security

How the service protects what it is sent.

Encryption
ShownTLS 1.3 in transit, AES-256 at rest.
ShownUnchanged.
Zero retention
ShownAvailable as a flag on each request.
Self-serveweek 7One account-level switch an admin sets.
Penetration-test summary
Not foundA yearly third-party assessment is mentioned. No summary or way to ask.
Request-onlyweek 5In the trust center, behind a click-through NDA.
Software bill of materials
Not foundNot in the docs, changelog or self-hosted repository.
Self-serveweek 11Published with every self-hosted release.

Compliance

The proof a procurement team files.

SOC 2 report
Request-onlyClaimed for Type 1 and 2. Three pages give three ways to ask.
Self-serveweek 4One route: the trust center, behind a click-through NDA.
Healthcare agreement
Request-onlyBy contact form, Enterprise plan only.
Self-serveweek 5Requested and signed in the trust center.
GDPR, CCPA, PCI
ShownStated on the docs and pricing pages.
ShownUnchanged.
FIPS 140-3
ShownValidated images for self-hosted since July 2026.
Shownweek 12Plus a plain statement of what holds for the hosted API.
FedRAMP
Not foundDeepgram’s own blog lists it as a limitation.
In motionweek 12A decision memo: tier, route and budget.

Experience

What the reviewer’s afternoon feels like.

Trust center
Not foundNo portal. Four static docs pages and one marketing page.
Self-serveweek 5Live, with documents, answers and status in one place.
Answered questionnaire
Not foundNot found.
Self-serveweek 6The standard cloud questionnaire, pre-filled and searchable.
Enterprise features on the pricing page
Not foundThe plan table compares rates only.
Shownweek 4Listed by plan.
Public pages agree with each other
Not foundThey disagree in eight places.
Shownweek 2Fixed, with an owner for each page.
Status page
ShownPublic, with 90-day uptime and alerts.
ShownUnchanged.
6shown2request-only12not found
17shown or self-serve1behind an NDA1in motion1not yet

“Not found” means not found on public pages. Deepgram may hold any of these privately. The buyer’s reviewer sees the same blank. Sources are on the evidence page.

The twelve weeks

Four phases that overlap. The first is cheap and fast on purpose: it tests this plan against what I cannot see from outside.

Weeks 1 to 2

Listen, rank, fix

The ranking on this page is an outsider’s. Two weeks with sales and security make it Deepgram’s.

  • Read the stalled deals with sales, and the last ten security questionnaires.Which missing piece stopped which deal, and what it was worth.SalesSecurity
  • Fix every place where public pages disagree.Eight today. Each is a page edit with a named owner. No engineering.Docs and site
  • Pick one route for compliance documents.Three pages give three routes today. One route goes on all of them now, before any portal exists.Docs and siteSecurity

How I will know. A ranked list of blockers with deal value beside each, agreed with the head of sales.

Weeks 3 to 6

Make it visible

Deepgram holds reports and agreements that buyers must ask a person for. Every rival I read runs a trust center.

  • A trust center, live.SOC 2 report and penetration-test summary behind a click-through NDA. Healthcare agreement, data processing agreement and subprocessor list self-serve.Docs and siteLegalSecurity
  • Single sign-on, launched properly.Documented, on the pricing page, and set up by the customer’s own admin.ConsoleDocs and site
  • An answered security questionnaire.The standard cloud questionnaire, pre-filled and searchable. ElevenLabs and OpenAI already publish theirs.SecurityDocs and site
  • Enterprise features on the pricing page.The plan table compares rates only. A buyer cannot tell which plan carries what.Docs and site

How I will know. Document requests handled by a person fall toward zero, and time in security review is measured for the first time.

Weeks 5 to 10

Close the access gaps

These are the questionnaire answers that are “no” today. Each ships in the Console with the product manager who owns it.

  • Multi-factor login an organization can enforce.The customer who asked in public needed it to pass an audit.Console
  • Service accounts.Keys that belong to the project. Today, removing a team member disables every key they created.ConsoleAPIs
  • An admin audit log.Who changed a role, made a key or signed in, exportable through the API.ConsoleAPIs
  • One switch for model training.Today, opting out is a flag on every request, or a call to Deepgram.ConsoleAPIs

How I will know. A buyer can answer the identity section of a questionnaire with yes, and point to where.

Weeks 8 to 12

Start the slow work

Federal readiness takes longer than twelve weeks. The job here is to start the clock on the right route.

  • A software bill of materials with every self-hosted release.Only one rival mentions one at all. Deepgram already ships FIPS-validated images, so this is a lead to extend.Self-hosted imagesSecurity
  • FedRAMP: a decision memo, not a promise.The 2026 rules add an entry tier that a SOC 2 Type II report qualifies for. The memo recommends a tier, a route and a budget.LeadershipSecurity
  • Say where FIPS applies.Validated images exist for self-hosted. State plainly what holds for the hosted API and for Dedicated.Docs and siteManaged endpoint

How I will know. Leadership decides on FedRAMP with real numbers, and self-hosted customers pull a bill of materials without asking.

What I would cut

  • Automated user provisioning.Only two rivals offer it. It follows single sign-on, not the other way round.
  • Custom roles.Three fixed roles answer most questionnaires. An auditor role is the first I would add.
  • ISO 27001.Four rivals claim it. It is an audit program that belongs to the security lead, not a product feature.
  • Full FedRAMP authorization.It takes longer than twelve weeks at any tier. The memo starts it.

What would change this plan

  • If most stalled deals are federal,the FedRAMP memo moves to week 3 and the access work waits.
  • If single sign-on is held back by quality, not staffing,its launch slips and the trust center goes first alone.
  • If security already has a trust center under way,I join that work instead of starting one.
  • If sales names a blocker that is not on this page,it goes to the top.

How I would measure it

Four numbers, reported every two weeks.

I can see no baseline for any of them from outside. Setting the baselines is week 1 work.

  • Days a deal spends in security review.The number this role exists to move.
  • Share of document requests served without a person.The trust center’s job.
  • Share of enterprise accounts on single sign-on with multi-factor login.Adoption, not launch.
  • Security questionnaires answered from the trust center alone.Each one is hours a sales engineer gets back.