// feature · benchmark

Learn from every rejection on the platform, not just your own.

Your tracker shows your history. Shared insights show the pool's. Every opt-in user contributes anonymized outcome data (no resume text, no names, no companies). Once the pool has enough data for a role category, you see patterns specific to it. Tips grounded in real opt-in outcomes for your role + level slice, sharpened as the pool grows.

In · Anonymized pool
Opt-in outcomes only
No names, no resume text
No company names
Month-level granularity
Surface
Out · Your dashboard insight
Senior Frontend roles:
TypeScript keeps showing up
as a common gap
in roles you have not landed
// how it works

How to use shared insights.

3 steps. Each one runs in seconds. Scroll in order.

  1. Step 01

    Opt in during onboarding

    A single toggle on your profile. Off by default. You can flip it on or off at any time and nothing new gets contributed while it is off.

  2. Step 02

    Every outcome you log contributes metadata

    When you mark a job as denied, offer, accepted, or interview-invite, the system writes an anonymized row: job title (normalized), experience level, which keyword categories were present, what outcome happened. Never resume text, never the company name, never anything identifying.

  3. Step 03

    The insights surface on your dashboard

    Once the pool has ten or more records for your role category, you see patterns specific to it. Below that threshold we show hardcoded default tips instead of noise from tiny samples (no AI call below the floor).

// worked example

What an insight looks like when it surfaces

One real example, same input reshaped two ways.

// context
You are a senior frontend engineer. You have logged three rejections this quarter. Keyword matches ranged 70% to 85%. You opted in to shared insights.
// insight served on your dashboard
For Senior Frontend Engineer roles in your level band:
  - TypeScript and testing skills (Jest, Playwright, Cypress) keep appearing as common gaps for candidates at your interview-invite rate.
  - Roles that list GraphQL alongside Apollo tend to be more selective about both showing on the resume.
  - Your own rejections: 2 of 3 were missing TypeScript. Worth a resume pass.

All insights pull from anonymized outcome rows. No company names. No resume text.
TakeawayNothing here names a user or a company. Every tip comes from opt-in outcome rows. Specific patterns only surface once enough people contribute to cross the threshold, and we sharpen them as the dataset grows.
// under the hood

The mechanics nobody hides.

You should be able to tell how a feature works before you trust it with your job search.

01

Zero PII ever

The shared insights table never stores a user ID, resume text, company name, or free-text notes. The schema is keyword categories, role normalization, experience level, and outcome. That is it.

02

Minimum-sample threshold

No insight shows below n >= 10 for the slice. Small-sample noise is worse than no insight at all. Below the threshold we fall back to general advice.

03

Freshness weighting

Older data weights down. The hiring market changes. An insight pulled mostly from 2024 should not carry the same weight as one pulled mostly from the last 90 days. Recent outcomes carry more signal.

04

Opt-in is explicit and reversible

You toggle it on. You can toggle it off and from that moment nothing new contributes. Past rows that already went to the shared pool stay (they are anonymous) but your future outcomes stop flowing.

// guardrails

What it deliberately does not do.

Honest limits read as trust signals. Hiding them does the opposite.

  • We do not share your resume, your job list, your company names, or anything identifying. Ever. Opt-in or not.
  • We do not show insights below the minimum-sample threshold. A pattern from 3 rejections is not a pattern.
  • We do not sell the insights pool. It is a product feature, not a data business.
// questions

Common questions.

If your question isn't here, email support and you'll hear back from the founder.

What exactly gets sent to the shared pool?

Normalized job title, experience level, which of a fixed set of keyword categories were present in your resume, and the outcome (interview invite, offer, denied). No resume text, no company name, no notes, no user identifier.

Can I turn it off after I turn it on?

Yes. The toggle is reversible. From the moment you turn it off, nothing new is contributed. Previously contributed rows stay in the pool because they are not tied to you, but nothing new flows.

When will I see insights for my role?

Once the pool has at least 10 rows for your role category and experience band. For common titles this happens quickly; for niche titles it may take longer.

Can non-Pro accounts see insights?

Yes, free accounts see the top insight for their role. Pro accounts see the full breakdown and historical trends.

How is this different from industry reports?

Industry reports tell you the average time-to-offer for a whole field. Shared insights tell you which specific skills correlate with callbacks for your exact title and level, using outcomes from people using the product today.

// try shared insights

Stop reading about it. Run it on a real job.

Create a free account in under a minute. First job tracked, first tailored resume, and first keyword breakdown all happen inside the onboarding flow.

No credit card · 2-minute setup · Cancel anytime