SS
Key Takeaways
- Your first weeks establish a reputation that is disproportionately hard to change later, so the early impression matters more than the early output.
- Spend the first month understanding before improving - new starters who arrive with immediate criticism damage themselves badly.
- Deliver one visible, useful thing within the first month, however small, to establish that you execute.
- Ask your manager explicitly what success looks like at 30, 60, and 90 days rather than guessing.
- Relationships built early are the infrastructure everything later depends on, and they are hardest to build once you are busy.
The first ninety days in a job are strange. You are being paid to do work you do not yet know how to do, in a system you do not understand, among people who are quietly forming a lasting impression of you.
Most new starters focus on the wrong thing. They try to prove competence immediately - suggesting changes, pointing out problems, moving fast - when the actual task is to understand the context well enough that their eventual contributions land.
This guide covers a structure for the three months, the mistakes that create lasting damage, and how the calculus changes when you are onboarding remotely.
If you are still preparing for the move, start with the free ATS score checker.
Before Day One
Rest if you can. A week between roles is worth taking - starting depleted affects your first months more than people expect. If your notice period ended early, use the gap.
Do light preparation. Read the company's public materials, recent announcements, and product documentation. Understand what the business actually does and how it makes money.
Confirm the logistics. Start time, location, dress code, what to bring, who to ask for. Small things, and getting them wrong on day one is an unnecessary distraction.
Set up your admin. Bank details, tax forms, and identification documents ready.
Days 1-30: Understand
The first month is for absorbing, not for fixing.
Learn how things actually work
Every organisation has a formal structure and a real one. The formal structure is on the org chart. The real one is who actually makes decisions, who has informal influence, whose approval unblocks things, and which processes are followed versus which are officially documented but ignored.
You learn this by paying attention and asking, not by assuming your last company's model applies.
Meet people deliberately
Aim for a short conversation with everyone you will work with regularly, plus people in adjacent teams.
Useful questions:
- What does your team do, and how does it connect to mine?
- What is working well right now?
- What is frustrating?
- What should I know that nobody will think to tell me?
- Who else should I talk to?
That last question builds the map faster than anything else.
These conversations are the single highest-return activity of your first month. They are also nearly impossible to schedule once you are busy, which is why the first month is when they happen.
Ask your manager what success looks like
Explicitly, in your first week:
What would a successful first 30, 60, and 90 days look like from your side?
Surprisingly few people ask, and the answer is the actual assessment criteria. Ask again at 30 days to check you are calibrated.
Ask questions freely
There is a window in which asking anything is expected and costs you nothing. It closes around the end of the first month. Use it - the questions you avoid asking in week two become embarrassing to ask in month four.
Write things down so you do not ask the same thing twice.
Do not criticise yet
The most damaging thing a new starter does is arrive and immediately explain how their previous employer did it better. Even when you are right, you have no credibility yet and no understanding of why things are as they are.
Note what seems wrong. Wait until you understand the history before raising it.
Days 31-60: Contribute
Deliver something visible
One useful, completed thing in the first month or so. It does not need to be large - a documented process, a fixed recurring annoyance, a report someone needed. What matters is establishing that you execute.
Small and finished beats ambitious and ongoing at this stage.
Start forming opinions
Now you have context, the things you noticed in month one can be raised. Frame them as questions rather than verdicts:
I noticed we run the reconciliation manually each week. Is there a reason it has not been automated, or is it just that nobody has had time?
That version invites the history. "We should automate this" invites defensiveness, and frequently there is a reason you have not heard yet.
Establish your working rhythm
How you communicate progress, when you are available, how you handle competing requests. Setting this deliberately in month two is much easier than correcting it in month six.
Get feedback early
Ask your manager directly at the 30-day mark:
Is there anything I should be doing differently?
Most managers will answer honestly if asked directly, and early correction is far cheaper than discovering a problem at your first formal review - see performance review preparation.
Days 61-90: Establish
Own something
By month three you should have clear ownership of an area - a process, a project, a client relationship, a system. Being the person people come to about something is what turns you from a new starter into a colleague.
Make a substantive contribution
Something that would not have happened without you. This is what your manager will point at when asked how the hire is going.
Build the wider network
Beyond your immediate team - adjacent departments, people whose work intersects with yours occasionally. These relationships are what make later work easier and they take time to form.
Review honestly
At 90 days, assess: are you doing what you were hired to do, is the role what was described, and is it working? If there is a gap between the job as advertised and the job as it exists, month three is when to raise it - not month nine.
Remote and Hybrid Onboarding
Starting remotely is genuinely harder, and it requires deliberate compensation.
Nothing happens by accident. In an office you absorb context from overheard conversations and hallway encounters. Remotely, every piece of context must be actively sought.
Over-schedule the introductions. Book fifteen-minute calls with everyone you will work with. It feels excessive and it substitutes for the informal contact you are missing.
Ask more questions, more explicitly. Nobody can see you looking confused.
Over-communicate progress. A short weekly update to your manager means they never have to wonder what you are doing. This matters more remotely than in person.
Turn your camera on early. People building a mental picture of a new colleague need a face.
Go in if there is an office option. Even occasionally in the first months. The relationship-building return is disproportionate.
Common Mistakes
Criticising before understanding. Arriving and explaining how your last employer did it better is the fastest way to damage credibility you have not yet built, even when your observation is correct.
Trying to prove yourself immediately. The first month is for absorbing context, and rushing to demonstrate competence usually produces work that misses what actually matters here.
Not asking what success looks like. The answer is your actual assessment criteria, and remarkably few new starters ask their manager directly.
Not asking questions while you can. There is a window where asking anything costs nothing, and it closes around the first month - questions avoided in week two become awkward in month four.
Skipping the introductory conversations. They are the highest-return activity of your first month and become nearly impossible to schedule once you are busy.
Delivering nothing visible for three months. Understanding is the priority, but one small completed thing establishes that you execute.
Assuming your old company's way applies. Processes usually exist for reasons you have not heard yet, and discovering the history before proposing changes is what makes the proposal land.
Not seeking feedback until the formal review. Early correction is cheap and a surprise at your first review is not.
Onboarding remotely without compensating. Context that arrives passively in an office must be actively pursued from home, and new starters who do not adjust for this fall behind quietly.
Frequently Asked Questions
How long does it take to feel competent in a new job?
Commonly three to six months, longer for complex or senior roles. Feeling behind in the first weeks is normal rather than a sign of poor fit.
Should I suggest improvements early?
Note them but wait. Raise them from around month two, framed as questions about history rather than verdicts - there is usually a reason you have not heard yet.
What if the job is not what was described?
Raise it at around the 90-day mark, factually and with specifics. Month three is early enough to be constructive and late enough that you understand the situation properly.
How do I build relationships when starting remotely?
Deliberately and in excess of what feels natural - short scheduled calls with everyone you will work with, camera on, and a weekly written update. The informal contact you would get in an office has to be manufactured.
Should I ask for feedback before my first review?
Yes, at around 30 days. Ask your manager directly whether there is anything you should be doing differently. Early correction is far cheaper than a surprise at a formal review.
What if I made a mistake in the first weeks?
Own it immediately, fix it, and do not repeat it. Everyone expects new starters to make mistakes, and how you handle one is more informative than whether it happened.
Is it normal to feel out of place?
Yes, and it usually passes by month three. If it has not by then, that is worth examining - though give it the full ninety days before drawing conclusions.
Starting somewhere new soon? Make sure the application lands first. Check your ATS score free.
Make This Practical
Ask your manager in week one what a successful 30, 60, and 90 days looks like from their side. Very few people ask, the answer is your actual assessment criteria, and it converts three months of guessing into a checklist.
Then spend the first month understanding rather than improving. Book short conversations with everyone you will work with, ending each by asking who else you should talk to, and resist the urge to explain how your previous employer did things - note what seems wrong and wait until you know the history.
Finally, deliver one small visible thing by the end of month one, ask for feedback at 30 days, and take clear ownership of something by month three. If you are onboarding remotely, over-schedule the introductions and send a short weekly update, because the context that arrives passively in an office has to be actively pursued from home. When your first formal review comes, prepare for it with performance review preparation.
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.
