Real, anonymous reports from people who interviewed for Software Engineer at United Airlines, newest first and distilled into what to expect across the loop.
I went through a campus placement interview that felt pretty straightforward. I started with a deep dive into my resume, and the technical portion leaned toward simpler DSA rather than anything mind-bending. Most of what I discussed was tied back to my projects, with follow-ups about how I built things and why I made certain choices.
My interview leaned medium in difficulty and ran on a compact technical format. I was asked two moderate DSA questions—one focused on arrays and the other on trees—and the interviewer stayed friendly the whole time.
The interview process typically includes multiple rounds, often starting with a technical screening followed by coding and managerial discussions. Candidates reported varying experiences with delays and communication issues between rounds.
Candidates faced a mix of technical questions, primarily focused on data structures and algorithms, with some also delving into system design and backend topics. The difficulty varied, but many emphasized the need for a deep understanding of concepts rather than surface-level knowledge.
Behavioral questions were common, often using the STAR method to assess candidates' experiences and thought processes. Interviewers frequently focused on candidates' projects, asking for detailed explanations of their contributions and decisions.
The overall tone of interviews varied, with some candidates describing a friendly and constructive atmosphere, while others noted negative experiences due to poor communication and perceived disinterest from interviewers. This impacted their overall impression of the process.
Many candidates expressed frustration with the lack of timely feedback and closure after interviews, which contributed to uncertainty and anxiety about their performance and the outcome of the process.
Candidates recommended preparing for both technical and behavioral aspects of the interview, emphasizing the importance of articulating past experiences and technical knowledge clearly. Some wished they had practiced more on specific technical topics or project details.
