Interview Experiences

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

Share yours, earn XP

4433 stories

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

ProdaptSoftware Engineer
Reported Aug 2026

Prodapt Software Engineer Interview Experience: OA focused on aptitude

My process began with an online assessment meant to filter many people quickly. It was mostly MCQs on attitude and reasoning, including data interpretation, numerical reasoning, and verbal-style questions, plus one medium-to-hard coding problem. The mix felt balanced to me: the aptitude portion could be tricky if I rushed, and the coding problem could easily decide the outcome. I felt reasonably…

RejectedOnline Assessment0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: quick move from assessment to virtual onsite

My process started with an online assessment that I completed in about three days. The HR contact asked when I could finish it, so timing mattered from the start. After that, I had a phone screen with behavioral questions and LeetCode. A couple of days later, I had the virtual onsite. It included more LeetCode, OOD, and system design. When I reported the experience, I had just completed the phone…

0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: uneven onsite question difficulty

I think my loop followed a classic coding-and-design structure, but the outcome went against me. I went through an assessment and several later stages. By the final onsite setup, it felt as though I was competing against other interviewers' question sets. At the onsite stage, I had the impression that some candidates got standard LeetCode questions while others got harder, less familiar variants.…

Onsite0
Accenture TechnologySoftware Engineer
Reported Aug 2026

Accenture Technology Software Engineer Interview Experience: A comfortable technical discussion

The experience felt positive overall. The interviewers were professional and engaging from the start, and the conversation stayed comfortable even when the questions became challenging. I talked through my experience and technical knowledge throughout. The questions did not feel random. They were meant to test how I thought. The difficulty kept me attentive, while the way people interacted with m…

0
Accenture TechnologySoftware Engineer
Reported Aug 2026

Accenture Technology Software Engineer Interview Experience: Angular, RxJS, and project scenarios

My interview started with technical rounds that leaned heavily on the frameworks in my resume. The first conversation centered on frontend work, including Angular, TypeScript and JavaScript, and RxJS. It also moved into broader questions about how I would approach frontend development and solve problems from real projects. The second technical stage stayed stack-specific but added REST API develo…

HR Screen0
Société GénéraleSoftware Engineer
Reported Aug 2026

Société Générale Software Engineer Interview Experience: PHP and Angular technical rounds

My process opened with a recruiter-style conversation where I introduced myself and talked through my background. Then I had two technical rounds, a first and second level, focused on my projects and problem solving, with a strong emphasis on PHP and Angular. The interviewers also asked about APIs, databases, and application architecture. In the first technical round, I started with an introducti…

HR Screen0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: Clarify before coding

The interviewer was friendly, and their questioning style made me feel less rushed. They would ask a question, wait for my answer, listen carefully, and then ask follow-ups. What stood out was the importance they placed on clarity before coding. They repeatedly appreciated it when I clarified the requirements and intended approach instead of jumping straight into writing code. That made the inter…

0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: graph and monotonic stack problems

After I was shortlisted from an online assessment, I was called for an interview that felt friendly and focused on solving. The interviewer gave me two medium-level DSA problems, one on graphs and one involving a monotonic stack. I was comfortable enough to talk through my approach while working, and the problems covered a useful mix of techniques rather than one narrow topic. I did not get an of…

0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: behavioral panel on Microsoft Teams

My interview was a roughly forty-five-minute Microsoft Teams call with a two-person panel. It was mostly behavioral, focused on my background and resume, with fewer technical questions than I expected. The pace felt more like a conversation than a coding session. The panel wanted me to explain my experience instead of pushing deeply into algorithms. I did not receive an offer. In hindsight, the f…

0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: Standard systems and LeetCode rounds

I went through technical rounds on systems and database knowledge, along with the usual LeetCode problems you see online. There were also behavioral rounds with stressful questions meant to evaluate social and communication skills. It felt boring and outdated to me, and I did not get an offer. I was disappointed by more than the outcome. The process did not bring anything new even though I had pu…

0
ActurisBusiness Analyst
Reported Aug 2026

Acturis Business Analyst Interview Experience: GMAT test and case studies

