Tata Communications Interview Questions
& Process

I interviewed with Tata Communications Transformation Services (TCTS) for a Voice & Accent / Training-related role on Monday November 17. The interview was conducted by an Operations Manager and went well. I was told about the next steps — a further round with leadership followed by HR. The interviewer was polite and gave a positive indication about the process moving forward. However, post-interview, the candidate experience was poor. Despite multiple polite follow-ups over the next two weeks, there was no formal update, no closure, and no clear communication from the HR Corporate Recruiter coordinating the process. I was told my profile was “on hold” and that I would receive an update on a specific date, but no update was provided. Repeated emails and calls went unanswered, leaving the process in limbo. This lack of responsiveness is disappointing given the time and effort candidates invest in preparing for interviews. Delays happen — that is understandable. What is not acceptable is silence, especially after interviews are completed and expectations about next steps are clearly communicated. For a Tata-group organization, this level of candidate experience does not reflect well and can easily be improved with basic communication and closure. Advice to Management: Please ensure recruiters provide timely updates and clear closure to candidates after interviews. Even a brief status update or rejection email shows professionalism and respect for candidates’ time.

Typically, the process kicks off with a recruiter screening, either by phone or video, to see if you're a good fit. After that, you'll likely go through several technical or functional interviews with hiring managers and team folks to check out your experience, skills, and how you solve problems. Sometimes, they might give you a written test, a case study, or an assignment to see what you can do in practice. The last step often involves meeting with senior leaders or people from other teams to gauge if you'll fit in and align with the company's long-term goals. They'll keep you in the loop with updates all along. If you're selected, you'll get an offer, and others might get some feedback.

So I applied online, then had an initial chat with HR about my background and why I'm interested in this role. After that, I did a technical interview focusing on SQL, Java, and general problem-solving. The last part was a behavioral interview, where they wanted to see how I work with others and if I fit the company culture. The whole thing took about two weeks, and they kept me updated.

For a network engineer role, it usually kicks off with a quick phone chat to see if your tech background, certs, and experience with network gear and protocols line up. Then, you'll dive into a technical interview where you'll tackle some real network problems, maybe even getting hands-on with device configs or network troubleshooting. Expect questions about routing, switching, security, subnetting, and protocols like BGP or OSPF. Sometimes they throw in a lab test too. The last part is often a behavioral chat to check out how you handle working with others, communicating, and solving problems. It's all about seeing if you've got the tech chops and if you'll fit in.