Answers to questions people ask about career documents and conversations. You can use the insight and the steps on your own. Where there is a starter prompt, it is optional — the work stays in your own tools; we do not store it here.
What an answer can include
One page if you have under about 10 years of relevant work. Two pages is normal for a longer or more senior career. Do not go to three pages unless a posting, an academic CV, or a federal application asks for that format.
An ATS-friendly resume is one the software can parse into fields. Use one main column, standard headings (Experience, Education, Skills), a common font, and a .docx or a simple PDF. Do not put your name, dates, or bullets inside images, text boxes, or complex tables. ATS-friendly is about parseability, not a secret keyword score.
Each bullet should be a consequence, not a job duty. Pattern: what you did, to what, with what result (who was affected, by how much, if you actually know). “Responsible for managing vendors” is a duty. “Cut vendor onboarding from six weeks to three by…” is a consequence. Do not invent numbers.
The reader cares what you can do for them. A traditional resume lists past tasks and leaves them to infer capability. A capability-forward resume names the capability, then gives evidence. Use labeled capabilities on the current or most recent role; keep older roles as proof bullets. Every fact must come from your notes.
A traditional chronological resume lists roles from most recent to oldest, with a short summary, education, and skills. It is what most applicant systems and many humans expect. Use the same evidence you would use for a capability-forward resume; only the shape changes.
A summary is three to five lines on the capability you want this reader to hire, plus enough evidence that it is believable. It is not an objective (“seeking a challenging role”) and not a personality paragraph. If you cannot point to evidence in the rest of the resume, cut the claim.
Lead with education, projects, campus or community roles, athletics, and any jobs, treated as evidence the same way you would treat paid work: what happened, the result, what you can do next. One page. A class project with a real outcome is more useful than a vague “leadership” line.
Keep evidence from the old field. Rewrite it as transferable capability for the next manager, not as a tour of the old industry. Cut duties that only make sense in the previous job. Target the posting. Do not keep a generalist dump and hope they translate it.
Use numbers you can stand behind: money, time, volume, people, frequency. Keep hedges (“approximately,” “more than”). If you only know “the backlog shrank,” say that. Never let a chatbot turn “improved the process” into “increased efficiency 40%.”
On a typical U.S. industry resume, leave off age, date of birth, photo, Social Security number, full street address, marital status, reasons for leaving, and “references available on request.” Also leave off anything you cannot defend in an interview or that you do not have the right to disclose.
In the United States, a resume is a short targeted marketing document (usually one or two pages). A CV (curriculum vitae) is a long academic record of publications, teaching, grants, and appointments. Use a CV for academic, research, and many international applications; use a resume for most U.S. industry jobs.
Skills are teachable capabilities (SQL, contract negotiation, facilitation). Strengths are patterns that explain effectiveness (judgment under ambiguity, calm with incomplete data). A resume skills section should be skills. Strengths belong in stories and interviews unless a posting asks for them.
Date the gap honestly. You do not need a long explanation on the resume. A one-line context can be enough (caregiving, study, layoff, health, travel) if you want it there. The fuller story belongs in the interview if they ask. Do not fake consulting to hide a gap you cannot discuss.
Also asked
A resume an applicant tracking system can parse: one main column, standard headings (Experience, Education, Skills), no essential text in images or complex tables, .docx or a simple PDF. ATS-friendly means parseable. It is not a secret numeric score from stuffing keywords into a footer.
Related: What is an ATS-friendly resume?
For most U.S. industry jobs, no. Photos can introduce bias and are not needed to parse an application. Include a photo only if you are applying in a market or occupation where it is clearly expected.
Related: What should you leave off a resume?
Follow the posting. If it does not specify, a text-based PDF or a .docx both work if the text is selectable. Avoid image-only PDFs. Keep a simple .docx when you know they use an older parser.
Related: What is an ATS-friendly resume?
Emphasize the last 10–15 years of relevant work. Older roles can be a short line or omitted if they add nothing for this reader. Academic CVs and federal resumes are different; they often want more history.
Related: How long should a resume be?
A chronological (or hybrid) resume by role is what most U.S. readers and applicant systems expect. A purely functional resume that hides dates often raises questions. If you are changing fields, reframe bullets inside a chronological structure rather than hiding your timeline.
Related: How do you write a traditional chronological resume?
School, degree or program, field, and year (or expected year) are enough for most industry resumes. Add coursework or GPA only if you are early in your career and it helps this reader. Put education higher on the page when it is your strongest context.
Related: How do you write a resume with little work experience?
Only if they are genuine evidence for this role (a relevant sport, a public project, a language you actually use). Otherwise they cost space. Do not list generic interests to seem “well rounded.”
Related: What should you leave off a resume?
Two pages is normal for a longer or more senior career. Put the strongest evidence on page one. Three pages is for special formats (academic CV, some federal resumes), not a default.
Related: How long should a resume be?
Start bullets with a verb that matches what you actually did (led, designed, negotiated, shipped). Verbs do not replace a result. “Spearheaded synergistic initiatives” is worse than a plain verb plus a real outcome. Use a thesaurus only if the word stays accurate.
Related: How do you write resume bullets?
Include a cover letter when the posting asks for one, when you are changing fields, or when a human is likely to read a file you email. Skip it when the form has no place for it. A letter does not fix a resume that does not match the role.
Keep a cover letter to about half a page to three-quarters, rarely over one page. Three short paragraphs are enough: why this role, evidence you can do the work, a clean close. Use only facts from your notes and the posting. Do not repeat the resume bullet by bullet.
Name the role and one specific fact about the work (not “I am excited to apply”). The second sentence should be the capability you are offering. Do not open with your name or “I am writing to apply.”
Also asked
About half a page to three-quarters, rarely over one page. Three short paragraphs are enough: why this role, evidence you can do it, a clean close.
Related: How do you write a cover letter?
The resume is evidence, usually in bullets. The letter is a short argument for this role: why them, why you, in prose. Do not paste resume bullets into the letter. If you only have time for one document, make the resume match the posting.
Related: How do you write a cover letter?
Use the same structure: why this role, evidence from school, projects, activities, or jobs, clean close. Do not apologize for inexperience. Do not invent internships. One page is already too long; stay closer to half a page.
Related: How do you write a cover letter?
List 6–8 real incidents that cover challenge, conflict, mistake, leadership, influence without authority, and a result you are proud of. Write each as STAR+LAI. Practice out loud. Map two stories to the posting’s top requirements. Do not invent incidents to fill the list.
STAR is Situation, Task, Action, Result: a way to answer “Tell me about a time…” so the story has context, your job in it, what you did, and what happened. Keep Situation and Task short. Spend the time on Action and Result. Use it for behavioral questions, not for every yes/no.
After Result, add what you learned, what you changed next time, and evidence that change helped. That is STAR+LAI (Lesson, Application, Impact). Interviewers remember stories that teach, not lists of tasks. Spoken length for a behavioral answer is usually 2–3 minutes.
Score 1–5 on Credibility (specific evidence), Relevance (maps to this role), Authenticity (sounds like you), Conciseness (no filler), and Answer quality (you actually answered what was asked). Rewrite the lowest score first. Quote your draft in the notes so the feedback is about this text.
Take 90 seconds to 2 minutes. Present, past, future: what you do now, the path that made that make sense, why this role is the next use of it. Do not start in childhood. Do not read the resume. End on this job.
Give a coherent career narrative in about 2–3 minutes, not a reading of bullets. Explain transitions. Use forward-looking language: what each stage taught you that you can do now. Spend more time on recent, relevant work. End by connecting that path to this opportunity.
Name two or three strengths that match this role. Support each with a specific example or result. Avoid clichés (“hardworking,” “team player”) unless you have proof. Sixty to ninety seconds is enough.
Pick a real limitation that would not disqualify you for this role. Say what it looks like in practice, what you put in place to compensate, and a recent example of the habit. Do not offer a strength in disguise (“I care too much”). Keep it under about 90 seconds.
Pick a real, recoverable failure you owned, what you changed, and later evidence of the change. Do not blame the team. Do not pick a trivial miss. Do not pick a failure that is disqualifying for this role. Use STAR+LAI. About 2–3 minutes.
Describe the disagreement without making the other person the villain, what you did to understand their constraint, how it resolved, and what you do differently in disagreements now. Unresolved grudges and “I was right” stories land poorly. Use STAR+LAI. About 2–3 minutes.
For a challenge: pick something meaningful, with your agency and a result — not a trivial inconvenience and not a story that only blames others. For an accomplishment you are proud of: pick one with evidence, and say why it mattered, not only that you won. Both work well as STAR+LAI, about 2–3 minutes.
Why this role: map your evidence to the work they described. Why this company: a specific, true reason you actually have — not a paraphrase of the about page. Why hire you: two or three capabilities they need, each with proof. Keep each answer under two minutes.
Why you are leaving: honest, short, and forward. Do not dump on an employer. Five years: a direction that could include this job, not a scripted title. What motivates you: a real pattern in your work, with one example. These answers are usually under 90 seconds each.
Ask questions that show you prepared, that you heard what they said in the room, and that you want their judgment — not questions whose answers are in the posting. A reliable pattern is PRAR: Provenance (something you researched), Reflection (a callback), Accolade (a specific true compliment), Request (“I would value your advice on…”). Prepare five; you may only get two.
“Tell me about yourself”: 90 seconds to 2 minutes. A behavioral story: about 2–3 minutes. A weakness answer: under about 90 seconds. If they asked a yes/no, do not tell a three-minute story. When in doubt, stop at two minutes and offer a deeper example.
Also asked
A real, recoverable failure you owned, what you changed, and later evidence of the change. Do not blame the team. Do not pick a trivial miss or a disqualifying disaster. Use STAR+LAI. About 2–3 minutes.
Related: How do you answer “Tell me about a failure or mistake”?
Describe the disagreement without a villain, what you did to understand their constraint, how it resolved, and what you do differently now. Use STAR+LAI. About 2–3 minutes.
Related: How do you answer “Tell me about a conflict with a coworker”?
Map your evidence to the work they described. Use the posting’s language only where it is true for you. Under two minutes. Do not recite their about page.
Related: How do you answer why this role, why this company, and why hire you?
Give a specific, true reason you actually have — product, problem, team, location — not a paraphrase of the marketing site. If you did no research, say less rather than inventing a passion.
Related: How do you answer why this role, why this company, and why hire you?
Two or three capabilities they need, each with proof from your notes. It is a tight case, not a recap of your whole life. Under two minutes.
Related: How do you answer why this role, why this company, and why hire you?
A direction that could include this job: capabilities you want to use, not a scripted title in their org chart. Honest and short, usually under 90 seconds. Do not invent a path you do not want.
Related: How do you answer why you are leaving, five years from now, and what motivates you?
Honest, short, and forward. One true reason (scope, location, layoff, growth) without a grievance list. Do not dump on an employer.
Related: How do you answer why you are leaving, five years from now, and what motivates you?
A real pattern in your work, with one example. Skip “I’m passionate about excellence.” Under 90 seconds.
Related: How do you answer why you are leaving, five years from now, and what motivates you?
A meaningful challenge with your agency and a result — not a trivial inconvenience and not a story that only blames others. STAR+LAI, about 2–3 minutes.
Related: How do you answer challenge and accomplishment questions?
Pick a real project. Say your role, how you handled disagreement or dependence on others, and the outcome. Avoid “I’m a team player” with no incident. STAR or STAR+LAI, about 2–3 minutes.
Give the method you actually use (urgency vs importance, stakeholder, deadline) and one example where you said no or sequenced work. Vague “I make lists” is not enough. Keep it under two minutes unless they ask for a full story.
Related: What is the STAR method?
Describe what pressure looked like, what you did (not just “I stay calm”), and the result. A STAR+LAI story beats adjectives. About 2–3 minutes if they want an example; shorter if they want a method.
State the tradeoff, the information you had, what you chose, and what happened. Include the lesson. Do not pick a decision with no downside. STAR+LAI, about 2–3 minutes.
Pick one with evidence and say why it mattered, not only that you won. Include what was hard. STAR+LAI, about 2–3 minutes.
Related: How do you answer challenge and accomplishment questions?
Add one thing not yet covered that helps this role: a constraint, a capability, or a story. Do not repeat your whole pitch. Thirty to sixty seconds. It is fine to say you have covered the important points and ask a PRAR question.
One honest sentence for the gap, then what is true now (skills kept, reason you are ready). Do not over-explain. Do not lie. If you did real work in the gap, say so with outcomes, not a cover story.
Phone screens are shorter: tighter “tell me about yourself,” fewer full STAR stories, more screening facts (location, salary band if they ask, why this role). Onsite or loop interviews can hold 2–3 minute stories. Match their clock; if they interrupt, stop.
Two or three strengths that match the role, each with evidence. Sixty to ninety seconds. Skip generic claims without examples.
For a stranger at an event, use about 20–30 seconds: name, what you do in plain language, why it matters, a light question. For a meeting or interview intro, use 60–90 seconds and a fuller model (problem you solve, how you work, or a short career arc). It must sound spoken — contractions, no tagline-speak. End with a question.
A hallway elevator pitch is 20–30 seconds for a stranger. “Tell me about yourself” in an interview is 90 seconds to 2 minutes, with present–past–future, and should end on this job. Do not use the lightning pitch as your full interview answer, and do not use a two-minute bio on someone you just met at a mixer.
Also asked
20–30 seconds for a stranger at an event; 60–90 seconds for a meeting or interview intro. If it sounds like a bio or an ad, rewrite it in spoken language. About 130 words per minute spoken.
Pick a model (lightning, problem-solution, how you work, or a short narrative). Draft out loud. End with a question. Cut jargon. Count words against the time cap. Do not invent accomplishments.
Send a short note within 24 hours to each person you met. Subject: thank you plus the role. Three sentences: thanks, one specific thing from the conversation, one sentence of fit. Do not attach a new resume unless they asked. Do not discuss salary in this note.
If they gave you a date, wait until after that date. If they gave none, a short note after about a week is reasonable. One reminder is enough unless they re-open the thread. Do not send a novel or a daily check-in.
Send something useful: a relevant article with two sentences of your take, a thank-you for a past introduction, an offer to connect two people, or a resource. Ask for a meeting only after you have given a reason they would want it. Do not ask for a job in that note.
Give a short context of who you are, why them specifically (a real detail), 15–20 minutes, and two topics you will not waste. You are asking for advice, not a job, in that email. Vague “pick your brain” notes get ignored.
Also asked
Within 24 hours, a short note to each person you met: thanks, one specific thing from the conversation, one sentence of fit. Do not attach a new resume unless they asked. Do not put salary in this note.
Related: How do you write a thank-you email after an interview?
Work backwards by role. For each, write: what you were asked to do, what you actually did, what changed, who benefited, how you did it. Then pull resume bullets only from that. A chatbot can interview you with those questions; it cannot remember your job for you. Do not let it fill gaps with plausible fiction.
Look at unsolicited feedback, what people ask you to do, and what you still get right under pressure. Strengths are repeating qualities, not tools. Skills are teachable capabilities. Confirm each item with one story. A long list of adjectives with no evidence is not a strength inventory.
Also asked
A skill is a teachable capability (facilitation, Python). A strength is why you are effective across contexts (stamina with incomplete data). Resume lists should be skills; interviews can use both if evidenced.
Related: Skills vs strengths on a resume?
For each duty, ask what changed because you did it, who benefited, and how. The accomplishment is the consequence, not the task list. If nothing changed, the duty may not belong on the resume.
Related: How do you write resume bullets?
Definitions of terms used in these answers: Glossary