Interview Experiences

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

Share yours, earn XP

4514 stories

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

LTMSoftware Engineer
Reported Jun 2026

LTM Software Engineer Interview Experience: Aptitude test to HR

The first stage was an online assessment on AMCAT. It was mostly aptitude based and entirely multiple choice, with some analytical reasoning and no traditional coding. Clearing that gate led to a technical interview. The technical conversation focused much more on my resume, background, and how I would work in the role. The interviewer led the discussion, seemed to know the work well, and was dir…

OfferOnline Assessment0
LovisaAccount Executive
Reported Jun 2026

Lovisa Account Executive Interview Experience: A quick retail interview

The first step was quick and low pressure. I received an email shortly before the interview, and the move from application to meeting felt fast. The conversation covered who I was, why I wanted to work at Lovisa, my availability, customer-facing work, and how I would handle different situations. The manager conversation was relaxed too, with standard retail questions, sometimes only a handful of…

Onsite0
Konrad GroupUX/UI Designer
Reported Jun 2026

Konrad Group UX/UI Designer Interview Experience: Portfolio and design challenge

I began with a short, easygoing HR or recruiter chat. We discussed why I was interested in design and the company, my salary expectations, and what I did outside work. It was friendly and conversational rather than an interrogation; it felt as though they wanted to understand me. Next, I presented my portfolio in person and answered behavioral questions as I walked through it. That was followed b…

HR Screen0
HylandCustomer Success Engineer
Reported Jun 2026

Hyland Customer Success Engineer Interview Experience: Three rounds and an unclear decision

I completed three interview rounds, and the format stayed fairly consistent throughout. Each technical round lasted somewhere between around 30 minutes and nearly two hours. After all three, it looked as though the process would continue with a larger shortlist. What happened next threw me off. They selected a group of interns, then abruptly changed course and chose a smaller subset, specifically…

Technical Screen0
Dell Tech LaboratoriesSoftware Engineer
Reported Jun 2026

Dell Tech Laboratories Software Engineer Interview Experience: A delayed schedule

The process felt streamlined overall. The HR contact was humble and responsive, including when I needed help scheduling around my availability. The frustrating part was the delay: I had to wait an entire day to complete the interview when it felt as though it could have happened sooner. Aside from that timing issue, the interaction did not seem especially complicated and the coordination was othe…

0
ADCI - KarnatakaSoftware Engineer
Reported Jun 2026

ADCI - Karnataka Software Engineer Interview Experience: Recruiter call and coding

My first substantive conversation was a phone interview over Chime with a recruiter. It began casually enough that I thought it might remain a relaxed chat. Instead, it quickly shifted into behavioral questions about how I had handled situations, along with one easy LeetCode coding problem. The difficulty was average, but the timing and change in tone caught me off guard. I did not receive an off…

HR Screen0
ADCI - KarnatakaSoftware Engineer
Reported Jun 2026

ADCI - Karnataka Software Engineer Interview Experience: Guided online test

Someone from the hiring side contacted me through LinkedIn, and after I applied, the process began with an online test. The questions resembled HackerRank problems, but they came with a few videos that explained the reasoning and approach the company expected. The difficulty felt average. This stage seemed to be testing how I reasoned rather than brute-force coding. I did not receive an offer, th…

RejectedOnline Assessment0
Accenture in IndiaSoftware Engineer
Reported Jun 2026

Accenture in India Software Engineer Interview Experience: Python and SQL

The technical interview followed a familiar sequence of question sets. It opened with basic Python, including decorators and generators, then moved to the difference between lists and tuples. From there, the discussion turned to SQL ranking functions such as rank and dense rank, before ending with a flatten-list type problem. It felt more like a check of common knowledge than an attempt to probe…

Technical Screen0
Accenture in IndiaSoftware Engineer
Reported Jun 2026

Accenture in India Software Engineer Interview: A group interview with five students

My process was straightforward. It started with a group round of five students, where the questions were basic and mostly behavioral. There was little technical probing, and it felt easier than I had expected. Because it was a group format and stayed on fundamental and behavioral questions, it did not feel like an interview that required deep specialization. The experience was low stress, and all…

OfferOther0
Accenture in IndiaFull Stack Engineer
Reported Jun 2026

Accenture in India Full Stack Engineer Interview: Three phone interview rounds

My process had three rounds, mostly by phone. It began with a recruiter screen lasting about 30 to 45 minutes. Next came a technical conversation with someone from a developer background, also about 30 to 45 minutes. The final round was behavioral and used the same call format. The pacing felt consistent: each call was focused and did not drag. The recruiter screen covered my background, while th…

