Product updates

Company updates

What changed in Quiet Search company workflows, why it matters, and where to find it.

Browse candidate updates

Clearer marketplace controls

Hiring and marketplace surfaces now make filters, actions, empty states, and status changes easier to understand.

MarketplaceAccessibilityCompany
Quiet Search Hiring workspace showing company-side marketplace controls

What changed

Company-side filters became real controls, clickable actions were repaired, and loading and error states were made more explicit.

Mobile layout, keyboard access, and marketplace state handling received the same usability pass as the candidate workflow.

Why it matters

A two-sided workflow needs to explain what is available, what is still private, and what action will happen next.

Find it in Quiet Search

Open Hiring for company-side work or Trust for verification and review boundaries.

Stronger account separation

Candidate, company, and operational records now have explicit per-user access boundaries throughout the marketplace data model.

Trust & privacyReliabilityCompany

What changed

Per-user isolation was enforced across hiring, watchlist, notification, entitlement, and profile data.

Marketplace tenant boundaries gained repeatable validation before release.

Why it matters

Private candidate proof and company workflows should never depend on an informal convention about which account can see a record.

Find it in Quiet Search

The protection is applied behind the Hiring, Trust, and account-specific marketplace surfaces.

Evidence-led employer workflows

Company-side review gained a clearer path from a hiring need to privacy-checked proof and human approval.

MarketplaceTrust & privacyCompany

What changed

The private employer workflow added bounded search, proof review, and safer capability checks without requiring paid data vendors.

Candidate proof validation and daily marketplace actions were connected into the same review path.

Why it matters

Company access should be earned through explicit proof and approval boundaries, not an opaque match or broad data exposure.

Find it in Quiet Search

Use Hiring for the company workflow and Trust to inspect verification and privacy state.

Validated Hiring and Trust workspaces

The private marketplace separated company action from proof review so each decision has a clearer owner and boundary.

MarketplaceTrust & privacyCompany

What changed

Hiring was rebuilt around validated talent requests, while Trust became a dedicated workspace for proof, review, and privacy controls.

Candidate-facing and company-facing states were modularized so sensitive evidence could stay behind explicit gates.

Why it matters

Separating action from verification makes it easier to see who can do what and where human review is still required.

Find it in Quiet Search

Open Hiring for company actions and Trust for proof review.

A hiring-signal inbox with receipts

Public hiring posts and proof integrations gained a dedicated review queue instead of blending into general market noise.

Hiring signalsTrust & privacyCompany

What changed

A company-side inbox was added for reviewing public hiring signals and their source context.

The proof marketplace began connecting public evidence to guarded review states.

Why it matters

Hiring evidence is only useful when reviewers can separate a genuine role or hiring post from unrelated promotion and service advertising.

Find it in Quiet Search

Open the Hiring signal inbox from the company workspace.

The private marketplace foundation

The first two-sided workflow connected candidate proof, company review, and operational controls behind private feature gates.

Early buildMarketplaceCompany

What changed

A dual-sided marketplace foundation, candidate proof flow, company review primitives, and operational controls were built behind private access gates.

Public social hiring signals were introduced as evidence inputs rather than direct claims about candidate or company intent.

Why it matters

This established the privacy and review boundaries needed before any company-facing workflow could be treated as more than an internal prototype.

Find it in Quiet Search

This is an archive milestone from the founder-used private build; it was not a public marketplace launch.