TCS Ninja Interview Experience

Anonymous2 months ago

I appeared for the TCS NQT on-campus recruitment process for the Ninja role. The selection process included an online assessment followed by a technical interview.

Status: Selected – TCS Ninja

Location: Kolkata, West Bengal

Applied Through: On-Campus Recruitment


TCS NQT – Online Assessment

Duration: 3 hours | Method: TCS NQT

The TCS NQT assessment included different sections:

  • Quantitative Aptitude

  • Logical Reasoning

  • Verbal Ability

  • Coding

The aptitude sections tested basic to moderate quantitative, logical, and verbal ability. There was also a coding section.

After clearing the assessment, I was called for the interview round.


Technical Interview

Duration: Around 15-20 minutes | Method: On-site

The interview was mainly based on my resume, projects, and full-stack development skills.

The interview started with "Tell me about yourself" and then quickly moved into technical questions. Since I had mentioned full-stack development and MERN-based projects on my resume, most of the questions were related to frontend, backend, database, Git, deployment, and some core CS concepts.

Frontend & JavaScript

The interviewer asked:

  • What technologies did you use for the frontend?

  • What is JavaScript?

  • What is a JavaScript function?

  • What is IIFE?

  • What is React.js?

For IIFE, the interviewer actually showed me the syntax and asked me what it was. I was able to identify it as a function, but I could not explain IIFE as clearly as I wanted to.

Backend

Questions related to backend included:

  • What did you use for the backend?

  • Why did you use Express.js?

  • What is the difference between Node.js and Express.js?

Database

The interviewer also asked:

  • Which database did you use?

  • What is the difference between SQL and MongoDB?

  • What is a collection in MongoDB?

  • What is cascading delete in DBMS?

Git, Deployment & CI/CD

I was also asked about my projects and deployment:

  • Did you deploy any of your projects?

  • Explain the steps of deployment.

  • What is Git?

  • What is a Git branch?

  • What is Git commit?

  • What is Git push?

  • Do you know about CI/CD?

  • What is CI/CD?

Docker and CI/CD were not mentioned in my resume, and I did not have hands-on experience with them. I could answer the basic questions, but I could not explain them in depth.


160-Day Coding Challenge

I had mentioned my 160-day GFG coding challenge achievement on my resume, and the interviewer noticed it.

They asked me:

  • What was the easiest problem you solved?

  • What was the hardest problem you solved?

I was happy that the interviewer asked about this because it was an achievement I had genuinely worked for.

There was no coding question where I had to write a complete program during the interview.


My Interview Experience

The interview was only around 15-20 minutes, but it felt like a rapid-fire round because the interviewer moved quickly from one topic to another.

Since my project was based on full-stack development, I was asked questions from almost every part of the stack. I was able to answer most of the questions, although I could not explain every topic clearly or in depth.

One thing I learned from this interview is that if you mention something on your resume, you should be prepared for questions about it. Even technologies that I had not used practically, such as CI/CD and Docker, were discussed.

Overall, I felt the interview went well.

After the technical interview, I also received a call from TCS regarding my location preferences. It felt more like an HR-related discussion because I was not asked any HR questions during the interview itself.

Result: Selected for TCS Ninja. šŸŽ‰


Preparation

For preparation, I mainly focused on:

  • Interview questions based on my resume

  • My projects and their implementation

  • Full-stack development concepts

  • JavaScript and React.js

  • Node.js, Express.js and MongoDB

  • Git and deployment

  • DBMS and other core CS subjects

  • Aptitude

  • DSA

I would especially recommend preparing your resume very well. Anything you mention in your resume can become a question in the interview.


Tips & Takeaways

  • Don't stay completely silent if you don't know an answer. Try to explain whatever you know in your own words.

  • Prepare every technology and project mentioned on your resume.

  • Be ready to explain your project and the reason behind your technology choices.

  • Practice aptitude regularly for the TCS NQT.

  • Practice DSA and coding if you want to target higher roles.

  • Don't mention technologies only because they look good on a resume. Make sure you at least understand the basics.

Overall, it was a short but fast-paced interview, and it gave me a good idea of how important resume-based preparation is.

Final Result: Selected for TCS Ninja. šŸŽ‰

Recommended Reads

Interview Experience

How my Java Backend Interview Went

Two technical rounds, a mix of DSA and backend concepts, and an on-site interview process. Company: TripJack Role: SDE-1 Java Backend Experience: 2 Years Educat

Interview Experience

Microsoft Interview Experience (3+ YOE)

I recently appeared for the Microsoft interview process for a position requiring 3+ years of experience. Sharing the questions and my experience from each round

Post

Salesforce SMTS Offer

Received an offer from Salesforce for the SMTS (Senior Member of Technical Staff) role with an overall CTC of approximately ₹75 LPA . My Profile Experience: 5 y

Post

Many artciles are missing fromA2Zsheet

many of the articles are missing from the a2z shet which is making it difficult for me to revise the uqedtions i marked for teh revision adn the website form is

Post

Help me I am struggling to convert logic into code in DSA

Can anyone please help me? I am a beginner in DSA, nd I currently learning recursion I can understand the concepts and but I unable to write the code on my own

Comments0