Career9 minMay 18, 2026

How to Survive (and Thrive in) Your First Year of a PhD

The first year of a PhD is when most students quietly burn out. Here's what to prioritize, what to ignore, and what to actually do in months 1–12.

Jin Park
Founder & Editorial Lead

1. What Year One Is Actually For

Year one is not when you publish your breakthrough paper. It is when you build the

machinery that will let you publish for the next four years. That machinery has

four parts: a working relationship with your advisor, a literature base in your

subarea, a daily research routine, and a finished coursework load. If you treat

year one as a sprint toward publications, you will arrive in year two with no

foundation and have to rebuild it under deadline pressure.

The students who finish in five years almost always built this foundation early.

The students who quit after three years usually skipped it.

Year-One Foundation Checklist

  • Weekly meeting cadence with your advisor (set by month 2)
  • Read ~100 papers in your subarea (spread across the year)
  • One reproducible code repo or pipeline you fully understand
  • All required coursework planned across years 1–2
  • One small project shipped — workshop paper, replication study, or technical report

2. Set Up the Advisor Relationship Early

Your advisor relationship is the single largest predictor of how your PhD goes.

Do not leave it to drift. In your first month, ask three concrete questions: how

often do you want to meet, what does a good week of progress look like to you,

and what format do you want updates in (slides, written notes, code demos)?

Write down the answers and follow them.

Send a short agenda 24 hours before every meeting — three bullet points is enough.

After the meeting, send a one-paragraph recap with action items. This sounds

excessive in month one. By month six, both of you will rely on it.

3. Read Like a Researcher, Not a Student

You cannot read every paper. You should not try. In year one, aim for 100 papers

total — roughly two per week — across three tiers. The top tier (10 papers) you

read end-to-end and can reproduce or explain in detail. The middle tier (30 papers)

you read carefully but selectively: abstract, intro, method, results. The bottom

tier (60 papers) you skim for the contribution and stash for later.

Keep a single reading list in one place with status, one-line summary, and

relevance score. Without a system, you will read the same paper twice and forget

the one you needed.

Three-Tier Reading Rule

  • Tier 1 (10): Deep read. Could you give a 20-minute talk on it?
  • Tier 2 (30): Structured skim. Method and results understood.
  • Tier 3 (60): Abstract + figures. Stored with a one-line summary.

4. Build a Daily Research Routine

The biggest difference between productive and unproductive PhD students is not

hours worked — it is consistency. Pick a fixed two-to-three-hour block each

weekday for deep research work and protect it ruthlessly. No meetings, no

coursework, no email, no Slack. The block matters more than the length.

Treat coursework, TA duties, and reading as a separate budget. Do not let them

consume your research block. If you skip your research block for three days in a

row, that is a signal something is wrong with your week's structure — fix it

before it becomes a pattern.

5. Coursework: Get It Done, Don't Optimize It

Coursework grades matter very little for your career after the PhD. They matter

enough that you must pass and meet your program's requirements. The right strategy

is "competent, not excellent" — a solid B+ in a hard required course is fine if

it preserves your research block. Front-load required courses in years one and

two so year three onward is research-heavy.

One exception: a course in a technique you will use in your research is worth

treating as research time. Probability theory for a Bayesian modeler, optimization

for an ML student, ethnographic methods for an HCI student. Pick one or two

courses where excellence pays off and let the rest be merely passed.

6. Ship One Small Thing

By the end of year one, you want one small artifact you can point to. Not your

first paper — that is unrealistic and unhealthy as a goal. A workshop paper, a

replication study, a strong technical report, an open-source release, or a

well-documented benchmark all count. The artifact serves two purposes: it forces

you through the full research cycle once, and it gives you something concrete to

show in year-two evaluations or fellowship applications.

Pick the artifact in consultation with your advisor by month three. If you wait

until month nine to start, you will be writing it at midnight before the deadline.

7. Manage the Mental Side

Imposter syndrome peaks in year one. Everyone around you sounds smarter because

they have been in the field longer — that is a timing effect, not a talent gap.

Talk to senior PhD students, not just your advisor: they remember year one and

will tell you which struggles are universal.

Build at least one non-PhD anchor. Exercise, a hobby, a community outside academia.

The students who collapse in years three or four almost always lost their non-PhD

identity in year one. Protect it like you protect your research block.

Warning Signs to Address Early

  • Working 70+ hours per week and feeling behind
  • Avoiding your advisor because you have no progress to report
  • No friends outside your lab or program
  • Reading without taking any notes for weeks
  • Coursework consuming all of your research block
Jin Park
Sobre el autor
Jin Park
Founder & Editorial Lead

PhD graduate who spent years tracking conference deadlines across computer science and engineering. Built ScholarDue after missing a submission window in the final year of candidacy and realizing no single tool tracked CFPs, extensions, and notification dates in one place.

Más información