An applied AI Interview Experiences

7 results

• AA

  An applied AI Software Engineer Interview Experience: clear recruiter handoff to hiring managerAn applied AI · Software Engineer · HR Screen · Aug 2026

  In progress

  The process for the Software Engineer role began with a straightforward recruiter screen. It was easy and focused on my background and whether I seemed like a fit. The communication was clear about what would come next. I then scheduled a hiring-manager round. The flow felt organized and respectful, and the timeline and coordination were timely. I appreciated that the recruiter explained the purp…

• AA

  An applied AI Software Engineer Interview Experience: Invitation promised, then rejection emailAn applied AI · Software Engineer · HR Screen · Aug 2026

  Rejected

  A recruiter told me I was moving forward and that an invitation for the first interview was coming. Before that, they sent questions in advance, and I answered everything. As far as I knew, none of those responses was a problem. The process then ended with a rejection email that gave no explanation or feedback. That lack of communication was the hardest part, especially because I had been told to…

• AA

  An applied AI Software Engineer interview: hostile and confusing interview conductAn applied AI · Software Engineer · HR Screen · Jul 2026

  The process began with an HR-style call and then technical and bar-raiser-style conversations, but it quickly felt hostile and disorganized. Interviewers would not turn on their cameras and resisted when I asked to see them. Two people in one meeting space had similar accents, which made it genuinely hard to tell who was speaking. In other rounds, people did not seem to listen closely and sometim…

• AA

  An applied AI Software Engineer interview: rushed EV charging design discussionAn applied AI · Software Engineer · Technical Screen · Jul 2026

  I got pulled into a Karat-driven stage that felt chaotic and rushed from the start. It was split evenly between system design and a DSA problem-solving block. I was asked to design an EV charging-station app that could find the nearest station and handle payments, and I was pushed to move quickly. The conversation barely felt like a design discussion. I spent a lot of time on basic whiteboard too…

• AA

  An applied AI Software Engineer interview: TCP, TLS, and system designAn applied AI · Software Engineer · Technical Screen · Jul 2026

  Offer

  I started with a deep technical round that gradually broadened into leadership-oriented conversations. The first round covered middleware and networking fundamentals, including TCP, TLS, certificates, and how an F5 Big-IP device is upgraded and configured. It was detailed enough that I needed to be precise, but I could answer most questions and keep the discussion moving. The next stage was a tec…

• AA

  An applied AI Software Engineer interview: technical, manager, and bar-raiser roundsAn applied AI · Software Engineer · Technical Screen · Jul 2026

  The process felt high-stakes and had two technical rounds, a managerial round, and a bar-raiser-style discussion. It opened with a coding round that could eliminate me. Once I finished it, the remaining stages came quickly. After a short gap of a couple of days, I completed the next rounds in a single day. The pace left little time to decompress, and I had to stay sharp across different formats.…

• AA

  An applied AI Software Engineer interview: unclear live coding expectationsAn applied AI · Software Engineer · Technical Screen · Jul 2026

  The initial screening felt normal, but the technical interview did not. I was given LeetCode-style questions, and the interviewer's behavior made the situation tense. They did not want to explain the question and expected a fully running solution while I was answering. That mismatch between the communication and the expectation put me under stress and did not feel supportive. I did not move forwa…