First Months
When the work you are given is the wrong size for you
Being handed something far above your level and being handed something far below it are opposite problems, and both are usually about the team rather than about you.
By Yash Agarwal3 min read

Two failures that look nothing alike
New joiners tend to worry about being out of their depth, and rather fewer worry about the opposite, which is a mistake because the second is at least as common and considerably harder to escape. Work arrives at the wrong level in both directions, and in most cases the cause has nothing to do with an assessment of your ability.
Allocation is usually a scheduling exercise carried out under pressure. Somebody has a list of things that need doing and a list of people who might do them, and the match is made on availability far more often than on fit. Understanding that removes most of the sting from either version, and it points at what to do about them, which is not the same thing in each case.
Being handed something well above your level
This happens for three ordinary reasons. Nobody else was free. The person allocating does not know in detail what the task involves. Or somebody has decided to stretch you deliberately, which is usually a compliment and is almost never explained as one at the time.
The failure mode is not that you cannot do it. It is that you spend three weeks not doing it, quietly, while everyone assumes it is in hand. That is the outcome to design against, and it is entirely preventable by saying at the outset which parts you can see a route through and which parts you cannot. That sentence is not an admission of weakness; it is the only information the person allocating actually needs from you, and they will not get it from anyone else.
Ask what the work is for and what happens if it is late, because those two answers tell you whether you are on a genuine stretch assignment with room to learn or in the path of something time-critical that should never have been given to a new joiner. They are very different situations and they justify very different amounts of pushing back.
Being handed something well below it
The low-level version is more corrosive because it is comfortable and there is no obvious moment at which to complain. You finish everything easily, you are told you are doing well, and eighteen months later you have very little to show that anybody outside the team would recognise as progression.
Some of this is legitimate. New people are given contained work while the cost of a mistake is still being estimated, and that is a reasonable precaution rather than an insult. What matters is whether it changes. If the same category of task is still arriving after six months, and colleagues who joined around when you did are being given wider things, the situation has stopped being a precaution and become the shape of your job.
Say the size out loud, in the language of the work
In both directions the move is the same: describe the mismatch as a fact about the task rather than as a feeling about yourself. “This looks like about three weeks and I can see a route through the first two” is a useful sentence. So is “I finished this in a day, so I have capacity — is there something coming up I could take a piece of?”
Neither reads as complaint, because both are phrased as information a manager can act on. The version that lands badly is the one about you: saying that work is beneath you, or that you feel unsupported, invites a conversation about your attitude instead of a conversation about allocation, and that is a worse conversation to be having.
Where this is the organisation rather than the task
Some workplaces are chronically short-staffed and everything is above everybody’s level, permanently. Some have a layer of work that nobody wants and it lands on whoever is newest, indefinitely. Neither is fixable by a well-phrased request, and it is worth deciding fairly early which of these you are in, because the effort you spend adjusting your approach in a place like that is effort that produces nothing.
The reliable test is what happens after you raise it once, clearly and without heat. A functioning team adjusts something within a month or two, or explains why it cannot, and both of those are acceptable answers. Nothing at all, twice, is also an answer, and it is the one worth taking seriously.
Common questions
Should I admit I do not know how to do something I have been given?
Yes, and early, because the cost of that admission rises sharply with every week that passes. Framing it as a question about approach rather than about capability — where would you start with this — usually gets you both the help and a reputation for being straightforward.
How long should I accept work that is below my level?
Through the first few months without much concern, since containment while you are new is normal. Beyond that, the question to ask is not whether the work is beneath you but what would need to be true for you to be given something wider, which turns a grievance into a plan.
Is a stretch assignment worth taking if it might go badly?
Usually, provided the risk is shared rather than parked entirely on you. Ask who else is close enough to the work to catch a problem, and if the honest answer is nobody, that is worth naming before you start rather than after something has gone wrong.
Contributing editor, After the First Job
Yash writes the explanatory pieces on first months, managing up, money at work and would rather show the working than assert the conclusion.





