A convincing response joins the role, the employer, and your proof. Compliments aren't enough. Hiring managers want to hear why the work interests you and what you'd contribute once hired.
Turns out, this isn't a five-minute invitation to praise the company. It tests fit, preparation, and motivation. Better to understand that before you're sitting in the chair.
Use this frame:
"I'm interested in this role because it focuses on [specific responsibility], which matches my experience with [relevant skill or result]. I was also drawn to [specific company detail]. I'd like to use that background to help with [team goal] while continuing to grow in [relevant direction]."
Keep your answer to 45 to 60 seconds. Make it conversational. Don't recite it.
What interviewers want to hear
Interviewers listen for connections. The work, the employer, and your contribution should support one another.
A strong answer covers the three main signals below, plus a sensible reason the move fits your direction. Leave one out, and the response usually feels thinner.
| Signal | What to explain | Evidence to prepare |
|---|---|---|
| Role fit | The responsibility that genuinely interests you | A project, task, or skill that matches the posting |
| Employer fit | What you learned about the company, product, mission, or team | One specific fact from reliable research |
| Contribution | The way you could help the team | A result, example, or practical strength |
| Direction | Why this role makes sense as your next step | A realistic growth goal connected to the job |
Keep your long-term plan in the background. The employer is hiring for this position, not for a promise about a job you may want later.
A simple formula for your answer
Lead with the work. Name the responsibility, problem, customer group, or skill area that interests you.
Then bring in the employer. Use a product, mission, operating priority, or team detail that you actually checked. "Your company is innovative" says almost nothing.
Proof should follow. A brief example carries more weight than several flattering adjectives. Explain what you did. Then say what changed.
Close by showing direction. Describe how the position builds on your background and gives you room to contribute at a higher level.
The formula is:
Role interest + company detail + evidence of fit + practical next step
Those four pieces don't need equal time. Give proof the largest share. Motivation should strengthen your fit, not replace it.
Research the employer before you write
Ten focused minutes can make a generic answer sound prepared. You don't need a research dossier.
Hays' employer research checklist points candidates toward mission, values, recent news, products, industry context, leadership, and employee perspectives. Pick one detail from that research. Use the one that connects naturally to the opening.
- Read the job description twice. Circle repeated responsibilities, tools, customer groups, and outcome words. Repetition often shows what the team needs most.
- Visit the employer's own pages. Look for a current product, service, initiative, or stated priority that relates to the role.
- Check recent context. Review company news and leadership updates. Leave unverified rumors out of your answer.
- Learn the market position. Understand what the employer does, who it serves, and how its work differs from competitors.
- Prepare one team question. Ask how the team operates, how success is measured, or which challenge needs attention first.
Save the job description before the interview. Listings change. The exact responsibility you noticed may matter later.
Ten sample answers you can adapt
Treat these as working templates. They aren't scripts.
Replace every bracketed detail with something you can explain if the interviewer asks a follow-up question.
| Situation | Sample answer | Personalize it with |
|---|---|---|
| Entry-level role | "This coordinator role interests me because it brings together customer communication and project tracking, skills I developed during my internship. I improved a handoff process and reduced follow-up delays by [X%]. Since your posting stresses cross-team support, I could contribute quickly while learning your systems." | A class project, internship, volunteer role, or work result |
| Manager position | "I was drawn to this role because it combines people leadership with operational improvement. In my current job, I led [team or project] through [change] and improved [business measure]. I'm ready to apply that approach with a larger team, especially around your verified priority of [priority]." | Team size, business outcome, and leadership challenge |
| Career change | "I'm moving from account management into customer success because the work I enjoy most is helping customers solve problems after the sale. Managing complex accounts, resolving escalations, and improving retention in my portfolio helped me build that skill. This position would let me use that experience in a more focused customer partnership role." | The transferable skill, not just the new job title |
| Internal promotion | "I want this position because I understand the current process and can see a practical opportunity to improve it. I recently helped reduce [errors, delays, or rework] by [X%], while also supporting newer teammates. I'm ready for broader ownership and want to help the team deliver more consistently." | A specific internal result and your first leadership priority |
| Amazon role | "Amazon's Customer Obsession principle appeals to me because I make better decisions when I begin with the customer's actual experience. In my last role, I reviewed feedback, found a recurring problem, and helped change the process behind it. I'd bring that habit of listening and acting to this position." | A real customer example and the result |
| Google or another large tech employer | "I'm interested in this role at Google because the team is working on [verified product or user problem]. The posting asks for [skill], which I used to achieve [specific result] in my last role. I'd like to work on a product at that scale while bringing a practical, user-focused approach to the team." | A current team or product detail you have verified |
| Sales position | "I want this sales role because it values consultative selling instead of simply moving volume. I have experience asking stronger discovery questions, matching solutions to customer needs, and building repeat business. Your focus on [customer segment or solution] fits the way I sell." | A sales result, customer type, and relevant product |
| Software engineering role | "This engineering position caught my attention because it involves building reliable systems that customers depend on. In my last role, I worked on [system or feature], improved [performance, reliability, or security measure], and partnered with product and support teams. I'd bring that mix of technical ownership and user awareness here." | A system you built and a measurable technical outcome |
| Operations role | "I'm interested in this position because it links process improvement with daily execution. I have mapped workflows, located the source of recurring delays, and worked with several teams to make changes stick. Your focus on [capacity, quality, cost, or delivery] is an area where I could add value." | The process, people involved, and operational result |
| Startup or mission-driven employer | "This opportunity interests me because I want to work closer to the problem your organization is addressing. I like roles where priorities shift and people take ownership beyond a narrow job description. My background in [skill] could help with [specific need], and your mission gives that work a clear purpose." | The mission, the ambiguity you can handle, and one relevant example |
Amazon says its 16 Leadership Principles guide decisions, projects, and hiring. If you mention one, attach it to something you actually did. Reciting a principle by itself won't carry much weight. You can review Amazon's interview guidance and Leadership Principles interview examples before you prepare.
The same care applies to Google, Amazon, and other large employers. Confirm the current role and team details. Old slogans, policies, and product claims still appear in recycled interview posts.
Use STAR when the interviewer asks for proof
The opening question usually needs a compact explanation. A follow-up like "Can you give me an example?" needs a story instead.
STAR gives that story a shape:
| Part | What to include | Example |
|---|---|---|
| Situation | The problem or surrounding context | New customers were waiting too long for onboarding support |
| Task | The responsibility you owned | I was asked to find the main source of the delay |
| Action | The steps you personally took | I mapped the process, reviewed support tickets, and worked with the implementation team to remove duplicate approvals |
| Result | The measurable or observable change | Onboarding time fell by [X%], and the team received fewer repeat questions |
Tie the example back to the opening afterward:
"That experience is one reason this position interests me. It combines customer understanding with process ownership, which is where I do my strongest work."
Don't force STAR into every response. Use it when the interviewer asks for evidence. A direct motivation answer works better for the first question.
Common answers that weaken your case
Generic enthusiasm takes almost no preparation. Specific interest does.
| Weak response | Why it creates doubt | Better direction |
|---|---|---|
| "It's a great company with a good culture." | The same sentence could describe almost any employer. | Name a verified product, value, customer group, or team priority. |
| "I need a job right now." | It explains your urgency, not your fit. | Show how the responsibilities match your skills and interests. |
| "I want better pay and benefits." | Compensation can matter, but it shouldn't lead this answer. | Start with the work. Discuss compensation when asked. |
| "My old manager was impossible." | Complaints make the response sound reactive. | Describe the kind of environment and work where you perform well. |
| "This is a stepping stone to a senior role." | The interviewer may worry that you'll leave quickly. | Explain how you would grow while succeeding in this position. |
| "I love your mission," with no job connection | You sound like a supporter, not a candidate. | Show how your skills could advance that mission. |
| A long list of company facts | Memorized research can sound unnatural. | Choose one detail and connect it to one responsibility. |
| A claim you cannot explain | Follow-up questions can expose weak preparation. | Mention only achievements, tools, and results you can discuss clearly. |
Thing is, practical motivations don't need to disappear. Put the work and your contribution first. The rest of the conversation has room for everything else.
Adjust the emphasis for your situation
Your background changes which part deserves the most attention.
If you're entry-level, emphasize curiosity, relevant practice, and coachability. Coursework, internships, part-time work, campus leadership, and volunteer projects can all provide evidence. You don't need to apologize for having less experience.
If you're interviewing for management, show people judgment and business judgment together. Talk about setting priorities, coaching performance, handling conflict, or improving execution. "I like leading people" is not enough by itself.
If you're changing careers, name the bridge between the old field and the new one. Customer communication, analysis, project coordination, sales, training, and process improvement often transfer across industries. Explain why you want the new work, not only why you want to leave the old field.
If you're seeking an internal promotion, state your result instead of assuming the interviewer knows your record. Then name the broader responsibility you want and the first problem you would help solve. Familiarity helps. It can't replace a clear answer.
If the employer is mission-driven, connect the mission to a concrete duty. Values become more convincing when you show how they shape your decisions, service, or standards.
If the employer is an early-stage company, discuss ownership and shifting priorities only if those conditions suit you. Don't claim to enjoy ambiguity if you need clearly defined work to do your best job.
If you found the role through a job board
To be honest, LinkedIn, Indeed, and other hiring platforms are discovery channels. They aren't the reason you want the job.
Before the interview, save the useful details from the listing:
- The exact job title and department
- Two responsibilities repeated in the posting
- One required skill you can demonstrate
- One employer or product detail from a reliable source
Build the answer from the posting, then confirm important company information on the employer's own website. If a staffing agency arranged the interview, ask which organization employs the person in the role and which details are confidential. You can discuss the responsibilities, team type, and skills without pretending you've researched an end client you haven't.
When the question is vague or repeated
Listen for the version of the question the interviewer is really asking. "Why do you want this job?" may mean "Why this company?" or "Why should we hire you?"
For why this role, focus on the duties and your relevant experience. For why this company, explain the employer detail that matters to you. For why you, start with the result or capability you would bring.
A repeated question calls for another layer, not the same script. You might address the team structure, a customer problem, or a specific part of the posting you haven't discussed yet.
Questions to ask after your answer
Your questions help you test the fit, too. Hays suggests asking about team working style and what employees enjoy about the company.
Keep a few questions ready:
"What would you want the person in this role to improve first?"
"How does the team measure success in the first few months?"
"Which part of the job tends to require the most judgment?"
"How would you describe the team's working style?"
These questions make the discussion more specific. They also give you useful information before you decide whether the role is right for you.
Your next step
Open the job posting. Highlight two responsibilities.
Find one employer detail you can verify. Then write a three-sentence answer using role fit, evidence, and contribution. Say it aloud once, remove any phrase you wouldn't use in normal conversation, and practice again with a timer.