How to Answer “Why This Role?” Without Repeating Your Resume

Answer “Why this role?” with one specific detail about the work or organization, then connect it to a truthful experience, interest, or goal. Don’t summarize your resume or rely on generic praise. If the prompt names a particular project, mission, or motivation, answer that directly instead of forcing a career-goal explanation.

A strong answer gives the reader a small, clear reason to believe you chose this opportunity deliberately. It does not need to prove that this is the only job you would ever accept. It needs to show that you understand something about this role, that the detail matters to you, and that your explanation is true.

That is a different task from summarizing your qualifications. Your resume says what you have done. This answer explains why this opportunity makes sense to you. The best short response joins those two ideas without retelling the same bullet points.

What does “Why this role?” ask you to explain?

The prompt asks for your motivation for applying to this particular role, organization, project, or opportunity. It is not simply asking whether you are qualified, whether you need work, or whether you admire the employer. Those points may matter elsewhere, but they do not answer the question on their own.

Application forms use different wording. You might see “Why are you interested in this position?”, “What attracts you to our organization?”, “Why did you apply?”, or “What interests you about this opportunity?” The phrasing gives you a clue about what belongs in the answer.

• “Why this role?” Focus on the work, responsibilities, or type of problem.
• “Why this organization?” Focus on a specific aspect of the organization, such as its work, audience, approach, or stated mission.
• “Why this project?” Explain what draws you to the project itself and, if useful, how your experience or interests connect.
• “Why are you applying now?” A change in direction, a next step, or a current motivation may be more relevant than a detailed discussion of the employer.
• “Why are you a good fit?” This asks for both motivation and evidence of relevant ability. Use a concise example that supports the match.

The categories can overlap, but don’t treat every prompt as interchangeable. A response that names the employer but says nothing about the work may miss a role-focused question. A response that only describes your ideal career path may miss a prompt that asks about the organization’s mission.

Read the full question and its nearby instructions before drafting. The form may give a word or character limit, ask for a particular topic, or provide another field for your relevant experience. Answer what is actually asked. Don’t make one small text box do the work of your resume, cover letter, career history, and personal statement.

A useful test is to remove the employer’s name. If the answer still fits dozens of unrelated organizations, it is probably too general. If it only works for this role because it refers to a specific responsibility, project, audience, or real motivation, it has a stronger reason for being there.

What is the best structure for a concise answer?

Use a three-part connection: one specific detail, why it matters to you, and a truthful link to experience or direction. That structure is flexible enough for different backgrounds and short enough for most application fields.

1. Name the detail. Identify a responsibility, project, customer group, technical problem, working context, or organizational priority that genuinely caught your attention.
2. Explain the personal connection. Say why that detail interests you. It might relate to work you have done, a skill you want to use, a subject you care about, or a direction you want to explore.
3. Add one piece of support. Give a brief, relevant example or state what you hope to contribute or learn. Keep the claim proportional to what you can truthfully support.

A simple drafting frame is:

I’m interested in [specific part of the work] because [why it matters to you]. In [real context], I [brief, accurate example], and I’d like to bring that experience or interest to [relevant part of the role].

This is a scaffold, not a script. Do not leave the brackets in, and do not force every answer into two sentences. The point is to make sure your response has both an employer-specific reason and a personal connection.

For instance, saying “I’m excited by the opportunity to contribute to your team” expresses positive feeling, but it gives no detail. Adding a specific responsibility makes the choice more legible. Connecting that responsibility to an experience, question, or skill gives the answer another layer. The exact example can be modest. It only needs to be true and relevant.

Career-services guidance from Harvard’s Mignone Center for Career Success makes a related distinction in its advice on applications and cover letters: tailor your material to the opportunity and explain the connection between the role, the organization, your interests, and your experience. That guidance is not a magic formula for a form response, but it supports the practical choice to be specific rather than repeat a generic statement of enthusiasm. Harvard FAS, GSAS Master’s Resume & Cover Letter and Harvard FAS, Recruiting Frequently Asked Questions

If you cannot yet fill in all three parts, don’t invent a connection. Research the role a little more, find a narrower motivation, or write honestly about what you do know. A plain, supportable reason is stronger than a polished claim you would struggle to explain in an interview.

How do you find a specific reason without forcing enthusiasm?

Start with the job description, not with a flattering sentence about the employer. Look for the actual work: what the person will do, for whom, with what kinds of problems, and in what setting. A meaningful reason usually comes from one concrete feature, not from the broadest statement on the company’s homepage.

