Answer "Why do you want this job?" by connecting the work, the employer's needs, and the strengths you'd bring. Begin with the role itself. Then add one specific company detail and a brief example from your experience.
Keep it close to a minute. Perks can wait. The work can't. Leave the interviewer room to follow up.
A useful answer usually has three parts:
- Role fit: Name the responsibilities that genuinely interest you.
- Evidence: Link those responsibilities to a skill, project, or result.
- Contribution: Explain what you'd improve, build, or support in the role.
Here is the shape in practice:
"I'm interested in this customer success role because it combines problem-solving with long-term client relationships. In my current position, I improved our onboarding process and helped reduce repeated support questions. Your focus on helping customers get more value from the product is a strong match, and I'd be excited to bring that process-minded approach to the team."
What interviewers want to hear
"Why do you want this job?" reaches beyond "Why did you apply?" The interviewer is listening for three connected answers: Do you understand the position? Is your interest believable? Does your background relate to the work?
The University of Pennsylvania career office guidance recommends researching both the position and the company. It also advises showing that you understand the challenge and have relevant experience to take it on. That is the basic assignment.
Specific details carry the answer.
| What they are testing | How to show it | Useful evidence |
|---|---|---|
| You understand the role | Mention a real responsibility from the posting | A task you have done or studied |
| You want this work | Explain what part of the job appeals to you | A project, subject, customer group, or problem |
| You fit the team | Connect your strengths to the team's likely needs | A relevant result or working style |
| You have a reason for choosing the employer | Refer to a verified company detail | A product, mission, market, or recent initiative |
| You are thinking beyond the application | Describe the contribution you want to make | A practical first priority or area of impact |
Don't use the whole answer to applaud the company. Connect each compliment to the work you'd actually do.
How to research the company before answering
Good research makes the response more precise, not more crowded. You don't need to memorize the company's full history, funding rounds, leadership changes, and product pivots. You need enough context to say why this position fits you.
Start with the job posting. The responsibilities usually tell you more about the day-to-day role than the qualifications section does.
- Read the responsibilities before the qualifications. Mark the two or three duties that seem most central. Then ask which one you would enjoy doing repeatedly, not merely once.
- Check the official company website. Look at the product or service, customer base, mission, and careers pages. Pay attention to wording that shows how the team operates.
- Look for recent developments. Search the company name with terms such as "news," "press release," "product launch," or "expansion." Use details you can verify.
- Review the team and role context. The same title can mean different work at a startup, a large corporation, a nonprofit, or a public agency. Note who the role serves and what it appears to own.
- Select one detail for your answer. It should help explain your interest. It shouldn't exist just to show that you visited several web pages.
The Career Sidekick company research checklist likewise recommends checking the employer's mission, recent developments, and social profiles. Employee reviews may reveal recurring themes, but they represent individual experiences. They aren't a promise about every team.
Turns out, one accurate detail often does more work than a paragraph of enthusiasm.
A simple formula for writing your answer
Draft four sentences before you practice aloud. You can trim them later.
"I'm interested in this [role] because it focuses on [specific responsibility or problem]. In my [current, previous, academic, or volunteer experience], I [relevant action], which led to [result]. I noticed that [company detail], and that connects with my interest in [specific area]. I would bring [skill or strength] and hope to contribute to [realistic priority]."
The brackets should become facts you can defend. Use a measurable result when you have one. If the number is confidential, describe the scale or outcome honestly rather than inventing a figure.
Your company detail needs a purpose. "You have a great reputation" doesn't give the interviewer much to explore. "Your team is expanding its self-service support resources, which connects with my experience improving help content" connects the employer to your background and the work.
That connection is the point.
How to use the STAR method without sounding rehearsed
STAR means Situation, Task, Action, and Result. It can give the evidence in your answer a clear shape. You don't need to announce each label.
Move quickly through the situation and task. Spend more time on what you did and what changed. Finish by tying the example back to the role.
"I'm drawn to this operations role because it involves improving handoffs between teams. At my previous employer, requests were often delayed because ownership was unclear. I mapped the process, created a shared intake system, and introduced a simple review step. The team had fewer missed handoffs, and I learned that I enjoy turning messy processes into workable routines. That is the kind of improvement I would like to support here."
The action should get most of the airtime. The result should close the loop.
If the interviewer wants more detail, expand the example. Otherwise, stop.
Sample answers by role
Use these examples to see how the parts fit together. Don't memorize them word for word. Keep the structure, then replace the details with your own experience.
Entry-level or no direct experience
"This entry-level marketing role interests me because it brings together writing, audience research, and performance tracking. For a campus project, I planned content, reviewed engagement, and changed the schedule based on what readers responded to. I like that the posting emphasizes learning across several channels because I'm looking to build a broad foundation. I would bring organization, curiosity, and a willingness to test ideas and improve them."
A related job isn't the only source of evidence. Coursework, volunteering, student organizations, freelance work, and an independent project can all show a relevant skill in use. The example doesn't have to match the position perfectly. It needs to show what you did and what you learned.
Technology role
Start with the engineering work that actually matches your background. Then use one project to support the connection.
"Your software engineering role interests me because it combines backend development with reliability and security. In a previous project, I worked on [feature or system] and helped address [technical problem] by [action]. I was especially interested in your focus on [verified product, customer need, or engineering priority]. This role would let me use my experience with [relevant technology] while contributing to systems users can depend on."
A long language list won't explain your interest. Choose the tools and engineering problems that relate to the posting.
Sales role
"I want this sales role because it starts with understanding a customer's problem before recommending a solution. In my previous position, I used discovery questions and consistent follow-up to move prospects through the pipeline. I learned that the conversation becomes much stronger when the recommendation connects to a clear business need. Your team serves [customer segment], which fits the consultative selling I want to keep developing. I would bring preparation, persistence, and a strong focus on customer fit."
Put a verified performance measure after the action if you have one. A quota, conversion rate, retention result, or account value can make the example concrete. Be ready to explain your part in the result.
Management position
Management answers need to show how you help other people perform. Individual output alone isn't enough.
"I'm interested in this management role because it combines delivery with coaching. In my current position, I have supported teammates through [project, process, or challenge], clarified priorities, and helped the group stay accountable for its work. Your posting emphasizes developing people while improving team performance, and that balance matters to me. I would bring a practical, supportive leadership style and a focus on clear expectations."
The important evidence is how you led through other people. Not just how much work you completed yourself.
Senior or career-change role
"After working in [current field], I'm ready for a role where I can apply my experience with [transferable skill] to [new function or industry]. The move makes sense because this position requires [shared responsibility], which has been a consistent part of my work. I was drawn to your organization because of [specific, verified detail], and I see a clear connection between that need and what I can contribute. To be honest, I know I have industry-specific learning to do, but I have already built the problem-solving and communication skills the role requires."
Career changers don't need to claim that every part of the move is identical. Explain the connection. Acknowledge the learning curve without apologizing for it.
Common mistakes and better alternatives
Weak answers tend to fail in familiar ways. They stay generic, focus only on what the candidate wants, or promise more than the candidate can support.
| Weak approach | Why it hurts | Better approach |
|---|---|---|
| "I need a job" | It doesn't explain why this role fits | Name the work, problem, or customer group that interests you |
| Talking only about salary or benefits | It can make your motivation sound transactional | Lead with the responsibilities, then discuss compensation when appropriate |
| Praising the mission without mentioning the role | Any applicant could give the same answer | Link the mission to a task you would perform |
| Repeating the job description word for word | It sounds copied and doesn't show your perspective | Rephrase one responsibility and connect it to your experience |
| Saying the company is "innovative" or "great" | The claim is too broad to be useful | Mention a product, initiative, customer need, or working practice |
| Telling a long career story | The answer loses its focus | Use one relevant example and save the rest for follow-up questions |
| Using results you cannot explain | Follow-up questions can expose overstatement | Use only accurate achievements and be ready to describe your role |
| Memorizing every sentence | A small interruption can derail the answer | Memorize the structure and key points instead |
Growth belongs in the answer when it supports the work. Explain what you want to learn and why that learning matters for the role. Don't make the position sound like a temporary stop you plan to leave.
How to answer follow-up questions
Your first response often determines the next question. Prepare for the likely branches, but don't script a second interview in your head.
"Why this company rather than another one?"
"The role itself is my main reason for applying, especially its focus on [responsibility]. I also noticed [specific company detail], which suggests the team is working on a problem I care about. That combination is more relevant to my background than a similar title without the same focus."
"Why are you looking now?"
Keep this answer pointed toward the future. Talk about the responsibility, scope, or type of challenge you want next. Leave a complaint about a current or former employer out of it.
A short answer is usually stronger here. Say what you want to move toward.
"What would you hope to accomplish first?"
Choose a first priority that follows from the posting. You can say:
"I would first learn how the team measures success, understand the main customer or internal pain points, and then look for a small improvement I could own."
That shows initiative without pretending you already understand the job before your first day.
"Is salary the main reason you want this job?"
Thing is, compensation can be part of your decision. You don't need to deny that. Say you want a role that fits your responsibilities and expectations, while making clear that the work, team, and opportunity matter too.
If the interviewer asks about pay directly, answer that question directly. Don't force salary into your motivation statement.
Turn the job listing into an interview brief
Your application tools can support this preparation, provided the notes stay tied to the exact role. If you apply through a job board or hiring platform, save the posting or copy its important sections into your job-search notes. Listings get edited, closed, and reposted with different wording. You don't want to rely on responsibilities that the current version no longer mentions.
Keep the title, employer, posting date, source, three central responsibilities, required skills, one company detail, and two questions you want to ask in the same place. Then set the posting beside the resume version you actually submitted.
Your interview answer should support the same story as your application. It should sound spoken, though, not copied from the resume.
A resume tool or application tracker can keep versions and notes organized. It can't decide whether the position is a genuine fit. Verify important details on the employer's official site before mentioning them in the interview.
Frequently asked questions
How long should the answer be?
Aim for roughly 45 to 90 seconds in a first interview. A shorter response works if the question is only a quick warm-up. Stop once you've made the point.
Should I mention company culture?
You can, if you can say what you mean. Instead of "I like your culture," point to a collaborative project, mentoring approach, customer focus, or decision-making style you found during your research. Then connect that feature to how you work.
A vague culture compliment sounds interchangeable. A specific observation gives the interviewer something to ask about.
How can I answer if I don't have experience?
Use evidence from school, volunteering, personal projects, temporary work, or community activities. Explain what you did, what you learned, and how that experience connects to the position.
Enthusiasm helps. Specific action makes it believable.
Can I use the same answer for every interview?
Use the same structure, not the same wording. Change the responsibility, company detail, and contribution so the answer reflects the actual position.
Before your next interview, paste the job description into a notes document. Highlight its three central responsibilities, then write one sentence connecting each responsibility to your experience. Choose the strongest connection, add one verified company detail, and practice saying the result aloud without reading it.