Jump to section ▾
Key takeaways
The seven things that matter most, if you read nothing else.
- Pick a target role and a list of 30–40 companies before you send a single application.
- Format your resume plainly so screening software can parse it, and write it specifically enough that a recruiter keeps reading past the first few seconds.
- Build your network months before you need it — referrals decide a large share of roles before they're ever posted.
- Eight to twelve tailored applications a week beats forty copy-pasted ones, and takes less total time.
- Prepare six to eight real stories from your own experience instead of rehearsing answers to specific questions.
- Expect rejection and silence as the norm; track weekly activity you control, not outcomes you don't.
- Your first role sets the trajectory for the next several — graduates who start underemployed often stay that way.
Where should I start my job search after college?
Start by defining a target, not by applying. Before a single application goes out you need three things: a specific role type, a specific tier of company, and a specific reason you're a credible candidate for both. A search without a target produces a hundred generic applications and no callbacks.
The reason this matters isn't motivational. Every downstream decision — what goes on your resume, who you reach out to, what you prepare for — depends on knowing what you're aiming at. Graduates who skip this step end up rewriting their resume for every application because they never decided what it was supposed to say in the first place.
It also changes how the search feels. An untargeted search has no finish line and no way to tell a good week from a bad one, which is exactly the condition under which people quit. A targeted search gives you a fixed universe of companies, a known set of requirements, and a way to measure progress that isn't "did anyone email me back."
Define the role, not the industry
"Marketing" is not a target. "Marketing coordinator at a mid-size B2B software company" is. Job titles are how postings get written and how recruiters search their databases, so your target has to be specific enough to match one.
Build a target list of 30–40 companies
Write them down somewhere you'll actually look. This list becomes the backbone of everything else — it tells you whose postings to watch, whose alumni to find, and where a referral is worth chasing. Without it you're reacting to whatever a job board decides to show you.
Audit the gap between you and the role
Pull five real postings for your target and list every requirement that appears in at least three of them. What you already have goes on the resume in the posting's own words. What you don't becomes a short list of things worth building over the next few months.
Expect the target to shift. Most graduates revise it once or twice in the first month as they read more postings and learn what the role actually involves. That's the process working — the goal is a target specific enough to act on, not one you commit to permanently.
Go deeperHow do you choose a career path when you have no idea what you want? →How do I write a resume that actually gets read?
Write for two audiences at once. The first is software that scans for keyword matches against the job description. The second is a recruiter who spends only seconds deciding whether to keep reading — an average of 7.4 seconds on the initial screen in an eye-tracking study by Ladders (2018). A resume that only satisfies one of them fails.
This is where most graduate resumes break down. They're formatted to look impressive — columns, graphics, skill rating bars, a photo — and that formatting is exactly what applicant tracking systems mishandle. Or they're plain enough to parse cleanly but say nothing specific enough to hold a person's attention past the first line.
What the software looks for
- Exact keyword matches to the posting's language
- Standard section headings it can parse
- A single-column layout with no text boxes
- Clean date formatting with no gaps it can't read
What the recruiter looks for
- Scope and result, not a list of responsibilities
- Numbers wherever a number is honestly available
- Evidence you've done something close to this job
- A top third that answers "why this person, for this role"
The fix is not choosing between them. It's a plain, parseable structure carrying specific, quantified content — which happens to be what both audiences reward. One column, standard headings, no graphics, and every bullet written as an action and a result rather than a duty.
On numbers: use them wherever they're honest and available, and don't invent them. "Managed social media for a student organization" becomes "Grew a student organization's Instagram from 400 to 1,100 followers over two semesters." Class projects, part-time jobs, and campus roles all produce real numbers if you look for them.
Go deeperHow do you write a resume with no work experience? →How do I network if I don't know anyone?
Start with people who already have a reason to reply. A large share of professional roles are filled through referrals and internal networks before they're ever posted publicly. That isn't a reason to stop applying — it's a reason to build relationships in parallel, months before you need one.
Networking has a reputation problem among students because it's usually described as something transactional and vaguely embarrassing. In practice the version that works is unglamorous: a short, specific message to someone whose actual job you're curious about, sent consistently, most of which go unanswered. Five a week for three months is around sixty conversations attempted, which is more than enough to change a search.
The warm path
Alumni from your school at companies on your target list. The shared institution is a real reason to reply, and response rates run meaningfully higher than cold outreach.
The cold path
Direct outreach to people doing the job you want. Keep it under 100 words, ask one specific question, and never attach a resume to a first message.
The maintenance path
Staying visible to people who already know you. One useful update every few months beats going silent and reappearing only when you need something.
What to actually say: name the specific thing that made you reach out, ask one question you couldn't answer from their company's website, and make it easy to reply in two sentences. What not to do: ask for a referral in a first message, send a paragraph about yourself, or ask someone to "pick their brain" without saying about what.
Most of these conversations won't produce a job, and that's the correct expectation. What they produce is information — what the role actually involves, what the team is hiring for, which of your assumptions about the industry are wrong. That information is what makes the next twenty applications better than the last twenty.
If you don't know anyone yet
Almost nobody starts with a network. You probably share something with people at your target companies already — the same school, major, hometown or club — and that shared connection is what makes a first message reasonable to send and reasonable to answer. Most messages will go unanswered, and that is the normal shape of this, not a sign it isn't working: the sixtieth message has the same chance as the first.
How many jobs should I apply to, and how do I apply?
Eight to twelve tailored applications a week, to roles you're genuinely qualified for. Volume is not strategy — twenty tailored applications will outperform two hundred copy-pasted ones, and they'll take less total time.
Tailoring gets described vaguely, so here's what it actually means: read the posting, identify the three requirements it repeats or leads with, and make sure those three appear in the top third of your resume in the posting's own language. That's the whole exercise. It doesn't require rewriting the document — it requires reordering and rewording a handful of lines.
It also helps to see where applications sit in the whole search. The five parts from the short answer at the top of this page depend on each other: the target decides what the resume says and who you reach out to, the resume and your network are what get you interviews, and the weekly system is what keeps all four running after the first round of rejections.
The second half is knowing when not to apply. If you meet roughly half the listed requirements, apply — postings describe an ideal candidate who usually doesn't exist. If you meet almost none of them, that time converts better on the target list, where the gap is smaller and the odds are real.
Cover letters are worth writing when the posting asks for one or when you have a specific connection to the company, and not otherwise. A generic cover letter costs you twenty minutes and changes nothing. A specific one — naming the team, the product, or the person you spoke to — is one of the few things that still gets read.
The 20-minute rule
If tailoring an application takes more than 20 minutes, the role is probably too far from your background to be worth it. That's not a reason to lower your standards — it's a signal about where your time actually converts.
How do I prepare for an interview as a new graduate?
Build six to eight real stories from your own experience rather than rehearsing answers to specific questions. Preparation means having material you can adapt to whatever gets asked, and understanding what the interviewer is actually assessing behind each question.
Six to eight stories will cover the overwhelming majority of what you'll be asked: a time you led something, a time you failed, a time you disagreed with someone, a time you solved a problem under constraint. Write them once, know them well, and the interview becomes a matter of choosing the right one rather than inventing something under pressure.
Behavioral questions
"Tell me about a time when…" is not a memory test. The interviewer is checking whether you can describe a situation clearly, explain what you specifically did, and name the outcome. Structure matters more than the impressiveness of the story — a well-told class project beats a vague internship anecdote every time.
Technical and case questions
These assess how you think, not whether you land on the right number. Say your reasoning out loud, state your assumptions, and check them as you go. Silence while you work is the most common avoidable mistake — the interviewer can't evaluate reasoning they can't hear.
The questions you ask them
Have three prepared, specific to the role and the team rather than the company. Questions you could have answered from the careers page signal that you didn't prepare. Questions about how the team actually works — what the first ninety days look like, how success gets measured — signal that you're evaluating the job seriously.
The follow-up
Send a short note within 24 hours referencing something specific from the conversation. It rarely wins the job on its own, but it keeps you present during a decision that often takes longer than anyone tells you it will.
One thing worth knowing from the hiring side: interviewers are usually comparing you against other candidates for the same role, not against an absolute standard. Being clear, prepared, and easy to talk to moves you up that comparison more reliably than being impressive in any single answer.
Go deeperWhat 8 stories should every new graduate prepare before an interview? →What should I do when I keep getting rejected?
Keep the weekly cadence and stop reading meaning into silence. You will be rejected far more often than you are advanced, and most rejections come with no explanation. The graduates who succeed aren't the ones who avoid rejection — they're the ones who don't stop for three weeks after a hard one.
Silence is the norm, not a verdict. Companies close roles, freeze headcount, and promote internally without updating anyone who applied. Some never respond at all. Reading a personal judgment into a non-response costs you time and energy you could spend on the next application.
The counterweight is a cadence you can hold on a bad week. Track the activity, not the outcome — outcomes are outside your control and the numbers below are not. If you hit these consistently for a month and still see nothing, that's real signal, and it usually points at the resume or the targeting rather than at you.
| Weekly activity | Target |
|---|---|
| Tailored applications sent | 8–12 |
| New outreach messages | 5 |
| Follow-ups on open threads | 3 |
| Interview preparation | 2 hours |
When you do get feedback, take it literally rather than personally. "We went with someone with more direct experience" usually means exactly that, and it tells you something useful about the targeting. Vague feedback tells you nothing and shouldn't be over-interpreted.
Go deeperWhy am I not getting interviews? →What should I do if I graduated and still don't have a job?
Rebuild the structure you lost. If you graduated without an offer, the search changes shape — you have more hours and less structure, and the risk shifts from "not enough time" to "no accountability."
The practical fix is treating the search like a job with fixed hours rather than something that expands to fill the day. Three focused hours in the morning will out-produce eight unstructured ones, and it leaves the rest of the day for the part-time work, projects, or skill-building that keeps the resume moving.
The first job you take also matters more than most graduates realize. Graduates who start out underemployed are more likely to remain underemployed years later — 73% are still underemployed a decade on, according to Strada and the Burning Glass Institute — the first role tends to set the trajectory for the next several, which is why the decision deserves more thought than "it's something."
Underemployment itself is common, and it is not new. In the second quarter of 2026, 41.95% of recent college graduates were working in jobs that don't require a degree, according to the Federal Reserve Bank of New York. In the New York Fed’s quarterly data, which begins in 1990, the rate has never dropped below about 37% or risen above about 48%.
Two different measures circulate, and they are not interchangeable. The Federal Reserve Bank of New York puts underemployment at 41.95% for graduates aged 22 to 27 (Q2 2026). Strada puts it at 52% one year after graduation. Different populations, different methods, and averaging them would be meaningless. This page uses the NY Fed figure throughout.
That said, waiting indefinitely for the right role carries its own cost, and long gaps get harder to explain the longer they run. The question is rarely perfect versus nothing.
Should you take the job that isn't quite right?
- Does it build a skill that appears in postings for the role you actually want?
- Is there a realistic internal path, or is this a terminal role at this company?
- Will you have the time and energy to keep searching while working it?
Two yeses is usually enough. Zero is a signal to keep looking — and to get help restructuring the search rather than repeating the same approach with more hours behind it.
Go deeperWhat should you do if you graduated without a job offer? →