The setting
buys homes from sellers, prepares them, and resells them. Its offers those homes through online listings, with licensed real estate professionals who work with buyers' agents from offer to closing.
Quiet AWS roles leave reviewers choosing between unnecessary access and occasional closing needs.
CloudTrail records recent activity, while service owners describe responsibilities that outlast its observation window.
Who you’d be doing this for
“My agent asked who could sort out the closing exception, and I still didn't have an answer when the lender called.”
Sameer Saxena · Home buyer · a character in this brief
Depends on authorized staff being able to handle exceptions without exposing purchase information to people who no longer need access.
What is at stake
Security reviewers face 180 AWS grants, including quiet roles that owners say closing work still needs. You decide when AI can propose keep or revoke from recorded use, and when it must seek an owner's explanation before proposing either.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- recent activity vs occasional operational need
- complete ownership context vs service-owner interruption
- source corrections vs interpretation of existing records
- consistent proposals vs legitimate role exceptions
Why Opendoor
AWS access supports resale, title and escrow workloads where occasional operational exceptions still need authorized people.
Written with these in mind
Not your kind of problem? 18 more at Opendoor, 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 Opendoor. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Application Security Engineer (opens in a new tab)
- Define, build and operate Opendoor’s application vulnerability identification capability - the tooling, triage workflow and remediation techniques across our consumer products, internal admin tools and GraphQL API powering home acquisition, resale, mortgage, title and escrow.
- Turn the patterns you see into rules, lint checks, and CI guardrails so the next team doesn't make the same mistake.
- Infrastructure Security Engineer (opens in a new tab)
- Identity and Access: Okta, Duo, AWS Identity Center, Okta for Kubernetes, Platform SSO (macOS), HashiCorp Vault
- As our Infrastructure Security Engineer, you'll own the security of everything Opendoor runs on including multi-account AWS, Kubernetes clusters, the identity plane connecting every system, and the cloud workloads behind home acquisition, resale, mortgage, title, and escrow.
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 is about people starting something and never quite finishing it.
Security engineers must judge 240 production grants, including rarely used recovery access.
Where will you require an owner’s explanation before AI can propose revoking a quiet grant?
Security reviewers chase service owners for context before they can decide on each access-review item.
You decide whether an identity that looks routine in one system and privileged in another is ranked by the routing or goes straight to a reviewer to judge.
29% of recent governed-dataset requests ended in workspace-wide or owner-level grants, with purpose and scope unclear at decision time.
You have to keep access fast without locking in permissions that are expensive to unwind.
Other problems with a similar purpose
In each of these, as in this one, the aim is to engineer security-critical controls whose correctness holds up even when carefully examined by skeptics.
Held content can be classified in most samples, but nothing proves that every retrieval surface enforces the split.
You have to ship enforcement, define the proof, and get sign-off before the irreversible migration.
A controller trust-path concern must be addressed within seven days across occupied sites.
You must weigh stronger remote protection against the chance of disrupting reliable door access.
An automated grader for AI-generated Python passes 97% of tests, but reviewers found real errors in code it marked safe.
You have to decide what evidence clears this for launch, since the code runs against customer warehouse data.
