Do the Job You Were Hired For
Most professionals spend the first 90 days of a new job trying to impress everyone. That's not what they were hired for or what they'll be measured on. If you want to manage your career well, start somewhere a lot less exciting.
The interview process ended on your first day. But the two questions the company was asking about you didn't end with it.
Can you do the job? Can you do it well?
Your first months are where you answer them for real, with results instead of interview answers. Here's why…
You Were Hired to Fill a Gap
Companies don't open a position because they feel like it. Somebody resigned, or the workload grew faster than the team could handle.
Think about it from the hiring manager's perspective.
Jane, a finance manager, lost her accounts payable specialist in March. Since then, she's been paying invoices herself, closing the books at night and answering vendor emails on weekends, all while writing a job description, sitting through a dozen interviews and asking every candidate the same two questions.
Then she picked you.
She hired you to take that specific work off her plate and do it well, and that's the only thing she's really watching during your first few months.
So in your first 30 days, find out exactly what that work is and how your performance will be evaluated at the end of the year.
Don't assume you already know. According to Gallup's 2024 engagement survey, only 46% of U.S. employees clearly know what's expected of them at work.
Reread the job description and highlight every responsibility and requirement. Then ask your manager directly:
"What does doing this job well look like to you, in numbers? What will you look at when you do my performance review?"
Write the answer down, because those two or three numbers are what your manager expects from you.
Do That Job, and Do It Well
Every "first 90 days" post on LinkedIn will tell you to chase "quick wins", volunteer for everything and bring fresh eyes to the team.
Sam, Jane's new accounts payable specialist, follows that advice to the letter. In his first 60 days, he:
- reorganizes the team's shared drive
- joins the culture committee
- pitches a new expense tool at the Monday meeting
- stays late to help sales with a client event
Meanwhile, month-end close is supposed to be finished by day 5. It ran 3 days late. Twice.
What do you think Jane remembers?
Not the shared drive.
Those are all activities, not results. Anyone on the team could reorganize a folder or volunteer for a committee, including the person who eventually replaces you.
What Jane needs is the books closed on time, vendors paid within their terms and no more weekend emails, because that's the result she hired you for.
Yes, the extra stuff is nice, and some of it will matter later in your career. But it counts on top of the core job, never instead of it. Until the core job is handled, it's noise, and it tells your manager you don't understand what your job is.
Do the job you were hired for. Then do it well.
Jobs Change, So Write It Down
Here's the catch: the job you were hired for won't stay the same for long.
A teammate resigns and you pick up half of her responsibilities. The department gets reorganized under a different director. Or your boss stops by at 4:45 PM and asks, "Can you also handle the invoices for the Canada entity? Just for now."
That's normal, and most of the time you should say yes.
The problem is that the job description doesn't change along with it. Six months later, the work you're doing and the document you'll be reviewed against describe two different jobs. Your manager has probably forgotten half of what she asked you to take on, because she has her own priorities and deadlines.
So keep a running list. Every time the job changes, write down the date, what you took on, who asked and roughly how much of your week it takes:
- Oct 3: took over Canada entity invoices (Jane asked), about 6 hours a week
- Nov 14: covering payroll reconciliation while Bob is on leave, until January
- Feb 2: now the main contact for the two largest vendors
It takes two minutes each time, and it becomes the evidence you'll need at review time.
Keep the list next to your career management document and review both at least once a quarter. But a list only helps if your manager sees it…
Get Your Job Description Updated
Your performance review is written against your job description. That's what your manager pulls up in December, and it's usually what HR looks at when it's time to decide on raises.
Now say 40% of your week went to work that isn't anywhere in it.
That 40% doesn't show up in your review. The parts of your original job that slipped because of it do.
Not a good trade.
That's why you bring the list to your manager during a one-on-one, well before review season. Something like:
"Since I started, I've picked up three things that aren't in my job description. Here's the list and roughly how much of my week each one takes. Can we update my job description and my targets so my review covers the work I'm actually doing?"
Most managers will say yes, because an accurate job description makes your performance review easier for them to write.
If she says the new work is temporary, agree on when it ends and write that down too. If she says no, at least now you know exactly what you're measured on, and you can plan your time around it instead of finding out in December.
Notice what this isn't. It isn't "only do what's in your job description." Extra responsibilities are how you grow into the next role. Take them on, and make sure they're written down so they count.
No One Will Update It for You
Not HR, and not your manager.
No one is going to manage your career for you except you, and that includes keeping your job description current.
Learn what you're measured on in your first 30 days, then do that job well. When the job changes, write it down and take it to your manager.
At the end of the year, the job description is what you'll be measured against. Make sure it describes the job you're actually doing.