Read the posting once for its overall purpose. On a second pass, mark details that sound distinct from a generic description of the profession. These might include:

• A recurring responsibility, such as turning research into guidance for a particular audience.
• A problem the team is trying to address.
• A named project or service described in the posting.
• A part of the process you would own or support.
• A group of customers, patients, students, clients, or community members the work serves.
• A collaboration pattern, such as coordinating between technical and nontechnical teams.
• A skill you would use often, rather than a keyword that appears once in a long list.
• A chance to develop in a direction that genuinely interests you.

Choose one. Two details can work if they form one coherent reason, but a list of four reasons usually turns into a list of employer facts. Your answer is not stronger simply because it contains more research.

Then ask what makes that detail matter to you. Be concrete. “I care about communication” is broad. “I like translating technical information into steps a customer can use” says more about the kind of work that holds your attention. “I want to help people” is sincere but too wide to explain why you chose this role. What people? What kind of help? What feature of this job makes the interest relevant?

You do not need a dramatic origin story. A useful motivation can come from a class project, a regular responsibility, a question you have been following, a type of problem you enjoy, or a skill you want to apply more often. It can also come from a practical fit, such as the role’s mix of analysis and client communication, if that is genuinely what you want.

If the organization’s stated mission matters to you, connect it to something real. You might have experience with the issue, a sustained interest in the audience, or a reason the organization’s approach stands out to you. Don’t imply personal experience you do not have. You can say that a mission interests you without claiming it is your life’s calling.

Avoid generic praise as the main reason. Words such as “innovative,” “dynamic,” “leading,” and “excellent culture” tell the reader little unless you identify what you mean and why it matters. If you cannot name a concrete basis for the praise, leave it out. A respectful, specific sentence is more convincing than exaggerated admiration.

How much research is enough?

Research enough to identify one accurate, relevant detail and understand it well enough to describe it in your own words. You are not writing an organization profile. One reliable detail that you can explain is more useful than several facts collected only to make the answer sound researched.

A sensible research sequence is:

1. Start with the posting. It is the closest source for the duties and expectations of the role you are applying to. Note what the person would actually work on, not just the list of desired qualifications.
2. Check the organization’s own material if you need context. Look at the relevant project, service, team, or mission page. Prefer a page about the exact work to a broad home page slogan.
3. Confirm details that may have changed. If you plan to mention a current initiative, product, leader, or recent development, verify it on a current, reliable page. A stale detail can make a carefully prepared answer look careless.
4. Stop when you have a usable connection. You need enough information to say what interests you and why. You do not need to pack the answer with facts to prove that you browsed.

Separate what the employer says from what you infer. If a company says a team is building a new service, you can say the project interests you. Don’t turn that into an unsupported claim that the service has transformed an industry or achieved a particular result. When you describe the organization’s work, keep the claim as narrow as the source.

If the posting is vague, the available information is thin, or you have little time, use the best detail you can verify. The role’s responsibilities may be enough. You can focus on the work itself rather than pretending to know the team’s culture or long-term plans.

Research should sharpen your reason, not supply a borrowed personality. Don’t write that an organization is your “dream employer” because you found a mission statement. Don’t claim that you have followed its work for years unless that is true. A reader can value straightforward interest without being told that every job is a lifelong ambition.

How do you connect the role to experience without retelling your resume?

Use an example that explains your interest, not a miniature version of your work history. One detail from your background is enough if it shows why a part of the role appeals to you or how you have already approached similar work.

Your example might come from paid employment, education, volunteering, a personal project, caregiving, or another genuine responsibility. The source of the example is less important than an accurate description of what you did and a clear connection to the role. If your experience is limited, describe a relevant activity without inflating its scope.

A resume bullet often answers: What did you do, and what happened? A response to “Why this role?” should answer: Why does that kind of work interest you, and why this opportunity? The same underlying experience can inform both answers, but the emphasis changes.

Imagine a candidate whose resume says they organized a weekly help desk rota. The application answer does not need to repeat every scheduling task. It might explain that the role interests them because it combines practical problem-solving with direct support for users, then mention that coordinating the rota taught them how much they enjoy making help easier to find. The resume records the responsibility. The answer explains why a related responsibility attracts them now.

Do not make the connection too neat. A past task need not prove that you have mastered the work. You can write that it introduced you to a type of problem, strengthened an interest, or gave you a useful foundation. Those phrases make a smaller claim, but a more believable one.

