READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 13 of 153
Interview experiences · Airbus Americas
Airbus Americas Software Engineer interview: bilingual fit discussion
One session combined HR and a developer in the same block. The questions were general, with no technical assessment, and the conversation switched languages: French first, then English. The wait afterward stretched for a long time, which I assumed was connected to security and background checks. Earlier in the process, I had another interview that was more relaxed and discussion-based. It did not…
Interview experiences · Airbus Americas
Airbus Americas Software Engineer interview experience: verbal coding to AI and HR
I began with a proctored online screen where I was given a coding question and had to answer verbally instead of writing code. It was a strange setup because it seemed to assess how I explained my thinking, not what I could put on the screen. For the next rounds, I went to the Airbus office. The second and third were fairly light and focused on my projects, what I knew about Skywise and Airbus, a…
Interview experiences · Airbus Group
Airbus Group Software Engineer HireVue and manager interview
The process started with a HireVue interview, which was unfamiliar to me. I recorded responses to questions with only a short preparation window before the camera started. It was fully automated, with no conversation partner, and that lack of interaction felt destabilizing. After I completed it, the next step was a manager interview if HR validated me. The flow was simple: recorded screening, HR…
Interview experiences · Airbus Group
Airbus Group Software Engineer interview experience: verbal coding and AI round
My proctored online screen felt unusual. It included a coding question, but I had to answer it verbally rather than write code in the usual way. For a screening round, it was more technical than I expected. A couple of rounds later, I traveled to the Airbus office. The second and third rounds were easier by comparison and focused on my background, the projects I had worked on, and what I knew abo…
Interview experiences · Airbus Group
Airbus Group Software Engineer interview: resume-based fundamentals
The panels worked closely from my resume. I spoke with two interviewers, each responsible for a defined set of questions. Some checked basic knowledge, while others probed the strength of my general engineering understanding. It was not a broad technical coding interview. Instead, the conversation was mostly about walking through my projects and discussing relevant fundamentals to confirm that my…
Interview experiences · Airbus Helicopters
Airbus Helicopters Software Engineer HireVue screening experience
Soon after applying, I completed an automated HireVue-style video interview. I answered predefined questions without a real interviewer in the room. The short preparation window before each recording felt destabilizing, although I had multiple takes for at least some responses, which made it a little less rigid. Once HR validated the video screen, I moved into live conversations with the hiring s…
Interview experiences · Airbus Helicopters
Airbus Helicopters Software Engineer interview experience: verbal screen and Skywise
The proctored online screen was an odd format. I got a coding question but had to explain the answer verbally instead of typing it. After that, I had to go to the Airbus office for the next rounds. The second and third rounds were easier and more relaxed than I expected. They were mostly about my projects and what I knew about Skywise and Airbus, with behavioral questions mixed in. I could talk t…
Interview experiences · Airbus Helicopters
Airbus Helicopters Software Engineer interview: situational flight context
My first contact was an HR style conversation about why I wanted Airbus, why I wanted the role, and why my location choice mattered. There were competency questions too, including a "tell me a time when" prompt. Later I spoke with someone in a manager type role. I was nervous that the discussion would be too technical, but they mostly explained the job and the profile they were looking for. I use…
Interview experiences · Airbus
Airbus Software Engineer HireVue pre-screen and manager interview
After applying, I completed a HireVue-style video pre-screen. I answered prerecorded prompts on camera with only a short window to prepare. With no actual conversation, just the clock, it felt a little destabilizing. After HR validated me, I spoke with the hiring manager. The live part was a discussion of relevant experience and how my background fit the role. The technical side was tied to the e…
Interview experiences · Airbus
Airbus Software Engineer interview: CV-led technical process
The early interviews were tied closely to my CV. The first technical conversation covered my background and fundamentals. A follow-up included Python and algorithms before going deeper into projects I had listed, and the last HR discussion asked about strengths and weaknesses. I was not asked to code live, but I had to explain my background in detail. The panel divided the questions so that each…
Interview experiences · AIRBUS U.S. Space & Defense
AIRBUS U.S. Space & Defense Software Engineer HireVue interview
My first step was an automated HireVue stage. I recorded answers to preset prompts with a short preparation window before the camera started. With only a prompt and timer instead of a person, it was unnerving. Some responses allowed retakes, which made the exercise feel focused on wording and structure. After getting through the video interview, I had a traditional conversation with the hiring ma…
Interview experiences · Airtable
Airtable Customer Success Engineer interview: scripted questions and unclear system prompts
The process started well. The recruiter seemed organized, and I was excited about the opportunity. Once I reached the interviews, though, it became difficult to take the process seriously. In one session, I was put on hold immediately. The recruiter then read questions from a script without much back and forth, and I didn't feel the interviewer was genuinely engaged with my background. The hiring…
Interview experiences · Airtable
Airtable Full Stack Engineer interview: UI flow and hierarchical data
I went through a longer interview loop that started with an online assessment and then moved quickly to a phone interview. The phone screen used an Airtable-style scenario. That set the tone for the live coding portion, where the questions were meant to feel realistic and the follow-ups focused on explaining my choices, not just producing working code. After that, I had several technical intervie…
Interview experiences · Airtable
Airtable Software Engineer Interview Experience — Weak BQ, a Dispatcher Coding Round, and a Fast Rejection
Onsite. The rest of the loop covered questions that have already been discussed elsewhere, so I won't go over them again in detail. The behavioral question round was the usual boilerplate. I hadn't prepared for it, and I also didn't click with the hiring manager, so I answered pretty badly — I'm guessing this is where I get rejected. One of their signature questions: they push an inclusive cultur…
Interview experiences · Airtable
Airtable Software Engineer interview: five-hour assignment and six-interview onsite
I started with a long independent programming assignment instead of a typical phone screen or live challenge. It took around five hours, and I received a $200 gift card regardless of how it went. The next step was an onsite in San Francisco with six interviews in one long day. The mix stood out right away. One interview focused on practical algorithms and design rather than the usual LeetCode sty…
Interview experiences · Airtable
Airtable Software Engineer interview: six-hour coding exercise and $200 certificate
I applied online and heard back quickly about a recruiter call, but the tone felt scripted and quota driven. It seemed like the person on the other end wasn't closely involved with the team or the role. The next step was a six-hour coding exercise before I had spoken with anyone from the actual team. I was told I'd receive a $200 Amazon gift certificate for completing it, but the exercise didn't…
Interview experiences · Airtable
Airtable Software Engineer interview: spreadsheet-style workflow screen
My first real step was a recruiter and phone screen combination. The recruiter was responsive and easy to follow, and the phone interview itself felt conversational. The follow-up questions seemed intended to understand how I thought rather than check whether I could recite a familiar pattern. The topic involved an Airtable spreadsheet-style feature. The recruiter had warned me that it wouldn't b…
Interview experiences · Airtable
Airtable Software Engineer interview with a sharp system design ramp
I started with an online assessment whose questions felt close to the kind of work Airtable actually does. After submitting it, I moved into a coding round focused again on data structures and algorithms, though it was framed more like a real-world task than pure LeetCode. The time limits and scoring varied, but the expectation stayed consistent: write clean code, handle edge cases, and make it w…
Interview experiences · Airtable
Airtable Software Engineer interview with live-coding trick questions
Recruiter outreach started the process, and the early conversation felt more like pressure to apply than an authentic screen. I then had a technical phone screen that felt like a live-coding trick problem. It seemed less focused on my actual experience and more focused on whether I noticed a specific inefficient behavior or used a particular "special term" they wanted to hear. The experience felt…
Interview experiences · Airtable
Airtable Software Engineer take-home assignment that took roughly eight hours
My recruiter call was followed by a take-home assignment that was supposed to take about four hours. The work didn’t feel close to that scope. I was expected to build a fairly substantial front-end library from scratch to support a complicated chart, something in the neighborhood of d3-style functionality. I spent roughly eight hours on it and still didn’t finish. After submitting it, I never rea…
Interview experiences · Airtable
Airtable Software Engineer take-home that took six hours or more
My process began with a call with a hiring manager, followed by a take-home assignment that took a very long time, six hours or more. After that, I went through an onsite that lasted six hours and included multiple rounds. There were coding and algorithm questions, design questions, a code review, and a culture-fit conversation with the hiring manager. The process felt manageable at first because…
Interview experiences · Airtable
Airtable Staff Software Engineer Interview Experience — Undo/Redo Design Round Plus a HyperAgent Take-Home
I was picked by the recruiter for the product omni team, working on Airtable's vibe coding agent. Airtable recently acquired DeepSky to build HyperAgent, and there are plans to connect it with Airtable itself, so it's basically multi-agent development (HyperAgent -> Omni). Recruiter call - 30 minutes, phone screen: why Airtable, what project I wanted to work on, my relevant past experience. Codin…
Interview experiences · airtel
airtel Account Executive interview: Noida round and HR coordination gaps
I began with an in-person first round at the Noida office, where everyone I encountered came across as unprofessional. HR then went silent for about two weeks. When communication resumed, the HR contact said she remembered me and tried to place me in an HRBP round that same day. I already had an interview scheduled in Gurgaon, and she told me to finish it and then go straight to their Gurgaon off…
Interview experiences · Airtel Digital
Airtel Digital Account Executive interview: stalled communication and uncertainty
The hardest part of this process was not technical difficulty. It was the gaps in communication and stalled updates. I went through long stretches without clear feedback and had to follow up repeatedly just to get a response. That made the timeline feel drawn out even though the interview rounds themselves were not described as especially complex. My schedule also shifted around an in-person HR-r…