What each document is for: the arc of your career, evidence of the work, and answers to the questions
Even when you describe the same experience, the reader of each document is looking for something different. Use the résumé for the arc of your relevant history, the career history for what you were responsible for and how you did it, and the cover letter for your answers to the questions and the judgment behind them.
Document names and formats vary by company. Some ask you to put project details into a free-form résumé, and some don’t ask for a separate career history at all, so check the actual job posting for which documents and sections to submit.
Comparing the résumé, career history, and cover letter
| Document | Main question | Core content | Common problem |
|---|---|---|---|
| Résumé | What relevant experience and skills do you have? | Dates, positions and projects, role, key results | Listing low-relevance experience at the same length |
| Career history | How, and in what scope, did you do that work? | Problem, scope of responsibility, actions, tools and methods, verified results | Writing only task names, or presenting team results as your own |
| Cover letter | How do you answer this question, and how do you decide? | The answer, context of the experience, reasons for your choices, connection to the role | Repeating the career list without answering the question |
This split is a guide to help you write. No particular length or page count applies to every employer.
One project written for each document
Below is a hypothetical project that organized recurring inquiries in an operations role. Replace it with work you actually did and results you confirmed.
Résumé: a summary of your role and key actions
Categorized customer inquiry types and organized shared reference documents to standardize the team’s response process.
Add the actual dates, organization, and role to this sentence, and the reader can see where it fits in your overall history. For the structure of the whole document, see the résumé writing guide.
Career history: scope of responsibility and how you did the work
Different team members described and handled recurring inquiries differently, so customers sometimes missed information. I categorized the inquiry types, compared existing answers, and drafted a shared checklist and response guide. After review by the team, I revised the documents and applied them to new inquiries. I was not in charge of the whole team’s operations; I was responsible for the categorization, the documents, and checking how they were applied.
If you measured whether omissions decreased after the change, add the baseline and the result. If you never measured it, don’t add an improvement rate. Dates, collaborators, tools, and deliverables only need to be included as far as they help the reader understand the experience.
Cover letter: your judgment and actions for each question
For a question about solving a problem, you can explain why you decided to standardize the guidance before trying to speed up responses. Support it with what you did: comparing past inquiries and answers to build a shared checklist, and revising the guide based on your teammates’ input.
If the question is about your motivation, explain how this experience connects to the target role instead of retelling the process at length. For structures that fit each question, see the cover letter writing guide.
Splitting summary and detail across documents
It’s fine to describe the same project in two documents. Summarize it in the résumé just enough to show the overall arc, and show more detailed evidence in the career history. When you do, check that the dates, role, and results don’t differ between them.
- Write down the dates, role, actions, and results in a master table.
- In the résumé, keep the core sentence closest to the role.
- In the career history, write the problem, method, scope, and how you verified it in more detail.
- In the cover letter, connect your answer to the question with why you chose what you did.
- Compare the documents to confirm that no facts or numbers differ.
For the detailed structure of a career history and examples by role, continue with the career history guide.
What entry-level applicants should submit in detail
Entry-level applicants don’t always have to submit a separate career history. Check which documents and experience sections the posting asks for. If it asks you to describe projects, research, or internships in detail, write your actual role and process in that format.
Don’t present a class project as employment or describe participation periods as if they were time on the job. Make the type and duration of each experience clear, and show what you yourself did.
Frequently asked questions
Do entry-level projects go in the résumé or the career history?
Check the documents and experience sections the posting asks for first. In the résumé you can briefly list relevant projects and your role; in a document that asks for detailed experience, you can write the problem, process, and results. Don’t turn coursework or personal projects into employment; use how to organize entry-level experience to show the real scope.
Is it repetitive to include the same project in my cover letter too?
What matters is whether you’re copying the same paragraph into each document, not whether you mention the same facts. In the cover letter, choose the judgment and actions the question asks about instead of introducing the whole project. Pick content that fits the structure for motivation, skills, and collaboration questions, and keep the dates, role, and results consistent with your other documents.
A checklist for comparing all three documents
- Do the dates, organization, role, and results of the same experience match?
- Can the reader quickly find the experience closest to the target role in your résumé?
- Does your career history separate your contribution from the team’s overall result?
- Does your cover letter answer each question directly?
- Did you follow the documents, file formats, and lengths the employer asked for?
Keeping one master record of your experience makes it easy to confirm the facts stay the same even when you change the explanation for each employer. Organize the evidence for your experience first, then adjust the length and order to the question each document needs to answer.