When your background does not match the role directly, connect through a transferable task or a purposeful next step. Maybe you have handled detailed records in one setting and want to apply that care in another. Maybe a project gave you a first view of a subject you want to explore. Name the difference between what you have done and what you want to do. Don’t present interest as experience.

If you have plenty of relevant experience, resist the urge to list it all. Choose the example that illuminates the reason you named. The reader can find the rest in your resume. Harvard’s guidance on application materials likewise warns against reiterating the entire resume when a small number of relevant examples will do. Harvard FAS, HES Create Impactful Resumes and Cover Letters

What if you are changing careers, new to work, or applying for a first role?

You can give a credible answer without a long record in the field. Explain the work that attracts you, the reason it matters, and the real experience or exploration that led you to apply. Your connection does not have to be professional history.

For a career change, make the direction clear without describing your past career as a mistake. Identify the part of the new role that interests you and show what has helped you prepare to pursue it. A relevant course, project, volunteer responsibility, or repeated task at work can show a considered move. Be clear about what is new for you.

For example, a hypothetical candidate moving from retail operations toward inventory analysis might be interested in roles that involve finding patterns in stock movement and helping teams plan orders. If the candidate has actually maintained a stock log or reviewed reorder information, they can mention that experience accurately. They should not claim to have built forecasting systems if they have not. The answer can make a case for direction and potential without disguising a gap.

For a first job, draw from education, part-time work, volunteering, a club, a personal project, or a responsibility outside formal employment. The point is not to pretend that these are equivalent to years in a professional role. It is to show what you have encountered and why the advertised work interests you.

A hypothetical student applying for a research assistant role might say that the chance to organize source material appeals to them because they enjoyed carefully comparing evidence in a course project. That is a modest connection. It does not claim professional research experience or a published finding. It gives the reader a real reason the candidate has noticed this task.

If you have not had a chance to try the work, talk about what you want to learn, but anchor the desire in something more specific than “I want experience.” Which part of the role do you want to learn? What made you curious about it? Is there a course, conversation, or adjacent responsibility that prompted the interest? You can describe an informed next step without claiming certainty about a field you have barely encountered.

If you are returning to work after a break, you do not need to turn this answer into a personal disclosure unless the prompt calls for it. Focus on why the role’s work interests you now and the experience you can bring. If the break matters to your motivation, explain only what is relevant and comfortable to share.

How do you answer when your main reason is practical?

Be honest, then make the answer about the role rather than pretending practical needs do not exist. Pay, location, schedule, stability, or a shorter commute can influence a job decision. You do not have to claim that these factors are irrelevant. But when a form asks why you want this role, a response that names only a benefit available in many unrelated jobs does not explain your interest in this one.

Look for the part of the work that is also true. Perhaps the schedule makes the role workable and the day-to-day responsibilities fit your interests. Perhaps the role is in a location where you plan to stay and involves a task you already enjoy. State the practical fit plainly if it belongs in the answer, but do not invent a mission-based motivation to make it sound nobler.

Some details belong in a different conversation. If the application asks about compensation expectations, answer that question according to its instructions. If it asks what attracted you to the position, focus on the opportunity itself. Don’t use one field to negotiate terms that were not requested, and don’t make a false promise that money, schedule, or location could never affect your decision.

If your main motivation really is a practical condition and you cannot identify a meaningful feature of the work, consider whether the role is right for you before writing. A polished answer cannot create a genuine connection. It can only express one clearly if it exists.

How should the answer change at different word limits?

Keep the same core idea as the limit changes. Shorten the explanation; don’t remove the specific reason and leave only a generic claim of enthusiasm. If the form gives a strict character or word limit, follow that limit. If it does not, a compact paragraph is usually easier to read than a long essay.

The examples below are hypothetical writing models. They are not real applicants, verified accomplishments, or claims about actual employers. Replace the details with your own evidence. If a model includes an experience you have not had, do not copy it as your story.

At about 25 words

I’m drawn to the role’s focus on turning research into clear guidance. I’ve enjoyed that work in class projects and want to develop it further.

This answer names a type of work, connects it to an honest setting, and describes a direction. It does not identify a specific organization, so it would need adapting if the prompt emphasizes “why us?”

At about 50 words

The role’s focus on turning research into clear guidance for community partners is what caught my attention. In a hypothetical course project, I compared several sources and wrote a short summary for classmates who were new to the topic. I’d like to keep doing that kind of careful, audience-focused work in a professional setting.

