FeaturesSalary intelligence
Assess

Know what the person probably earns before you call.

A range estimated by company, title and seniority, with the confidence level stated. It feeds the acceptance prediction and blocks an unrealistic salary back at the definition of the role.

The problem

Why this exists

How it works today

You find out the salary expectation in the third conversation, after investing hours. Or worse: you find out in the offer that gets turned down, when both sides have already built expectations.

How it works with EVO

The estimate appears in the assessment, before the first contact. If the person probably earns above the role’s ceiling, you know that when deciding whether to reach out, and with what argument.

How it works

Salary intelligence from the inside

1The estimate

Four sources, and the confidence stated.

The model’s market knowledge, your organization’s own base that grows with every use, web research, and what you correct by hand. The result comes with a confidence level and the factors that weighed on it.

Your own base decays over time: data from two years ago weighs less than data from last month.

The estimate is never exposed in outreach. It is there for you to decide, not to negotiate with the person.
Salary estimate · Juliana Ferraz
Estimated rangeconfidence: medium
Candidate todayR$ 28–34k

monthly · estimated, CLT contract

Role offersR$ 22–28k

range published in the JD

↗ ~+18% above the ceilinglikely to ask for an upgrade at offer stage
Factors
current company (Nubank · large)3 years thereGPM senioritySão Paulo

A market estimate, not something the candidate declared. It crosses your own organization’s history with intelligence by title, company and seniority. It is never exposed in outreach.

2The effect on the role

It also blocks an unrealistic salary before the search starts.

When the role’s range falls below the local market, EVO opens a challenge during the definition of the description, with the number and the practical consequence of insisting.

It is the same data serving twice: to calibrate the expectation about the candidate and to question the expectation of the company.

EVO JD · phase 3 of 6, Challenge
✓ 1 Briefing✓ 2 Interview3 Challenge4 Drafting5 Audit
BLOCKERB2 · incoherent seniority
You asked for a "Senior Specialist", but described a management role.

Of the responsibilities we captured, six are people leadership: defining what each analyst works on, running development plans and 1:1s, and owning the team’s capacity.

The practical consequence: you will attract a strong IC who turns down the management part, or a manager who accepts and then asks for the title back. Both scenarios cost you a cycle.

Suggestion

Reclassify as Team Leader and keep the scope. The range goes up ~25%: salary intel estimates R$ 18–24k for a Discovery TL in São Paulo, against R$ 14–19k for a senior specialist.

"I want your confirmation on both blockers before I write. I am not drafting this with the wrong seniority."

Under the hood

Treated as an estimate, never as a fact

Salary data is the kind of number that gains undue authority once it appears on a screen. These are the caveats built in.

confEvery value carries its confidence level, and the screen shows when it is low
decayYour own base loses weight over time, in 12 and 24-month windows
currencyMulti-currency, with the local market considered explicitly
youYou correct the estimate once you know the real number, and the correction feeds the base
What comes next

How it fits into the rest of the journey

Bring a role that is hard to fill

It takes a real role to see EVO work, not a canned example.

Start using it