Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

6 stories

Likes earn the author +10 XP for the first 3 likes each day

VirtusaSoftware Engineer
Reported Jul 2026

Virtusa Software Engineer interview: fundamentals, arrays, SQL, and HR

I had a straightforward set of rounds built around fundamentals and light coding. The technical flow began with theory and linked-list basics, then a small task to find an element in an array. SQL followed. I also explained my projects and why I chose particular technologies. In another technical conversation, I introduced myself before the interviewer followed with questions tied to my coding kn…

Technical Screen0
VirtusaSoftware Engineer
Reported Jul 2026

Virtusa Software Engineer interview: online assessment, abbreviated technical round, and HR

My interview followed a standard order: an online assessment, then a technical interview, and finally HR. The screening checked problem solving and programming fundamentals, while the later steps were more about technical fit and communication. OOPS concepts were a large part of the technical round. The session started late and ended quickly, so it did not get far beyond what they needed to cover…

Online Assessment0
VirtusaSoftware Engineer
Reported Jul 2026

Virtusa Software Engineer interview: Java, architecture, and HR rounds

I went through two technical rounds followed by a final HR conversation. The technical questions repeatedly returned to the details on my resume rather than staying at a surface level. The topics leaned toward programming fundamentals and Java-centered systems: OOPS concepts and language features, microservices design and patterns, authentication, and multithreading. I also faced coding questions…

Technical Screen0
VirtusaSoftware Engineer
Reported Jul 2026

Virtusa Software Engineer interview: programming fundamentals and relocation

I had one technical interview followed by a short HR round. The technical discussion covered object-oriented concepts, Python and Java basics, and DBMS. I also solved a simple coding problem to demonstrate the fundamentals. HR focused mainly on practical availability matters such as relocation. I was surprised by how many topics the technical round combined. Overall, the process felt easy, straig…

Technical Screen0
VirtusaSoftware Engineer
Reported Jul 2026

Virtusa Software Engineer interview: AWS experience stopped progress

At a walk-in event, I completed an AI assessment and then a technical round, which I cleared. I was told a virtual HR call would follow, but it arrived about ten days later. After that call, I had another technical interview and felt it went smoothly. I did not progress because they said I lacked hands-on AWS experience. That was frustrating because the interviews themselves had gone well, and it…

RejectedOnline Assessment0
VirtusaSoftware Engineer
Reported Jul 2026

Virtusa Software Engineer Interview Experience: Detailed JavaScript and React round

My virtual first round split heavily between frontend JavaScript theory and hands-on JavaScript coding. On React, I discussed the virtual DOM, why useMemo and useCallback matter, when react.memo helps, context API, Redux-style flow, and the difference between useRef and useState. For JavaScript, I wrote and explained the pattern 9 8 7 4 5 6 1 2 3, described as a snake-and-ladder-style pattern. I…

0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP