READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 37 of 153
Interview experiences · Avanade
Avanade Software Engineer interview: 48-hour assignment review
I began with an introductory session and then had online technical and HR interviews. The technical conversation covered team leadership, projects I had delivered, and work at previous companies. I then received an assignment with 48 hours to complete it. After I submitted it, I spoke quickly with the hiring manager about my solution and why I made those choices. I received an offer. The path fro…
Interview experiences · Avanade
Avanade Software Engineer interview: brief HR and technical steps
After a recruiter chat, I had a technical conversation about a week later with the hiring manager’s area leader. It was mostly technical and lasted about half an hour. I also had a brief HR conversation, around fifteen minutes, about me, my career context, and general personal background. That part was relaxed. The process was calm and easy to follow, with the main shift being from personal HR qu…
Interview experiences · Axon
Axon Senior Software Engineer Interview Experience — Camera Footage Upload Design, Advancing to a Five-Round Onsite
The well-known stun gun company Axon, phone screen. I applied for Senior Engineer I. HR told me the phone screen would already need to happen in San Diego, and only after that would they decide which direction to move me in. The interviewer was a senior engineer, with a newly joined staff engineer shadowing. The question was pretty much the same as other write-ups on this forum — it was about upl…
Interview experiences · Axon
Axon Software Engineer Interview Experience — A Rolling-Window Officer Status Lookup System Design Question
I applied for this position online on a whim and didn't expect to actually land an interview. The company works in public safety. The question was to design a system for looking up an officer's status record near a given point in time. The system continuously receives data from police officers' devices. For each officer, while they're active, their device generates a record every 5 seconds. Each…
Interview experiences · Axon
Axon Software Engineer Interview Experience: a take home system design presentation
The process began with a recruiter conversation about logistics and my background. That was followed by a hiring manager discussion focused on my previous work experience, and that part went very well. I then completed a take home system design deliverable. I submitted a written document and presented the design to two team members. Their follow ups went into deeper detail, so it was not simply a…
Interview experiences · Axon
Axon Software Engineer Interview Experience — Rejected After a Behavioral-Heavy Hiring Manager Screen
I applied on a whim through LinkedIn Jobs. The first round was an HM screen, mostly chit-chat and behavioral questions. It wasn't the hiring manager for the role I actually applied to, but the manager of a larger group — maybe our personalities just didn't click, because I got rejected. Here are the questions I remember: Why did you choose Axon? Walk me through your career path — what's driven yo…
Interview experiences · Axon
Axon Software Engineer Interview Experience — System Design Stumble and a Grueling Behavioral Round
SD: This was about fulfillment center truck routing and container/inventory. I didn't perform well in this round — I started off saying too much fluff about FR/NFR, and the interviewer caught it and challenged me on it, which put me under time pressure. I wasn't very familiar with this problem, since I've never worked on anything fulfillment-related. Looking back, I realized it was basically a si…
Interview experiences · Stripe
Backend Engineer
It was a multipart question. The question was based on string split, slicing, matching and basic checks. Attempting the question in python will really give us the edge instead of using any verbose language like Java. Given multiple strings separated by commas mapped as individual merchant information. First part was to retrieve merchant info from each string and then further parts was to perform…
Interview experiences · BAE Systems
BAE Systems Software Engineer Interview Experience: embedded C/C++ and hardware integration
After a quick application stage, I had a recruiter-style conversation and then a screen that combined behavioral prompts with technical questions. There were about six behavioral questions and fewer technical ones. The atmosphere stayed standard rather than confrontational, and the in-person part took place at Salmesbury. The technical discussion focused on day-to-day embedded and low-level softw…
Interview experiences · BAE Systems
BAE Systems Software Engineer interview experience: timed games and video questions
The main assessment leaned heavily on games and video. I completed HireVue recordings with several recorded questions and additional written prompts. It felt difficult because it tested speed, pattern recognition, and mental math, not just recall. One numeracy game gave me a starting number and a set of operations. I had to choose the pair of numbers that reached a target through addition, subtra…
Interview experiences · BAE Systems
BAE Systems Software Engineer interview: redacted feedback and internal-candidate concern
The process was long and did not feel meritocratic to me. I had an in-person interview with two interviewers and another person remote. They took turns asking STAR questions. It felt like a formality, as though an internal candidate had already been chosen. Recruitment had suggested bringing project examples could help, so I prepared one for a "tell me about a time" question. Although the in-room…
Interview experiences · Bae Systems Usa
Bae Systems Usa Software Engineer interview experience
I had an interview lasting about an hour and fifteen minutes. There were nine questions: six behavioral competency questions and three technical questions tied to the role and job description. The technical section was connected to what they were hiring for, not purely abstract. Near the end, I could ask my own questions, which made it feel like a two-way conversation instead of only an evaluatio…
Interview experiences · Bain &
Bain & Business Analyst Interview Experience: partner-led case studies
The first round mixed a market-sizing case with behavioral questions. The process itself was straightforward in structure and pacing, with multiple interviews in each round and interviewers who kept things moving. In the second round, I completed two more case studies with partner-level interviewers. The partner interviews were much more interviewer-led in a different way. They gave me less struc…
Interview experiences · Bain &
Bain & Consultant Interview Experience: Profit-decline case and behavioral fit
After a recruiter-style HR conversation, I moved into interviews focused on performance as well as conversation. The HR portion lasted about half an hour and covered my background, fit for consulting, why I wanted the role, and working hours. Then I had a manager interview that combined a case drill with behavioral assessment. The case involved analyzing a profit decline and building an improveme…
Interview experiences · Bain &
Bain & Consultant interview: remote cases and in-person day
Once the earlier steps were over, the scheduling moved quickly. I had two case interviews remotely on the same day, which left little time to recover between them. Each case required me to stay structured while adapting to the interviewer's direction. Later I went in person for the next stage. That day included a case interview, a presentation, and a behavioral interview. The mix felt consistent…
Interview experiences · Bain &
Bain & Consultant interview with inconsistent two-person case interview
The beginning felt uncertain and drawn out. After an initial assessment step, I completed an online test and then heard nothing for a while. About five weeks later, I was invited to schedule an interview roughly two weeks out. For case preparation, I received a link to a practice platform. The case interview itself was not smooth or enjoyable. I met with two people who seemed to have different ap…
Interview experiences · Bain Capability Network
Bain Capability Network Consultant interview: quant assessment and chart-heavy cases
Before live interviews, I completed online assessments in quant and general problem solving. They were medium in difficulty and covered critical thinking, numerical reasoning, and data work. Each quiz had a set time limit, so I could not rush it. Once interviews began, the process was straightforward but demanded preparation. Case work required clean execution, and math could slow me down if I wa…
Interview experiences · BairesDev
BairesDev Backend Engineer interview with junior-level expectations and technical lead discussion
I entered the process expecting something aligned with the role, but it quickly felt disrespectful and poorly scoped. During the interview, the recruiter seemed impatient and interrupted my answers, moving to other topics before I could finish. That made it difficult to stay comfortable. Although the job was described as junior, the expectations felt closer to full mastery of advanced technologie…
Interview experiences · BairesDev
BairesDev Frontend Engineer interview with lengthy automated assessments
The process relied heavily on assessments, and it felt endless. Even after I completed the suggested tests successfully, there was no guarantee that I would reach the role. I found the funnel hard to trust, especially because the test materials and knowledge seemed outdated compared with the latest framework versions. Much of the process was machine evaluated. It started with a long block of prob…
Interview experiences · BairesDev
BairesDev Software Engineer automated testing with math and puzzle questions
Most of my time went into automated testing. I spent several hours answering a large set of questions and received no meaningful feedback afterward, which made the experience feel very impersonal. The math section started with easy questions and continued in much the same way. There were also puzzle-style items that felt more like filler than a reliable signal. The tone and relevance threw me off…
Interview experiences · BairesDev
BairesDev Software Engineer interview: approachable interviewers and an easy pace
My experience felt smooth from the start. The interviewers were approachable and friendly, and the conversations had an easy flow. It felt like they were genuinely trying to understand my responses instead of rushing me through scripted checkpoints. I had room to express myself, and the tone made it feel less like an interrogation and more like a real discussion. The questions matched the job I w…
Interview experiences · BairesDev
BairesDev Software Engineer interview: exam submission error and unfinished tasks
My process started promisingly, but I didn't finish everything. I ran into technical problems during the exams, and when I tried to submit what I had completed, the system marked it as an error in the console. I also lost time because of distractions and couldn't complete the remaining activities. Because I couldn't get past the submission issue or finish the full set of tasks, I didn't reach the…
Interview experiences · BairesDev
BairesDev Software Engineer Interview Experience: Approved but placed on a waiting list
The journey had the feel of a complete pipeline: a short video presentation, tests on the company platform, an HR screening, a technical interview with engineering, and another conversation with a team leader. The technical interview focused on technology rather than live coding. Architecture and overall structure came up, but the questions remained general instead of going deep into a specific j…
Interview experiences · BairesDev
BairesDev Software Engineer interview: Python fundamentals and concurrency
My process picked up after I filled out my online profile. I had a short HR screening where the conversation moved between Spanish and English, and then I was scheduled for the technical interview. The technical round was entirely in English and lasted about forty minutes. It surprised me because it focused heavily on open-ended, textbook-style questions about core Python concepts. I was asked ab…