After I applied, I received a short GMAT-style test with 20 questions and about 30 minutes to complete it. A recruiter followed up, and I went through three interviews. Each round paired case study analysis with more personal questions. The schedule felt intense but structured: two interviews on the same day, followed by a final round on another day. The first Teams interview began with getting t…

0
Accenture TechnologySoftware Engineer
Reported Aug 2026

Accenture Technology Software Engineer Interview Experience: design-level questions after recruiter call

Right after I applied through the job portal, a recruiter called to check my basic communication and whether my experience matched the job description. I was then scheduled for an online interview of about an hour, with several time slots to choose from. The interviewer asked design-level questions. It felt like the assessment was testing how I approached bigger-picture problem solving, not just…

HR Screen0
Honeywell TechnologiesSoftware Engineer
Reported Aug 2026

Honeywell Technologies Software Engineer Interview Experience: System design and AI themes

The process focused on explaining concepts and showing how well I understood the work behind them. Rather than going straight into coding, it centered on the systems side of software engineering, and I spent a lot of time talking through system design ideas. There was also a noticeable focus on newer AI themes. I tried to connect what I knew to the current "latest trends" type of questions. The b…

0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: rising coding difficulty under time pressure

My first assessment round involved difficult coding with limited time. I remember occasional helpful hints, but it was still very hard to finish under the clock. The questions grew harder as the round went on, which made the final part the most stressful. I was also frustrated that there was not more real-time guidance from an interviewer while I worked. I did not complete the full coding portion…

0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: behavioral focus with easier coding

My interview loop was more straightforward than I had heard. There were two rounds, both combining behavioral questions with easier LeetCode-style questions. The first was with a manager and the second with a team member. The difficulty felt manageable, and the behavioral conversation was not harsh. Leadership principles clearly mattered, but the discussion did not feel adversarial. It felt like…

Offer0
ADCI - KarnatakaSoftware Engineer
Reported Aug 2026

ADCI - Karnataka Software Engineer Interview Experience: Familiar technical loop

The experience felt dated and generic. I went through technical rounds on systems and databases, along with the usual LeetCode-style questions available online. The behavioral rounds used stressful prompts to evaluate my social skills. It never felt tailored, and by the end it was not engaging enough to match the effort I had put in. I ended without an offer. What stayed with me was how standard…

0
ValeoSoftware Engineer
Reported Aug 2026

Valeo Software Engineer Interview Experience: C code tracing and embedded protocols

I started with an online assessment on HackerRank, which immediately set the tone. It leaned heavily on data structures and algorithms in C, with many code-tracing prompts where I had to predict how snippets would behave and whether they would compile. There were also multiple-choice questions on embedded systems and communication protocols, especially UART, SPI, and I2C. After the assessment, I…

HR Screen0
RenesasSoftware Engineer
Reported Aug 2026

Renesas Software Engineer Interview Experience: HirePro assessment and LRU cache

I took a HirePro online assessment that was structured and time-boxed. It began with multiple-choice questions on operating systems, DBMS, and firmware-related material. There was also a small coding section with two questions tied to articulation points, and I discussed my project details during the process. After that, I got more DSA-focused questions about cache memory. The main task was imple…

Online Assessment0
Accenture TechnologySoftware Engineer
Reported Aug 2026

Accenture Technology Software Engineer Interview Experience: SQL written on paper

I went to a physical interview for a .NET role, but the technical assessment was not what I expected. Instead of only having a typical interview conversation, I was given SQL and stored procedure work to write on paper, along with scenario questions meant to mirror real life. There was no update afterward and no clear rejection. I later realized that I had not followed up, and once the process we…

0
Accenture TechnologySoftware Engineer
Reported Aug 2026

Accenture Technology Software Engineer Interview Experience: DSA, design, and leadership principles

After my recruiter call, I moved into a structured sequence. First came a DSA-focused round, then a system design interview. The final step returned to DSA and added Amazon Leadership Principles with more behavioral questions. The difficulty stayed in the average range, but moving between coding-heavy and conversation-heavy expectations without much time to settle was mentally tiring. I did not g…

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