The example is explicitly hypothetical as presented here. A real applicant should replace it with a true example or remove it. The answer uses one role detail and one small piece of relevant experience. It does not claim that a class exercise is professional work.

At about 100 words

I’m interested in this role because it combines research with communication for people who need to act on the information. The posting’s emphasis on preparing clear guidance for community partners stood out to me. In a hypothetical course project, I compared source material and wrote a short explanation for classmates who were new to the topic. That experience made me interested in the step between finding information and making it usable for someone else. I’d like to build on that interest in a role where careful research and clear writing support the work of a specific audience.

This longer version adds a little explanation, but it still has one main reason. It does not need a second motivation, a list of flattering claims about the organization, or a compressed retelling of the candidate’s entire background.

At about 150 words

The part of the role that interests me most is turning research into clear guidance for people who need to make practical decisions. The posting describes preparing material for community partners, which is a more specific kind of communication than simply summarizing information. In a hypothetical course project, I compared several sources and wrote a short explanation for classmates who were new to the subject. I found that I enjoyed deciding what a reader needed to understand first, then making the evidence easier to follow without overstating it. I’d like to develop that skill in a role where research and communication serve a defined audience. I’m also interested in how this team approaches its partner work, and would welcome the chance to learn more about the priorities behind the projects described in the posting.

This version has room to describe the motivation in more detail, but length alone does not make it better. If the form asks for 100 words, trim it. If it asks a narrow question about a particular project, the answer should focus more on that project and less on the general appeal of research communication.

At about 250 words

A longer limit can justify an additional layer: what you understand about the role, why the work matters to you, and how your preparation connects. It still should not become an unsolicited cover letter. Here is a hypothetical example:

I’m interested in the role because it combines research with communication for people who need to use the information. The posting’s description of preparing guidance for community partners caught my attention. I like the challenge of making a careful explanation clear without flattening the evidence or assuming the reader already knows the subject.

In a hypothetical course project, I compared several sources and wrote a short summary for classmates who were new to the topic. That was a small academic exercise, not professional partner work, but it helped me notice how much I enjoy deciding what a reader needs to know first. I would like to develop that ability in a role where clear communication supports work beyond the classroom. The opportunity to learn how this team works with its partners is also a specific reason I applied.

The longer response distinguishes a classroom example from professional experience. That qualification is not an apology. It tells the reader exactly what the example does and does not show. If a form gives you a large limit, use the extra space only when another detail adds useful information. A 250-word answer does not need to reach 250 words.

What makes an answer sound generic or unconvincing?

An answer is weak when it could fit almost any job, claims more than you know, or tells the reader something already obvious from the application. The repair is usually not more enthusiasm. It is a sharper, more supportable reason.

“I have always admired your company”

This can work only if it is true and relevant. Otherwise it is praise without information. Replace it with the particular work, audience, approach, or project that interests you. If you have followed the organization for a real reason, say what you followed and why it connects to the role.

“I’m passionate about helping people”

The sentiment may be genuine, but it is too broad to distinguish one role from another. Explain what kind of help the position involves and why that form of work matters to you. If you do not yet know, return to the posting before drafting.

“This is a perfect fit for my skills”

That is a conclusion, not an explanation. Name one relevant responsibility and one truthful connection. Avoid claiming a perfect fit, especially when you have not yet done parts of the work. A specific, limited match is more credible than a sweeping label.

“Your innovative culture is exactly what I’m looking for”

“Culture” and “innovative” are often too vague to carry an answer. If a particular way of working attracts you, name it and identify where you learned about it. Don’t make claims about the team’s culture from a slogan or a guess.

A list of company facts

Research is not the same as motivation. Listing a founding date, office locations, products, and mission statement shows that you gathered facts; it may not show why the job interests you. Choose the one fact that bears on the work and explain the connection.

A second resume summary

“I have five years of experience, strong communication skills, and a record of teamwork” mostly answers “What qualifications do you have?” Use one detail only if it helps explain your interest. Let the resume carry the broader list of evidence.

“This job will launch my career”

Your development matters, but an answer focused only on what you hope to get from the employer can sound one-sided. Connect what you want to learn with the work the role involves and what you can contribute honestly. Don’t promise an employer that you will stay forever or call an ordinary next step a lifelong calling.

Unsupported claims about the organization

Don’t say a product leads the market, a team has a particular culture, or a project changes lives unless you can support the statement. You can express interest without making grand claims. Describe what you observed and what it makes you curious about.

