Keep your interview skills active, collect evidence of useful work, compare roles at the same level and location, and negotiate a written offer. Move when the opportunity is clearly better; a calendar alone is not a reason to resign.
1. Test the market 1–2 times a year and stay ready to switch
Changing employers can open a different pay band, but it is not an automatic raise. ADP’s August 2026 analysis reports that job changers can still receive meaningful pay gains, while emphasizing slower hiring, search costs and differences between industries. That is evidence for evaluating external opportunities, not evidence that everyone should change jobs once or twice every year.
Use one or two deliberate search periods a year as a planning habit. During those periods, speak with recruiters and attend multiple interviews for roles you would seriously consider. Between searches, keep preparing through mocks and short practice sessions. You want enough interviews to see repeated questions and understand the market, without letting an endless search undermine your current work.
The Atlanta Fed’s Wage Growth Tracker measures the median percentage change in individual hourly wages over 12 months using U.S. Current Population Survey data. It separates job switchers and stayers, but it is not a tech-only experiment, does not measure total compensation, and cannot tell you the best job-switching frequency. Its switcher definition also covers some occupation or industry changes. Avoid interpreting the gap as a guaranteed return from resigning.
Before moving, compare the written offer with your current role: recurring cash, realistic equity value, responsibilities, manager, working hours, growth opportunities and any compensation you would forfeit. A strong internal promotion may be the better next step. If the external role is clearly better, move deliberately rather than waiting indefinitely for a routine review.
- Keep a short list of employers and roles you would actually accept.
- After each interview, record the topic, where your answer broke down and one drill to fix it. Use your own notes; respect interview confidentiality.
- Prepare for the employer’s actual process. Amazon’s published SDE guidance, for example, covers coding, data structures, algorithms and system design; other tech roles need different practice.
2. Build proof of impact before asking for a higher level
A stronger salary case starts with work you can explain. GitLab’s public job-framework guidance connects progression to expectations at the next level, including scope, influence and problem solving. It also says business need matters. This is one company’s framework, not a universal promotion rule, but it gives you a useful question to take to your manager: what evidence would show that I am already contributing at the next level?
Create a private impact log. Once a month, capture one project’s problem, the decision you owned, the result and your contribution. Choose an outcome your team cares about: latency, reliability, cloud cost, customer adoption or time saved. Include the measurement period and distinguish your work from the team’s result. If you cannot measure an outcome, describe what changed and how you know it helped.
Turn the log into three concise stories you can use in a review or interview. Ask your manager which gaps remain, which project would demonstrate the missing scope, and when the next decision can happen. This is a practical exercise derived from the framework, not a promise that a document will produce a promotion.
- Use this template: problem → my decision → evidence → result → next lesson.
- Illustrative example: an engineer identifies repeated API calls, owns a batching change and checks whether p95 latency improves. Fill in real measurements rather than inventing a percentage.
- Keep confidential code, customer information and internal metrics out of public portfolios. Describe the work at an appropriate level.
3. Choose the pay band before investing in a long interview loop
The same job title can hide very different responsibilities and compensation. Levels.fyi’s 2025 report compares compensation by employer, location and career level, and explains that its figures include salary, stock and bonuses. Its leveling standard uses scope and responsibility to compare company-specific titles. The data comes from people who choose to submit compensation, so it is a useful benchmark rather than a representative survey of everyone in tech.
Build a small shortlist of comparable roles. Match the country or city, actual scope, level and compensation components before comparing numbers. Ask recruiters about the budgeted base range and the expected level early enough to avoid a long process for a role that cannot meet your needs. Where the employer shares a range, clarify what would place a candidate near its upper end.
Select one skill gap that appears repeatedly in the roles you want. Then demonstrate it with a project, operational example or clear interview answer. A fashionable skill without evidence is a weak reason to expect more pay. A title change without a better package may also leave you worse off.
- Compare recent data for the same role, location and level; check the sample size when available.
- Separate base salary from variable bonus, annual stock vesting and one-time sign-on cash.
- Write down your minimum acceptable recurring cash and the kind of work you want before applying.
4. Negotiate the written offer with a specific, supported request
Harvard Business School Online recommends researching market pay, explaining your value, practicing your talking points and evaluating the full package. Use that preparation to make a respectful counteroffer once you have an offer. A request tied to the role’s scope and relevant evidence is easier to discuss than an arbitrary percentage increase.
Thank the recruiter, confirm the decision deadline and name the component you want to improve. If base salary is constrained, ask which other components have flexibility. Keep recurring compensation distinct from a sign-on payment, and read the vesting and repayment terms. Treat uncertain equity as uncertain rather than assuming the headline value is spendable cash.
Practice a short script: ‘I’m excited about the role. Based on its scope, comparable positions and my experience with [relevant result], could we explore a base salary of [researched amount]?’ Replace the brackets with real evidence and your own target. Discuss genuine alternatives honestly; do not invent competing offers. Employers have different constraints, and negotiation can end without agreement.
Use RecallDeck to make interview preparation a regular habit
Pick the RecallDeck track that matches your next role and answer the due interview questions from memory before revealing the explanation. When you miss a concept, explain it aloud, check a source and apply it in a small task or mock interview. Spaced review can support the knowledge part of preparation; timed coding, system design and behavioral practice still need their own sessions.
Try this manageable routine: short RecallDeck reviews during the week, one mock interview a week, and a monthly update to your impact log. Review your target employers during one or two planned market checks each year. This cadence is an editorial starting point you can adjust to your workload, not a research-tested optimum.
The next action is small: visit recalldeck.dev, choose your target track and complete today’s review. Then schedule the practice your target employer actually assesses.
Quick answers
Frequently asked questions
Should I change jobs once or twice every year to grow my salary?
The cited sources do not establish that frequency as a reliable strategy. We recommend testing the market once or twice a year, attending interviews for roles you would accept and moving when the written offer and growth opportunity are clearly better. Job-switching wage data is observational and cannot guarantee an individual raise.
How can I ask for a raise without changing companies?
Agree on next-level expectations with your manager, document your contribution and outcomes, and ask for a specific review date. Consider your employer’s pay band, promotion process and available scope. External benchmarking can help you evaluate whether the internal path is competitive.
Does RecallDeck replace mock interviews?
No. Use RecallDeck for regular recall of interview concepts. Combine it with role-specific practical tasks, timed exercises, system design discussion and behavioral mocks as needed.
Source notes
References and review policy
Information checked on October 6, 2026. Section links identify sources for factual claims and technical explanations. Interpretations, practice scenarios and preparation recommendations are RecallDeck’s editorial work.
- ADP Research: Does it still pay to switch jobs? (August 11, 2026)
- Atlanta Fed: Wage Growth Tracker and methodology
- Amazon Jobs: Software development interview topics
- GitLab Handbook: Job frameworks and career progression
- Levels.fyi: 2025 End of Year Pay Report
- Harvard Business School Online: How to Negotiate a Job Offer & Salary
From reading to recall
Practice the full interview loop.
RecallDeck schedules the concepts you miss and keeps coding, design, and behavioral fundamentals available when the interviewer changes direction.