READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 74 of 153
Interview experiences · Intuit
Intuit Staff Software Engineer Interview Experience — Two Long Screens and a Final-Round Rejection
Intuit's interview process had two rounds. The process was long, but HR was patient. The final round was a big production too. First round: Coding The interviewer was very nice and kept encouraging me. The first coding problem was to design a rate limiter. Requirement: design a rate limiter that allows five people through during each time period. Then the design was extended: when VIP users arriv…
Interview experiences · Ipsos
Ipsos Research Analyst interview experience: timed skills assessment
I began with a standard recruiter screen about my experience and the role. It was not highly technical and focused on my background, motivation, and understanding of the company and function. Next came a timed skills assessment, followed by video or in-person conversations with the hiring side. They asked why I wanted the job, how I dealt with challenges, my strengths, and questions from my resum…
Interview experiences · Ipsos
Ipsos Research Analyst interview: fresher-friendly HR and research-fit discussions
The early rounds felt friendly and low-drama. I had an initial recruiter or HR screen about my experience and why I was applying, and the interviewer also explained what the company did. As a fresher, I was not pushed into technical questions. The conversation was more about fit and whether my interests aligned with market research. The next steps were online or on Teams and stayed efficient: sho…
Interview experiences · IQVIA
IQVIA Business Analyst interview: graphs, SQL, and aptitude
I had a technical, assessment-heavy process. It began with an HR or recruiter-style resume conversation, then moved to a formal technical screen focused on analytics and reasoning. I worked through line-graph analysis and puzzle-style questions. Later rounds mixed data work with logic: SQL, spreadsheet skills, Excel questions, more puzzles, and a separate aptitude test covering logical reasoning…
Interview experiences · IQVIA
IQVIA Consultant Interview Experience: interview content overshadowed by inconsistent follow-through
What I remember most is the chaos around the process rather than the questions. After recruiter contact, scheduling took weeks of chasing, and the call eventually ran late. It ended positively, with an indication that I would move forward once the team returned from vacation. After that came a long run of generic follow-ups that did not explain what was happening. The process included recruiter a…
Interview experiences · IQVIA
IQVIA Consultant interview: market sizing and case discussions
I began with a roughly fifteen-minute recruiter phone screen. I introduced myself, discussed expected salary, and talked about whether I had collaborated on studies with industries beyond my university. Later rounds mixed consulting work with business judgment. I handled a brief market-sizing question, a more formal case approach, and behavioral questions throughout. The rhythm was talk, case, th…
Interview experiences · ISS STOXX
ISS STOXX Data Analyst interview: Excel assessment through final on-site discussion
After applying, I went through a structured process starting with an Excel-skills assessment. Passing it led to an online HR interview, business interviews, and a final on-site discussion. HR emailed clear next steps and deadlines. Before the interviews, there was a hands-on technical exam on data handling and report-output case scenarios, including data visualization and manipulation. The instru…
Interview experiences · IT Partner España
IT Partner España Account Executive interview: sales results and cultural fit
The recruiter call felt like a fit check. We covered the role at a high level and my relevant sales experience, including numbers and results from previous work. The recruiter asked about the daily responsibilities in my last job and what attracted me to the company and its culture. It was an easy conversation to settle into, with nothing overly technical. I felt they wanted to know whether I cou…
Interview experiences · Itc Infotech
Itc Infotech Consultant interview: telephonic and HR rounds followed by a fast offer
I went through a straightforward process at ITC Infotech in 2022. It started with a telephonic round and then an HR round, and the early stages moved smoothly. Once I cleared them, things progressed quickly. I received an offer letter within about two days. After onboarding, the next step was client-facing: a client interview for the project I would be assigned to. The experience felt efficient a…
Interview experiences · IXL
IXL Senior DevOps Engineer Interview Experience — Bait-and-Switched Into a Role I Didn't Prep For
I mass-applied online for a general backend position (3-5 YOE), and since I work in infra, HR set up a call saying they'd have me interview for an ops role — except the only opening was a Sr role requiring 7+ YOE. When I asked about the green card policy, HR was evasive and just said they could do it. After the call I checked the forum first, and it turned out you had to wait a full year after jo…
Interview experiences · J.B. Hunt Transport
J.B. Hunt Transport Software Engineer career fair panel and short technical segment
I met recruiters at a career fair and interviewed shortly afterward, with the virtual session about a week later. A recruiter and another interviewer joined the call. It was mostly behavioral: we discussed my background and team experience, with only a small amount of programming discussion. I did not have a separate coding assessment, so it felt more about fit and communication than problem solv…
Interview experiences · J.P. Morgan
J.P. Morgan Quantitative Researcher Interview Experience — Two Screens and Long Decision Waits
The author describes two quantitative-research applications at J.P. Morgan, involving a credit team and a market/treasury risk team. Each reached one technical interview with a hiring manager. The author reports waiting several months both for interviews and for eventual rejections. The interviews required complete code written in the applicant’s own notes rather than a shared coding environment.…
Interview experiences · J.P. Morgan
J.P. Morgan Software Engineer II Interview Experience — Four Rounds from System Design to RAG
Round 1: Hiring Manager System design: choose a project you previously worked on, design and explain its architecture end to end, and answer related follow-up questions. Database optimization: given a database table with user_id and region columns and more than one million rows, how would you optimize a query that looks up a specific record? Database indexing. Table partitioning. Sharding. Replic…
Interview experiences · J.P. Morgan
J.P. Morgan Software Engineer Interview Experience — Minimizing a String by Removing AB and BB
[Problem description] Given a string seq consisting only of the characters 'A' and 'B'. You can repeatedly perform the following operation: Delete any occurrence of the substring "AB" or "BB". After deletion, the remaining parts of the string are joined together. Your task is to determine the minimum possible length of the string after any number of valid deletions. Note: A substring is a contigu…
Interview experiences · J.P. Morgan
J.P. Morgan Software Engineer Interview Experience — Superday, a Buggy PR Review, and a 90-Day Team Match Wait
Applied at the end of May, got the OA the same day, and finished it within three days — two medium-difficulty questions. Got an email from HR pretty quickly saying I passed the OA, asking for my resume and LinkedIn. A day later they called to schedule the superday. The call was only a few minutes, didn't ask about my work experience at all — I had prepared a self-introduction but never got to use…
Interview experiences · J.P. Morgan
J.P. Morgan Software Engineer Interview Experience — Text-Note LRU Coding and an Interviewer Who Just Hung Up
I've been job hunting recently, and an HR person from my old company reached out to me and set up an interview. It started with 2 rounds, BQ + coding. I didn't really want to go back to a former employer, but I figured I'd use it as practice, so I took it. Overall the experience was the same familiar flavor — mainly just terrible. The first round was BQ with an interviewer who'd been there a good…
Interview experiences · J.P. Morgan
J.P. Morgan Software Engineer interview: timed screening and panel
After applying, I took an online screening before speaking with an engineer. It combined multiple-choice questions and one coding problem to finish in about two hours. In the live rounds, DSA and OOP fundamentals remained central. The pace seemed aimed at seeing whether I could reason through normal problems rather than repeat memorized tricks. There was a deeper technical phone screen with an ex…
Interview experiences · Jain Global
Jain Global Data Engineer Interview Experience — Three Rounds on Data Quality, User Support, and a Compliance Modeling Case
round 1: What data issues have you run into during backtesting? How do you do identifier resolution? How do you choose among multiple vendor sources and backfill between them? How do you handle stale data, missing data, and outliers? How do you avoid look-ahead bias in data like earnings estimates? If backtest results suddenly change, how do you determine whether it's a model, code, or data probl…
Interview experiences · Jane Street
Jane Street Intern Software Engineer Interview Experience — Exchange Arbitrage and Quote Throughput
It was a low-level-design problem. Core problem: An Exchange Arbitrage System for stocks. Assume there are multiple exchanges, each with a market feed continuously publishing bid and ask prices for different instruments or stocks. Design and implement an arbitrage strategy. The example gave AAPL on exchange A a bid of \$1.00 and an ask of \$1.10, while exchange B had a bid of \$0.90 and an ask of…
Interview experiences · Jane Street
Jane Street Intern Software Engineer Interview Experience — Recursive Arithmetic with Invalid Intermediate Results
An algorithms/LeetCode-oriented question. Problem description: Given a string expression, evaluate it and output the arithmetic result. Restrictions and constraints: Only positive integers are supported. Intermediate-state validation: At any stage of the calculation, if a negative number appears (for example, an intermediate result below 0) or a non-integer appears (for example, division that pro…
Interview experiences · Jane Street
Jane Street New Grad Software Engineer Interview Experience — A Stream-Transformer Coding Question from the Phone Screen
This is an old one — sharing a question from my campus recruiting interview back in the day. Given a set of M codes and N timestamps, the ideal shape for the data is an N x M matrix, where the rows are sorted by time and the columns are sorted by the code's lexicographic order. But not every code has data at every timestamp. You're given a stream of std::vector<std::tuple<int, std::string, int>>,…
Interview experiences · Jane Street
Jane Street Quantitative Analyst interview experience: probability progression
I went through math-focused interviews that started with easier questions and became harder. The rounds centered on probability. Early questions established the fundamentals, then the difficulty increased. Each round also began with a behavioral check-in, which set expectations before the technical work. In a similar run, I had three phone interviews along the same probability track. The first co…
Interview experiences · Jane Street
Jane Street Quantitative Analyst interview: probability games before superday
I had several Zoom interviews, with three technical rounds before a superday. The questions were built around games presented by the interviewers and relied heavily on probability and game thinking. The early games were more straightforward and closer to deterministic setups. Later rounds brought more randomness and more game theory. In the more open-ended game rounds, I needed to optimize outcom…
Interview experiences · Jane Street
Jane Street Quantitative Analyst interview: probability rounds and nerves
After applying online, I had a resume screen and a first technical round. It was my first quant interview, and I was nervous enough that I did not answer as smoothly as I wanted. I did not move past that round. I later entered through a program that sent me directly to interviews. There were two 45-minute Zoom technical rounds. The first was clearly easier than the second, and the interviewers we…