What to track in your first 90 days at a new job
The first 90 days are the highest-density period of your career for provable, interview-ready material. Most people forget almost all of it within 6 months. Here's what to capture each week so that doesn't happen.
You just started a new job. Everything is new: the people, the systems, the unwritten rules, the problems nobody told you about in the interviews. In three months, you'll be settled in. In six months, you won't remember most of what the first weeks felt like.
That's a waste. The first 90 days are the highest-density period of your career for learnable, trackable, provable things. You're absorbing more, making more observations, and demonstrating more adaptability than at any other point. And almost nobody writes any of it down.
Why the first 90 days matter for your career record
Two years from now, someone will ask you: "Tell me about a time you onboarded into a complex environment." If you tracked your first 90 days, you have months of specific material. The stakeholder mapping you did in week two. The process gap you spotted in week four. The first project you delivered in week eight. If you didn't track, you have a vague sense that "it was a lot."
Week 3 at the new job
“Realized the three regional teams were duplicating effort on customer reports. Proposed a shared template in the Friday sync. Manager asked me to lead the consolidation.”
18 months later, in an interview
“I think I did something with reports early on? There was some kind of overlap issue.”
The first 90 days also produce a natural career narrative: you arrived, you learned, you contributed. That arc maps directly onto the kind of stories interviewers ask for. But only if you capture the specifics while they're fresh.
What to track each week
Not everything. You're already overwhelmed with onboarding. The goal is selective capture: a few minutes per week, focused on the moments that will matter later.
Weeks 1-2: Orientation
Who are the key people and what do they care about? What's the actual state of the team or project compared to what you were told in interviews? What surprised you? What questions do you have that nobody has answered?
This is pure observation. You're mapping the terrain. Write down the gap between expectations and reality -- that gap often becomes your first contribution.
Weeks 3-6: Learning
What processes did you learn? What tools? Where did you spot inefficiencies or gaps that nobody else seems to notice? What did you deliver or contribute for the first time?
You're transitioning from observer to participant. The deliverables start small (a document, a fix, a suggestion in a meeting) but they're your first evidence of impact.
Weeks 7-12: Contributing
What did you own? What decisions did you make? What impact did those decisions have? What feedback are you getting? How has your understanding of the role changed from the job description?
By this phase, you're producing real work with measurable outcomes. These are the entries that become interview stories and review evidence.
The fresh-eyes advantage
The single most valuable thing about being new: you see things that everyone else has normalized. Broken processes, missing documentation, communication gaps, customer pain points that the team stopped noticing three years ago.
This advantage has a shelf life. By day 90, you'll have normalized most of it too. The workaround that seemed absurd in week one will just be "how things work" by week ten.
What new hires notice (week 2)
- The deploy process requires 4 manual steps that could be automated
- Two teams are building similar features without knowing about each other
- Customer complaints about the onboarding flow are filed but never triaged
- The wiki has three contradictory guides for the same setup process
What the same person thinks (month 6)
- "That's just how deploys work here"
- "Yeah, there's some overlap but it's fine"
- "Onboarding complaints are a known issue"
- "Just ask Sarah, she knows the right setup"
Capture those fresh observations in your first 30 days. They become powerful career stories later: "In my first month, I noticed the deploy process had 4 manual steps. I automated 3 of them, cutting deploy time from 45 minutes to 12." That kind of specific, early-impact story is interview gold -- and you can't reconstruct it if you didn't write it down when you noticed it.
What 90 days of tracking produces
After 12 weekly entries, you have more career material than most people accumulate in a year of not-tracking.
~12 weekly entries
Each one a snapshot of what you learned, contributed, or observed. Raw material for future interview prep, performance reviews, and promotion cases.
8-10 usable stories
Not every entry becomes a full story, but most weeks produce at least one moment worth citing. After 12 weeks, you have coverage across multiple themes: learning, initiative, collaboration, problem-solving.
A baseline for growth
In 12 months, you can compare week-1 you to month-12 you. The scope expansion, the skills developed, the relationships built. That comparison is concrete evidence for your first review at this company.
A simple 90-day template
Three questions, every Friday, five minutes. Adapted for new starters, where the learning curve is the story.
What did I learn this week that I didn't know before?
Could be a technical skill, a team dynamic, a business context, or how a decision gets made. In the first weeks, this will be long. By week 10, the entries get shorter. That shrinkage is itself a signal of how far you've come.
What did I contribute or deliver?
Even "reviewed the onboarding docs and flagged 3 inaccuracies" counts. Small contributions compound. In the first two weeks this might be empty, and that's fine.
What do I want to remember about this week in a year?
The thing that surprised you, the person who helped you, the decision that didn't make sense yet, the small win that felt good. This is the texture that makes future stories specific instead of generic.
If three questions feel like too much in the middle of onboarding chaos, do one. "What do I want to remember about this week?" alone captures 80% of the value.
For a deeper look at the weekly journaling format, the career journal template post walks through variations for different roles and seniority levels.
The habit on-ramp
A job transition is the easiest time to start a new habit. Everything is already disrupted. You're already in "figure things out" mode. Adding a 5-minute Friday entry barely registers against the cognitive load of learning a new codebase, remembering 30 new names, and figuring out where the good coffee is.
If you've been meaning to start a career journal, this is the moment. Not because the tool matters, but because the window for starting a tracking habit is open right now and it closes faster than you think. By month four, you're settled and the activation energy goes back up.
Your first 90 days will be the most useful raw material of your next 2 years. The only question is whether you capture it or let it fade.