READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 35 of 153
Interview experiences · ASML
ASML Software Engineer interview through Microsoft Teams with two interviewers
My interview was concise and conducted online through Microsoft Teams. I spoke with two people who assessed my knowledge and problem-solving while also asking about my background. The questions seemed intended to clarify how I think rather than test whether I could recall concepts from memory. I was comfortable explaining my experience, and the pacing stayed natural. I didn’t get the role, but th…
Interview experiences · ASML
ASML Software Engineer interview, transactional recruiter screening
My biggest frustration came before I reached any technical depth. The recruiter interactions were my first real signal, and they didn't feel aligned with what the role actually required. In our conversations, the recruiters seemed more focused on ticking boxes and pushing me to name a salary than on understanding my background or motivation. One screening call felt especially transactional. It se…
Interview experiences · ASTEK
ASTEK Software Engineer interview: short, flexible, and responsive
The process felt very smooth and fairly short. Once I had been contacted and scheduled, I moved through the steps without waiting for weeks. I felt the team concentrated on the substance: getting to know me and seeing whether my profile fit the role. Their willingness to work around scheduling constraints also stood out. I did not feel there were an excessive number of stages. Communication was r…
Interview experiences · AstraZeneca
AstraZeneca Research Scientist interview: five rounds in China
I went through a structured five-round process. It started with a recruiter screen with HR, conducted in Chinese because the role was based in China. About a week later, I had an informal 30-minute conversation with the hiring manager that felt more like a chat than an interrogation. The next panel round had me present a past project and answer questions from people who seemed to represent my pot…
Interview experiences · AT&T
AT&T Account Executive interview: late arrivals and silence after extra step
The recruiter joined my screen about 15 minutes late. When the interview began, other people were gathered around the recruiter’s desk watching, which made me uncomfortable. The main portion was a long run of behavioral questions. I could answer them, but I did not get much clarity about the role or company, and some of my questions went unanswered. I was told I had advanced to a final interview,…
Interview experiences · AT&T
AT&T Account Executive interview: objections, cold calling, and customer recruiting
The process opened with a straightforward recruiter-style conversation, but the questions quickly turned to how I had handled work situations. One main prompt asked about my best and worst scenarios. I had to explain what happened, how I got there, and what I did to work through the challenge. I then had a short, structured set of interviews centered on sales fundamentals. We discussed overcoming…
Interview experiences · AT&T
AT&T Account Executive interview: third-party calls after withdrawal
This experience was less about interviews than about how my information seemed to be used. I stepped away from an earlier interview after accepting a better offer elsewhere, then kept receiving calls from third parties claiming to work with AT&T and trying to schedule another interview. It eventually seemed that my number had been shared or surfaced somewhere it should not have been. That made th…
Interview experiences · AT&T
AT&T Software Engineer interview: a three-hour HackerRank and project code review
After applying, I took a HackerRank assessment that lasted around three hours and felt aligned with LeetCode-style medium problems. When I finished, a recruiter called to invite me to the next step. The process stayed technical and became more role specific. The next round focused more on building and explaining work I had done. I walked through a Java and Spring Boot project and had a code-revie…
Interview experiences · AtkinsRéalis
AtkinsRéalis Software Engineer interview
The interview itself was structurally simple, but the silence afterward was what I remembered. There was no rejection email or recruiter call after the interview, only no response, which made it difficult to know where I stood. The conversation was okay and relied heavily on examples from past experience. The interviewer used many prompts tied to ICE-style attributes, including repeated "tell me…
Interview experiences · AtkinsRéalis
AtkinsRéalis Software Engineer interview: reasoning through two open questions
The interview used two longer, open-ended questions. I had about five minutes to think about each one before presenting an answer and walking through my reasoning. I was surprised that being logical mattered more than landing on a single correct answer. The interviewer paid attention to how I organized my thoughts, explained tradeoffs, and stayed coherent under time pressure. It was challenging b…
Interview experiences · Atlas Copco Group
Atlas Copco Group Software Engineer interview: aptitude, group discussion, and elimination
I began with a moderate online assessment full of aptitude puzzles and game-like questions. Time felt tighter than I expected, but I was selected to continue. The next day brought a group discussion and interview at a campus event. Moving directly from one to the other made it hard to settle in, and only a small number of people were advancing. I was rejected during that elimination-style sequenc…
Interview experiences · Atlas Copco Group
Atlas Copco Group Software Engineer interview: remote assessments and presentation
I first spoke with a recruiter about my background and expectations. About a week later, I began the main stage remotely and completed lengthy aptitude assessments before the technical portion. I thought the assessments could have been shorter, but the interviewer was pleasant and the process moved smoothly. The second stage also stayed remote, which spared me a long return trip for an in-person…
Interview experiences · Atlassian
Atlassian Account Executive interview: five-week plan stretched to eight weeks
A recruiter told me the process would be structured, about five weeks long, with at least four or five interviews and a required presentation. Scheduling was the part that threw me off. My interview times kept being rescheduled, and while I understood that things change, it kept pushing the calendar. End to end, the process took about eight weeks instead of the original expectation. The loop soun…
Interview experiences · Atlassian
Atlassian Senior Software Engineer Interview Experience — Shortest Unique Substrings for UI Shortcuts
In a Web UI dropdown, users needed help quickly memorizing keyboard shortcuts. For every string in an input list, find its shortest unique substring and wrap that substring with the tags <u> and </u>. Implement a function that performs this transformation. The detailed requirements were: Uniqueness: The chosen substring must not appear anywhere as a substring of any other string in the input list…
Interview experiences · Atlassian
Atlassian Software Engineer interview: AI-assisted password bug fix
After a recruiter screen, I had a hands-on technical interview built around AI-assisted coding. I was given a small backend-style website with a real bug and had to find and fix it while using an AI coding agent. In my case, the problem was in the password functionality, so I had to understand the existing logic, make the correct change, and stay consistent as I worked. What threw me off was the…
Interview experiences · Atlassian
Atlassian Software Engineer Interview Experience — Passed a Coding Round I'd Seen Before, Then Walked Away
I was contacted on LinkedIn. At the time I was already interviewing with several other companies at once, but I replied anyway to give it a shot. I passed the phone screen, then scheduled the onsite (VO) with the recruiter. Their onsite can be split across several days — day one is coding. If you fail the coding round, they don't move you on to system design. The first coding round was actually a…
Interview experiences · Atlassian
Atlassian Staff Software Engineer Interview Experience — Music Player Design and Product Discussions
The author describes interviewing for an ML/AI product engineering role with BCNY, a small company acquired by Atlassian, and cautions that this team’s process may differ. A phone screen used a music-player exercise to assess object-oriented design and communication, including playback controls, queuing, repeat behavior, and shuffled playlists. Onsite discussions included designing comments for a…
Interview experiences · Atos
Atos Consultant interview: brief meetings without closure
The process initially seemed structured. I had a quick HR call with generic questions and a short explanation of expectations, then a fast interview with someone from the team that covered the basics. After that, the momentum disappeared. I waited without clear updates, useful progress feedback, or closure from recruiting while the role seemed to keep circulating. The interviews themselves were b…
Interview experiences · Atos
Atos Consultant interview: three-stage stakeholder process
I began with a recruiter screening and then a three-stage process in which each conversation seemed to build on the last. The early conversation covered my experience, what I wanted to do next, and how I handled stakeholder management and delivery as a consultant. The recruiters and interviewers were friendly and professional, and the process was easy to follow. Next, I completed a technical chal…
Interview experiences · Atos
Atos Software Engineer interview: recruiter silence after assessment
After an initial recruiter contact, the process stalled in a way that stayed with me. The recruiter asked me to complete a form on a messy website, then called without warning. The call itself felt uncomfortable because she repeatedly laughed about my Polish accent. She said she would forward my CV to the hiring manager and keep me updated. I heard nothing. I followed up about a week later and re…
Interview experiences · Attentive
Attentive New Grad Software Engineer Interview Experience — Coding and System Design Blended Into One 75-Minute Screen
It was 75 minutes long. They said it would be coding + system design, but in practice the two were mixed together, and the questions were pretty scattered and casual. The last 5 minutes were reverse behavioral questions, where I got to ask them things. The problem wasn't quite like a LeetCode problem — they didn't clearly spell out what the input was. They wanted me to design it myself and then j…
Interview experiences · Attentive
Attentive New Grad Software Engineer Interview Experience — Nailed Every Round, Still Rejected
This was the last round — three interviews back to back: coding + debug + HM. Coding: the interviewer had a straight face the whole time. Gave me LeetCode 1209, first simplified k down to k=3, and I solved it fast — covered edge cases and asked all the clarifying questions. The interviewer saw there was a lot of time left and started following up: first asked how to change it back from 3 to gener…
Interview experiences · Attentive
Attentive Software Engineer Interview Experience: dismissive managerial conversation
After a recruiter screening, I had a managerial round. I received the job description, but the details about the structure and expectations turned out to be wrong. Before the questions even began, the interaction felt uncomfortable because the tone did not feel respectful. The conversation came across as skeptical and dismissive. My answers were treated as though they had been discounted from the…
Interview experiences · Attentive
Attentive Software Engineer Interview Experience — Leveled Up to Senior Bar, Rejected After a Messy System Design
I applied for SWE II. HR call - 2026-08-26 The questions were: How much do you know about Attentive? Are you actively interviewing right now? Do you have any offer deadlines? Do you need sponsorship? What are the compensation range you are targeting? Then they asked me to introduce myself. Are you able to talk about a feature or product that you work on like end-to-end or a zero-to-one product? W…