Invented personal history

Never claim you have used a service, attended an event, followed a project, or experienced a cause if you have not. A false detail can raise questions that are harder to answer than the original prompt. If your connection is recent or still developing, say so in ordinary language.

When should you answer a different motivation directly?

Answer the motivation the prompt actually names. The default structure of specific role detail plus a truthful personal connection is useful, but it is not a template to impose on every question. If the employer asks why a mission matters to you, discuss the mission. If it asks about a named project, explain why that project interests you. If it asks why you are making a career change, answer the change.

This is the strongest exception to a career-goal formula. Don’t begin with “This role is the next step in my career” when the question asks what draws you to a particular project. Don’t steer every answer toward your skills if the prompt specifically asks about your motivation. You can still include a brief, relevant experience where it helps, but it should support the requested answer rather than replace it.

Suppose an application asks, “Which part of our community health mission motivates you?” A role-detail answer that talks only about wanting to grow as a project coordinator avoids the question. A direct response would identify the part of the mission that matters to you, give an honest reason, and avoid implying personal experience you do not have.

If the question names a project you know little about, don’t bluff. Refer to the information you have actually read, describe what interests you about it, and, if appropriate, say what you would like to understand better. Specific curiosity is better than false familiarity.

The same principle applies to prompts about location, timing, or career direction. Follow the prompt’s emphasis. The structure is a tool for answering, not a rule that outranks the question.

How can you revise the answer without overworking it?

Draft quickly, then make one pass for relevance, one for truth, and one for length. Don’t polish a generic answer into a more elegant generic answer. First make the reason specific; then edit the words.

Pass 1: Find the real reason

Write down the role detail that caught your attention. Then complete the sentence “That matters to me because…” Use plain language. If your answer is still “because it seems like a great opportunity,” ask what makes it great for you.

Pass 2: Choose one truthful connection

Find the experience, interest, or goal that relates most directly to that detail. You do not need the most impressive thing you have done. You need the clearest relevant connection. Mark where your experience ends and your aspiration begins.

Pass 3: Check the employer-specific detail

Ask whether your answer could be pasted into an application for a different organization without changing anything but the name. If so, add a real detail from the posting or remove a broad claim that is not doing useful work. Do not add a fact merely to make the answer look personalized.

Pass 4: Cut the resume recap

Underline every sentence that lists a qualification. Keep the one that best explains your motivation. Move the rest out. If another field asks for evidence of fit, put supporting qualifications there instead.

Pass 5: Check every claim

Can you explain where you learned the fact about the role or organization? Is the experience yours? Does the wording accurately describe what you did, what happened, and what you hope to do next? Replace an inflated verb or sweeping claim with a precise one.

Pass 6: Match the requested length

Follow the stated word or character limit. If there is no limit, stop when the answer has a reason, a connection, and any context needed to make those clear. A short answer is not incomplete just because it leaves the reader wanting more details for an interview.

Pass 7: Read it aloud

Remove the phrase you would never say to a person. Replace stiff language with direct words. Make sure the answer sounds interested, not worshipful; confident, not certain of an outcome; specific, not crowded.

A final check can be as simple as this:

• Did I answer the exact prompt?
• Did I name something specific about this role, organization, project, or motivation?
• Did I explain why it matters to me?
• Is every statement about my experience true and accurately sized?
• Did I avoid repeating my resume?
• Did I meet the form’s limit?

If the answer passes those checks, stop. More editing can make it smoother, but it cannot manufacture a reason you do not have.

How do “Why this role?” and a cover letter differ?

A form response is usually a focused answer to one question. A cover letter has room to introduce the application, connect several parts of your background to the employer’s needs, and develop a broader case. They can share a central idea, but they should not be identical by default.

If an application asks a short “why” question and separately requests a cover letter, use the answer to make one point well. The letter can develop a wider explanation with a different example or a fuller account of your fit. If the form gives plenty of room, it can still remain focused; a large text box is not an instruction to copy a letter into it.

If you are applying without a cover letter, the form response does not need to become one. Answer the prompt, then let the resume show the history and evidence that the short field cannot hold. Harvard’s recruiting guidance distinguishes application requirements and notes that employers may collect cover letters or answers to questions through their own websites, so follow the instructions for the particular application rather than assuming one document replaces another. Harvard FAS, Recruiting Frequently Asked Questions

A simple division of labor keeps the materials from competing:

The materials should agree about your history and direction. They do not need to repeat the same sentences.

