“What was your previous salary?” Why DC area engineers increasingly decline to answer.

Salary history questions can severely impact your salary. That’s why state and local governments increasingly ban them. In DC, new data shows that software engineers increasingly refuse to answer.

Have you ever been asked “what is your current salary?” during a job interview? Or, have you ever filled out an application that required you input previous salaries?

These questions provide valuable information for potential future employers. Once they have your salary history, they have a general answer to questions like:

  1. Can they afford to hire you?
  2. What is the lowest possible salary offer you’ll accept?

When you’re interviewing for a new role, you don’t want an employer to have the answer to #2. Once a potential employer knows your future salary, they have the upper hand in salary negotiations. You won’t be able to negotiate a higher salary. If your current salary is already near their high end, an employer may decide to focus on cheaper candidates.

The Decline of Salary History

We have some good news. Salary history questions are increasingly uncommon or even illegal. Many software engineers in the DC area refuse to answer them altogether. If you don’t want to provide your salary history, you’re in good company.

Salary history questions aren’t just annoying and uncomfortable for interviewees. They’re problematic for employers too. There are three primary reasons some employers shy away from salary history questions:

1. When employers focus on candidates’ previous salaries, not skillsets and job requirements, they risk imbalances in compensation. That could be unfair or even discriminatory. In the DMV, male developers average salaries that are 10% higher than female developers. If you base compensation off of previous salaries, you are likely to end up with the same imbalance.

2. Employers who ask for salary histories also risk marginalizing candidates from disadvantaged backgrounds. If you pay someone just slightly more than their previous salary, you could be exacerbating a cycle of unfair pay. An applicant’s previous salary doesn’t necessarily reflect her ability.

3. Employers who only care what an engineer made at their last job can lose talented candidates. When candidates are in high demand, they have a lot of choice in where they go for their next position. They might avoid anything they perceive as a red flag or speed bump in the recruiting process.

As a result, some businesses, and even state and local governments, have started to ban salary history questions. That’s why our hometown, the DMV metro area, has started to take the issue seriously. Both Washington DC and Montgomery County, MD, have banned salary history questions for certain jobs.

We expect this trend to continue. A survey by HRDrive found that 17 states and 19 localities have banned the practice so far. Salary history questions will become increasingly uncommon.

An increasing number of applicants don’t provide salary histories.

According to research by hatch I.T., the number of software engineers in the DC Metro area who said they did not provide their salary histories to employers increased from 2016 to 2019.

In 2016, only five percent of job applicants said they did not disclose salary histories to their future employers. In 2017, the number had increased to 1 in 10. In a 2018 hatch I.T. survey of 629 job applicants for software engineering positions, over 1 in 5 said they haven’t disclosed salary histories to their employers.


2019 DC MD VA Software Engineering Compensation Report

Download the full report on the DC metro area’s salary history disclosures, average salaries by title and skillset, and more.


Based on the high demand for engineering talent in the DC metro area, and the increase in engineers who keep their salary histories private, we expect salary history questions to go out of fashion in the next few years. Companies that don’t remove those questions from their hiring processes may find that the best tech talent is looking elsewhere.

How to handle salary history questions in an interview

While the trends are changing, you may still encounter the question of salary history. We’ve listed out some tips for navigating this situation.

Keep in mind that every situation is different, and you should always do your homework in advance. If you know what the pay range is for the position, what you want, and what you’re worth, you’ll have an easier time responding to salary questions. Make sure that you know your own value as well. You should have a good understanding of what someone with your background, experience, and skillset can expect to make.

Stay Up-to-Date on DC Tech Trends

Provide the salary

You can, of course, choose to provide your salary history. Just accept that this may limit your options for negotiation later. This may be a good option if you expect to receive a similar level of compensation to your current position. If you believe the company can afford your desired salary and know that you are in high demand, sharing your salary may be the right choice.

Shift the focus to the new role

You can respectfully explain that the new role will be different than your last role, so you’d like to keep the conversation focused on what you’ll be doing at your new job. If you believe your background is a strong fit for the position, but that the new role will come with a different set of responsibilities, perks, or challenges, this may be the right option for you.

Start with their budget

Explain that you know they already have a budget for the position. You can politely explain that you’d like to start with what they have budgeted for the position and go from there. This can be a good option for positions with a set salary range. If you want the job, but know that the company has a set compensation package for your level, this may be the right option for you.

Establish your baseline

Is there a minimum compensation package you’ll accept, regardless of your previous salary? Courteously explain that there is a baseline compensation range that you’re seeking based on the current market. If you are coming from a strong position, and your desired salary is reasonable, this may be the right response for you.

Come back to it later in the process

The final option is to delay. Say that you’d like to discuss compensation later, once you’ve learned more about the role. If the salary question has been asked too early, this will give you time to get a better feel for how you want to respond.

author Chris Mills

join hatchpad

An original look at DC's high-growth startups, tech jobs, tech events, and more. Straight to your inbox.


* indicates required