Getting paid below your level hurts twice. You feel the gap in compensation, and you also start second-guessing whether you can prove it well enough to push back. That is why being underpaid can go unaddressed for months without leading to a useful conversation. The friction is rarely just confidence. More often, the evidence is scattered, the comparison points are fuzzy, and the story sounds like frustration instead of a documented case.
For an IC, this gets worse when your strongest work is invisible in the places that matter. You keep fixing difficult problems, absorbing extra ownership, training newer teammates, or becoming the person everyone asks when something is blocked. If none of that is logged clearly, you may be carrying senior-level expectations with mid-level proof.
Mistake 1. Treating workload as proof by itself
A lot of people start here because the pain is real. You are busy, people rely on you, and your plate keeps expanding. But volume alone does not establish that you are underpaid. Companies can dismiss workload complaints as a prioritization problem, a staffing issue, or a temporary crunch.
What changes the conversation is showing that the work is not just more work, but higher-value work. That means documenting moments where you took ownership in ambiguity, handled decisions with broader consequences, improved a system others depend on, or delivered outcomes beyond the level you are paid for.
Replace a generic claim like "I do a lot" with a tighter record:
- work that expanded beyond your formal scope
- outcomes that stuck, not just tasks completed
- judgment calls you made without close supervision
- examples of teammates or partners relying on your expertise
Mistake 2. Using market pay talk without a role-specific case
External salary data can help frame the discussion, but it does not rescue a weak internal case. Even when compensation data is directionally useful, your manager still needs to explain why your pay should change inside your company, with your actual work as the basis.
This is where many compensation conversations stall. You show broad market references, but the internal evidence is thin. Your manager may agree in principle and still have nothing concrete to carry forward.
A stronger approach is to build from your work outward. Start with the responsibilities you actually carry, the impact those responsibilities create, and the proof that those patterns are consistent. Then, if you use external data at all, it supports the case instead of trying to substitute for it. The same holds for an internal comparison, such as learning that a newer hire earns close to what you do. That narrow gap may point to pay compression, but one figure cannot prove it on its own.
Mistake 3. Waiting until frustration spills over
By the time many people act on signs that they are underpaid, they are already irritated. That usually leads to a conversation shaped by pent-up emotion rather than clear evidence. The result is a discussion that feels urgent to you and blurry to everyone else.
The better move is to prepare before the conversation becomes loaded. Keep a running list of work examples that show scope, ownership, outcomes, and repeated reliance from others. Then when you ask about compensation, progression, or level expectations, you are not building the case live.
This matters even if compensation decisions are tied to review cycles. A calm, evidence-first discussion tends to travel further than one that sounds like accumulated resentment.
A compensation conversation gets stronger when another person can summarize your value without borrowing your emotion.
Mistake 4. Mixing effort, impact, and level into one blur
One reason a pay case gets deflected is that people describe everything at once. They talk about hours worked, difficulty, reliability, responsiveness, and outcomes as if those are interchangeable. They are not.
Effort says you worked hard. Impact says something improved because of your work. Level says the shape of your contribution matches a more advanced role, whether through scope, independence, complexity, or influence.
If you mix those together, your case becomes easy to deflect. Someone can praise your work ethic without addressing your level. Someone can acknowledge a good outcome without agreeing that the responsibility was materially different from your peers.
Break your evidence into cleaner categories instead:
- responsibilities you own that carry broader consequences
- decisions you make that others depend on
- outcomes tied to those decisions
- patterns that show this is repeatable, not a one-off stretch assignment
That structure helps in promotion discussions too. The same accomplishment can support a pay conversation, a self-review, or a case for expanded scope when the evidence is organized well.
Mistake 5. Bringing examples from memory instead of records
Memory usually keeps the headline and drops the useful details. You remember that you rescued a project, smoothed a launch, or rebuilt a broken process. You may not remember the exact constraint, who was blocked, what you changed, or what happened after.
That missing detail matters because compensation discussions often turn on credibility. Specifics help another person trust your read on your own contribution.
Keep a lightweight record as the work happens. Save the date, the context, what you owned, what changed, and any proof you can safely summarize. Do not copy restricted internal material into a personal tool, but do preserve enough detail that the example still holds up later.
This is where ImpactLogr can be useful. Instead of trying to reconstruct your value when the issue finally becomes urgent, you can keep a steady record of the work that supports a stronger case over time.
What to do if you suspect you are underpaid
If you suspect you are underpaid, do not jump straight to a compensation demand built on frustration. First, audit the friction in your own case.
Ask yourself:
- Can you name the responsibilities that exceed your current level or pay?
- Do you have recent examples with clear ownership and outcomes?
- Can your manager retell the case in a room where you are not present?
- Are you relying on feelings of unfairness, or on documented patterns of higher-value contribution?
If those answers are weak, fix the record before you force the conversation. If they are strong, you are in a much better position to open a conversation with your boss about pay and ask informed questions about level, expectations, and compensation timing.
To make those conversations less dependent on memory, start keeping a clearer record of the work behind your case in ImpactLogr.