Put this into action
Turn this guide into better conversations with Articuler
Use this guide as the research layer, then turn the next step into a live networking workflow: search by intent, prep for the conversation, and send outreach that is built for replies.
Try the Articuler workflowThe fastest way to answer "What attracted you to this position?" is to connect three things: a specific part of the role, something concrete about the company, and where it fits your career goals. Skip the vague enthusiasm. Name the responsibility that excites you, point to a real detail you found in your research, and explain why it makes sense for where you're headed.
Done well, that takes about 60 to 90 seconds. Done badly, it sounds like you'd take any job that pays. This guide gives you the framework, several example answers for different roles, and the mistakes to avoid.
What the interviewer is really asking
This question looks friendly, but it's a screen. Hiring managers ask it to find out two things fast.
Did you do any homework? They want to know if you read the job description and looked into the company, or if you mass-applied and forgot which job this even is. SHRM's guidance on answering common interview questions is blunt about it: candidates should name what drew them in from the job description and tie it to the organization's mission. A generic answer tells them you're casting a wide net.
Will you actually stay and care? A candidate who's drawn to the specific work tends to last longer and perform better than one chasing a paycheck. So they're listening for genuine fit, not flattery.
Structured interviews exist precisely to weed out vague answers. SHRM notes that structured interviews are roughly twice as predictive of job performance because they tie every question to job-relevant criteria. Your answer should hand them that relevance directly.
The role + company + goals framework
Strong answers cover three pieces. You don't need equal time on each, but you need all three.
| Piece | What to say | What it proves |
|---|---|---|
| Role | A specific responsibility or challenge in the job description | You read the posting and understand the work |
| Company | A concrete detail — product, mission, recent move, team | You researched them, not just the title |
| Goals | How this advances where your career is heading | You're intentional, likely to stay |
Lead with whichever is strongest, then tie the other two in. Keep the whole thing under 90 seconds. Robert Half's recruiters and most interview coaches agree: focus on reasons that benefit the employer, even when your real motivation is personal.
A quick template:
> "I was drawn to [specific responsibility] because [relevant experience or skill]. I've followed [company detail], and [why it matters to you]. Long term I want to [goal], and this role moves me toward that."
Example answers for different roles
These are samples. Don't memorize them word for word — interviewers can hear a script. Use them to see how the three pieces fit together, then swap in your own details.
Software engineer
> "The part that grabbed me was owning the payments service end to end. I spent two years untangling a fragile checkout flow at my last job, so building a clean one from scratch is exactly the kind of problem I want next. I also saw your engineering blog post on cutting deploy time to under five minutes — that culture of shipping fast is rare, and it's where I do my best work."
Marketing manager
> "Two things. First, the role splits time between brand and performance, and most jobs force you to pick one. I've run both and I'm better when I can connect them. Second, I've been a customer of yours for a year — the way you launched the referral program last spring was sharp, and I want to be part of a team that markets like that."
Registered nurse
> "I was attracted by the focus on patient education in this unit. I'm at my best when I have time to actually teach families how to manage care at home, and your discharge program is built around that. I read that you reduced 30-day readmissions last year, which tells me the leadership backs that approach instead of just rushing turnover."
Entry-level / career switcher
> "I'm moving into UX from teaching, and what attracted me here is that you pair new designers with a senior mentor for the first six months. I learn fastest with feedback, and that structure is exactly what I need. I also use your app daily, and the onboarding redesign you shipped is what made me realize this is the work I want to do."
Notice the pattern: every answer names a real role detail, a real company detail, and a reason that's true for that person. That's what makes a sample sound like a person instead of a brochure.
Common mistakes that sink the answer
Most weak answers fail in predictable ways.
- "The pay and benefits are great." True, maybe, but it tells the interviewer you'd leave for an extra dollar elsewhere. Lead with the work.
- Generic flattery. "You're an industry leader with a great reputation" applies to a thousand companies. If your answer would fit any employer, it fits none.
- Reciting the About page. Reading their mission statement back to them proves nothing. Show what you *did* with the research — a reaction, a connection to your experience.
- Making it all about you. "This is a great stepping stone for my career" centers your benefit, not theirs. Frame goals as a fit, not a launchpad.
- Trashing your current job. "I need to get out of where I am" turns the answer negative. As the HBR guide to common interview questions advises, keep the framing on what excites you about this role, not what you're escaping.
If you can swap the company name in your answer for a competitor's and it still works, it's too generic. Start over.
How to research the role and company first
You can't fake specificity. Twenty minutes of research is what separates a memorable answer from a forgettable one. Work through these:
- Re-read the job description. Underline the two or three responsibilities that genuinely interest you. Those are your "role" hooks.
- Read the company's recent news. A product launch, funding round, or new market. Reference something from the last six months so it's clearly current.
- Check the team and product. Look at who you'd report to and what they ship. The Wikipedia overview of the job interview notes that candidate preparation and knowledge of the organization measurably improve interview outcomes.
- Find one genuine connection. A shared value, a product you use, a problem you've solved before. One real detail beats five recycled ones.
The hardest part is usually finding *who* you'd actually work with and what they care about. That's where most candidates stop at the company's homepage. If you can name the hiring manager and the problem keeping their team up at night, your answer writes itself.
This is exactly the kind of prep Articuler is built for. Describe the role and team in plain language, and its AI meeting prep builds a Playbook on the specific person you're interviewing with — what they've shipped, what they prioritize, what they'd want to hear. You walk in with a "what attracted me" answer aimed at a real person instead of a job board.
How it differs from "Why do you want this job?"
These two questions overlap, but they're not the same, and answering them identically is a missed signal.
| "What attracted you to this position?" | "Why do you want this job?" | |
|---|---|---|
| Emphasis | The pull — what drew your attention | The push — your motivation to commit |
| Best lead | A specific role or company detail | Your fit and what you'd contribute |
| Tense | What caught your eye | Why it makes sense going forward |
| Risk if generic | Sounds like you didn't research | Sounds like you'd take anything |
"Attracted" is about the spark — the responsibility or detail that made you click apply. "Why do you want this job" is about commitment and contribution. The Michael Page guide on answering "why do you want this job" leans harder on how your skills serve the company. If you get both in one interview, shift the weight: attraction first, contribution second.
If salary comes up in the same conversation, handle it separately and deliberately — see our guide on how to answer salary expectations. And if the role leans on past examples, prepare for behavioral interview questions too, since "what attracted you" often leads straight into "tell me about a time."
Next step
Use Articuler to act on what you just read
Start with one concrete goal: investor intros, sales prospects, event meetings, hiring-manager outreach, or expert conversations. Articuler turns that goal into people, prep, and messages.
Start networking with intentFAQ
How long should my answer be?
About 60 to 90 seconds. Long enough to cover role, company, and goals with one concrete detail each; short enough to keep the interviewer's attention. If you're past two minutes, you're rambling.
Can I mention salary or benefits at all?
Not as your main reason. Compensation as the headline signals you'd leave for a better offer anywhere. Lead with the work and the fit. Save the money conversation for when they raise it, and frame it on its own terms.
What if I'm not that excited about the role?
Find one true thing. Even a job you're lukewarm on has a responsibility, a team, or a mission detail you can honestly connect to. Interviewers can tell genuine from forced, so build the answer around the real hook, however small, rather than inventing enthusiasm.
Should I write out my answer beforehand?
Draft it, then don't memorize it. Writing helps you organize the three pieces and pick your best details. But reciting a script sounds robotic. Practice the structure, then say it in your own words each time.
How is this different from "Why should we hire you?"
"What attracted you" is about your interest in them. "Why should we hire you" is about their reason to pick you — your skills and results. One sells your motivation, the other sells your value. Prepare both, and don't blur them. The same goes for trickier prompts like what are your weaknesses, which test self-awareness rather than enthusiasm.