This handbook has covered a lot of ways to make your experience specific. That leaves one more question: you can adjust the wording, order, and emphasis of the same experience, but which version is one you can explain and stand behind?
When I edit resumes, I often ask students, “Can you defend this?” It’s not enough for a line to sound good. When the interviewer follows up, you need to be able to explain what it means, why you did it that way, and what role you yourself played.
“If you can defend it in an interview and it holds up under questioning” is an important test in how I coach students. But in practice, a percentage or “it should be fine” isn’t enough. You need to take the content apart and look at it.
First, Find Out What the Student Means by “Not True”
One student told me at first that only about 60% of her resume was true. When I asked more, she explained that she had done the projects and did know the tools she listed; it was just that some of those tools hadn’t been used in that particular project.
That’s a different problem from not knowing a tool at all, or putting in an entire project you never did. If you don’t ask, it’s easy to delete things she really does know along with everything else, or, the other way around, to write off every doubt as “lack of confidence.”
In that conversation, I wanted her to see how much she actually knew, instead of discounting all her abilities up front. But when you write your materials, you still need to keep things separate: knowing a tool, having done a project, and having used that tool in that project are three different pieces of information.
Skills can go in your skills section, while each project should describe what you actually used and how. An analysis you later redid with a different tool can be described as a later replication or extension. That way you show your ability without blending two situations together.
Match the Difficulty and Wording to What You Actually Know
Some students’ resumes have been edited, by AI or by other people, into something so complex that they read like the work of a seasoned expert, while the student can only recite the surface-level steps.
When that happens, bring the difficulty down. Cut advanced terms you can’t explain yet and that don’t matter for the target role, and make the analysis you really understand specific. For things you still need to learn, plan time to learn and test them, but don’t let an inflated resume dictate all your preparation from here on.
I’ve also had a student list quantitative analysis on her resume, and it came out in conversation that the internship didn’t involve any quantitative project at all. I set that part aside first and had her talk about the non-quantitative work she had done. Sometimes the real experience already contains good industry judgment that just was never properly organized.
Another student wanted to prove her ability to learn by saying she’d “learn everything within six months of starting.” I told her directly that a promise like that isn’t credible in itself. Telling a story about how you learned something unfamiliar and solved a real problem is more convincing than overpromising what you’ll do in the future.
Emphasize Your Contribution, but Keep the Real Division of Work
Students tend to describe teamwork as “It was all my boss’s idea; I just helped.” The research, analysis, communication, and execution you did can all be stated clearly.
Say the boss proposed evaluating a plan to rent apartments furnished, and the student was responsible for researching the market, comparing competing listings and what tenants needed, and then taking the analysis to the landlord. In her materials, she can absolutely focus on her own research and the way she moved things forward, without repeatedly explaining who assigned the task.
But “I evaluated and drove the plan” is still different from “this direction was my idea in the first place.” Use active verbs for the work you really did, but also know which decisions, results, and responsibilities belong to the team or to other people.
Similarly, if you watched a conflict from the sidelines, you can talk about what you observed and what you did afterward. To answer how you handled a conflict, though, you need to have actually been involved in handling it. Swap your role in the story, and the responsibility, judgment, and process that follow all change too.
Numbers, Titles, and Project Status Have to Line Up
I pay special attention to official titles, dates of employment, the nature of each project, and key numbers, because these can easily end up contradicting each other across different materials.
For work beyond your title, describe the scope of your responsibilities; there’s no need to add “senior” or “manager” yourself to look more experienced. Terms like pre-seed and Series A also mean different things, and you can’t relabel one funding round as another just because the amounts look similar.
How far a background check goes depends on the specific process. “Nobody’s going to check” is no substitute for confirming the facts. An interviewer may also start probing from a tiny detail, so at the very least you need to know what you wrote.
The same goes for numbers. The amount of money covered by an analysis is different from how much the company actually saved. A model’s evaluation results are different from its business results after launch. Making a recommendation is different from having it adopted.
Results that haven’t been verified yet can be written as estimates or potential impact, with your assumptions and calculations ready. When you have verified results, state their scope and your contribution. When information is incomplete, go back to the reports, the records, or people who can confirm it. Don’t use polished wording to fill in what you don’t know.
Your Resume, Your Interviews, and Your Other Materials Should Tell the Same Story
When you prepare for interviews, you can change how much detail you give and highlight what’s relevant to the question, but the basic facts have to match. Say your resume has you handling the analysis, but in the interview you’ve suddenly become the project lead, or dates and team size change between versions. Go back and sort that out first.
Real experiences can be told clearly in the past tense. A hypothetical analysis should be labeled as hypothetical. The past tense can make your wording sound more certain, but it can’t turn something that didn’t happen into past experience.
If you discover something inaccurate after you’ve already submitted your materials, start by listing the errors. Separate unclear wording, things you misremembered, and substantive factual problems, then think about how to correct them within the current application process. Don’t keep adding more inaccurate details just to make several documents look consistent.
Start by checking a single experience:
- What did I actually do? Which parts were my own judgment, and which were the team’s or someone else’s work?
- For every method, number, and result I included, can I explain where it came from?
- Have I written an idea up as a result, a skill as a tool I actually used in the project, or participation as leadership?
- If someone keeps asking follow-up questions, is what’s missing practice in explaining it, understanding of the subject, or does the line itself need to change?
Once you’ve sorted through these questions, you’ll know better where to write with confidence, where you need more material, and where to adjust your wording. Your resume doesn’t need to be a blow-by-blow account, and it doesn’t need to be much more complicated than the real you. What keeps the conversation going is a resume that shows people what you can do and holds up when you explain it.