How many rounds is the Itc Infotech Full Stack Engineer interview process?

Candidates report 3 stages: Aptitude Assessment, Technical Rounds, and Managerial/HR Interview. The interview process section above breaks down what each stage covers.

What topics come up in the Itc Infotech Full Stack Engineer interview?

Itc Infotech Full Stack Engineer interviews most often cover Data Structures & Algorithms (DSA), SQL, Core Java, Collections Framework Internals (HashMap), and Database Fundamentals, based on topics extracted from real candidate reports.

What questions does Itc Infotech ask Full Stack Engineer candidates?

Recent candidates report questions like "Can a protected member be accessed outside the package?" and "Balance Debt and Feature Delivery". The question bank above tracks 20 questions for this role, ranked by how often they come up in Itc Infotech interviews.

Itc InfotechFull Stack Engineer

Updated May 11, 2025

Itc Infotech Full Stack Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Full Stack Engineer at Itc Infotech, newest first and distilled into what to expect across the loop.

Get your personalized Itc Infotech Full Stack Engineer prep plan

Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.

Build my free plan

Hot & recentNewest first

> 1 year

Easy Positive Usāwān

My interview experience at ITC Infotech felt easy and pretty fast. I was given full details about the job upfront, and that reduced a lot of uncertainty before I ever spoke with anyone.

I had three interviews in total. The overall process took a little longer than I expected, but the explanation I accepted was that managers and clients were busy, so scheduling took time. Still, communication felt supportive enough because they followed up afterward, so I wasn’t completely left in the dark.

> 1 year

Easy Positive Bhopal

My interview was just a single technical round. It started with me introducing myself, and then the interviewer used my resume as the anchor for the questions.

The difficulty was easy, and the interaction felt more like a conversational walkthrough than a long technical grilling. I was essentially evaluated by how well I could respond based on what was written on my resume.

Unlock every Full Stack Engineer interview experience

Real Full Stack Engineer interview experiences

Difficulty, sentiment and outcomes
New reports added every week

See all experiences

Share your interview experience

Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.