Katkat

real interview stories, told over a cup of tea ♡

Interview Experiences

3935 interview stories from candidates at 857 companies: how each round went, what was asked and how it ended. Every company page links to practice questions in the same style.

3935
Experiences
857
Companies
532
Offers

3935 results

  • EXL Service Philippines Business Analyst interview: extra client roundEXL Service Philippines · Business Analyst · Senior+ · Technical Screen · Jul 2026
    Rejected

    I expected a straightforward process, starting with a hiring-team interview that went well, then further rounds with a VP and what was described as an AVP final step. The earlier conversations covered the same basic hands-on skill that later became an issue, and I felt I had answered it well. After I thought the process was done, recruiting added a client interview. I was eventually rejected on t…

  • Extra System Design Round, Then a Template RejectionOpenAI · Software Engineer · Technical Screen · Jul 2026
    Rejected

    Coding: It was the same as what's in the other interview write-ups, the chatbot that needs a refactor. The only difference was that for every person who is away, whenever someone @s them, the bot just directly replies with the away status. SD: CloudIDE. Maybe the interviewer wasn't very clear on what they wanted either, so I gave them an SSH version, where one person or several people can share a…

  • Facebook Software Engineer interview: BFS matrix task and unfinished technical loopFacebook · Software Engineer · Technical Screen · Jul 2026

    After the recruiter step, I had a coding-centered technical round with two questions in about 45 minutes. One required a normal solution followed by an optimization follow-up, which made the round more demanding than I expected. In the next video-conference interview, the interviewer was very communicative and answered questions as they came up. The coding challenge used BFS: I was given a matrix…

  • Facebook Software Engineer interview: coding loop, system design, and offerFacebook · Software Engineer · Onsite · Jul 2026
    Offer

    A recruiter phone screen led into a classic technical sequence. After the call, I did two back-to-back LeetCode medium coding interviews with engineers. The tone was collaborative and friendly, with emphasis on explaining my thinking, writing good code, and improving my solution in follow-ups rather than being caught out. Later, the onsite had a full-loop structure: two coding sessions with two L…

  • Facebook Software Engineer interview: recruiter screen, LeetCode loop, and no offerFacebook · Software Engineer · Technical Screen · Jul 2026
    Rejected

    After a recruiter contacted me on LinkedIn, I had a scheduled screen about my background and what I wanted from a new role. It was clearly a gate: if the alignment looked right, I would move forward. The technical sequence followed a familiar pattern, starting with a phone screen and then an onsite that mixed coding, behavioral questions, and system design. The coding questions were LeetCode-styl…

  • Facebook Software Engineer interview: two coding questions and onsite loopFacebook · Software Engineer · Technical Screen · Jul 2026

    After a recruiter call, I had a technical screen that began immediately with coding. I answered two LeetCode-style questions and had to communicate clearly as I worked. The questions were heavily Meta-tagged, so targeted preparation mattered more than generic DSA practice. The onsite loop added behavioral, two more coding questions, and system design. The recruiter was accommodating and the proce…

  • Family Dollar Stores Account Executive delayed interview on a very hot dayFamily Dollar Stores · Account Executive · Jul 2026
    Offer

    The process was easy, but it dragged. I kept getting stopped between interviews, and by the time I entered the room it was brutally hot, like walking into a heatwave. The conversation itself was not difficult, but it lasted longer than I expected. I moved through the steps without much friction. The interview was not the hard part. The timing was. Location: Richmond, VA. Overall feedback: Negativ…

  • I had a straightforward sequence: an HR screening, two technical interviews, and a discussion with the hiring manager. Every step felt professional and friendly. The interviewers gave me time to think, which made it easier to stay calm. The technical conversations covered my past experience, the problems I had worked on, and my approach to problem solving. One round returned to resume-based work,…

  • Finacle Consultant interview: agentic frameworks and RAGFinacle · Consultant · Technical Screen · Jul 2026
    Offer

    After a recruiter call, I was scheduled for two technical rounds. They focused on whether I understood agentic frameworks and how I would build RAG pipelines. A couple of basic programming questions kept the conversation practical rather than overly theoretical. The second round returned to day-to-day work. I discussed async and await, microservices, and work I had built at my previous company. T…

  • Finacle Full Stack Engineer interview: unclear scheduling and second-round uncertaintyFinacle · Full Stack Engineer · Technical Screen · Jul 2026

    I found the process messy from the start. It began through job-portal connections with an HR call where the speaker talked so fast that I struggled to take in the details. I filled out a form with my available times, but the interview was scheduled around the interviewer's convenience instead. The technical interview was the one clearly positive part. The interviewer was friendly and professional…

  • Finacle Full Stack Engineer virtual technical interview experienceFinacle · Full Stack Engineer · Technical Screen · Jul 2026

    My interview began with a virtual screening call set up as a timed DSA round of about 30 minutes. Technical questions covered Java, Spring Boot, system design, and my AI experience. They described a next step for selected candidates: an HR manager call to discuss compensation, role, and location before a final offer. They said the offer would be released within a week after that stage and estimat…

  • Finacle Software Engineer interview: campus DSA, SQL, and systems topicsFinacle · Software Engineer · Technical Screen · Jul 2026
    Offer

    I interviewed on campus for about an hour with two interviewers. The first asked me to solve DSA questions using LeetCode and also covered SQL. The second went into dynamic programming, how a database connects to a backend, APIs, microservices, and questions based on my resume, including altered versions of my own coding rounds. I also discussed merge sort, trees, graphs, React, MERN, and HTTP me…

  • Finacle Software Engineer interview: Java, Spring Boot, and reasoningFinacle · Software Engineer · Technical Screen · Jul 2026
    Offer

    The technical discussion focused on Java, Spring Boot, SQL, Azure, and Terraform, then shifted into project-based scenarios. I explained how my project was implemented, the approach I used, and my own contribution. After introducing myself, I worked through a DSA problem by describing a brute-force solution and then an optimized one. The conversation also covered operating systems, OOP, networks,…

  • Financial Analyst interview at Goldman Sachs Asset & Wealth Management: SuperDayGoldman Sachs Asset & Wealth Management · Financial Analyst · Jul 2026
    Offer

    After a resume drop and recruiter call, I completed a one-way video interview. The HireVue felt like a difficult gate, with tougher questions than I expected and advancement that felt uncertain. Later I attended a SuperDay with three back-to-back interviews lasting about 30 to 45 minutes each. Most of the SuperDay questions were behavioral, but they demanded precise, prepared examples and clear f…

  • Financial Analyst interview at J.P. Morgan: HireVue and SuperdayJ.P. Morgan · Financial Analyst · Jul 2026

    I applied with my resume and experience, selected preferred locations, and was then invited to HireVue. About a month later, the next step was a Superday. Before it, I attended a learn-more component with a case-related activity and networking. The networking mattered because people who made connections there seemed to receive attention. The Superday involved short conversations with several inte…

  • Financial Analyst interview at J.P. Morgan: timed HireVueJ.P. Morgan · Financial Analyst · Jul 2026

    After I applied, the first screen was a timed one-way HireVue. I recorded responses to behavioral prompts, with little or no technical content in the versions I saw discussed. Preparation was short and answers were constrained. In my format I had about 90 seconds to respond, while each question could allow roughly two minutes, and there was an option to retry. I preferred to submit a clean first…

  • I had an easy, low-friction start. I spoke with someone by phone, answered a couple of questions, and they set up a more detailed interview within about a week. The process was smooth and welcoming, and the recruiter treated it as a real two-way conversation instead of a checklist. In the interviews, the role and expectations were explained clearly. The team seemed intentional about making sure I…

  • First Quality Laboratory Account Executive interview: long process without closureFirst Quality Laboratory · Account Executive · Jul 2026

    I went through several rounds, assignments, tests, job shadowing, and final interviews. It became longer and more exhausting than I expected. Communication was frequent, but the follow-through did not match the time I was investing. The process felt inconsistent: expectations were presented strictly, yet the candidate experience did not feel equally respectful. After putting in so much time, I wa…

  • First Trust Capital Management Business Analyst month-and-a-half aptitude processFirst Trust Capital Management · Business Analyst · Jul 2026

    The process was structured and took close to a month and a half. The waiting stood out more than the interviews. It began with an aptitude test covering general math, English, and reasoning, followed by a telephonic confirmation and then interviews. The next stages were communicated clearly. One call covered my background and why I wanted the role. A later video interview went deeper into my acad…

  • First Trust Capital Management Financial Analyst interview: practical finance and behavioral fitFirst Trust Capital Management · Financial Analyst · Other · Jul 2026
    Offer

    The process was smooth and low-stress, and the panel made a point of keeping it comfortable. It started with a recruiter screen, then team interviews. I discussed prior experience and roles, along with behavioral questions about strengths and weaknesses, time management, and working under tighter schedules. The technical discussion was practical rather than theoretical. I covered core finance and…

  • Five Onsite Rounds and Feedback for Leaning Too Much on AIHex · Software Engineer · Onsite · Jul 2026

    I just got done with my onsite interview at Hex, so I wanted to contribute this data point. For the full stack track, I went through quite a few rounds: web dev, system design, product taste, behavioral, and a CTO round. The feedback I ended up getting was that the web dev round relied too much on AI... Personally, I think the line for this kind of AI-native interview format is actually pretty ha…

  • FNZ Business Analyst interview: promised offer and lost follow-throughFNZ · Business Analyst · Technical Screen · Jul 2026
    No response

    My experience with FNZ felt less like a clean interview and more like a process that drifted after I had already done the work. I made it through multiple rounds, technical and HR, and the recruiter collected documents and told me that an offer letter would be released. It looked as if things were moving forward. Then communication disappeared. I waited, followed up, and did not get the transpare…

  • Ford Hospital and Research center Software Engineer interview: a long timelineFord Hospital and Research center · Software Engineer · HR Screen · Jul 2026
    Rejected

    The hardest part was the timeline. About three months passed between my application and the rejection email, and the process kept changing as it went. I started with a recruiter discussion and then a brief meeting with the hiring manager. Next came a panel with the hiring manager and two engineers. They later brought me in person for another interview, returned to my resume, and had me solve prob…

  • Forward-Deployed Engineer interview at Palantir: collaborative debuggingPalantir · Forward-Deployed Engineer · Technical Screen · Jul 2026

    After I applied, a recruiter reached out and the process moved quickly into a technical conversation. I expected the recruiter to conduct the early screen, but an engineer joined instead. The exchange felt collaborative: I could ask questions, explain my thinking, and offer different approaches. The technical work was mostly coding and problem solving. One session was a straightforward LeetCode-l…

  • Four-Part Onsite Ending in RejectionVanta · Software Engineer · Onsite · Jul 2026
    Rejected

    I had my onsite (VO) on Monday and Tuesday. Three days later, today, the recruiter just emailed saying they decided to move forward with other candidates who are the best fit for the role. They asked if I wanted to talk through feedback. Overall I felt the interviewers were pretty good — they were responsive. At the start the recruiter gives you a Google doc with a pretty detailed writeup describ…

  • Four-Round Onsite, Rejected After Two AI Coding RoundsMeta · Machine Learning Engineer · Onsite · Jul 2026
    Rejected

    I applied online to a search/ads/recommendation MLE role. The onsite was four rounds in total: behavioral, system design, and two rounds of AI coding. The behavioral round was just everyday questions, and the system design was a recommendation system. For coding, one question was a triple card game and the other was the maximum number of unique characters, both of them questions you can find onli…

  • Four-Round Virtual Onsite, Rejected in Three DaysDoorDash · Software Engineer · Onsite · Jul 2026
    Rejected

    Interview timeline: 6/15/2026 – DoorDash HR reached out on LinkedIn asking about my availability for an interview. 6/23/2026 – DoorDash first VO round, CodeCraft interview. The question was Dasher Pay — there are already write-ups about this problem, both here and elsewhere. There was a follow-up asking how to handle the double pay rate for dashers during peak hours. After I finished the code, th…

  • Fragomen Consultant interview: written assessment and same-day offerFragomen · Consultant · HR Screen · Jul 2026
    Offer

    I began with a friendly HR call about logistics and my background. Soon after, I completed a written assessment with plenty of time, so it felt more like a check than a trap. I then had two interviews with team staff. They were relaxed but role-related, and the interviewers kept even the challenging parts supportive. I felt they were trying to understand how I would work rather than score points.…

  • Full Loop Ending in an AI Search Index System Design I Couldn't AnswerClickup · Software Engineer · Onsite · Jul 2026

    HM round - with an org director. We mostly talked about my own experience, no BQ or anything like that. It felt like they were mainly checking whether the things I've done match what they need. Coding - fairly easy, one of the questions from the forum's interview question bank, the doc edit events one. Project deep dive - talked with an org tech lead about my own experience, and it was mostly abo…

  • Full Onsite Loop with a Claude-Assisted Coding RoundScale AI · Backend Engineer · Onsite · Jul 2026

    I mass-applied for an infra role that sits under the ML research org. The interview process matched what other people have already posted here on the forum. Onsite loop: Task scheduler VO BQ: Standard questions, and it ended early. The highlight was during the time to ask questions back — I asked the interviewer if there was anything she didn't like about Scale AI, and she said that because of RT…