What if you are applying to several roles at the same organization?

Write a distinct answer for each role when the work is meaningfully different. The organization may be the same, but a research position, customer support position, and operations position do not call for the same explanation. Tailoring is not just changing the title in the first sentence.

Start with the duties that separate each role. Identify what interests you in that work and which part of your background or goals connects. One organization detail can still matter across both applications, but it should not crowd out the role-specific reason.

If the jobs are nearly identical, you may share a core explanation and adjust the details that differ. Check the actual posting and avoid claiming that each role is uniquely perfect. If the application asks why you applied to multiple openings, answer honestly and explain the common thread, if there is one.

Harvard’s recruiting FAQ advises applicants to tailor materials when applying to more than one position at an organization. The practical reason is clear: a distinct answer shows that you have considered the actual opportunity rather than treating the employer as the only relevant detail. Harvard FAS, Recruiting Frequently Asked Questions

What if you cannot find anything distinctive in the job posting?

Use the most specific responsibility you can verify, or reconsider whether you understand the opportunity well enough to explain your interest. Some postings are generic. You can still answer with a concrete task, a relevant audience, or a type of problem the role appears to involve.

Don’t invent a special project or team value to compensate for thin information. You can say that the responsibilities interest you because they match a real skill or direction. If a key detail is unclear and you have a legitimate way to ask, seek clarification through the stated contact or recruiting process. You do not have to turn a missing fact into a confident claim.

If the application deadline is near, choose the clearest detail available and keep the answer appropriately narrow. “The position’s mix of data checking and coordination interests me because I enjoy work that requires accuracy and follow-through” is more defensible than a claim about the employer’s culture that you cannot verify.

Frequently asked questions

Should I mention the company by name?

Usually, yes, if it fits naturally and the prompt asks about the employer or a specific opportunity. But naming the organization is not the same as explaining your interest. One accurate detail about the work matters more than inserting the company name several times.

Should I say I am passionate about the role?

Only if that word is accurate and helps explain your reason. “Passionate” by itself is weak because it names a feeling without showing what causes it. Describe the work, problem, audience, or mission that interests you. Plain interest can sound more credible than grand language.

Should I talk about what I will learn?

Yes, when learning is a genuine part of your motivation. Pair it with the work itself and, where relevant, what you can contribute. Avoid making the whole answer about what the employer can give you. A role is more than a training opportunity, and your answer should reflect the responsibilities on offer.

Is it acceptable to say this is a step toward a long-term goal?

Yes, if the connection is real and the prompt leaves room for it. Explain what part of the role relates to the goal. Don’t force every answer into a career-plan story, especially when the question asks about a specific project, organization, or mission.

Can I use an example that is not on my resume?

Yes, if it is true, relevant, and described accurately. A form response can add context or a small example that does not fit on the resume. Don’t make a small example sound like a larger job responsibility, and don’t add private or sensitive details that the prompt does not require.

What if my honest reason is that I need a job?

That is a real practical reason, but it does not explain why this role in particular interests you. If you can identify a genuine feature of the work that suits you, discuss it. Do not invent a deep connection. If no such feature exists, think carefully about whether you want to apply rather than trying to disguise the mismatch.

How specific should I be about the organization?

Specific enough to show that your answer belongs to this opportunity, but not so specific that you rely on an uncertain or irrelevant fact. A duty in the posting is often safer than an unverified assumption about the team. Use current source material for details that can change.

Should I repeat the wording in the job description?

You can use accurate terms that describe the work, but don’t copy a string of phrases and present them as your motivation. Put the detail into your own sentence and explain why it matters to you. The goal is a truthful connection, not keyword imitation.

Can an answer be only one sentence?

Yes. A one-sentence answer can work when it names a specific reason and connects it to you. If the form asks for more detail or the motivation needs explanation, use more space. Do not make it longer just to sound serious.

Write a reason you can stand behind

The best answer is not the most enthusiastic one. It is the one that makes a clear, truthful connection between the opportunity and the person applying. Name a real detail. Explain why it matters. Support the connection with one accurate example or a genuine direction.

Then respect the prompt. If it asks about a project, answer about the project. If it asks about a mission, explain your response to the mission. If it asks why this role, show why the work stands out to you. Your resume can prove what you have done; this short answer should explain why you chose to apply.

Before you submit, check that the answer says something you could comfortably explain in a conversation. If it does, stop polishing and return to the rest of the application. For a clear, readable resume that supports the same application, explore the free resume editor.