READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 40 of 153
Interview experiences · Boeing
Boeing Frontend Engineer interview, Korean and English technical sessions
My interview was split into two technical segments with different interviewers. First, I had a 30-minute technical interview in Korean with three engineers. Then I had another 30-minute technical session in English with two hiring managers. The overall atmosphere felt comfortable, and the technical questions were mostly based on what I'd put on my resume. Because the questions were tied closely t…
Interview experiences · Boeing
Boeing Software Engineer interview: a recruiter call followed by an offer
After I applied online, a recruiter called me out of the blue, and that call ended up being the interview. It was surprisingly relaxed. I talked through my resume, and it felt more like a conversation than an interrogation. I didn't have to jump through many hoops or sit through multiple rounds, which made the whole thing feel low stress. The recruiter's questions stayed focused on my background…
Interview experiences · Boeing
Boeing Software Engineer interview: cognitive tasks, phone screen, and panel interview
The process began with screens that didn't feel like a traditional back-and-forth interview. First, there was an online section with cognitive-style tasks such as mental math and matching objects. I then had a phone screen with real people, where the questions focused more on my background and fit. After that, I had a panel-style virtual interview with several team members. The format was consist…
Interview experiences · Boeing
Boeing Software Engineer interview: C++17, concurrency, and architecture
I entered the process through an in-person recruiting event where I met the hiring manager. The next step was an online assessment that felt similar to HackerRank. One problem asked me to work with a decimal-to-binary print format. After that, I had an hour-long interview over Zoom. The Zoom session started with questions about my resume and background. The rest of the hour became a slide-deck di…
Interview experiences · Boeing
Boeing Software Engineer interview: waiting for the technical round
My first interview for the role went well, and I was told I would move on to a technical interview. I spent time trying to understand what Boeing usually asks in that round because the first conversation gave me little detail about the format beyond the expectation that it would be technical. Although I felt good about how the initial call went, the uncertainty about what would come next stayed w…
Interview experiences · Boeing
Boeing Software Engineer interview with a one-hour behavioral panel
Recruiter outreach led to a virtual interview with several hiring managers. The conversation was heavily behavioral and lasted about an hour. They asked about my background, what I'd done before, and how my experience could benefit the company. I was repeatedly asked to explain my past work clearly instead of simply naming projects. It started with the usual "tell me about yourself" question, the…
Interview experiences · Boeing
Boeing Software Engineer interview with HackerRank and panel rounds
I went through a fairly standard entry-level process that began with a recruiter conversation and moved quickly into a technical assessment. We discussed the role and reviewed my resume, and the recruiter explained what the process would look like. About a week later, I had a screen that combined behavioral prompts with a coding component. The technical assessment used a HackerRank-style platform…
Interview experiences · Boeing
Boeing Systems Engineer interview, depth and clarity questions
The interview went really well for me and stayed grounded in solid technical questions. They probed depth and clarity instead of testing for buzzwords, and the interviewer understood the underlying details well enough to make the conversation engaging rather than checklist-like. What stood out was that the discussion was genuinely challenging but fair. I was pushed to explain the "why," not just…
Interview experiences · Boeing
Boeing Systems Engineer interview with STAR questions and coding
I went through two rounds focused on how I worked with other people. Most questions used STAR-style answers as the structure. The hiring managers and team leads asked how I collaborate and handle difficult situations, with a few technical questions mixed in. I came prepared to discuss my projects and felt that my communication could carry me, but the technical portion still affected how the round…
Interview experiences · Booking
Booking Software Engineer Interview Experience — Priceline Canada Screen with AI and Java
One hour. It started with a conversation about my background and previous work experience, followed by AI-related questions: how I normally use AI tools, how I would design AI into a real workflow, how I would plan an AI workflow, and how to use and prompt an AI agent, including skills, hooks, and similar things. The coding portion used Java. The interviewer provided template code first. The firs…
Interview experiences · Bosch
Bosch Software Engineer interview: missed response date after a technical interview
HR approached me and scheduled a technical interview with several people involved. Afterward, I was told I would hear back by a particular date. That date passed without the promised response, and the delay is what made the experience negative for me. I did not hear the outcome I had hoped for. More than that, I was frustrated by the lack of a proper reply. Waiting without clarity is hard enough,…
Interview experiences · Bosch
Bosch Software Engineer interview: technical, manager, and HR rounds in one week
My process moved surprisingly quickly. After a recruiter call, I had three interviews: a technical round, a manager round, and an HR round. The whole process took about a week, which was faster than I expected. The manager interview was entirely in English with a senior person from Europe. That made language and direct communication feel important. The interviews were reasonably paced and organiz…
Interview experiences · Box
Box Account Executive final presentation process
I interviewed for the Account Executive role at Box and went through a fairly standard process over a few rounds. The difficulty felt moderate, although the experience varied between feeling supported and wanting more clarity. The process included a recruiter screen about my background and fit for the role. There was also a virtual manager or hiring manager interview. In some accounts, that conve…
Interview experiences · Box
Box Account Executive interview with delayed updates and limited feedback
I interviewed for an Account Executive role at Box. The process felt average to poor in terms of coordination, with delays and weak feedback that made it harder to stay confident and prepared. The recruiter screen included conversations that either went fine at first or failed to meet the expectations that had been set. The hiring manager and next-round interviews were virtual, and urgent request…
Interview experiences · Box
Box Frontend Engineer interview: unclear final coding feedback
The interviews were technically focused, but the final coding conversations soured the process for me. After the earlier rounds went smoothly, I reached a final coding interview where the interviewer couldn’t explain the questions or feedback clearly. It was hard to stay focused on implementing the solution because I kept feeling like the target was moving while I worked. The feedback afterward m…
Interview experiences · Box
Box Senior Software Engineer Interview Experience — Aced Five Rounds, Failed on the Resume Deep-Dive
A recruiter reached out to me about a Senior SDE position — half development, half DevOps. I didn't have DevOps experience, but I said yes anyway. Round 1 was the technical phone screen, the classic four questions. The interviewer laughed and admitted the questions hadn't changed in years. A system has failed and you can only SSH in to check the logs. The log file is huge — what do you do? Answer…
Interview experiences · Box
Box Software Engineer interview: React todo list and full-stack tasks
My early Box process felt smooth and organized. I started with a recruiter screening where I introduced myself, walked through my job history, and shared my expectations for the role. The recruiter was understanding and helpful, and answered my questions as they came up. The technical part moved into practical frontend work. I fixed a dropdown implementation on the frontend and then built a simpl…
Interview experiences · Box
Box Software Engineer interview that grew to seven rounds
The process started out promising and turned into a long endurance test. I went through several rounds with a professional, easy-to-talk-to interview team. Around the middle of the process, I was told that I had cleared everything. The hiring timeline kept stretching after that. I then entered a "cooling-off" period of about four weeks with no communication. Just when I thought the process was ov…
Interview experiences · Box
Box Software Engineer interview with a two-hour technical screen and LLD round
My Box Software Engineer interview felt like a classic LeetCode-style process, with more emphasis on data structures than algorithms. The first technical screen lasted about two hours. The interviewer joined at the beginning and again at the end just to discuss the results. The next coding and DSA round took about an hour, with the interviewer on the call the entire time. After that, there was a…
Interview experiences · Box
Box Software Engineer interview with delayed final rounds and rejection
My experience started with a lot of momentum and then collapsed into confusion. After I applied, I completed three one-hour interviews covering coding, data structures, and system design. The recruiter's feedback was very positive, and I was described as the top candidate. I was asked to wait while the team looked for the right fit across several teams. That's when things became unclear. After I…
Interview experiences · Box
Box Solutions Engineer interview: manager conversation with little room to respond
The process had a disappointing start. The first round was a conversation with a manager, but the interviewer was so quiet that it didn't feel like a dialogue. I didn't get much chance to explain my experience before the call moved on. From my perspective, it wasn't a serious evaluation of fit or skills. I felt as though I wasn't allowed to contribute, and I didn't move forward afterward. What I…
Interview experiences · Brex
Brex Account Executive interview: timed prospecting and discovery role-play
I went through a recruiter screen first, followed by conversations with managers and a panel-style component. The process felt fairly standard for sales, with a clear sequence from one step to the next. The recruiting team communicated well, and the overall tone was professional. The people I spoke with were generally nice. The more intense part was the live sales work. I completed a timed, scena…
Interview experiences · Brex
Brex Account Executive interview with mock cold-call rounds
My process with Brex didn’t feel smooth, even though it started in a fairly normal way. I went through the usual early screening setup, but the scheduling and follow-through immediately gave me a strange feeling. One calendar invite was outside the availability I’d provided. When I asked questions beforehand, they were mostly brushed off. On the day of the interview, the interviewer was late and…
Interview experiences · Brex
Brex Frontend Engineer interview with interrupted live coding
I started with an interview that felt straightforward and respectful, and the recruiter seemed involved and supportive. Then I moved into a technical coding interview where the interviewer repeatedly required me to talk while coding. I found that counterproductive. The constant interruptions made it easy to lose focus and added anxiety to an already stressful live coding environment. I was trying…