The message from HR arrives on a Friday evening: "Your project is ending. From Monday you will be on the bench."
For many IT employees, especially in service companies, this is a stressful moment. Am I going to lose my job? Will this look bad on my resume? Should I start applying elsewhere right now?
Being on the bench is common and is not, by itself, a sign that you are in trouble. But how you use those weeks makes a big difference to what happens next. This guide explains what the bench is, how bench policies usually work, and a practical plan to get back onto a project quickly.
What does "bench" mean in IT?
In a service company, most employees are billable: a client pays for their time on a project. When you are not on any billable project, you are "on the bench" (sometimes called "unbilled" or "in the pool"). You are still an employee, you still get your salary, and you are expected to be available for new projects.
Why do people go on the bench?
- Project ended or the client reduced the team size.
- Freshers after training waiting for their first allocation.
- Returning from long leave, or completing an onsite assignment.
- Skill mismatch: new projects need skills different from yours.
- Slow business periods when fewer new projects start.
Most of these reasons have nothing to do with your performance.
How bench policies usually work
Every company is different, and policies change with business conditions, so always read your own company’s policy. Common features include:
| Practice | What it usually means |
|---|---|
| Resource management team (RMG) | A team that matches bench employees to open project requirements |
| Internal interviews | You interview with project managers for internal openings, much like an external interview |
| Bench time limit | Some companies set a period after which extended bench time is reviewed; the length varies widely |
| Training and certification | You may be asked to complete courses or certifications to improve your chances of allocation |
| Internal or non-billable work | Proof-of-concept projects, internal tools or support for pre-sales |
| Location flexibility | Openings may be in a different city; flexibility helps allocation |
A practical plan for your bench period
Week 1: Get organised
- Meet your RMG or resource manager. Ask what requirements are open and which skills are in demand.
- Update your internal profile and resume with your latest project, skills and achievements. Many allocations happen through internal profile search.
- Ask your last project manager for a short note of feedback or a referral to other managers.
Weeks 2 to 4: Upskill with a target
- Pick one skill that open requirements actually ask for, not a random trending topic. If most requests need Spring Boot microservices or a specific cloud platform, learn that.
- Finish one certification relevant to those requirements, if your company values it.
- Build a small hands-on project with the new skill so you can talk about it in internal interviews.
Throughout: Stay visible and say yes
- Attend every internal interview you are offered and prepare as seriously as for an external one.
- Volunteer for internal tools, proof-of-concept work or helping pre-sales teams. These count as experience.
- Be flexible where you reasonably can: shift timings, technology, domain or location. Refusing several projects is the fastest way to lengthen the bench.
- Log your learning in a simple tracker. If your manager asks what you did on the bench, you have a clear answer.
Should you look for a job outside while on the bench?
It is sensible to keep your resume updated and stay aware of the market, especially if your bench period is getting long or if your company’s communication suggests difficulty. Be practical:
- Keep giving your best to internal opportunities. Leaving on good terms matters for references and background checks.
- Check your notice period terms in advance. Read our guide on notice periods in IT jobs.
- Prepare your project story properly. See how to explain your project in an IT interview.
How to talk about the bench in interviews
If an interviewer asks about a recent gap in project work, be honest and positive: "My last project ended in July when the client reduced the team. While waiting for allocation, I completed a cloud certification and built a small microservices project to strengthen my skills, which is part of why I am applying for this role." Recruiters understand the bench. What they look for is whether you used the time well.
For freshers waiting for the first project
If you finished training and are waiting for allocation, this is a great time to get ahead of your batch. Strengthen the skills from your training, practise coding daily, and keep in touch with your trainer and RMG. Freshers who show initiative are often picked first. If you are still choosing your first company, our comparison of service and product companies explains where the bench fits in.
Frequently Asked Questions
What does bench mean in IT companies?
Being on the bench means you are employed and paid but not currently assigned to a billable client project. It is common in IT services companies between projects.
Do employees get salary during the bench period?
Yes. You remain an employee and normally receive your regular salary while on the bench, subject to your company’s policies.
Can I be terminated for being on the bench too long?
Policies vary. Some companies review employees who stay on the bench beyond a certain period, especially if they decline projects or fail internal interviews. Ask HR about the policy that applies to you.
What should I do during the bench period?
Update your internal profile, meet your resource manager, learn a skill that open projects need, complete a relevant certification, build a small project and attend every internal interview.
Does bench time look bad on a resume?
Not if you explain it honestly and show how you used it, such as certifications, projects or internal work. Recruiters are familiar with the bench in service companies.