READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 1 of 153
Interview experiences · A healthcare data
A healthcare data Software Engineer interview: client-facing technical discussion
My interview followed a classic sequence: two technical-style rounds, a manager round, and an HR touchpoint. The first technical discussion focused on my core skills and what I could actually do, with enough fundamentals to judge whether my background matched the role. The second round was more advanced and realistic. I spoke with someone closer to a client setting, and they went deeper technical…
Interview experiences · A healthcare data
A healthcare data Software Engineer Interview Experience: A clear fit check and basic programming questions
I started with a recruiter conversation that felt more like a fit check than an interrogation. We discussed my interests and projects, the technologies I knew, and how I preferred to work. I also got the usual personality and behavioral questions about collaboration, teamwork, and how I behaved with colleagues. After that, the process stayed straightforward. There was a technical side, but it did…
Interview experiences · A healthcare data
A healthcare data Software Engineer interview: graduate assessment logistics
I attended a graduate assessment center, but the logistics felt poorly handled from the beginning. I was told to arrive early for a late start, and when I arrived no one was at the front desk, so I waited without guidance. At the introduction, I learned it was supposed to start later than I had been told and was meant to include a peer session. The people who appeared for that session were mostly…
Interview experiences · A healthcare technology
A healthcare technology Business Analyst interview: absent interviewers
I passed an online technical test and expected the live interview to proceed normally. Instead, when I joined the scheduled online meeting, no interviewer appeared. I waited about half an hour before the system automatically moved me to the next day. The same thing happened the next day: I logged in and again there was no interviewer. It was unsettling because I could not tell what they were look…
Interview experiences · A healthcare technology
A healthcare technology Business Analyst Interview Experience: microphone troubleshooting and SQL
My interview began with the usual conversation basics, then quickly became a mix of communication, role fit, and practical technical checks. I introduced myself, discussed what I enjoyed outside work, location preferences, whether I could handle shift work, and my willingness to relocate. On the technical side, I was asked fundamentals and small scenario prompts. One question was what I would do…
Interview experiences · A healthcare technology
A healthcare technology Software Engineer Interview Experience: Java, SQL, and OOP basics
My process used online assessments followed by a practical technical interview. The assessment covered programming fundamentals and SQL, while the technical screen stayed close to basic OOP and core language skills. I was asked Java and SQL questions, including a query to find the second highest salary in an employee table, along with a Java logic question. There were also versions of the process…
Interview experiences · A healthcare technology
A healthcare technology Software Engineer Interview Experience: unclear required in-person HR step
I got far enough to be told that I needed an HR discussion, but the requirement was confusing. It sounded mandatory to do it face to face in a specific location far from my hometown. I asked what the round involved and what kinds of questions they planned to ask because I did not understand its purpose or format. The process lacked basic transparency, which made preparation difficult. Beyond the…
Interview experiences · A healthcare technology
A healthcare technology Software Engineer interview: screening, coding, and campus path
My process felt relatively easy and structured. It moved from an online screen to a communication round, then a coding round and final assessment, followed by a final interview. In at least one path, I also experienced an on-campus setup with an aptitude screen followed by a technical process that included SQL and coding questions. Across both paths, the difficulty stayed manageable, and the ques…
Interview experiences · ABB
ABB Software Engineer interview: fundamentals and a difficult final round
The process started with a familiar technical sequence but became a test of both fundamentals and performance under pressure. I faced medium-level data-structures and algorithms questions, plus computer-networks and operating-systems topics with a clear cybersecurity-basics tilt. There was also a group discussion, which made it feel less like a one-shot evaluation and more like an assessment of h…
Interview experiences · ABB
ABB Software Engineer interview: logical test and office meeting
I applied through Workday, was contacted, and chose a time for a recruiter call. That simple portal setup moved quickly into a more demanding process than I had expected, although it seemed well managed. I first took a cognitive or logical test and then had an online Teams round. After that I met people in person at the office, including the department for the role, HR, and possibly other manager…
Interview experiences · ABB
ABB Software Engineer interview: one quick behavioral conversation
I had one behavioral interview that lasted about half an hour, followed by a short wait while they followed up. Things moved quickly once the interview ended: an offer arrived roughly 15 minutes later. There was plenty of time for questions during the conversation, and I appreciated being able to ask and clarify things. It was a very good experience. The quick, conversational format made it easie…
Interview experiences · ABB
ABB Software Engineer interview: system design with manager and team
My interview path was straightforward: an HR screen, a conversation with the hiring manager, and then a meeting with the team. The second stage was the real technical checkpoint, and it focused much more on system design than deep coding. Once I was there, the structure was clear and there were no surprises about the format. I concentrated on explaining my thinking through the system-design promp…
Interview experiences · AbbVie
AbbVie Account Executive first interview experience
My first interview felt good from the beginning. After scheduling, I met one interviewer who was professional and friendly. The discussion was comfortable and easy to follow, communication was clear, and the interview did not feel rushed. It was a straightforward conversation. I did not feel set up for anything tricky, and I left understanding what they were looking for and feeling there was soli…
Interview experiences · AbbVie
AbbVie Software Engineer interview: academic and project science questions
Two managers spent most of the interview on my academic background and project work. They asked scientific questions about what I had done during my bachelor's degree and in the projects I had worked on, so the discussion stayed close to my own experience. The questions were specific and technical enough that the difficulty felt high. I could answer them fairly well because they connected to work…
Interview experiences · ABC Education
ABC Education Software Engineer aptitude and DSA interview experience
The process had three levels: an aptitude and coding test, a technical interview, and an HR interview. I found the aptitude and coding test easy to clear. The technical round focused on basic data structures and algorithms, including sorting, then touched briefly on databases. It was not especially complex. The HR discussion was more about fit than difficulty. The overall atmosphere was relaxed a…
Interview experiences · ABC Education
ABC Education Software Engineer interview: OS, DBMS, OOP, and DSA
I started with an online assessment that combined coding with multiple-choice questions in OS, DBMS, OOP, SQL, and aptitude. Soon after, the first technical round covered my resume and projects, then DSA and broader computer-science fundamentals. I spent most of it explaining my reasoning rather than only stating answers. The next technical round was harder: a deeper coding problem, project follo…
Interview experiences · ABC Family
ABC Family Software Engineer fundamentals interview experience
My process had three stages: an aptitude and coding test, a technical interview, and an HR interview. The first test felt easy to clear, and moving into the technical round was not overwhelming. Technical questions leaned on data structures and algorithms, especially sorting, with some database concepts. I did not feel they were trying to trick me. They wanted to see whether I understood the fund…
Interview experiences · ABC Family
ABC Family Software Engineer Interview Experience: Testing and validation background
The interview centered on my testing background and real validation work. In discussing my projects, I covered automation and API validation, then moved into SQL and integration testing. I liked that the conversation remained connected to the work involved in the role. It did not feel as though I was being tested with random trivia. Instead, the focus was on whether I could explain my process and…
Interview experiences · ABC Family
ABC Family Software Engineer interview: four coding-heavy rounds
I went through four rounds that were coding heavy from the start. The online assessment combined coding with multiple-choice questions on OS, DBMS, OOP, SQL, and aptitude. The first technical interview covered my resume and projects before moving into DSA and core computer-science fundamentals. The next technical round was tougher. I had a more difficult coding problem, deeper questions about my…
Interview experiences · ABC
ABC Software Engineer aptitude, sorting, and HR interview experience
The process had three levels: an aptitude and coding test, a technical interview, and an HR interview. The aptitude and coding test was very easy to clear. The technical round had simple data-structures and algorithms questions, especially sorting, plus database basics. HR was about fit rather than deep technical work. Overall, it felt manageable and landed on the easier side of the spectrum. Loc…
Interview experiences · ABC
ABC Software Engineer interview experience
The process was coding-heavy and structured from the start. After recruiter outreach, I completed an online assessment with coding questions and multiple-choice questions on OS, DBMS, OOP, SQL, and general aptitude. Later, the first technical interview went through my resume and projects, DSA, and core computer-science concepts. The next technical round was tougher, with a harder coding problem,…
Interview experiences · Abercrombie & Fitch
Abercrombie & Fitch Account Executive interview: casual group setting
I had a casual, low-pressure group interview in a store setting. I sat with other applicants while the interviewer asked a small set of questions. It seemed intended to gauge how I carried myself, particularly around customer service, interacting in the moment, style, outfit presentation, and the energy I would bring to the brand. The questions covered my past experience, time management and orga…
Interview experiences · Abnormal AI
Abnormal AI Software Engineer interview: AI agents used throughout a real-work loop
After a recruiter call, I met a hiring manager to discuss my background, projects, and what I hoped to learn from the team. Everyone was welcoming and responsive, and the handoffs between rounds were clear. The technical work centered on AI rather than classic LeetCode prompts. In a large codebase, I used AI to understand the structure, implemented a feature with AI assistance, and wrote tests. T…
Interview experiences · Abnormal AI
Abnormal AI Software Engineer interview: feature implementation in an existing codebase
My technical interview focused on AI-assisted coding. I was placed in a fairly large existing codebase and first had to make sense of it with AI tools. Then I used that understanding and AI support to implement a feature and write tests for the changes. It felt less like a pure algorithm check and more like a test of whether I could turn a task into working code while using AI in a controlled way…