READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 122 of 153
Interview experiences · Boeing
Software Engineer at Boeing: DBMS, coding, and work-life balance
I had a face-to-face interview that focused directly on technical topics. We talked about DBMS concepts and basic coding, and the interviewer was chill and friendly throughout. We also discussed work-life balance at the company, which made the setting feel more human than purely evaluative. Because the technical topics were clear and not overly mysterious, I felt more at ease than I expected in a…
Interview experiences · Accenture España
Software Engineer interview at Accenture España: smooth early rounds
I had an HR round and a business round, and the process wrapped up in about two weeks. It was straightforward, and I left feeling I had performed well. I was not selected, though the rejection communication was professional. Elsewhere in the process, delays and logistics problems showed how inconsistent the candidate experience could be. I came away feeling that confidence in the interviews did n…
Interview experiences · Accenture Technology
Software Engineer interview at Accenture Technology: early rejection and rapid manager call
I reached the online-assessment stage but did not advance. The rejection email was polite, so the stop felt more respectful than silent. In another hiring-manager conversation, I was asked only a few questions about my projects and was asked to explain them. It ended in under five minutes, without a deep technical discussion. These early experiences felt lightweight and did not always let me demo…
Interview experiences · Accenture Technology
Software Engineer interview at Accenture Technology: virtual and office rounds
The process moved quickly through several rounds. The early conversations were virtual, while a later round took place at an Accenture office, which made the interaction feel more direct. Recruiter and later rounds kept returning to my background, work history, and fit for the role. The difficulty was average and the interviews seemed intended to confirm consistency rather than introduce unrelate…
Interview experiences · Amazon India (ADCI)
Software Engineer interview at ADCI - Karnataka: difficult DSA and GenAI
The process moved from an OA-style round to DSA and then a GenAI-focused round, but late stages still included LeetCode-style DSA work. One problem used graph algorithms and another required more ad-hoc reasoning; both felt genuinely hard. Amazon Leadership Principles shaped the behavioral framing throughout, linking impact and ownership to problem solving. The difficulty kept rising, especially…
Interview experiences · Amazon India (ADCI)
Software Engineer interview at ADCI - Karnataka: DSA and AI-assisted coding
There were four stages in total, but I did not clear the first. It contained two questions: a DSA problem and an AI-assisted, repository-based coding task. I produced a solution for the DSA question but struggled with edge cases, then ran out of time before I could debug and iterate properly. The second task differed from a standalone LeetCode question because it used a codebase and a limited ass…
Interview experiences · Amazon India (ADCI)
Software Engineer interview at ADCI - Karnataka: DSA and GenAI
The process had two compact rounds. In the first, I solved two medium LeetCode-style DSA problems and discussed a project. The second combined one DSA question with basic GenAI questions and more project discussion about both individual and team work. The difficulty felt reasonable, but I had to explain my answers clearly and connect technical decisions to leadership-principle ideas such as trade…
Interview experiences · Amazon India (ADCI)
Software Engineer interview at ADCI - Karnataka: DSA and Leadership Principles
I had one direct interview round with two LeetCode-based DSA questions. One was an array problem in the style of classic book allocation; the other combined math and arrays. I needed to show sound fundamentals and a clear implementation. Amazon Leadership Principles were not an afterthought. They were woven into how I explained decisions, tradeoffs, and reasoning. The conversation was technical,…
Interview experiences · Amazon India (ADCI)
Software Engineer interview at ADCI - Karnataka: networking depth
A phone screen began with my ongoing work and projects, but every answer led to deeper follow-up. I used STAR-style stories to keep the conversation structured as the interviewer drilled into my experience. The technical part covered TCP/IP and routing topics including OSPF and BGP. The interview assessed both how I described impact and ownership and whether I could reason through practical netwo…
Interview experiences · ALTEN Belgium
Software Engineer interview at ALTEN Belgium
There were three straightforward rounds: HR first, then the client account manager on the Alten side, followed by a client panel. HR was about general fit. The account-manager conversation covered the projects and what the role would look like day to day. The client panel felt like a final check that I understood the mission and could discuss relevant experience honestly. Nothing in the process s…
Interview experiences · Alten Spain
Software Engineer interview at Alten Spain: interview experience
The process was direct and pleasant in its interactions. I was mainly asked to discuss my skills, with a clear aim of understanding what I could do and matching my experience to a possible role. I had one introductory interview where they listened carefully without making the process complicated. It did not turn into a long chain of stages. The focus seemed to be on the initial assessment and the…
Interview experiences · Altimetrik
Software Engineer interview at Altimetrik: relevant frontend discussion
After recruiter conversations, I had a practical technical discussion on JavaScript, React, TypeScript, system design, performance optimization, and general problem solving. It felt connected to actual frontend work rather than random trivia. The HR round was transparent about role expectations and the hiring process, and the interviewer was approachable. Background verification and later communi…
Interview experiences · Amazon Advertising
Software Engineer interview at Amazon Advertising
This four-round loop was about DSA execution and being thorough with edge cases. Early on, I saw ordinary algorithm questions alongside an AI-assisted, repo-based coding task. I could usually find the central DSA idea, but I did not get all the edge cases right or leave enough time to debug. The later rounds kept the same theme, with coding problems at different levels and behavioral moments mixe…
Interview experiences · Amazon Advertising
Software Engineer interview at Amazon Advertising: interview experience
The process had three stages and placed Amazon leadership principles alongside coding. I did not complete the first stage. It began with two coding questions under set time limits and then moved to a workstyle assessment. The later format, as I understood it from the process, involved one or two technical rounds with DSA-heavy problems and leadership-principle prompts throughout. In my own DSA-fo…
Interview experiences · Amazon Advertising
Software Engineer interview at Amazon Advertising: Leadership Principles
The process covered several technical levels, bar-raiser-style evaluation, and a program-manager round. Expectations were communicated clearly, and Amazon Leadership Principles were central even during technical discussions, where impact and ownership still mattered. The full process took nearly a week in business-day terms. I did not receive an offer, but the structure stayed consistent enough t…
Interview experiences · Amazon
Software Engineer interview at Amazon Development Center U.S.: interview experience
The loop had several distinct themes, and it was clear what each interviewer was assessing. Multiple technical rounds began with troubleshooting and GenAI fluency, then moved into coding problem-solving and the DSA-style reasoning Amazon looks for. Later rounds became more behavioral and principle-based. A hiring-manager-style discussion covered earning trust, learning curiosity, and operational…
Interview experiences · Amazon DSP
Software Engineer interview at Amazon DSP: four DSA rounds
I went through four rounds that mixed DSA and behavioral evaluation. The first included two medium-hard questions with DP and graph themes, plus project discussion. The second had two easier-medium DP and string questions with more behavioral material. The third included one easy sliding-window-style problem. Although I felt some answers were reasonable, I did not make it past the earlier cutoff.…
Interview experiences · Amazon DSP
Software Engineer interview at Amazon DSP: interview experience
I had four interview rounds, each about an hour long, with people from different countries. The sessions were respectful and organized, mixing technical material with behavioral evaluation. Amazon Leadership Principles were central, and I needed concrete examples rather than general statements. The loop included several DSA-focused rounds with leadership-principle questions throughout. There was…
Interview experiences · Amazon DSP
Software Engineer interview at Amazon DSP: principle-driven loop
My interview flow started with a recruiter screen, then an online assessment and technical interviews. Coding and behavioral evaluation were tied closely to Amazon Leadership Principles, particularly how I described ownership, impact, and decisions. GenAI concepts also appeared. The process was organized and serious, but I did not receive an offer. I understood the material, yet I could not turn…
Interview experiences · Amazon
Software Engineer interview at Amazon: leadership narrative challenge
My three-round loop had two DSA rounds and a Leadership Principles round. The first DSA round included two medium LeetCode questions. The second had one medium and one hard question involving DP and graphs. The Leadership Principles interview was harder for me than DSA because it required a convincing narrative about how I would operate under Amazon's values. I did not receive an offer. The proce…
Interview experiences · Amazon
Software Engineer interview at Amazon: networking follow-ups
A phone screen began with my current experience and projects, then each response drew deeper questions. I used STAR structure for behavioral answers as the interviewer pressed past surface-level descriptions. Technical discussion covered TCP/IP and routing topics, including OSPF and BGP. It was an engaging but difficult conversation because of the depth expected in both storytelling and networkin…
Interview experiences · Anaplan
Software Engineer interview at Anaplan: collaborative pair programming
I began with a recruiter introduction to align on expectations and discuss my background. Technical conversations then went deeply into projects I had actually worked on rather than trying to catch me with gotcha questions. In pair programming, I debugged and coded collaboratively, with attention to how I approached problems. I later presented a system to the hiring manager and discussed tradeoff…
Interview experiences · & General Intuition
Software Engineer interview at & General Intuition
I went from an HR conversation into a LeetCode-style debugging exercise through an external recruiter. After I passed it, I spoke with HR again before a problem-solving-heavy onsite. The onsite included a customer-facing problem, two coding challenges, and a final leads chat about culture, motivation, how I think, and the role I wanted to grow into. I was constantly on, and the customer discussio…
Interview experiences · Arch Global Services Philippines
Software Engineer interview at Arch Global Services Philippines: prolonged silence
The hardest part was the disorganized communication after I invested time. In one assessment flow I did not advance but at least received a rejection email. In others, I completed interviews or assessments and then heard nothing when I expected scheduling or status updates. Gaps between rounds reached three to four weeks, and after a final round the silence lasted months without feedback or an of…