Salary question in an interview: Response strategies for IT professionals in 2026
The salary question: more than just a number
In the recruitment process for IT positions, the salary question in the interview poses a particular challenge for many applicants. If you want to accurately assess your market value, you need to look closely at industry trends, the requirements of the role and your own qualifications. The situation is often characterised by a dichotomy: on the one hand, the goal is to adequately represent one's own potential - on the other hand, too high a demand should not burden the selection process prematurely. Particularly in IT, where qualified specialists are still in high demand, the answer to the salary question can set a decisive course. A well-founded presentation improves the starting position for subsequent contract negotiations.
The topic of salary regularly crops up at various points in the application process - sometimes surprisingly early on, sometimes only in the final interview. This uncertainty makes it difficult for many IT professionals to respond appropriately. The manner of communication is of great importance here: it not only reflects the salary expectations, but also conveys negotiating skills and personal confidence. The salary question is thus developing into an indicator of essential soft skills that are increasingly in demand in the IT environment.
The employer's perspective should by no means be underestimated: Companies take care to integrate new employees seamlessly into existing salary structures and to preserve the project budget. It is therefore advisable to research the common salary bands for similar positions in addition to your own expectations. Salary reports from industry associations, online platforms or experience reports can provide valuable starting points here. Being prepared for this part of the interview signals professionalism and knowledge of the market.
Preparation: Determine your own market value
A convincing answer to the salary question requires an intensive examination of your own competences and the relevant market situation - ideally before the actual interview date. For IT specialists, this means consulting various sources of information on industry salaries and taking into account parameters such as region, company size or specific technologies. Platforms such as Stack Overflow, kununu or studies by renowned industry associations provide concrete benchmarks. For example, research for a cloud engineer position with three years' experience in a major city in 2026 reveals a salary range of around €58,000 to €72,000 per year. Additional knowledge, for example in Kubernetes or Terraform, can push the salary level up further.
In addition to the basic salary, it is worth looking at additional benefits early on. Many IT employers offer remote options, flexible working hours, extra holidays or annual training budgets. These benefits should be evaluated together with the salary as part of the scope for negotiation. A prepared note, for example "My target range is between 65,000 and 70,000 euros gross, depending on the overall package and development opportunities", creates clarity - this allows you to argue confidently in the interview.
Market differences are often greater than is apparent at first glance: a venture-funded FinTech usually pays a different level than an established medium-sized company. It is helpful to draw up a personal salary range - including a minimum target, realistic target and desired value. This self-selected range serves as a guideline during the interview and helps you to react flexibly to unexpected questions. Formulations in the subjunctive mood - such as "I could imagine ..." - show flexibility and keep the door open for negotiations.
Response strategies in dialogue: Between openness and tactics
The job interview often begins with an exchange about expectations of the position and then quickly moves on to the general conditions - including the question: "What is your salary expectation?" Those who come prepared here take the opportunity to show competence and self-confidence. Different strategies can be used depending on the situation.
One tried and tested method is the mirror technique: instead of immediately quoting a figure, the question is answered with a counter-question, for example: "Have you defined an internal salary range for this position?" Many companies today work with transparent remuneration models and then provide a framework. This gives you time to formulate your own arguments and avoid positioning yourself at the lower end. If no specific details are provided or if there is any pressure, it is advisable to specify a suitable salary range that takes into account the industry, location and personal experience: "With my background in the DevOps environment and the planned responsibility for this role, I see my salary range as being between €68,000 and €75,000 gross per year."
Absolute demands, on the other hand, narrow the scope for negotiation. Statements such as: "Depending on the overall package and opportunities for further development, I see my target remuneration as being between ... and ... Euros per year." This maintains openness while at the same time communicating a clear idea. It is often advisable to back up the expectation with concrete examples, for example by referring to relevant project experience ("Due to my expertise with TypeScript and proven experience in leading agile teams, I consider the upper end of the usual range to be appropriate"). This is a factual way of underpinning your own value.
International companies or remote jobs bring other variables into play. Independence of location, flexible working time models or additional benefits can influence the overall value of the offer. It is a good idea to bring these aspects into the conversation alongside the salary: "In addition to the salary, the work culture and specific learning and development prospects are key for me. I would like to consider further details about the position for a final classification."
Flash from the field: typical scenarios
When applying for a job as a backend developer at a large German IT service provider, the HR manager explicitly asks for a salary in the second interview. A convincing answer could be: "With my eight years of professional experience and specialisation in microservices architectures and cloud deployment, I have observed the market intensively. For the advertised role, I am aiming for a total annual salary of between 80,000 and 87,000 euros." If this is followed by a question about the bonus or participation model, this shows how important flexibility is with regard to other remuneration components.
If the salary question is raised at an early stage - for example, before the tasks and requirements are clarified in detail - it is worth taking a differentiated position: a data engineer could answer: "In order to formulate my salary expectations in a well-founded manner, it would be helpful to first receive details of the area of responsibility. I would be happy to discuss the salary issue in the further course of the selection process." This approach signals both professionalism and care in evaluating the offer.
Follow-up: Dealing with difficult situations
The salary question in the interview rarely follows a fixed pattern. It can happen that offers are below your own expectations or the impression arises that the interviewer is hoping for a low figure. In such situations, it is important to act calmly and signal a willingness to talk. For example, if you respond with: "That's below my current level. Is there any flexibility here, provided there is a technical fit?", this opens up a constructive dialogue and avoids premature rejection. This often opens up room for manoeuvre in the negotiation process.
If you are asked to justify your salary expectations, you will benefit from a factual, comprehensible argument. One possible answer: "I have analysed various salary studies, reflected on my career and included my most recent certifications in the cloud and cybersecurity sector. From my point of view, the range mentioned therefore reflects the professional value I can bring to the table." The more structured the reasoning, the more professional the appearance.
If employers don't want to quote figures, it pays to ask diplomatically. Phrases such as "Could you tell me whether the salary is within the normal market range for this senior position?" or "To adjust my expectations, a rough guide would be helpful - for example, is the offer within the range of comparable positions in Hamburg?" create transparency without creating pressure and document negotiating skills.
After the interview: Renegotiate or adjust?
The final offer may differ from the original expectations. If the interview is otherwise promising, a further meeting is recommended for clarification. It helps to refer to specific content from the selection process: "Additional responsibilities were discussed in the further talks. Under these circumstances, it seems sensible to me to increase the salary towards the upper salary limit - is that possible in principle?" This approach shows professionalism and creates a comprehensible basis for internal consultations with the employer.
It is also advisable to record all agreements made in writing. Especially in the dynamic IT environment, this ensures transparency in the offer and avoids misunderstandings. In addition, exchanging ideas with colleagues from your own network often provides valuable information to help you make a well-founded assessment of your own market position and secure your decision in favour of or against an offer.
Conclusion: score points with preparation and self-confidence
The salary question in an interview is not just an obstacle, but an opportunity to present your own value realistically and convincingly. Sound preparation, authentic communication and a confident demeanour help to make constructive use of the special features of the IT sector. If you formulate realistic goals, demonstrate flexibility and clearly communicate your skills profile, you will create the best conditions for successful negotiations and an optimal start in the new team.
