DataTalks.Club Podcast Wiki

Wiki

Salary Negotiation

How DataTalks.Club guests discuss salary conversations in data and AI hiring: ranges, current salary, market research, competing offers, recruiter transparency, and freelance pricing.

Related Wiki Pages

Job Search Hiring Job Descriptions CV Screening Career Growth Freelance

Salary negotiation is the part of a data or AI career conversation where people decide whether the money, level, risk, and work match. In the DataTalks.Club archive, it appears in recruiter screens and offer discussions. It also appears in job-description transparency and freelance pricing. It connects directly to Job Search, Hiring, and Job Descriptions.

The archive’s main definition is practical. Salary negotiation isn’t a way to extract an arbitrary number. It’s a market check, and candidates bring role fit. They also bring level, competing options, and evidence of value.

Employers bring salary bands, leveling, budget, and hiring urgency. Freelancers add a different calculation because they price risk, unpaid time, client acquisition, and project scope.

Common Definition

DataTalks.Club guests usually define salary negotiation as an early expectation-setting conversation that should stay connected to the role. In Hiring Data Scientists and Analysts, Alicja Notowska says around 36:25 that the recruiter screen covers notice period and availability. It also covers current interview activity and salary expectations. That makes compensation part of the hiring timeline, not only a final-offer topic.

Alicja’s advice at 40:33 separates current salary from expected compensation. Candidates don’t need to disclose current salary. They can ask how the company handles levels and bands before naming a range. If the company has clear bands, a low candidate number shouldn’t place a senior candidate under the senior band. If the company leaves pay mostly to negotiation, the candidate should be careful not to anchor too low.

Oleg Novikov gives the candidate-side version in Data Science Interview Guide. At 42:02, he frames offer evaluation around the full package and market comparison. At 50:17, he tells candidates with low current salary to avoid making the old number the reference point. The company has already interviewed the candidate and decided the candidate has value. The negotiation should be about that value and the new role.

Guest Differences

Guests agree that candidates should know the market, but they stress different risks. Alicja speaks from a recruiter workflow. She wants expectations early enough to avoid wasting time when the gap is too large.

At 45:05 in Hiring Data Scientists and Analysts, she says recruiters may ask what a high number is based on. Market data, Glassdoor-style salary reports, and other offers make the number easier to understand. A random high number can stop the process if the candidate treats it as a fixed demand.

Oleg focuses more on candidate power after the company has shown interest. His 50:17 advice in Data Science Interview Guide is to avoid revealing a weak anchor. He also asks what the company can do when the offer feels low.

The disagreement is mostly timing. Recruiters need enough information to manage the funnel, while candidates need enough context to avoid turning a low past salary into a low future salary.

Luke Whipps adds a recruiter transparency boundary in Land Data Scientist Roles. At 52:22, he says asking about salary early isn’t a red flag when candidates are trying to avoid wasted calls. He also treats low salary expectations as a possible signal that a candidate may be underpaid, not as proof of low value.

Tereza Iofciu pushes the company-side transparency point further in Data Science Jobs. At 37:08, she discusses salary ranges in job descriptions as a fairness and trust signal. Missing ranges can show internal pay problems, regional inconsistency, or weak hiring discipline. That links salary negotiation to Job Descriptions, not only to the final call with a recruiter.

Market Signals