OfferHR Screen0
Cloud Big Data TechnologiesSoftware Engineer
Reported Jun 2026

Cloud Big Data Technologies Software Engineer Interview: A harder onsite coding round

I went through a Google-style, DSA-heavy loop that became much harder at the onsite level and ended in rejection. I passed the recruiter or phone screen, where the bar felt lower and the focus was role fit and coding ability. I then completed multiple DSA and coding interviews in a standard LeetCode-style format, with follow-ups about optimizing or implementing similar solutions. At the onsite, t…

RejectedTechnical Screen0
MicrosoftSoftware Engineer
Reported Jun 2026

Microsoft Software Engineer Interview: Two SDE2 online assessment problems

I started with an online assessment for a Software Development Engineer 2 role. It had two DSA questions, one medium and one harder. I got full marks on every test case for the medium problem. I came close on the hard one, but it was not perfect. After the OA, I waited and tried to work out whether I might get a callback. I had no further detail from the process; the assessment result was the onl…

Online Assessment0
FIRSTNET GLOBALSoftware Engineer
Reported Jun 2026

FIRSTNET GLOBAL Software Engineer Interview: Project work and behavioral questions

I applied online and then completed a pre-employment assessment. The next steps included a phone screen, a technical round, and a behavioral round. The process kept returning to my project work: what I built, the challenges I ran into, and the people side of teamwork. The behavioral questions covered teamwork, conflict, and communication under pressure. The difficulty did not feel extreme. It see…

RejectedTechnical Screen0
LinkedInSoftware Engineer
Reported Jun 2026

LinkedIn Software Engineer Interview: Notification-service design and an accepted offer

About a week after a recruiter call, I had a technical screen that surprised me with its intensity. It ran about 45 minutes and combined behavioral and technical questions. The technical work leaned toward system design: I had to reason through a notification-delivery service, including reliability and scaling, rather than just draw a high-level picture. The later interviews stayed rigorous, with…

OfferTechnical Screen0
LenovoAccount Executive
Reported Jun 2026

Lenovo Account Executive Interview: Recruiter call and two-person team interview

After I applied, I had an easygoing recruiter conversation that moved quickly, with clear next steps. It helped me understand the broader company and role while they assessed whether the fit worked from both sides. Later, I had an online interview with two team members. The discussion centered on my match for the position, but the feedback was not specific. It threw me off that they seemed not to…

OfferHR Screen0
Marks & SpencerAccount Executive
Reported Jun 2026

Marks & Spencer Account Executive Interview: Shop-floor exercise and role play

I arrived early and was first sent to the shop floor to identify a few things that could be improved. Afterwards I went upstairs for a more formal interview. The setting felt welcoming, and the conversation moved quickly from who I was to what I could bring to the role. They asked about my background, what I knew about the brand, customer service, teamwork, and how my previous experience related…

Onsite0
MongoDBCustomer Success Engineer
Reported Jun 2026

MongoDB Customer Success Engineer interview: customer-meeting presentation

My process took a couple of months. It began with an HR screen, followed by a hiring-manager interview on the role and typical customer-success questions, then a peer interview covering databases and cloud-native infrastructure. The last stage was a presentation challenge framed as a customer meeting. I had a prep call before presenting to a fictitious customer panel, with interviewers playing di…

HR Screen0
NatixisNetwork Engineer
Reported Jun 2026

Natixis Network Engineer interview: fifteen coding problems

After a phone screen, I had two more rounds with hiring managers. The pace was fast but structured. The first two conversations were straightforward; the third was the real stamina test. That last interview was a full sheet of LeetCode-inspired coding problems: roughly fifteen questions in about forty-five minutes. Many were easier problems, but the time limit made the exercise intense. Some requ…

Technical Screen0
ScaleSoftware Engineer
Reported Jun 2026

Scale Software Engineer interview: card-game coding exercise

The recruiting flow felt friendly at first, then the technical work proved unlike a standard LeetCode trick question. The coding prompt used a card-game theme and was more about implementing many conditions than finding an elegant idea. It moved through multiple cases, so I had to track the logic and states carefully. In the live coding round, I needed to work through those conditions quickly. Th…

Technical Screen0
RevolutProduct Manager
Reported Jun 2026

Revolut Product Manager interview: hypothetical business case

My process felt lighter than the intense multi-round processes I had seen elsewhere. It started with an HR screen and moved into a case-style evaluation. Recruiter interactions were straightforward, prep materials were provided, and I was expected to do structured analysis. For the case, I worked through a business scenario and gave reasoning and a recommendation. The examples were hypothetical r…

RejectedHR Screen0

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