The setting
makes cloud-managed physical security systems for organizations with many sites. Its lets people manage doors, access schedules and user credentials from web and mobile devices.
A successful visitor interaction is not the same evidence as a recorded entry.
Audit-reporting drafts need useful context from calls without treating that context as proof of physical access.
Who you’d be doing this for
“The auditor asked who actually entered, and I had to explain that the call record only showed who answered.”
Riyad Aoun · Security Administrator · a character in this brief
Prepares access evidence for a facilities audit spanning several offices.
What is at stake
PM reviewers dispute seven claims in audit-reporting drafts because visitor calls don't clearly prove entry. You decide whether the checker can flag a missing entry record as a gap, or must leave that interpretation as a question for the PM.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- interaction context vs proof of entry
- edge-case coverage vs annotation noise
- consistent checks vs legitimate product uncertainty
- customer detail vs evidence minimization
Why Verkada
Intercom and Voice Directory evidence sits beside door records in specs that shape what security administrators can tell an auditor.
Written with these in mind
Not your kind of problem? 77 more at Verkada, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Verkada. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Senior Product Manager, Access Management (opens in a new tab)
- We expect you to build things to think, not only to write specs about them.
- Anything that changes who can open a physical door needs review, attribution, and a clean path to undo
- Lead Product Manager, Users & Permissions (opens in a new tab)
- Senior Product Manager, Intercom Calling (opens in a new tab)
- Today, conversational AI handles low-risk tasks like sharing basic information about a business and its policies (Info Desk) and finding the right tenant to call (Voice Directory).
- Calling is at the heart of the Intercom experience, and we need a product manager to own it end to end: every call, from the moment someone presses the button to the moment someone answers and helps them.
- Lead Product Manager, Connectivity / Gateways (opens in a new tab)
- Verkada's Connectivity products secure people and property in remote and edge environments.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these turns on crossing a deadline that can't be undone.
Seven of 24 checks for a host-pricing launch have disputed or outdated evidence.
You decide whether AI may mark reused evidence as met or must send that judgment to a program manager.
Engineers reviewing test software retrace result fields even when checks pass.
You decide whether AI can mark a path as covered from code analysis, or only after an executed test supports that claim.
Red-team checks found 6 of 180 polished statements merged assumptions from documents that conflict, with no signal to the reader.
You have to settle on a model and a review design before reporting season.
The same setting, from another role
Each is set around Verkada’s Access Control, written for a different role. They’re separate briefs, not the same scenario.
Vulnerability findings reach engineers without the controller context needed to judge their severity.
You have to decide where the route stops assembling firmware and exposure evidence for a finding and where an engineer takes over to set its severity.
Security and network objections are appearing after customers request deployment plans.
You must decide which evidence earns attention and which judgment stays with the Solutions Lead.
Late events leave security administrators with conflicting accounts of what a door did.
You must decide what AI can assemble and what engineers must verify before acting.
Other problems with a similar purpose
In each of these, as in this one, the aim is to find the real question hiding behind incomplete evidence and choose a reversible next step instead of guessing.
Product managers read homeowner, pro and metric evidence on urgent repairs separately and reach different conclusions.
You have to decide where the AI's clustering of that evidence stops and a product manager's framing of the problem begins before a test is shaped.
A major advertiser may move $1.5 million after finance disputes whether reported sales were incremental.
You must weigh a compelling cross-format growth case against the evidence each claim can support.
A 4,000-seat business program may not renew because executives dispute what learner progress proves.
You have to weigh a fast commercial save against claims the evidence cannot support.
