READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 76 of 153
Interview experiences · Josh Technology Group
Josh Technology Group Software Engineer interview experience
The experience was straightforward, and the people I met were polite. There was no fixed interview timing, so interviews could be attended at any time. I showed up when scheduled and worked through the rounds. The first round covered basic CS material such as input and output, tree concepts, and a small coding component. It also included OOPs and basic C. I was asked about infix and postfix, and…
Interview experiences · Josh Technology Group
Josh Technology Group Software Engineer Interview Experience: 35 questions before a timed coding round
I entered the software-developer process through college recruitment. It all happened in one day across five rounds. First was an online technical assessment on Safe Exam Browser with 35 questions in 60 minutes. It mixed multiple-choice technical questions with subjective prompts tied to code snippets. I had to predict output, spot errors, and work through basic logic-style programming questions.…
Interview experiences · Josh Technology Group
Josh Technology Group Software Engineer interview: secondhand account of three online DSA rounds
I did not complete the full process myself, but I heard what the online rounds looked like. There were three of them, mainly medium-level DSA. The topics included trees, linked lists, and a string question. From that account, the OA sounded like a medium-level filter focused on core data structures rather than anything unusual. Location: Gurgaon, Haryana. Overall feedback: positive. Offer status:…
Interview experiences · Josh Technology Group
Josh Technology Group Software Engineer interview: unstable internet during an on-site OA
The process began with a standard online assessment, but the setting changed how it felt. I had to take the OA at a college venue, where the facilities were limited and the internet fluctuated enough to distract me. The test itself followed a typical structure of programming fundamentals and code-related questions, but those logistics made it harder to concentrate. After clearing that stage, I ha…
Interview experiences · JP Morgan Chase
JP Morgan Chase Financial Analyst Interview Experience: A relaxed fit-focused loop
This felt like a standard interview loop, and the questions were more normal than I expected. I prepared for the usual themes, and the interviews centered on my background, why I was interested in the company, and other motivation prompts. Communication had a lot of back-and-forth, which helped me stay relaxed. I did not encounter difficult surprises or deep technical grilling. The conversations…
Interview experiences · JP Morgan Chase
JP Morgan Chase Financial Analyst Interview Experience: Analyst panel before superday
After applying, the process ran for a couple of months before my superday. I first did HireVue, then a recruiting group discussion. Before the superday, I attended a special session with current analysts on a panel to learn how the business worked. The roughly two-hour superday included two interviews with VP/EDs from different CCB areas. The conversations covered fit and how I thought about prob…
Interview experiences · JP Morgan Chase
JP Morgan Chase Financial Analyst Interview Experience: Recorded HireVue pressure
My recorded HireVue was more stressful than the later conversations. It lasted close to half an hour and used two prompts, with two chances to re-record each answer. The timing and self-recording mattered as much as the content. Later, I had a VP/ED interview covering motivation, my CV, and a technical component. I also went through separate ED assessment interviews that mixed technical, fit, and…
Interview experiences · JP Morgan Chase
JP Morgan Chase Financial Analyst interview: timed assessment and stock pitch
The process began with a HackerRank assessment containing two LeetCode-style questions. It took me about twenty minutes because I kept optimizing more than I expected to, when I had expected something closer to fifteen minutes. Later, I gave a stock pitch and then had to solve a very difficult math problem in the interview loop. There were short, timed answer windows and no chance to redo an answ…
Interview experiences · JP Morgan Chase
JP Morgan Chase Software Engineer interview: assessment, HireVue, and hackathon path
I did not pass the online assessment. The process felt highly competitive, even though people were encouraging. The described path began with resume shortlisting, then an online assessment, followed by a HireVue interview. After that, there was a hackathon at the Mumbai office, and offers seemed tied to how well participants connected with mentors at the event. Location: Mumbai. Overall feedback:…
Interview experiences · JP Morgan Chase
JP Morgan Chase Software Engineer interview: HackerRank and Super Day
The first step was an online HackerRank assessment with multiple tasks. The questions felt like easy-to-medium LeetCode problems, and it was a real gatekeeper rather than a quick formality. Afterward I had an HR screen, where recruiters helped arrange a longer interview. I was invited to a three-hour Super Day. The interviews were packed back to back across behavioral, design, and coding tracks,…
Interview experiences · Jpmorgan Chase &
Jpmorgan Chase & Business Analyst interview: poor interview experience
This Business Analyst interview left me shaken. The interviewers seemed unprepared and had trouble guiding the discussion. When I asked ordinary questions, they appeared to get tangled up in their answers, and I perceived a tone that bordered on mockery. Instead of feeling comfortable or guided, I felt interviewed by people who were not ready to do it. I also sensed pressure about returning to fu…
Interview experiences · Jpmorgan Chase &
Jpmorgan Chase & Business Analyst interview: strong first feedback then silence
I received strong feedback on the same day as my first-round interview, which made me optimistic. Then a long period passed without an update, and the silence started to feel strange. When I followed up, I was told they were working on it. Eventually I moved on because I found another job in the meantime. I never saw the process close properly after that promising first impression. The interview…
Interview experiences · Jpmorgan Chase &
Jpmorgan Chase & Financial Analyst interview: HireVue fit screen
I began with an online HireVue. The questions were about why the firm and role, finance basics, and behavioral topics. I had around 30 seconds to prepare before answering, with a limited number of takes depending on the question. The timing made even straightforward questions feel tight. The prompts also covered why I wanted banking, teamwork, and market awareness or trends. The format seemed fai…
Interview experiences · Jpmorgan Chase &
Jpmorgan Chase & Software Engineer interview: secondhand hackathon path after failed OA
I expected the JPMorgan process to be competitive, and it was. It stretched over several weeks with multiple checkpoints, starting with resume shortlisting and online assessments. The difficulty felt high enough that strong effort still did not guarantee meeting their bar. I also heard about a later, high-pressure in-person part: a hackathon connected to an office location. Those reports describe…
Interview experiences · Jpmorgan Chase &
Jpmorgan Chase & Software Engineer interview: timed Super Day
After a recruiter touchpoint, I completed a tight HackerRank-style assessment with four easy-to-medium LeetCode tasks. I then joined a Super Day over Zoom that lasted about three hours. The Super Day combined behavioral, coding, and system-design interviews in a shuffled order. Each block was about 45 minutes, with short breaks. The coding question was easy to medium LeetCode style, while system…
Interview experiences · JPMorganChase
JPMorganChase Business Analyst interview: managing-director conversation
After I applied, HR emailed to schedule an interview with the managing directors for the group I was targeting. The meeting lasted about 45 minutes and stayed focused on my experience and fit for the role. I left feeling that they had real context for what I brought to the conversation. It did not feel like generic small talk. The meeting itself was not long, but the seniority of the people invol…
Interview experiences · JPMorganChase
JPMorganChase Business Analyst interview: recorded answers and delayed follow-up
My first step was an online video assessment with prerecorded prompts. I had about a minute to prepare each response, then recorded myself answering for the camera in a few takes. I waited afterward for an email about moving forward. After clearing that stage, I had a first-round interview with strong feedback that day. The follow-up then stretched out, so I reached back out and was told they wer…
Interview experiences · JPMorganChase
JPMorganChase Financial Analyst interview: timed finance tests and senior interviews
The process felt intense from the start. After an online recorded interview, I faced timed assessments with little room to think. One test had difficult math and finance questions without a calculator. I also answered interview-style questions with very little preparation time. It felt like speed and composure mattered alongside what I knew. The live stages stayed difficult. My superday involved…
Interview experiences · JPMorganChase
JPMorganChase Quantitative Analyst interview with probability, DSA, and machine learning rounds
The recruiter side was smooth and fast. The recruiter was prompt and answered my questions about what to expect. After that initial call, the process moved into interviews aimed squarely at the core of the role, with the last conversation involving a partner's team. I went through multiple rounds that leaned heavily on probability. One mixed projects and probability theory with a single DSA-style…
Interview experiences · JPMorganChase
JPMorganChase Software Engineer interview: assessments, hackathons, and high-pressure paths
The process began with an online coding assessment and felt competitive from the start. I was then called back for a super-day with behavioral and coding interviews. Even though I kept a positive attitude, I did not move on to an offer. Another version of the journey had the same screen-first, difficult-later shape. Candidates were shortlisted from their resumes, completed an online assessment, a…
Interview experiences · JPMorganChase
JPMorganChase Software Engineer interview: internet search and notes-based coding
My interviews leaned on software engineering fundamentals, not only coding. I was asked what happens when someone makes an internet search, including the behavior under the hood and what the system does end to end rather than just definitions. There were also a couple of LeetCode-style questions, but I answered them in a notes-style environment instead of compiling code. The difficulty felt tough…
Interview experiences · JPMorganChase
JPMorganChase Software Engineer interview: precise coding and a same-day superday
The first technical round went straight into coding. The interviewer wanted an exact output, and I couldn't produce it within the time limit. It felt more demanding than an introductory question and set a sharp tone. Later, several rounds were grouped into a same-day superday with short breaks. They covered DSA, system design and behavior. Coding questions included greedy-style reasoning and tick…
Interview experiences · Jump Trading
Jump Trading Data Scientist Interview Experience — A Live O(1) Rolling Mean Question and Deep Factor Grilling
Since this is an experienced hire, there are relatively fewer coding questions. There's a lot more talk about your resume and the methodology behind your past factors — and they go into it in real depth, the kind that gives you chills and makes your heart pound. If you don't actually have results to back it up and you're just talking up your own effect, it's basically very hard to get through. Li…
Interview experiences · Juniper Networks
Juniper Networks Software Engineer interview: HPE office rounds and datapath decision
I had a face-to-face interview at an HPE office in Mahadevapura, and the schedule felt designed to be thorough. The first round was online with the hiring manager, followed by three in-person rounds. They spent a lot of time on projects from my resume and checked my skills one by one. At this level, I expected more emphasis on problem solving than on low-level incremental knowledge. Instead, the…