READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 80 of 153
Interview experiences · LinkedIn
LinkedIn Software Engineer Interview Experience — Phone Screen to Full Onsite, Rejected on Code Quality
Applied in a big October application wave. Interviewing for a junior role. Phone screen: 1 hour, and we spent the first 15 minutes just chatting about my resume. Question 1 was a variant of a problem I only had a coded name for — it started with just () parentheses, then the follow-up expanded it to three different types of brackets. We discussed a stack-based approach versus one using a counter,…
Interview experiences · LinkedIn
LinkedIn Software Engineer Interview Experience — Two of Four AI-Coding Tasks Completed
I just received a rejection. The feedback was reportedly that the AI-coding round had four tasks and I had only completed two. I'd like to ask everyone, especially people with experience inside LinkedIn: what exactly is expected in this kind of AI-coding interview? Was I led down the wrong path? First round: System design. Design a system to collect user activity, with queries for the last minute…
Interview experiences · LinkedIn
LinkedIn Software Engineer Interview Experience — Two Optimal Solutions in a 60-Minute Screen
The technical phone screen lasted 60 minutes. There were two interviewers, and both were relaxed and friendly. One was shadowing, while the other led the interview. After a brief introduction, the lead interviewer asked about a project on my resume and went straight into its details. The two coding questions were LeetCode 179, Largest Number, and LeetCode 244, Shortest Word Distance II. For both…
Interview experiences · LinkedIn
LinkedIn Software Engineer Interview: Notification-service design and an accepted offer
About a week after a recruiter call, I had a technical screen that surprised me with its intensity. It ran about 45 minutes and combined behavioral and technical questions. The technical work leaned toward system design: I had to reason through a notification-delivery service, including reliability and scaling, rather than just draw a high-level picture. The later interviews stayed rigorous, with…
Interview experiences · LinkedIn
LinkedIn Staff DevOps Engineer Interview Experience — Downleveled from Senior Staff, Four Rounds, Then Silence
Back in February or March I applied for a senior staff role at LinkedIn, something pretty close to what I'm doing now. The first round was behavioral, and I've always felt I hadn't quite prepared it right — I leaned too hard on execution. I interviewed at Stripe recently too and got the same feedback. In the end they told me they wanted to downlevel me to staff. LinkedIn's senior staff, on levels…
Interview experiences · LinkedIn
LinkedIn Staff Machine Learning Engineer Interview Experience — Phone Screen Plus a Five-Round Onsite Full of Probability Questions
The phone screen was 1hr, there was a lot of content, but it was all questions that had already shown up in other interview reports. Coding - biased coin Input: A method getRandom01Biased() that generates a random integer in [0, 1], where 0 is generated with probability p and 1 is generated with probability (1-p) Output: A method getRandom06Uniform() that generates a random integer in [0, 6] with…
Interview experiences · Lockheed Martin
Lockheed Martin Software Engineer interview about project work and resume experience
My first step was a conversation with a recruiter who set expectations and kept things simple. The recruiter asked basic questions about eligibility, went over my relevant experience, and introduced the business unit and the project work I'd be involved with. The atmosphere was calm, and it felt like the time was meant to help me get comfortable before moving on. After that introduction, the proc…
Interview experiences · Lockheed Martin
Lockheed Martin Software Engineer interview: conversational STAR format
The interview felt more like an extended conversation than a strict test. It was virtual and conversational throughout, with technical leaders asking about my experience and following with situational behavioral questions. They also asked object-oriented-programming questions, and I used STAR to organize my answers. It began with the usual "tell me about yourself," then they described the role to…
Interview experiences · Lockheed Martin
Lockheed Martin Software Engineer interview experience
I expected my first interview to go into technical depth, but it was surprisingly light. It was short and straightforward, more like a quick check-in, with an easygoing tone and a strong emphasis on behavioral and fit questions. They asked basic questions rather than anything that felt like a difficult technical screen. I spent most of the time connecting my background to the role. One question w…
Interview experiences · Lockheed Martin
Lockheed Martin Software Engineer interview: four-person behavioral panel and a quick offer
The process was slow to start. My application took about three weeks to move forward, but once it did, the interview part was fairly compact and organized. I had a behavioral-focused interview with a panel of four. They did not expect me to know everything. Instead, they used scenario questions to see how I thought when I did not have certainty. It felt less about finding a single right answer an…
Interview experiences · Lockheed Martin
Lockheed Martin Software Engineer interview: STAR and LQR
After applying, I followed a familiar structured path: a recruiter-style step and then a standard virtual interview with several behavioral questions and one technical prompt. The process was tightly schedule-driven through email invitations, and the interview questions closely matched what had been described publicly. I answered a full set of STAR-based behavioral questions and one technical que…
Interview experiences · Lockheed Martin
Lockheed Martin Software Engineer interview with a months-long virtual process
I interviewed for a specific program and was genuinely excited because the company was one of my top choices. The interview was virtual and included multiple interviewers, but the atmosphere was uneven and made it hard to feel comfortable. Some interviewers seemed disengaged. One reacted dismissively while I was answering and kept looking elsewhere, which immediately put me off. The full process…
Interview experiences · L'Oréal
L'Oréal Marketing Analytics Specialist Interview Experience: Collaborative group case
I enjoyed this process because it felt collaborative instead of purely transactional. After the recruiter stage, I did a group task where we worked through a case and presented what we came up with. The experience felt welcoming throughout and gave me a real view of how people might work together day to day. It was harder than a straightforward HR screen. The group format and presentation made me…
Interview experiences · L'Oréal
L'Oréal Marketing Analytics Specialist Interview Experience: Initial fit screen
The process began with an HR interview framed as an energy check. HR would decide whether they liked my vibe before taking me further. I would have met the rest of the team afterward, but I did not get past the first conversation. This was more about whether the discussion landed well than about role-heavy content. It was clear that the first round was intended to filter for interpersonal fit. Th…
Interview experiences · Lovisa
Lovisa Account Executive Interview Experience: a group format without enough substance
The interview was designed to be social, but I left feeling unable to show what I could do. The group format began with an icebreaker and quick introductions to the interviewers. By the time it was my turn, my background had been reduced to a couple of lines. I worried that the hiring managers did not have enough detail to understand my strengths for an account executive type role. The larger set…
Interview experiences · Lovisa
Lovisa Account Executive Interview Experience: A quick retail interview
The first step was quick and low pressure. I received an email shortly before the interview, and the move from application to meeting felt fast. The conversation covered who I was, why I wanted to work at Lovisa, my availability, customer-facing work, and how I would handle different situations. The manager conversation was relaxed too, with standard retail questions, sometimes only a handful of…
Interview experiences · LSEG (London Stock Exchange Group)
LSEG (London Stock Exchange Group) Business Analyst interview with eight timed HireVue responses
After a recruiter-style check-in, I went straight to an on-demand HireVue-style interview. The format was structured: eight questions, as much preparation time as I wanted, then about ninety seconds to answer once each prompt started. The questions were mainly behavioral, about workplace situations and how I approached day-to-day collaboration when things happened a certain way. It was not a deep…
Interview experiences · LSEG (London Stock Exchange Group)
LSEG (London Stock Exchange Group) Software Engineer interview: assessment centre
I began with timed assessment activity and then an online assessment centre running from late morning into the afternoon. It included a group round, a technical interview, and a motivation-focused interview. The questions were mostly standard, but it felt competitive because every part seemed tightly measured against other candidates. The process then had aptitude, coding, and group-discussion co…
Interview experiences · Ltimindtree
Ltimindtree Software Engineer Genesys Cloud technical interview and generic rejection
A recruiter call started the process, and my resume was shared with the hiring team. Once I was shortlisted, I had a technical interview focused heavily on my Genesys Cloud experience. I discussed architecture, contact center implementation, and my migration approach. The interviewer stayed professional throughout. I thought the technical discussion went well and that I had answered clearly. What…
Interview experiences · Ltimindtree
Ltimindtree Software Engineer interview: aptitude, chatbot and fundamentals
I started with an online aptitude-style round, then moved into an AI chatbot interaction and technical discussions. The technical interview ranged from SQL basics to DSA fundamentals such as strings, arrays, numbers, and pattern questions. Depending on how the conversation went, the interviewer also returned to projects on my résumé. Although the topics were broad, the difficulty felt manageable.…
Interview experiences · Ltimindtree
Ltimindtree Software Engineer Interview Experience: a hands-on Java coding session
The interview began directly with technical questions. I shared my screen and wrote code in a simple editor during a session that lasted about half an hour. The pressure came from having to work hands-on rather than only talk through theory. The focus was Java fundamentals in a deeper, practical form. I covered Java concurrency and transaction handling, then OOP and core Java. There were under-th…
Interview experiences · LTM
LTM Software Engineer interview
After a recruiter call, I had a technical screen built around a coding and design prompt. I needed to create an API that returned a transaction identifier, then explain API versioning and exception handling. The follow-ups covered real microservice implementation and the tradeoffs among batch processing, messaging queues, and event-driven approaches. They also asked about Google Cloud Storage, Bi…
Interview experiences · LTM
LTM Software Engineer interview: cancelled offer after document checks
I completed every technical face-to-face round and felt confident I had cleared the hardest part. The process then moved to employment documents. I was asked for material from my previous employers, but I could not provide a bank statement from my first employer because that job was from several years ago. I submitted everything else I could, including PF records and bank statements from later em…
Interview experiences · LTM
LTM Software Engineer Interview Experience: Aptitude test to HR
The first stage was an online assessment on AMCAT. It was mostly aptitude based and entirely multiple choice, with some analytical reasoning and no traditional coding. Clearing that gate led to a technical interview. The technical conversation focused much more on my resume, background, and how I would work in the role. The interviewer led the discussion, seemed to know the work well, and was dir…