Every year when I review new grad resumes, one question comes up over and over:
"The biggest problem with my resume is—I don't have any work experience. Why would anyone believe in me?"
I get the logic behind the question. But the premise is wrong.
Hiring managers are never looking for work experience in a new grad. Work experience is flat as a dimension before you've had your first job. What they're actually looking for is: How well does this person learn? When they hit a problem, do they figure it out themselves or wait for someone to tell them? Can they work with other people on a team?
These are called soft skills. And the good news is, they can be proven on a resume—not just stated.
Let's break down the three most important ones—learning ability, critical thinking, and teamwork. I'll tell you what hiring managers are looking for and how to write about each one.
1. Learning Ability: Don't Say "I Learn Fast"—Show the Receipts
Let's start with the biggest mistake new grads make.
Go read ten new grad resumes and at least six of them will have "Strong learning ability, able to quickly adapt to new environments" in the self-evaluation section. Then the hiring manager scrolls down three pages and finds zero evidence related to learning.
This is the classic "stated soft skill"—you claim to have it, but your resume doesn't back it up. It's a sentence anyone can write.
What kind of evidence do hiring managers actually want to see?
Three types work best:
1. You learned something from scratch and produced a real result
Don't write "self-taught Python." Write:
Learned Python from zero in the first semester of junior year. Three months later, completed a COVID-19 data visualization project (crawler + Flask + ECharts) with automated data fetching, storage, and display. Deployed on Alibaba Cloud and ran continuously for six months.
The key signals here aren't "Python"—they're "zero → three months → shipped → running." The hiring manager doesn't need you to say "I learn fast." They've already figured it out.
2. You went from outsider to competent in a new field quickly
This one matters especially if the role you're applying for isn't a perfect match with your major.
Non-finance major. Took an interest after an elective course on quantitative investing. Spent two months self-studying Pandas and financial time series analysis. Completed a paper on "CSI 300 Index Volatility Forecasting Based on ARIMA-GARCH" that was recommended by the professor for a department paper competition.
What does this paragraph say? It says: this person can pivot into a new field and produce publishable-quality work within two months. For someone without a finance background, that's the best proof of learning ability you could ask for.
3. A tangible "learn → apply" loop
For most new grads, learning and doing happen in separate buckets—classes over here, projects over there. If you can write about a time when you learned something and immediately used it, that loop itself is persuasive.
After learning Linux process management concepts in my Operating Systems course, I independently built a simplified shell interpreter in C that supports pipes, redirection, and background execution. ~1500 lines of code.
See it? "Learned something → built something right away." That action is the most direct proof of learning ability there is—stronger than any grade or rating.
The formula for writing about learning ability: Where you started + how long it took + what you made + what level that output reached (shipped? selected? adopted?).
2. Critical Thinking: Hiring Managers Look at How You Work
More than "what you did," experienced hiring managers care about how you went about doing it.
Critical thinking sounds abstract. But on a resume, it comes down to three things: What problem did you find? How did you analyze it? What decision did you make?
A lot of new grads write project experience as just "what I built" without saying "why I built it that way." That's a wasted opportunity to show how you think.
How to turn "what I did" into "how I think"
Compare these two versions.
Basic version:
Developed a campus secondhand trading platform using Java Spring Boot + MySQL for product listing and search functionality.
This is a standard "translated requirements into a tech solution" description. It tells the hiring manager you did work, but not how you approached it.
Improved version:
Built the backend service for a campus secondhand trading platform (~300 daily active users). When designing the product search feature, compared MySQL LIKE queries against Elasticsearch. Given the early-stage data volume (<5000 records) and operational overhead, chose MySQL's full-text index, keeping query latency under 200ms. Designed the architecture with an abstraction layer to allow future migration to ES if needed.
This paragraph shows three levels of critical thinking:
- You made a technical decision based on trade-offs, rather than using whatever someone told you to use
- You considered multiple dimensions: data volume, cost, scalability
- You made a deliberate "start lightweight, leave room to upgrade" decision—exactly the kind of thinking used in real work
If a new grad can show this level of reasoning on their resume, the hiring manager will spend an extra two minutes reading it.
Same principle applies outside of engineering:
While running the college department's WeChat official account, I noticed open rates were steadily declining (from 15% to 6%). I analyzed data from 12 articles over the previous two months and found that the cover image style and headline length were the main drivers. After switching to infographic-style covers and keeping headlines under 18 characters, the average open rate recovered to 11% over a 4-article test run.
Let's map it: identify problem → analyze data → find root cause → take action → verify results. That's a complete critical thinking loop. Whether you're in marketing, operations, or product, this structure works.
A quick self-check: For every entry on your resume, ask: Would the hiring manager's impression of my problem-solving ability change if I deleted this line? If the answer is no, the entry is too shallow.
3. Teamwork: Don't Say "Good Communicator"—Show What You Contributed
Teamwork is the fluffiest section on any new grad resume, bar none.
Nine out of ten new grads write "Strong communication skills, team player." But same as before—the hiring manager reads that and thinks, "Okay, prove it."
The most effective way: write about your role and contribution within a team.
Teamwork isn't "everyone got along and finished the work." It's "there was disagreement, pressure, or friction, and here's what you did in the middle of it."
A few angles to write about:
1. You took on an extra role beyond your job description
Beyond handling the technical development on the startup competition team, I proactively took on project management: set up a Notion task board, ran weekly sync meetings, and maintained meeting notes to keep three workstreams aligned. The team completed the prototype on schedule and passed the mid-term review.
This isn't saying "I code well." It's saying "I made the team function better." Any hiring manager reading this would think, "This person would be easy to have on a team."
2. You helped other people on the team
In a course design group, I voluntarily taught two teammates Git branching and collaborative workflows, reducing code merge conflicts by 90%. The team adopted the unified workflow going forward and delivered the project two days early.
The elegant thing about this example: it shows both technical skill (knows Git) and collaborative willingness (taught others). And it has a result—people were actually helped.
3. You drove a decision when the team was stuck
During a university debate competition, our team hit a disagreement on argument direction. I proposed we each spend 30 minutes listing supporting evidence for our positions, then vote on the option with the strongest case. We won the match, and the team captain called it a turning point.
Conflict and disagreement happen in every team. If you can show you pushed things forward through the disagreement, that's worth more than "actively cooperated."
One core principle for writing about teamwork: Don't write about relationships—write about roles. What was your relationship to the team? What function did you serve? What would the team have been missing without you?
4. One More Thing: Initiative—A High-Signal Quality That's Easy to Miss
Beyond the three competencies above, there's something hiring managers really pay attention to, but that's hard to showcase through any single experience—initiative.
Put plainly: when nobody told you to do something, did you find something to do anyway?
This isn't a separate section you need to add. It's something you can weave into any of the experiences above.
For anything on your resume that was a "task assigned by the teacher" or "course required project," try adding one of these:
- After finishing the required part, what extra did you do? (Optimized it? Iterated? Extended it?)
- While working on it, you found a problem that wasn't in the plan—did you fix it while you were at it?
The course project required building a basic library management system. After finishing the core features, I added an "auto-overdue-notification" feature that scans the borrowing table every night, finds overdue records, and sends email reminders. A professor from another department saw it and asked if we could deploy it for their class too.
The last line is the killer detail: "A professor from another department saw it and asked for a copy." It casually proves two things: first, you did more than what was asked; second, someone else recognized the value of your work.
Before vs. After: See the Difference
Here's a side-by-side comparison to show how much information density changes when you apply all the principles above.
Before:
Participated in the National College Student Innovation & Entrepreneurship Training Program. Served as a team member responsible for market research and data analysis. Project received national-level funding.
After:
National College Student Innovation & Entrepreneurship Training Program (National-level funding — only top 15% of projects selected university-wide)
Project context: 4-person team building a campus ridesharing mini-program. During the proposal phase, I noticed competitors were focused on long-distance rides while campus short-distance rides were an untapped market. I proposed narrowing the project scope from "campus mobility platform" to "campus short-distance ridesharing." The advisor approved this direction, and it became the final project focus.
My role: Market research & data analysis | Proactive project management
- Designed and collected 320 valid survey responses; performed cross-analysis using Excel + SPSS, producing a 12-page research report (including user personas and feature priority ranking)
- Used survey data to recommend a "Minimum Viable Feature Set" for the product roadmap — adopted by the team
- Set up shared documentation and a team schedule, coordinating progress across three workstreams
Results: National-level funding (top 15% approval rate), completed prototype with 50-person beta test, user satisfaction score of 4.3/5
The "before" version makes the hiring manager think: "Okay, they were on a school project."
The "after" version makes them think: "This person spotted a market gap, pushed the team toward a clear direction, validated their judgment with quantitative analysis, and coordinated the team—and they're only a junior? I want to talk to them."
Same project. Nothing fabricated. Just written in a way that surfaces the actual capabilities you demonstrated.
Post-Writing Checklist
- Every entry: remove "was responsible for" and "participated in"—replace with specific actions (proposed, built, designed, drove, optimized)
- At least one entry shows "how you went from not knowing to knowing something" (learning ability)
- At least one entry explains "why you did it that way" rather than just "what you did" (critical thinking)
- When mentioning a team, you wrote "what role you played" not just "what the team did" (teamwork)
- At least one entry goes beyond the original requirements (initiative)
- Every entry has a concrete number attached (how many surveys, how much improvement, how many people)
Run your resume through this checklist, and it goes up at least one level.
If you finish editing and still aren't sure how your resume reads—honestly, it's hard to judge your own writing. You know every word, but you lose the ability to see if the whole thing works. DeepResume's free resume diagnosis can run a full scan, scoring your resume on results quantification, role-fit, and clarity, with specific improvement suggestions for every section.