On the bench in an IT company: what to do and what to avoid
Being "on the bench" means you are employed and paid but not currently allocated to a client project, which is common in IT service companies, especially for freshers after training or between projects. Use the time to build skills that are in demand for upcoming projects, keep in regular touch with the people who allocate resources, and keep a written record of what you do. A short bench period is normal; a long one is a signal to push harder for allocation or to start preparing for other options.
Why people end up on the bench
Service companies keep some trained people available so they can staff new client projects quickly. You might be on the bench because:
- You've just finished training and are waiting for your first allocation
- Your previous project ended or was scaled down
- Upcoming projects need skills you don't have yet
- Your location or shift preferences limit which projects fit
It usually isn't personal, and it isn't a judgement of your ability. But how you spend bench time can affect how quickly you get a good project.
What to do on the bench
1. Find out which skills upcoming projects need. Ask your resource manager or the team that handles allocation which technologies are in demand right now. Learn those, not random topics.
2. Learn with proof. Finish internal trainings or certifications that the company recognises, and build small projects that show the skill. Allocation teams often search internal profiles by skill, so update yours as soon as you complete something.
3. Stay visible. Check in with your resource or allocation manager regularly and politely: "I've finished the cloud fundamentals course and a small deployment project. Are there any openings where I could use this?" Being proactive helps you get considered for openings.
4. Say yes to interviews and shadowing. Clients or project managers may interview you before allocation. Treat these like real interviews: prepare, research the project, and ask good questions. Offer to shadow a team or help with small tasks while you wait.
5. Help internally. Internal tools, documentation, proof-of-concept work, helping trainers or reviewing code all count as experience and give you something to talk about.
6. Keep a log. Each week, write down what you learned, completed and applied for. It protects you if your utilisation is questioned, and gives you material for appraisals and your resume.
What to avoid
- Disappearing. Not responding quickly to calls or emails from the allocation team is the fastest way to stay benched.
- Refusing every project. It's fair to state preferences, but turning down several suitable projects can count against you. If you have a genuine constraint (health, family), explain it clearly and early.
- Only watching videos. Courses without practice don't show up as skills. Build things.
- Ignoring company policies. Some companies have rules about how long someone can stay unallocated. Learn your company's policy from HR or your manager rather than from rumours.
How long is "too long"?
There's no single answer; it depends on the company, the market and your skills. As a rough guide:
| Situation | What to do |
|---|---|
| A few weeks after training or between projects | Normal. Upskill, stay in touch with allocation |
| A couple of months with interviews but no allocation | Ask for feedback from those interviews and fix the gaps |
| Several months with few or no opportunities | Escalate politely to your manager or HR, ask about other skills or locations, and quietly start preparing for external options |
If you start preparing to leave, prepare properly: update your resume with what you've actually done, practise interviews, and read how to answer "why are you leaving" so you can explain the bench honestly and positively.
How to talk about bench time in interviews
Interviewers at other companies understand benching. Be honest and focus on what you did:
"After my project ended in March, I was unallocated for about two months. I used that time to complete a cloud certification and build a small deployment pipeline for an internal tool, which I can walk you through."
That answer is honest, specific and shows initiative. Avoid blaming the company or pretending the gap didn't exist.
Turning bench time into an advantage
The bench is frustrating, but it's also rare paid time to learn without project pressure. People who use it well often get better projects than the one they left. Pick an in-demand skill from skills to learn in your first two years in IT, go deep, show proof, and keep talking to the people who allocate work.
Frequently asked questions
Will I be paid while on the bench?
In most companies you continue to receive your salary while unallocated, though variable pay or bonuses may depend on utilisation. Check your company's policy.
Can I be let go for being on the bench too long?
Some companies have policies about long periods without allocation, and in difficult market conditions benched employees can be more at risk. Stay active, keep records, and understand your company's actual policy.
Should I accept a project in a technology I don't like?
Often it's worth accepting a reasonable project and learning what you can, while working towards your preferred area. Long bench periods can be harder to explain than an imperfect project.
Is it okay to apply to other companies while on the bench?
Many people do. Keep doing your current responsibilities properly, follow your company's policies, and don't use company time or resources for interviews where that's against the rules.