The strongest salary signal in the archive is a range tied to evidence. Alicja recommends asking how the salary structure and leveling work before giving an expectation ([Hiring Data Scientists and Analysts](/podwiki/podcasts/hiring-data-scientists-and-analysts/, 40:33). The answer tells the candidate whether the company has a real compensation system or whether every candidate is negotiating from scratch.

Alicja says at 40:33 in Hiring Data Scientists and Analysts that candidates can update expectations after research or another offer. At 1:01:49 in the same episode, she asks them to keep recruiters informed when other offers or timing changes affect the process.

Market research matters because data titles vary. Oleg notes at 15:29 in Data Science Interview Guide that “data scientist” can mean product analytics, SQL-heavy experimentation, or production machine learning. Salary research should match the actual job, not only the title. Read this alongside Data Scientist Role, Data Engineer Role, and Data Science Careers.

Sarah Mestiri makes a similar argument from job-search strategy. At 20:01 in Tech Job Search Strategy, she tells candidates choosing between data engineering, MLOps, and ML engineering to study the job market. Target salary and target environment are part of that study. Compensation becomes one filter among skills, interests, and demand.

Job Search Advantage

Negotiating power starts before the offer. In Land Data Scientist Roles, Luke connects recruiter confidence to several signals at 16:15, 19:50, and 25:04. Clear CVs, industry alignment, project evidence, and business impact all matter. They make the candidate easier to place and easier for the hiring manager to justify.

Oleg gives a similar job-search loop in Data Science Interview Guide. At 13:24, he describes the typical funnel from recruiter screen to offer. At 18:28, he says the CV should work like a landing page. At 25:51, he asks candidates to show personal contribution and remove noise. Negotiation is stronger when the candidate has already shown fit for the specific role.

Competing offers create the clearest negotiating power. Oleg says at 42:02 that candidates should compare offer components and market baselines. At 50:17, he still gives options for candidates without another offer.

They can compare the offer with staying or declining. They can also ask how the company can bridge the gap. That keeps the conversation about the candidate’s decision, not about old salary.

Communication also affects negotiating power. Alicja warns at 1:01:49 in Hiring Data Scientists and Analysts that accepting an offer and reopening it later because another offer arrived damages trust. A candidate can keep options open, but shouldn’t create surprise after making a commitment. That advice connects salary negotiation to Career Growth because reputation continues after this one process.

Portfolio Proof

Portfolio proof gives candidates a reason to argue for the higher side of a range. Oleg says at 46:17 in Data Science Interview Guide that candidates without industry experience can create evidence through projects, writeups, and company-specific work. The project should show problem definition and modeling or analysis. It should also show evaluation, communication, and next steps.

Sarah makes portfolio work part of the job-search system. At 26:28 in Tech Job Search Strategy, she treats projects as skill validation that goes beyond course completion. At 59:46, she adds that explaining what you learned helps later in interviews. That public explanation can become negotiation evidence because it makes skill and judgment visible before the offer.

Luke’s recruiter advice gives the same signal. At 19:50 and 25:04 in Land Data Scientist Roles, he wants a portfolio to connect tools and projects to real use cases. Business impact is part of that connection. That’s why salary negotiation should link back to Machine Learning Portfolio Projects, Data Engineering Portfolio Projects, and Open Source Portfolio Evidence.

Portfolio proof doesn’t replace market data, but it makes the market argument credible. A candidate who asks for the top of a range should be able to show why the role, level, and demonstrated work support that number.

Freelance and Consulting Alternatives

Freelance and consulting pricing follows a different rule than salary negotiation. The candidate isn’t only pricing skill. They’re pricing availability and client risk. They’re also pricing unpaid selling time, taxes, legal setup, and the chance that the next project won’t appear immediately. That makes Freelance, Freelance Data Engineer, and Data Engineering Freelance adjacent pages rather than synonyms.

Adrian Brudaru explains the risk calculation in Freelance Data Engineering Playbook. At 7:06, he frames freelance income through occupancy rate. At 18:12, he discusses hourly rates and negotiation. At 53:02, he warns that charging the equivalent of a salary can fail because the freelancer also has occupancy risk and business overhead.

Dimitri Visnadi gives a channel-based pricing model in Becoming a Data Freelancer. At 25:24, he separates platform work, recruiter channels, and direct work. He also discusses other client-acquisition paths.

At 27:30 and 28:50, he recommends benchmarking against platform profiles and directories. Recruiter ranges and the client’s expected budget matter too. At 54:11, he adds runway planning before leaving employment.

Freelance guests differ from employment-focused guests on negotiation power. For employees, it often comes from competing offers, level fit, and the company’s band. For freelancers, it comes from positioning and proof. Network and client urgency matter too.

Dimitri says at 55:01 that people often misprice freelance work when they assume credentials alone justify high rates. Adrian says at 55:30 in Freelance Data Engineering Playbook that good clients expect proactivity, ownership, and outcomes.

These pages cover the surrounding career and hiring context.