A stronger pay request begins with the job the employer is asking you to do. Establish its level, location and responsibilities, then bring evidence that matches those terms. A national salary headline or a credential-holder average can provide background, but neither tells the employer why your offer or current role belongs at a particular point in its range.
Ask for the applicable range first
Find out which level the vacancy fills and which geographic range applies to you. If the advertised range spans several levels or locations, ask for the narrower one before naming a target. The answer makes the rest of the conversation more concrete and reduces the chance of comparing different jobs.
Ask what distinguishes placement within the range. The employer may consider independent responsibility, relevant experience or particular skills. Request examples rather than assuming every certification, year in IT or lab project receives the same weight. A range is useful only when the recruiter can explain how it relates to the role.
For an internal review, ask for the current level definition and the responsibilities expected at the next level. A request based on a genuine expansion of work is different from a routine annual review. Make that distinction explicit so the discussion reaches the person who can approve the appropriate change.
Use occupation data as context
BLS's guide to using wage statistics in salary negotiations recommends examining occupation, industry and location. Follow that order when choosing a source. A security analyst estimate is a weak benchmark for a senior executive or a software engineering role simply because both involve protecting systems.
Keep the observation date and pay measure attached. The BLS wage-data guide points to different programs; an annual median wage and a survey mean total package are not equivalent. If you present both, explain why each is relevant rather than using the larger figure without its definition.
A source can still be useful when it does not settle your target. Use it to ask why the employer's range differs and which responsibilities it includes. A precise government figure does not make every offer below it inappropriate, especially when the dataset covers a different location or career stage.
Present work the employer can evaluate
Choose examples that show the responsibilities attached to the desired level. Explain the situation, the decision you owned and the outcome you can substantiate. For incident work, distinguish leading containment from assisting with log collection. For architecture, distinguish choosing a design from reviewing a standard checklist.
Keep confidential details out of the evidence. A sanitized description or a lab reconstruction can demonstrate judgment without revealing a client's or employer's systems. If the result involved a team, make your own contribution clear instead of claiming the whole outcome as an individual achievement.
Connect the evidence to the proposed work. A credential can support that connection, but CISSP and Security+ do not create fixed salary supplements. ISC2's CISSP experience rules also show why a certified-holder average contains experience differences before any effect of the exam is considered.
Make a request with an explanation
State the range or compensation change you are requesting and tie it to the employer's level and your relevant evidence. Keep the explanation short enough that the recruiter or manager can repeat it to an approver. A request that depends on a long list of unrelated survey averages is harder to assess.
If the employer cannot move base salary, ask which parts of the package are negotiable and compare them separately. A signing payment, target bonus, equity grant and paid training have different conditions. Our bonus and equity guide explains why a larger headline total may not provide the recurring cash you wanted.
Avoid trading a clear request for an undocumented promise. If the proposed alternative is a later review, ask what triggers it, who decides and when it occurs. A review is an opportunity to reconsider compensation, not a guaranteed increase unless the written agreement says otherwise.
Evaluate the response and your alternatives
An employer may explain a genuine range limit or may reveal that the role is leveled differently from what you expected. Use that information to decide whether the opportunity still fits. You do not need a universal negotiation success statistic to compare a defined offer with the alternatives available to you.
Consider the working arrangement alongside compensation. On-call duties, travel, location rules and support from the team can change your preference. Keep those judgments personal rather than claiming a standard cash value for every benefit or inconvenience.
For a first role, our entry-level pay article separates beginner offers from occupation percentiles. For an experienced worker changing sector, industry wage comparisons keep the job definition fixed.
Our view is to negotiate with evidence the employer can check and terms you can understand. Ask for the applicable range, explain the responsibility you can own and obtain any agreed change in writing. A defensible request is more useful than a promise that a particular phrase or certification produces the same raise for everyone.
Sources
- BLS wage data in negotiations: occupation/industry/location comparisons, checked October 2026
- BLS wage-data guide: selecting consistent wage measures, checked October 2026
- ISC2 CISSP experience: experience and certification selection, checked October 2026