# Answering 'why this role' and salary expectation questions Answer 'why this role' by connecting a specific part of the job to work you have done and a direction you can explain honestly. For salary, research the market, prepare a range you can justify, and ask about the budgeted range and compensation structure instead of guessing. Rules about salary questions vary by location. About 6 min read. ## On this page - [Why recruiters ask these questions](https://preprole.com/guides/motivation-and-salary-questions#why-asked) - [Build a 'why this role' answer from evidence](https://preprole.com/guides/motivation-and-salary-questions#why-this-role) - [A worked 'why this role' example](https://preprole.com/guides/motivation-and-salary-questions#motivation-example) - [Handle salary expectations deliberately](https://preprole.com/guides/motivation-and-salary-questions#salary-expectations) - [Prepare the questions that travel with these](https://preprole.com/guides/motivation-and-salary-questions#related-questions) - [Rehearse both answers aloud](https://preprole.com/guides/motivation-and-salary-questions#rehearsal) ## Why recruiters ask these questions Motivation and salary questions are screening tools. 'Why this role?' checks whether you understand what you applied for and whether the job matches a direction you can articulate. 'What are your salary expectations?' checks whether the conversation is viable at all before either side invests more time. Neither question is a trap by default, but both punish vagueness. A motivation answer that could apply to any employer suggests a mass application. A salary answer improvised on the spot can anchor you badly in either direction. Prepare both as deliberately as your technical answers; they often arrive earlier. ## Build a 'why this role' answer from evidence A credible answer connects three things: something specific in the job description, something real in your experience, and a direction you can state honestly. The job-description part proves you read it. The experience part proves you can do the work. The direction part explains why you would stay. Be honest about mixed motives. 'The compensation is strong' or 'I need a job' may be true, but they give the recruiter nothing to evaluate. If part of your motivation is practical, such as location or stability, you can say so alongside the work-specific reason. What you cannot fake is the specific connection; if the job genuinely does not excite you, that is worth knowing before the interview rather than during it. - Specific: one element of this role, not engineering jobs generally. - Experience: the work you have done that connects to it. - Direction: why this is a sensible next step for you now. - Honest: a reason you can expand under a follow-up question. ## A worked 'why this role' example Illustrative example, not a customer answer. Notice that it names something concrete in the posting, links it to real experience, and states a direction without flattery or grand claims about the company's mission. > The posting mentions migrating reporting workloads off a legacy pipeline, and that is close to what I have been doing for two years. I redesigned a reporting flow at my current role and enjoyed the messy middle part where the old and new systems had to run side by side. I want to keep doing platform work, and this role is that work on a larger system, which is the step I have been looking for. ## Handle salary expectations deliberately Research before the call: public ranges for the role level and location, any legally required posted range in the job listing, and your own floor. Decide on a range you can say aloud without flinching, and know the reasoning behind it. 'Based on the ranges I have seen for this level and my experience, I am expecting something in the X to Y range, though I would want to understand the full package' is a complete answer. Asking 'what range is budgeted for this role?' first is legitimate and often answered. If the recruiter presses for your number first, giving a researched range is usually safer than refusing or inventing one. Remember that base salary is one component; equity, bonus, benefits, and level all change the picture, so do not evaluate the number in isolation or negotiate final terms at the screening stage. Rules vary by location. Some jurisdictions require employers to post ranges, and some restrict asking salary history. This guide is preparation advice, not legal advice; check what applies where you are interviewing. ## Prepare the questions that travel with these Motivation and salary rarely arrive alone. Expect 'are you interviewing elsewhere?', 'what is your notice period?', and 'do you have offers?' Answer all of them factually. Being in other processes is normal and worth stating briefly; inventing offers or timelines to create pressure can collapse under a follow-up question, and it hurts your credibility even when nobody checks. For notice period and availability, know your contractual answer before the call and do not improvise an earlier date to sound eager. If your situation is complicated, such as a visa or a relocation, say that plainly and offer to confirm details afterwards rather than guessing under pressure. - Other processes: state that you are interviewing, at whatever level of detail you are comfortable with. Do not fabricate offers. - Notice period: give your real contractual answer. - Start date: distinguish earliest possible from preferred. - Constraints: raise visa, relocation, or arrangement needs factually and early. ## Rehearse both answers aloud These questions feel easier on paper than out loud, which is why they deserve spoken rehearsal. Say the motivation answer once and ask whether a listener could tell which job you applied for. Say the salary range three times until the numbers come out smoothly; hesitation at the moment of quoting reads as uncertainty about the range itself. Then rehearse the awkward versions: the recruiter asks for a number before you wanted to give one, or names a range below yours. Practise a calm response such as asking how the total package is structured or noting the gap between the range and your expectations. The goal is to leave the exchange without committing to something unresearched. ## Frequently asked questions ### Should I give a salary number first or ask for theirs? Asking for the budgeted range first is reasonable and often answered. If pressed, give your researched range rather than refusing repeatedly, which can read as evasive. Either way, decide your numbers before the call so neither answer is improvised. ### What if their range is lower than my expectation? Say so plainly and ask how the compensation is structured. Level, equity, and bonus can change the comparison, and sometimes the posted range is negotiable. You can also keep the process moving and decide later; you are not required to accept or reject a range during a screen. ### Should I say I have other offers to strengthen my position? Only if it is true. Invented offers risk follow-up questions you cannot answer and can end a process if checked. Being genuinely in other processes is common and worth mentioning factually; it needs no embellishment to be useful information for a recruiter. ### Is the recruiter screen the right time to negotiate? Usually no. The screen establishes ranges and viability; negotiation typically happens after interviews when there is an offer or a clear signal. Trying to negotiate final terms before either side has evaluated fit wastes the little leverage you have. ## Practise the next answer Choose Recruiter Screen with your real job post so the motivation question is tailored to the role you actually applied for. Rehearse your range and your deflection aloud; written numbers feel different when spoken. The sample trial does not cover compensation questions. Practise for your job: https://preprole.com/setup ## Sources and scope Employer sources describe their own processes, which may change. The exercises and illustrative examples are PrepRole editorial guidance, not employer questions or hiring criteria. - [Microsoft Careers: interview tips for all roles](https://careers.microsoft.com/v2/global/en/hiring-tips/interview-tips.html) - [Amazon Careers: software development interview topics](https://amazon.jobs/content/en/how-we-hire/interview-prep/software-development-topics) ## Related guides - [Prepare the rest of the recruiter screen](https://preprole.com/guides/recruiter-screen-preparation) - [Open with a focused introduction](https://preprole.com/guides/tell-me-about-yourself) - [Prepare questions that help you decide](https://preprole.com/guides/questions-to-ask-interviewers) AI feedback can be wrong. A practice Verdict is not a hiring decision.