READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 72 of 153
Interview experiences · Infosys (Finacle)
Infosys Finacle Software Engineer interview: production, security, and cloud depth
This process was demanding and centered on systems and production thinking. I first handled several system-design tasks, then discussed my resume and worked through in-person DSA questions at about medium LeetCode or CodeChef level. There were also cryptography questions and deployment-like scenarios. Another comparable technical deep dive began with a DSA written test and pushed further into pro…
Interview experiences · Infosys (Finacle)
Infosys Finacle Software Engineer interview: project-focused managerial round
I went through a straightforward set of rounds that felt organized and tied to how I would approach real work. There was a virtual round, then an offline managerial round at an Infosys office, followed by an HR interaction. The managerial conversation stayed focused on my project and the technologies I had actually used. I was asked scenario questions about how I would handle different situations…
Interview experiences · Infosys (Finacle)
Infosys Finacle Software Engineer interview: project walkthrough and optimized DSA
The interview began with my introduction and a detailed walkthrough of my project. The interviewer kept asking about my implementation, approach, and what I personally contributed, so it felt like a real discussion instead of a checklist. Then I moved to DSA, where I had to give a brute-force approach before optimizing it. The final part covered Operating Systems, OOP, Computer Networks, DBMS, an…
Interview experiences · Infosys (Finacle)
Infosys Finacle Software Engineer interview: projects and ML in an HR round
I started with a medium-difficulty aptitude round and then had an HR conversation. We discussed my projects and the ML concepts on my resume. Much of it became behavioral, with the interviewer asking for examples from work rather than checking technical vocabulary in isolation. The process felt organized and comfortable. I could connect my experience to the role, and the questions followed the st…
Interview experiences · Infosys (Finacle)
Infosys Finacle Software Engineer interview: Salesforce trigger exercise
I went through a short virtual interview that was still fairly technical and focused on Salesforce development. It moved from basic concepts into harder areas around Apex, LWC, and how the pieces fit together. I had to reason through integration scenarios, triggers, and related admin and runtime concerns instead of just defining terms. The session lasted about half an hour, and I had to write a t…
Interview experiences · Infosys (Finacle)
Infosys Finacle Software Engineer interview: SQL, coin change, and system design
The interview began with a booking-data SQL problem involving filtering and aggregation, then moved to a coin-change DSA exercise. It also covered dependency injection and a design-flavored RAG-with-images question. Later I got a MySQL system-design and scaling question, so it was not only coding. I had to reason about architecture and tradeoffs. We also covered resume-aligned framework concepts…
Interview experiences · Infosys (Finacle)
Infosys Finacle Software Engineer interview: technical depth and clear storytelling
My selection process started with an online assessment, then a technical interview and an HR conversation. It was moderate to difficult. The interviewer kept returning to technical concepts, problem-solving, and how well I could communicate. I discussed my projects and how I solved project-based problems. It felt like they were checking whether my explanations matched my actual experience. The HR…
Interview experiences · Infosys (Finacle)
Infosys Finacle Software Engineer interview: two coding choices and deep fundamentals
The process began with an online assessment. After I cleared it, I met an interview panel that focused first on coding and then on the core subjects listed on my resume. I got two coding questions and could choose which one to focus on. After coding, the panel moved into OOP and SQL, including query-style SQL questions. They checked both my fundamentals and whether I could apply them to practical…
Interview experiences · Infosys (Finacle)
Infosys Finacle Software Engineer interview: two coding rounds before DSE offer
My process had three rounds in a clear order. First came the OA coding stage, then another coding round, and finally a one-on-one technical interview. The OA tested problem-solving. In the live coding stage I received two questions and had to complete one within the time limit. After I cleared coding and was shortlisted, the one-on-one interview became a deeper technical discussion. Earlier DSA q…
Interview experiences · Infosys (Finacle)
Infosys Finacle Software Engineer interview: Wingspan coding and complexity
My process began with an online coding assessment on the Wingspan platform. I had to solve a programming problem within the time limit. Once I cleared it, I moved into a technical interview where I explained DSA approaches, time and space complexity, and possible optimizations. The interviewer connected the discussion to my resume. We talked in depth about projects so I could show I understood wh…
Interview experiences · Infosys (Finacle)
Infosys Finacle Software Engineer interview with escalating DP and graph questions
My interview started with four questions that ranged from easy to complex. Even the supposedly easy first question involved greedy thinking. The second moved into dynamic programming. The third combined DP with graph-related elements. The fourth was described as extremely hard, which set the tone for the interview. I could not complete everything, and the sequence made me feel they wanted to see…
Interview experiences · Infosys (Finacle)
Infosys Finacle Software Engineer interview with timed DP and trees
My first major round was DSA focused. I had to choose one question from two options and answer it within 30 minutes. The difficulty was high enough that I had to be careful with DP and tree-related problems under time pressure. The technical round then shifted entirely to AI concepts. Moving from DSA to AI so quickly made the process demanding and unusual. I felt the interviewer was checking whet…
Interview experiences · Infosys (Finacle)
Infosys Finacle Systems Engineer Interview Experience: Coding then managerial round
The process was simple and felt more like a filter than a string of endless rounds. I had two main interviews: a coding round followed by a managerial round. I heard that a test can sometimes be included, but my own process stayed with that coding-then-managerial sequence. The overall difficulty felt manageable. I kept hearing internally that referrals mattered, which made the experience feel par…
Interview experiences · Instacart
Instacart AI Analytics Lead II Interview Experience — An API Data-Ingestion Gap Ended the Process
There was no interview experience for this role on the forum, so I am sharing mine. From the job description, this role looks like an analytics engineer plus a product analyst. With the impact of AI, one person really can do all of this work. Process: After a friend referred me, the recruiter reached out. Online assessment: six or seven SQL questions, not hard. I passed. HM interview: the HM seem…
Interview experiences · Instacart
Instacart Data Scientist interview: case study and SQL screen
One part of my process felt light technically for how long it took. After a recruiter-style step, I completed a live case study that lasted 1.5 hours. I used Python, or another tool of my choice, for the main technical task. The case study took up most of the time; I also gave a presentation and answered questions from people presented as stakeholders. In a separate recruiter-to-tech-screen path,…
Interview experiences · Instacart
Instacart Data Scientist Interview Experience — Four Rounds Including a Bar Raiser Case and a Project Presentation
Four rounds. Round 1 — Problem Solving (30 min): We partnered with a local grocery store to add a smart cart. Users could use the smart cart to find this store's own products and prices, and at the same time see products and prices from other stores on the Instacart app through the same cart. They asked whether this is a good idea, what the hypothesis would be, which metrics to look at, and how t…
Interview experiences · Instacart
Instacart Data Scientist Interview Experience — HR Screen, Take-Home, and Two BQ Rounds I Didn't Pass
I. First was an HR call. They asked me to tell them about myself, about my related experience (Data/Strategy), sponsorship, and why this role. After it wrapped up they sent me a sponsorship intake form to make sure I'd actually be able to work here. II. Then came the take-home challenge. The day after I filled out the form they sent it over — not hard, 7 or 8 questions, step by step. Two tables:…
Interview experiences · Instacart
Instacart Data Scientist Interview Experience — Product Sense, Experiment Design, and SQL in 45 Minutes
Overall the experience was good. The interviewer was very nice and the conversation flowed smoothly. In 45 minutes we covered product sense, experiment design, experiment analysis, and SQL. Question 1 How to investigate a metric decline. Pretty standard question. Seasonality, product changes, user segments, external competition — anything reasonable works. Question 2 If you were launching a new p…
Interview experiences · Instacart
Instacart Full-Stack Engineer Interview Experience — A 90-Minute AI-Assisted OA and Next-Day Rejection
I took the Instacart Full-Stack Engineer Assessment on Codesignal on September, after referred by an employee of the company. It was similar to what posted in the platform here: 5 questions, 90 minutes. Two questions involved chatting with the AI to get the requirements. Two AI assisted Coding with Claude Code, and One bug fixing question withouot AI. There was a tab that showed the live results…
Interview experiences · Instacart
Instacart Senior Backend Engineer Interview Experience — A 5-Part OA That Was Basically Vibe-Coding With Claude
I've compiled some tips I saw online and added my own experience. The deadline was two weeks. What surprised me was that this OA was completely different from the Instacart OAs I had seen discussed before. It was a 5-part assessment, and the overall format felt more like "AI-assisted full-stack feature implementation" than a traditional coding assessment. Time limit was 90 minutes. The assessment…
Interview experiences · Instacart
Instacart Senior Data Scientist Interview Experience — Four Onsite Rounds Including a Bar Raiser Case
Four rounds. Round 1 — Problem Solving (30 mins): partnered with a local grocery store to add a smart cart that lets users find that store's own products and prices on the smart cart, and at the same time see products and prices from other stores on the Instacart app through the same cart. Asked whether this is a good idea, what the hypothesis would be, which metrics to look at, and how to design…
Interview experiences · Instacart
Instacart Senior (L6) Software Engineer Interview Experience — Grocery Pricing Coding, Inventory System Design, and a 20-Minute Behavioral
Two coding rounds, one system design round, and one behavioral round. Coding question 1 Given input strings in the format SKUid|SKUNAME|QUANTITY|Price, output the total quantity and the total price in dollars. The price in the input is in cents. Watch out for bad input. Besides the input above, there is also a discount input, in the formats SKUid|axf|20 and SKUid|bxf|5|2. The first format is a 20…
Interview experiences · Instacart
Instacart Senior Software Engineer Interview Experience — Fast Coding and a Difficult Bar Raiser
The virtual onsite had two coding rounds, one design round, and one bar-raiser round. The coding questions were ones from interview reports, and easier than the versions on the forum. I breezed through both. For the calculate-expression question, the interviewer said in part two that there would always be spaces around the +, =, and - signs, so parsing was straightforward. In part three, the only…
Interview experiences · Instacart
Instacart Senior+ Data Scientist Interview Experience — Five Questions on Product Sense, Experiment Design, and SQL
Overall the experience was good. The interviewer was very nice, and communication was smooth. The 45 minutes covered product sense, experiment design, experiment analysis, and SQL. Question 1 How to investigate a metric decline. Pretty standard question. Seasonality, product changes, user segments, external competition — as long as it's reasonable, that's fine. Question 2 If you want to launch a…