READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 133 of 153
Interview experiences · TCS
Tata Consultancy Services (North America) Business Analyst interview
I had a technical round, then a management round, followed by HR. The stages felt connected: if the technical and management conversations went well, HR would move things on. Afterward, I completed the iBegin portal and entered the compensation details I had already discussed. There were few surprises, and the process felt smooth from start to finish. The final step was mainly confirming the CTC…
Interview experiences · TCS
Tata Consultancy Services (North America) Business Analyst interview experience: aptitude before HR
I began with an aptitude test, which felt somewhat harder than I had expected. After I cleared it, I moved to an HR interview. That conversation was easier to get through. The sequence was simple: aptitude first and HR second. I attended at the Chennai Sholinganallur office. Leaving the HR stage, I felt relieved because its questions were less intense than the aptitude screen. The conversation ha…
Interview experiences · TCS
Tata Consultancy Services (North America) Business Analyst Interview Experience: architecture and Java depth
The interview began with a detailed walkthrough of my current project. I had to explain the full architecture: design, microservice communication, database interactions, authentication, deployment, technologies, and the reasoning behind decisions. They then covered Java collections, multithreading, exceptions, OOP, and Streams operations such as filtering, mapping, grouping, sorting, and reducing…
Interview experiences · TCS
Tata Consultancy Services (North America) Consultant interview experience: quick project start
The recruitment process felt smooth and transparent to me. I could follow each step in the TCS Ibegin portal, and HR and the team walked me through the background-verification work. What stood out was that I was never left on the bench for even a day. Everything seemed to keep moving. Project work and code generation started around the day after the project assignment. I found the overall process…
Interview experiences · TCS
Tata Consultancy Services (North America) Consultant interview: walk-in follow-up stalled
The process lasted much longer than I expected. It started with a walk-in interview. After some time, I got a call asking me to upload documents, and later I was asked to take a screenshot with a panel. That was where everything slowed down. I waited for the next message and checked again weeks later, but there was still no meaningful update. The questions themselves were not the main problem. Th…
Interview experiences · TCS
Tata Consultancy Services (North America) Software Engineer campus interview with Java and multithreading
This was a campus-placement setup where TR, MR, and HR seemed to run in parallel. I began with TR, and the questions started with DSA and AI basics. That put the focus on foundational concepts rather than anything especially specialized. Then the discussion moved into Java and operating systems, with extra attention to multithreading. It felt like they wanted to know whether I could handle core p…
Interview experiences · TCS
Tata Consultancy Services (North America) Software Engineer interview: basics to HR
The technical portion was manageable and covered string manipulation, arrays, and regex. It felt focused on practical fundamentals rather than obscure material. The second round was HR, including salary discussion. We reached agreement and I was selected. In another part of the process, I saw the same practical approach: OOP, DBMS, JavaScript, a couple of SQL queries, DSA exercises such as Fibona…
Interview experiences · TCS
Tata Consultancy Services (North America) Software Engineer interview experience: Priority Campus NQT
I went through the Priority Campus NQT process: an online assessment, a technical interview, and an HR interview. The assessment followed the usual aptitude-and-reasoning pattern and included two coding questions. Once I cleared it, I was shortlisted for the Digital track. The technical interview leaned heavily on my resume. I walked through my projects and core computer science basics, then answ…
Interview experiences · TCS
Tata Consultancy Services (North America) Software Engineer interview: frontend work and simple coding
The interview opened with my frontend and integration experience: React.js, JavaScript, TypeScript, HTML, CSS, and API integration. We then discussed projects and how I solved problems while building. Programming questions appeared in the conversation too. I walked through simple tasks such as reversing strings, followed by related prompts. The HR portion was more conversational, covering interes…
Interview experiences · TCS
Tata Consultancy Services (North America) Software Engineer interview: fundamentals and manager round
My process was straightforward. It began with a basic technical screen and moved into a managerial discussion. The technical questions stayed grounded in software-development concepts, database principles, and standard CS knowledge, and they connected those subjects to my earlier project experience. The managerial discussion lasted about 20 to 30 minutes. It mixed technical checks with questions…
Interview experiences · TCS
Tata Consultancy Services (North America) Software Engineer interview: HR and technical overlap
My screening-to-HR flow was unusual because the HR conversation did not feel purely HR related. I went through the usual MCQs and technical questions first, then an additional nontechnical HR round that still included technical questioning. The interviewer's style stood out too. When I answered, they seemed to have little patience. It felt more like a rapid test than a normal back-and-forth, and…
Interview experiences · TCS
Tata Consultancy Services (North America) Software Engineer interview: Java fundamentals
The process began with aptitude and reasoning, then coding. I received two coding questions: one easy-to-mid level and one mid-to-hard DSA problem. Each part seemed to require clearing before the next advanced. The technical discussion went deep into Java and CS fundamentals: String versus StringBuilder/StringBuffer, string immutability, equals and hashCode, ArrayList versus LinkedList, checked a…
Interview experiences · TCS
Tata Consultancy Services (North America) Software Engineer interview: long venue wait
My experience at the venue was disappointing because the day felt poorly managed. I arrived early but waited a long time before my name was called for the first round, late in the evening after most of the day had gone by. There were many other candidates, and I could not tell how the calling order was decided. The invitation gave a smaller time window, but the process ran until around the evenin…
Interview experiences · TCS
Tata Consultancy Services (North America) Software Engineer interview: NQT fundamentals
After clearing the online NQT, I was invited to a combined technical, managerial, and HR interview. The NQT included aptitude, logical reasoning, verbal ability, and coding. In the interview, the panel checked what I had put on my resume and connected it to core computer-science fundamentals. The technical discussion covered data structures and algorithms, DBMS, OOPs, and operating systems. I als…
Interview experiences · TCS
Tata Consultancy Services (North America) Software Engineer interview: repeated logic questions
The interview felt tough almost immediately. I was given a steady stream of logic problems, with little room to recover if I stumbled before the next one. I felt the interviewers were considering more than my answers. Technical reasoning mattered alongside confidence, communication, attitude and professionalism. I had to keep my thoughts organized and stay composed while working through the quest…
Interview experiences · TCS
Tata Consultancy Services (North America) Software Engineer interview with DevOps and cloud topics
My interview had a clear structure: an HR screening, a technical interview on DevOps and cloud, and a final technical and managerial discussion. That last discussion returned to my project experience and expanded into Kubernetes, AWS, CI/CD, security, and Python. After that came another HR conversation. The difficulty felt average, and each stage gave me a clearer sense of what they cared about:…
Interview experiences · TCS
Tata Consultancy Services (North America) Software Engineer interview with resume-based API code
I expected a wide range of technical topics, but the conversation stayed close to my resume. The interviewer focused on what I had already listed and did not pull in much outside my background. My panel felt uneven. Some questions were very easy, but for me they went deeper into integration-style code, arrays, and Python basics. That resume-first pattern came up again with AWS because I had a cer…
Interview experiences · TCS
Tata Consultancy Services (North America) Software Engineer NQT interview with coding gap
The NQT process I went through had two main rounds after the test. First was a combined technical and managerial round covering resume knowledge, coding, and problem solving. Then came an HR round on fit, cultural comfort, willingness to relocate, and confirming background details for final selection. I had been categorized for roles based on my NQT performance. I did well on several aptitude and…
Interview experiences · TCS
Tata Consultancy Services (North America) Software Engineer office interview experience
After clearing the TCS NQT exam, I was shortlisted for interviews at a TCS office. Early questions covered core Java, SQL, and DSA. The route from the exam through shortlisting into technical and HR-style evaluation was clear. The in-person rounds combined technical work and fit. I introduced myself and connected answers to my resume. They asked why TCS, why they should hire me, my expected packa…
Interview experiences · TCS
Tata Consultancy Services (North America) Systems Engineer rushed round
One interview round was rough. The interviewer arrived late, and with time already tight, I was not given a real chance to discuss or explain my reasoning. Questions came quickly and felt more like rapid checking than conversation. Near the end, they wrapped up by asking only a few more questions and telling me I was not a fit for the role. The difficulty felt high largely because I did not get t…
Interview experiences · Tavant
Tavant Software Engineer interview experience: fast technical rounds
The process moved quickly. After an initial coding step, I had two back-to-back technical rounds and then an MR and HR discussion. It all finished in about a week, with little slack between stages. For the final round, I was expected to visit the office. That made the last part feel more formal and committed than the earlier fast sequence. I did not receive an offer. Still, the cadence was effici…
Interview experiences · TCS
TCS Software Engineer Interview Experience: Long fresher-oriented timeline
After applying online, the TCS process stretched close to 6 to 12 months, though it was organized once underway. It moved from technical coding to an advanced coding/problem-solving round, then a managerial discussion of my technical experience and projects, and finally HR topics: compensation, notice period, policies, and next steps. The NQT exam was important for shortlisting. My listed slot wa…
Interview experiences · TCS
TCS Software Engineer Interview Experience: long onsite technical and SQL day
I waited in a hall while candidates were called one at a time, then entered a technical round based directly on my CV. I was asked at least one DSA question, so the interview tested both fundamentals and problem solving. The day was long and exhausting. The format I recall had a technical segment first, followed by coding and SQL queries, and interviewers would help when I got stuck. It ran from…
Interview experiences · TCS
TCS Software Engineer interview: incomplete AVL tree and a Digital-role offer
After the recruiter call, I sat for the TCS Prime interview. It was focused and structured, lasting about 40 to 50 minutes. It covered DSA, core programming, my projects, and Python OOP. The technical section began with an AVL-tree coding task. I had to build an AVL tree from scratch with insert, delete, search, and LL, RR, LR, and RL rotations. I could not finish the implementation completely, a…