real interview stories, told over a cup of tea ♡
Interview Experiences
3935 interview stories from candidates at 857 companies: how each round went, what was asked and how it ended. Every company page links to practice questions in the same style.
- 3935
- Experiences
- 857
- Companies
- 532
- Offers
3935 results
- Accenture in India Software Engineer Interview Experience: on-campus assessment to online interviewAccenture in India · Software Engineer · Online Assessment · Aug 2026Offer
I went through an on-campus drive that was structured from start to finish. The online assessment began with mental ability, then basic-computer-science MCQs, followed by three questions on frontend, backend, and DBMS. That stage was eliminatory across all of those parts. Next came a communication round that I found easy, followed later by a 15 to 20 minute online interview. That shorter intervie…
- Accenture in India Software Engineer Interview Experience: Paper SQL assessmentAccenture in India · Software Engineer · Aug 2026
I interviewed in Malaysia for a .NET role, but the day did not fully match that expectation. The technical assessment focused on SQL and stored procedure style work, and I wrote part of it on paper. There were also scenario questions that seemed intended to map directly to real-world tasks. The assessment itself felt fairly normal, but I received no update afterward and no formal rejection. I did…
- Accenture in India Software Engineer Interview Experience: polite scenario-based role discussionAccenture in India · Software Engineer · Aug 2026
The interview was comfortable from the start. The interviewer was polite, asked for a short introduction, and explained the job description and role expectations. The discussion then moved to scenario-based questions. It was less technical than many interviews and focused on how I would respond in realistic situations and think through the context. I did not receive an offer, but the experience w…
- Accenture in India Software Engineer Interview Experience: programming, SQL, projects, and HR scenariosAccenture in India · Software Engineer · Online Assessment · Aug 2026
I started with an online assessment, then had separate technical and HR interviews. The technical round covered programming concepts, SQL, my projects, and core computer-science fundamentals. It felt like they wanted me to connect theory with how I actually build. The HR round focused on how I present myself and work with others. I introduced myself, discussed strengths and career goals, and talk…
- Accenture in India Software Engineer Interview Experience: Python, SQL, Spark, and data modelingAccenture in India · Software Engineer · Aug 2026
The interview covered a broad set of topics: Python, SQL, Spark, Databricks, cloud concepts, data analysis, and data modeling. I approached it feeling that focused revision could cover a lot, and that proved useful because of the range. The data discussion asked how I would think through datasets and structure the modeling side. I did not receive an offer, but the difficulty felt more about bread…
- Accenture in India Software Engineer Interview Experience: Shortlisted but prolonged processAccenture in India · Software Engineer · Aug 2026
The technical content was not the main issue. Even after I was shortlisted, the process had many steps and long waits between updates. The back-and-forth communication felt excessive, and the delays added frustration rather than clarity. On paper, the process looked thorough, but its timeline made it hard to stay engaged. I did not receive meaningful signals at a pace that matched what the proces…
- Accenture in India Software Engineer Interview Experience: spaced system-design discussionsAccenture in India · Software Engineer · Aug 2026
I went through three interviews: a recruiter call followed by two technical rounds. The recruiter was very communicative, but the technical interviews were more about system-design-style discussion than hands-on coding. The pace also stood out. There was roughly one to two weeks between each step, so it felt stretched out rather than like a sprint. After the process, I had a phone call with the r…
- Accenture in India Software Engineer interview with DSA and AI basicsAccenture in India · Software Engineer · Technical Screen · Aug 2026Offer
My interview covered data-structures-and-algorithms basics, AI usage, and scripting basics. It began with the interviewer explaining things clearly and walking through my resume with me. The experience was good. The interviewer spoke slowly and clearly, and I did not feel rushed. That helped me stay focused while answering. I received an offer. The calm pace made the technical parts easier to han…
- Accenture in India Software Engineer interview with instant assessment rejectionAccenture in India · Software Engineer · Technical Screen · Aug 2026Rejected
The interview rounds were reasonable and professional, and the technical part felt manageable. I covered React and JavaScript topics such as hooks, reconciliation, HOCs, and performance patterns, plus some architecture discussion. A managerial round followed on past projects, team fit, and how I communicated through experience. After I cleared both interviews, I was given an online assessment cov…
- Accenture Technology Software Engineer Interview Experience: A comfortable technical discussionAccenture Technology · Software Engineer · Aug 2026
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…
- Accenture Technology Software Engineer Interview Experience: Angular, RxJS, and project scenariosAccenture Technology · Software Engineer · HR Screen · Aug 2026
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…
- Accenture Technology Software Engineer Interview Experience: design-level questions after recruiter callAccenture Technology · Software Engineer · HR Screen · Aug 2026
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…
- Accenture Technology Software Engineer Interview Experience: DSA, design, and leadership principlesAccenture Technology · Software Engineer · Aug 2026
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…
- Accenture Technology Software Engineer Interview Experience: DSA, scripting, and AI tools basicsAccenture Technology · Software Engineer · Technical Screen · Aug 2026
I had what felt like a straightforward interview process. I began with a brief introduction about myself, then the interviewer explained the job description and what the role involved. The questions moved to simple scenario prompts. The tone was easygoing. The interviewer was kind and spoke slowly enough that I didn't feel rushed. The discussion stayed mostly on basics: data structures and algori…
- Accenture Technology Software Engineer Interview Experience: SQL written on paperAccenture Technology · Software Engineer · Aug 2026
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…
- Accenture Technology Software Engineer interview with Databricks and PySparkAccenture Technology · Software Engineer · Online Assessment · Aug 2026
I started with a data-platform assessment containing Databricks multiple-choice questions and a PySpark coding problem. Soon after, I had a virtual interview focused on Databricks internals, including AutoLoader, plus another PySpark problem. The later in-office round went deeper into the same ecosystem. We discussed CDC, SCD types, and Unity Catalog, and I again solved a PySpark coding question.…
- Accenture Technology Software Engineer interview with unclear final statusAccenture Technology · Software Engineer · Online Assessment · Aug 2026Rejected
After I applied, the process moved quickly through an online coding assessment, a technical interview, and an HR discussion. The technical work covered core Java, Spring Boot, SQL, JavaScript, React, Git, and SDLC. We spent a lot of time discussing the projects on my resume, alongside scenario and HR questions. It felt moderately difficult and professionally run. What stayed with me was the lack…
- Accion Labs Software Engineer interview experience: an unattended rescheduled meetingAccion Labs · Software Engineer · Other · Aug 2026
Repeated communication failures derailed this interview, beginning with the scheduling. They postponed it only hours before the agreed time, and I agreed to meet the next day. When I joined the Microsoft Teams call, I waited to be admitted. Someone let me in after the scheduled time, then immediately left without saying a word. I sat alone for the entire 30 minutes the interview was supposed to l…
- ACI Worldwide Software Engineer Interview Experience: OOP, DBMS, and motivationACI Worldwide · Software Engineer · Aug 2026
I began with an introduction conversation about what the company does and what the role involves. It felt more like a fit check than an interrogation because they asked about my interests and details from my personal background. The next step was a technical round on fundamentals. I was asked theory about OOP and DBMS, implementation questions about interfaces, and some data-structures topics. Th…
- Acturis Business Analyst Interview Experience: GMAT test and case studiesActuris · Business Analyst · Aug 2026
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…
- Acuvate Software Software Engineer Interview Experience: Aptitude-heavy processAcuvate Software · Software Engineer · Online Assessment · Aug 2026
I began with a recruiter-style interaction. About a week later, I took a test that leaned heavily on aptitude and felt tricky. It seemed to judge more than experience. Even with a background, there was a clear emphasis on reasoning and aptitude questions. The sequence felt structured and demanding from the start. After the aptitude round came a group discussion, where communication and confidence…
- ADCI - Karnataka Software Engineer Interview Experience: A year of waitingADCI - Karnataka · Software Engineer · Aug 2026
This was frustrating mostly because it dragged on. The technical and personality parts were not the main problem. I had been interviewing for more than a year and did not feel that anyone kept me updated or consistently looped me in. The sequence was a home technical exam, then a home technical and personality set, followed by a Zoom technical exam. I kept waiting for clarity about timing and wha…
- ADCI - Karnataka Software Engineer Interview Experience: AI-assisted debugging and leadership principlesADCI - Karnataka · Software Engineer · Online Assessment · Aug 2026
The process began with an online assessment that had one DSA coding task and an AI-assisted debugging exercise. For the debugging part, I was given a coding database and had to use an assistant through prompts to work out why something failed. The stage ended with leadership-principles style questions. After that, I had three technical rounds. Each combined a DSA question with leadership-principl…
- ADCI - Karnataka Software Engineer Interview Experience: arrays by hand and bidding designADCI - Karnataka · Software Engineer · Technical Screen · Aug 2026
My loop began with an in-person first round that the interviewer said would take about an hour. We started with my resume and past experience, then moved into HR-related questions tied to that background. The technical portion was a medium arrays problem that I had to solve by hand. The second round was online and focused on backend design for bidding at an advertising agency. Moving from a hand-…
- ADCI - Karnataka Software Engineer Interview Experience: behavioral focus with easier codingADCI - Karnataka · Software Engineer · Aug 2026Offer
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…
- ADCI - Karnataka Software Engineer Interview Experience: behavioral panel on Microsoft TeamsADCI - Karnataka · Software Engineer · Aug 2026
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…
- ADCI - Karnataka Software Engineer Interview Experience: binary search, BFS, and AI questionsADCI - Karnataka · Software Engineer · Aug 2026
I went through two interview rounds. The first had two DSA problems. One used binary search on the answer, and the other was BFS. During that same round, they also asked about AI and hallucinations. The second round was a crypto number style question. The topics were varied, and the AI portion in the first round surprised me because it moved the conversation away from pure coding. I did not get a…
- ADCI - Karnataka Software Engineer Interview Experience: binary tree serialization and complexityADCI - Karnataka · Software Engineer · Technical Screen · Aug 2026
The first round had two DSA problems, with about 30 minutes for each. One was about serializing and deserializing a binary tree, followed by questions on time and space complexity. I handled both concepts in that round and moved forward, but things did not work out after that. The process stayed focused on fundamentals. They wanted me to implement a solution and explain its efficiency. When I did…
- ADCI - Karnataka Software Engineer Interview Experience: Bug finding and a relaxed culture fitADCI - Karnataka · Software Engineer · Online Assessment · Aug 2026Offer
The process was compact and low-stress. I first had an online assessment to find bugs in code, followed by another online assessment with two medium LeetCode-style problems. Then I had an in-person conversation about my experience and a LeetCode problem. The last stage was a culture-fit test that also had an online-assessment component. Everyone I spoke with was relaxed and easy to talk to. The t…
- ADCI - Karnataka Software Engineer Interview Experience: Clarify before codingADCI - Karnataka · Software Engineer · Aug 2026
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…
