TD
Key Takeaways
- Managers form a working impression within a few weeks, and it is hard to move afterwards.
- Asking questions early reads as diligence; asking the same question in month three reads as inattention.
- Write things down. Being told twice is normal, being told four times is a pattern people notice.
- Delivering something small and complete in the first month beats being nearly finished with something large.
- Your first review is largely about reliability and communication, not technical brilliance.
What is actually being assessed
Graduates arrive expecting to be judged on technical ability. That is a small part of it, and knowing the real weighting changes what you spend effort on.
Reliability. Do you do what you said, by when you said. This is the single largest factor in how a new graduate is described after three months, and it is entirely within your control from day one.
Communication. Do you say when you are stuck. Do you give status without being chased. Can you explain what you did to someone who was not there. Managers value this disproportionately because it determines how much supervision you require.
Trajectory. Not where you are, but the rate of change. A graduate who was slow in week two and independent by week ten is read very differently from one who is at the same level in both. This is why the second month matters more than the first.
Coachability. How you receive correction. The first piece of critical feedback is a test of this, and the answer is "thank you, let me think about that", followed by a visible change.
Judgement about when to escalate. Knowing what to handle and what to raise. New graduates err in both directions — escalating trivia, and sitting on genuine problems — and calibrating this is one of the real skills of the first year.
Technical ability matters, and it is assumed. You were hired; they believe you can do the work. What they do not yet know is any of the five things above, which is why those are what the first quarter is actually establishing.
The practical consequence: a graduate who ships modest work reliably, communicates clearly and improves visibly will be rated above one who is technically stronger but has to be chased. This is not unfair — it is a description of what makes someone useful on a team.
Weeks one to two: absorb and record
Write everything down. Names, systems, acronyms, how to request access, who owns what. You will be told a great deal in the first fortnight and you will not remember it.
This single habit has an outsized effect on how you are perceived. Being told something twice is normal. Being told it a fourth time is a pattern, and people quietly adjust their opinion.
Ask questions freely now. There is a window where every question is expected. Use it. The same question in month three costs you something.
Learn who does what. Not just names and titles — who to ask about which system, who is the actual decision-maker on your team, who has been there longest.
Set up your environment properly. Access, tooling, permissions, the local build. Spending two days on this is normal; discovering in week five that you never had the right access is not.
Weeks three to six: deliver something small
The goal of the first month is not a large contribution. It is one complete, visible thing.
A small bug fixed and shipped. A document that did not exist and now does. A manual process automated. Something with a beginning and an end that someone else noticed.
Small and finished beats large and pending, for two reasons. It proves you can navigate the whole path — code, review, testing, deployment, or the equivalent in your function. And it gives your manager something concrete when someone asks how the new hire is doing.
Ask for feedback deliberately. "Is this the level of detail you wanted?" after your first piece of work is a cheap, high-value question. It also signals that you want to be corrected, which changes how people treat you.
Weeks seven to twelve: reduce supervision
By this point the expectation shifts from "is learning" to "is contributing with less oversight."
Stop asking questions you can answer yourself. The pattern that works: try to find it, then ask with what you have tried. "I looked at the config docs and the older ticket, and I still can't see where the timeout is set — do you know?" That takes thirty seconds of your colleague's time instead of ten minutes.
Communicate status without being asked. A short update at the end of a working session — what you did, what is blocked, what is next — puts you in the small group of people nobody has to chase.
Own something end to end. Take a task from definition to delivery without being managed through it. This is the transition from "new hire" to "team member" and it is noticed.
Say when you are stuck, early. The failure mode that damages reputations is silence — going quiet for four days and then revealing you were blocked on day one. Being stuck is expected; hiding it is not.
Asking for help without looking lost
The tension every new graduate feels: ask too much and look incapable, ask too little and waste days. There is a workable rule.
Most teams have an informal time limit — commonly thirty to sixty minutes of being genuinely stuck before you ask. Find out what yours is by asking your manager directly in week one: "What's the norm here for how long to try something before asking?" Managers appreciate the question and almost nobody asks it.
Ask well. Not "this doesn't work", but: what you are trying to do, what you tried, what happened, and what you think might be going on. That version takes the helper thirty seconds instead of ten minutes, and it demonstrates that you did the work first.
Say when you are stuck, early. The genuinely damaging failure is silent struggling — three days on something a colleague would have unblocked in ten minutes, discovered at a status meeting. Managers are far more troubled by being surprised than by being asked.
Batch the small questions. Keep a running list of minor things and ask them together rather than interrupting six times a day.
Write down the answers. Asking the same person the same question twice is the specific thing that creates an impression of inattention.
Things that quietly cost you
None of these are dramatic and all of them shape how you are described when your manager is asked.
Missing small commitments. Saying you will send something by Thursday and sending it Monday. The task rarely matters; the pattern is read as a proxy for whether you can be relied on with something larger.
Being invisible in meetings. Attending for three months without speaking. You do not need to contribute constantly — one question or observation per meeting is enough to be a participant rather than an attendee.
Not reading the room on hours and communication. Teams have norms — when people are online, how quickly messages get answered, whether cameras are on. Watch for two weeks and match, rather than assuming your preferences are neutral.
Treating feedback defensively. The first piece of critical feedback is a test of coachability more than of the thing itself. "Thank you, let me think about that" and then a visible change is what is being looked for.
Overpromising in your first month. Enthusiastic commitments made before you understand the systems produce missed deadlines in month two.
Disappearing when something goes wrong. Owning a mistake immediately, with what you are doing about it, is nearly always recoverable. Concealing one is not.
For international graduates
Two extra things worth tracking from day one.
Keep your own paperwork. Employment start date, job title, salary, and copies of everything. These matter later for status applications, and reconstructing them years afterwards is unpleasant.
Understand the timeline you are on. If your work authorisation has an expiry and the next step is employer-sponsored, the conversation about sponsorship has to happen well before it becomes urgent. Raising it around your first review, calmly, is far better than raising it in a panic — and by then you have performance to point to.
The first review
Most graduate programmes review at three or six months. It is rarely a surprise if you have been asking for feedback.
Prepare for it: a short list of what you delivered, what you learned, and where you want to grow next. Managers appreciate not having to reconstruct your quarter from memory, and it puts your framing in the room first.
If something has gone badly, raise it yourself before they do. Self-awareness at a review is scored well; defensiveness is not.
The three phases, in practice
The first quarter has a predictable shape, and knowing which phase you are in tells you what behaviour is appropriate — the same action that reads as diligent in week two reads as inattentive in week ten.
Weeks one to two: absorb and record.
Nobody expects output. What they are watching is whether you are organised and whether you engage.
Write everything down. Not selectively — everything. Names, systems, acronyms, how the deploy works, who owns what, where the runbook lives. Being told something twice is normal; being told it four times is a pattern people notice and mention.
Ask questions freely now. This is the window where curiosity is free. A question in week two costs nothing and a question in month three about something you were told in week two costs something real.
Learn who does what. Book fifteen minutes with everyone on the team and with two or three people adjacent to it. Ask what they do, what is annoying about it, and what they wish someone had time for. That last question frequently hands you your first useful task.
Set up your environment properly. Do not limp along with a half-working setup for a month because fixing it feels like a distraction. It is not; it is the foundation of everything after.
Weeks three to six: deliver something small and complete.
The single most valuable thing in the first quarter is one finished thing. A bug fixed, a report automated, documentation corrected, a small feature shipped.
Complete beats large. Being nearly done with something substantial at week six is worth much less than having finished something modest at week four. Finishing teaches you the whole path — review, testing, approval, deployment — which is where most of the real complexity of a new job lives.
Communicate status without being asked. A two-line update to your manager at the end of the week. What you did, what is next, what is blocking you. Almost no graduate does this and every manager values it.
Weeks seven to twelve: reduce supervision.
The transition that decides your first review.
Stop asking questions you can answer yourself. By now you know where the documentation is and how to read the code. The shift is from "how do I do this?" to "here is what I think, does that sound right?"
Own something end to end. Take a piece of work and carry it through without being chased. This is what "reliable" means concretely, and it is what your manager is trying to establish about you.
Ask for feedback deliberately. "Is my pace where you'd expect at this point?" Ask at around week six and again at week ten. It converts vague anxiety into something actionable and signals that you want to improve.
Working out how your team actually operates
Every team has rules nobody writes down, and learning them fast is most of what "fitting in quickly" means.
How decisions get made. In the meeting, before the meeting, or by one person afterwards. Watch for two weeks before assuming the visible process is the real one.
What "urgent" means here. Some teams mean today and some mean this fortnight. Getting this wrong in either direction — panicking over routine work, or being relaxed about something genuinely time-critical — is a common early misread.
Communication norms. Whether questions go in a channel or a direct message, whether people expect replies out of hours, whether cameras are on. Match what you observe rather than importing your own preferences.
Who reviews what. The named owner in the documentation and the person people actually ask are frequently different. Find out which is which.
How disagreement is handled. Directly, in writing, in private, or not at all. This one varies enormously and misjudging it is the fastest way to create a problem.
What gets celebrated. Shipping, thoroughness, firefighting, documentation. Whatever the team praises tells you what it values, and that is more reliable than anything in your onboarding pack.
The way to learn all six is the same: ask the person who has been there longest and is not your manager, and then watch. Both parts matter — people describe the official version accurately and the real version only partially, so the observation is what completes the picture.
Common Mistakes
- Not writing things down. The cheapest habit with the largest reputational effect.
- Going silent when stuck. Being blocked is fine; hiding it is what damages trust.
- Chasing a large first project. Small and complete beats large and unfinished.
- Asking without trying first. After the first few weeks this pattern becomes visible.
- Missing small commitments. More corrosive than a single big error.
- Waiting for the review to ask how you are doing. By then the impression is set.
For international graduates, and your first review
Keep your own paperwork. Every authorisation document, every signed form, your supervisor's details including a personal contact, exact start dates and job title as written. HR systems are replaced and people leave; the folder is yours and takes ten minutes a quarter. This is the same discipline the employer requirements guide sets out, and it prevents an entire category of later problem.
Understand the timeline you are on. Know your dates, know when reporting obligations fall, and put them in a calendar with reminders well ahead.
Raise the next step at the right moment. Not in week one. Once you are established — three to six months in — asking your manager or HR about the employer's approach to longer-term sponsorship is a normal planning conversation.
Your first review is not about technical brilliance. At almost every employer it is about reliability, communication and trajectory: does this person do what they said, do they tell us when they are stuck, and are they getting faster.
Which is worth knowing, because graduates prepare for a review by listing accomplishments when the useful preparation is different: keep a running note from day one of what you shipped, what you learned, and what feedback you received and acted on. Three lines a week, and at review time you have specifics while everyone else has impressions.
Building relationships without networking at people
The social half of the first quarter, which technically-minded graduates frequently neglect and then find has cost them.
Book fifteen minutes with everyone on your team in the first month.
Not a networking pitch — ask what they work on, what is annoying about it, and how they got here. People enjoy the question and it is how you find out how the team actually works.
Find the person who has been there longest and is not your manager.
They know why things are the way they are, they are usually pleased to be asked, and that context is unavailable in any documentation.
Say yes to the social things early. Lunches, team coffees, the Friday thing. You can decline later once relationships exist; declining before they exist is how people end up isolated for a year.
Meet two or three people outside your team. Someone in the function your work depends on. It makes cross-team requests dramatically easier later and it takes two coffees.
Be useful to your peers. The other graduates who started with you are the people you will still know in ten years. Help them, ask them things, compare notes.
Thank people specifically. "Thanks for explaining the deploy process, it saved me a day" is remembered; a generic thanks is not.
Do not confuse visibility with self-promotion. Being known for doing a specific thing well is different from talking about yourself, and the first is achieved by finishing things and telling people the outcome.
The one thing to get right
If the whole quarter reduces to one instruction: finish something small, early, and tell someone it is done.
It sounds trivially modest and it does more than anything else available to you. It proves you can navigate the whole system rather than just write the interesting part. It gives your manager something concrete to say about you. It converts you from a person being onboarded into a person contributing, which is the transition the entire first quarter exists to make.
Graduates instinctively want their first contribution to be impressive. Impressive is a year-two problem. Finished is a month-one problem, and the people who understand that ordering are the ones whose first review goes well.
Setting up your own record
A small habit from week one that pays at your first review and for years after.
Three lines a week, in one file. What you shipped, what you learned, and any feedback you received. Thirty seconds on a Friday.
Why it matters at review time. Managers write reviews from memory and recency, and a graduate who can supply specifics from month two is supplying material the manager did not have. Everyone else arrives with impressions.
Why it matters later. These lines become your resume bullets, your interview stories, and the evidence for a promotion case. Reconstructing what you did eighteen months ago is genuinely difficult, and most people simply lose it.
Record the feedback especially. Both what was said and what you changed. "I was told my updates were too infrequent, so I started sending a Friday summary" is a complete growth story, and it is invisible unless you wrote it down when it happened.
Keep it somewhere you will still have access to if you leave the company.
Frequently Asked Questions
How long should I take to ramp up?
Most employers expect meaningful contribution by around three months and full productivity considerably later. Ramp-up is budgeted for; what is watched is the trajectory.
Is it bad to ask a lot of questions?
Early, no — it is expected and it is the fastest way to learn. What matters is whether the questions change over time and whether you show what you tried.
What if I make a serious mistake?
Say so immediately, explain what happened, and propose a fix. Nearly every mistake a new graduate can make is recoverable; concealing it is what is not.
Should I socialise with the team?
Where it is natural, yes. Being known makes collaboration easier. It is not an assessment, and forcing it is worse than declining occasionally.
When can I ask about promotion?
Not in the first 90 days. Focus on the first review, then ask what the path to the next level looks like — the answer tells you what to prioritise.
What if I do not like the job?
Give it a genuine six months before deciding. Early discomfort is often unfamiliarity rather than mismatch. If it persists, that is information — but leaving a first job very quickly needs explaining later.
What is your resume scoring right now?
Scan it against a job description and get your ATS match score in about a minute.
Drop your resume here or choose a file
PDF only. Max 2 MB.
We never share your data or use it to train AI models.
Was this guide useful?
Be the first to rate it.
