After a recruiter call where we talked through my background and what I wanted from the role, I moved into technical discussions with the hiring team. The technical part felt very interactive, and the interviewer pushed me to go deeper on my current projects—explaining more than just what I did, but how I thought about the work and what decisions I made along the way. I also had to walk through my past experience and responsibilities clearly.
Once the technical portion was done, the final step was an HR conversation. That part felt easy compared to the technical round, and the overall process was relatively quick—tied to finishing within about a day for at least one version of the process I experienced. My main impression was that it was structured and straightforward, and the questions were aligned to my experience rather than being completely generic.
3 months ago
Average Neutral Gurgaon, Haryana
My first technical conversations were pretty hands-on and web-focused. I went through questions around HTML, CSS, and JavaScript—things like what a semantic tag means, the difference between div and span, and how you’d go about converting a span into a div. We also talked about styling semantics like bold versus strong, and then shifted into layout basics like the position property.
After that, the deeper technical side got into core programming foundations and database work. I covered core Java concepts along with OOP and SQL, and at various points I had to handle a medium string question too. The interviewer was friendly and made it feel like an actual discussion, but the scope still went beyond surface-level facts, with questions reflecting the projects I’d worked on and the web technologies I’d used.
5 months ago
Average Positive Pune
My interview journey followed a fairly multi-stage pattern where HR and technical rounds were clearly separated. I remember it starting with an HR-rel…
6 months ago
Easy Positive Netanya
The process centered on a timed take-home style technical test, and it was intense in a very specific way. I had a strict one-hour window for a mixed …
7 months ago
Difficult Positive Calcutta
I had a short but heavy set of interview slots lined up, and I remember the pacing being very compressed. It was a sequence of three rounds with HR an…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically consists of distinct HR and technical rounds, which can be structured and quick, often wrapping up within a few days to two weeks. However, some candidates reported longer timelines and delays in receiving offer letters, leading to frustration.
HR roundTechnical evaluationTimeline
Technical Evaluation Focus
Candidates can expect a hands-on technical evaluation that dives into core programming concepts, web technologies, and database knowledge, often requiring them to explain their thought processes and project experiences in depth.
JavaSQLWeb technologies
Behavioral & Communication Assessment
The HR rounds emphasize communication skills and alignment with company values, with candidates expected to articulate their experiences clearly and respond to behavioral questions effectively.
CommunicationBehavioral questionsSTAR
Problem-Solving Under Pressure
Some candidates faced timed assessments that tested their problem-solving abilities in SQL and programming, requiring them to explain their reasoning and approach during follow-up discussions.
Timed assessmentProblem-solvingSQL
Depth of Technical Questions
The technical interviews often include medium to firm difficulty questions, with a focus on practical applications and deeper understanding rather than just surface-level knowledge, which can catch candidates off guard.
Medium difficultyPractical applicationsDeep understanding
Overall Candidate Experience
While many candidates found the interview process structured and supportive, some experienced a lack of clarity and responsiveness from HR, which negatively impacted their overall impression despite the technical discussions being positive.