READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 75 of 153
Interview experiences · Jane Street
Jane Street Quantitative Trading Intern Interview Experience — Three Phone Rounds, All Game Theory
I'll share my experience with the three phone-interview rounds for a quant trading internship at Jane Street's NYC office. Jane Street likes to test with games — no math brainteasers, no algorithms, none of that standard stuff. You don't need to answer fast either; taking a minute or two to think or calculate before giving an answer is completely fine. Round 1: two questions, both original questi…
Interview experiences · Jane Street
Jane Street Software Engineer Interview Experience — Maximizing Reward as Pixels Reveal One Row at a Time
The interview was about solving an actual problem. The setup was an image classification problem using the FashionMNIST dataset. The model (a plain CNN) and the training code were already written, and the task was to modify it question by question from there; the environment they gave me was a Jupyter notebook (.ipynb). There were mainly two parts. After understanding the code (there wasn't much…
Interview experiences · Jane Street
Jane Street Software Engineer Interview Experience — OA Then a Phone Screen With Palindrome and Dice-Game Brain Teasers
I submitted my resume and got the OA email the next day. The problem was one that's already floating around the forum: using Excel to calculate a haircut, plus general Excel formula usage. Same numbers as the version posted on the forum, nothing changed. My suggestion if you're filling in the spreadsheet and need to use data from the problem's own table: use a reference, not copy-paste. The probl…
Interview experiences · Jane Street
Jane Street Software Engineer Interview Experience — Onsite System Design on Orderbooks, Rejected Before the Coding Round
Real-time report from the London office. The OA and first-round phone interview are already covered elsewhere on the forum, so this is just filling in the details on R2 and the onsite. R2: a coding interview (sort trade) — this one's also up on Glassdoor. Compared to a typical algorithm question, the setup was closer to "how would you implement this feature in a trading system," testing your logi…
Interview experiences · Jane Street
Jane Street Software Engineer interview: final onsite mattered most
I started with a virtual round and then moved to an onsite. The questions blended coding with system-design-style work, but they emphasized real-world systems more than academic exercises. By the onsite, it was clear that this was the most important stage and that the bar was highest there. I did not perform well enough in that final stage to move forward. The process was intense, and my main tak…
Interview experiences · JD Finish Line
JD Finish Line Account Executive interview: relaxed store conversation
I applied online, received a call to arrange an interview, and then went to the store to speak with a manager. I usually did not wait long after arriving. The manager explained the basic role before asking questions. Most discussion concerned my previous experience and customer service. I was asked why I wanted the job, what I liked about the store, my availability, and how I would handle particu…
Interview experiences · Jerry.Ai
Jerry.Ai Software Engineer Interview Experience — GPS Trivia in the Recruiter Screen, Stuck on "move" in the OA
Recruiter Screen The interviewer was really friendly. She started by walking me through the company, then asked if I had any questions for her. In the middle she threw in an unusual question: how GPS works / the underlying design. Roughly, how GPS works, how the signal propagates, and why errors happen — for example the difference between the satellite's atomic clock and the clock on your phone.…
Interview experiences · JFrog
JFrog Customer Success Engineer interview experience: Docker and Linux background discussion
After a recruiter conversation of about 30 minutes, I met with a hiring manager for roughly 40 minutes. We talked through company policy and what the day-to-day job would involve, including shifts and the kinds of work that came up regularly. It was structured, and I left with a clearer sense of the expectations. The first technical round was a detailed conversation about my background and projec…
Interview experiences · Jio Platforms
Jio Platforms Software Engineer interview: campus placement and C/C++ basics
I entered through campus placement for a limited GET-type role, and the process turned into a simple, resume-driven conversation. The coding segment was easy in level and focused on C and C++. The interviewer was friendly and helped when I got stuck, which made the experience less stressful than I expected. We also discussed my resume and projects before moving to my future plans. The overall dif…
Interview experiences · Jio Platforms
Jio Platforms Software Engineer interview on ML and deep learning
I had a compact process with one technical round led by a technical manager. The conversation stayed close to my resume, especially the machine-learning and deep-learning topics I had listed. I also got a small set of basic DSA questions. There was a behavioral discussion by the end, so it was not purely technical. The difficulty felt average, though the follow-ups demanded that I be thorough and…
Interview experiences · JOHN LEONARD
JOHN LEONARD Software Engineer interview: timed HireVue
A few business days after I applied, I received an interview invitation that went straight to HireVue. I read prompts one at a time and had preparation time, but the total recording window was tight. I answered on camera with limited attempts for each question. Most prompts were behavioral and used STAR, but a coding challenge appeared at the end inside the same timed window. I could not ask clar…
Interview experiences · Johnson & Johnson
Johnson & Johnson Software Engineer interview: recruiter silence
I did not find the process transparent. Getting an interview after applying was difficult, and when recruiters finally contacted me, their communication was direct but short on details. I never got a clear sense of how long the process would take. I received the invitation and completed a recruiter conversation, then things essentially went quiet. I heard nothing further about the position. The u…
Interview experiences · Johnson & Johnson
Johnson & Johnson Software Engineer interview: remote panels and a slow finish
After applying, I started with an HR-style screening call about my interests and compensation. Further interviews were remote on Microsoft Teams, and the sequence felt organized. The second conversation had more of a panel format. I met several team members alongside the person leading the hiring decision. We discussed my experience and how it fit the role. The questions were friendly, direct and…
Interview experiences · Johnson Controls
Johnson Controls Software Engineer interview: virtual manager and team
After an HR call, I interviewed with the engineering manager. That first conversation was mostly about my experience, and it felt relaxed and fluid. Soon afterward, I met three people from the team in another smooth, conversational interview. Once those rounds were done, I received an offer. Everything happened virtually, with no site visit required, which kept the path straightforward from start…
Interview experiences · JOHNSON HEALTH TECH TRADING
JOHNSON HEALTH TECH TRADING Software Engineer interview: engineers and a virtual panel
An interview was arranged quickly after I applied, and I met two engineers. They were friendly and straightforward, asking about my experience, projects and interests. It felt like a conversation about fit. A little later, I had a second, virtual round with the hiring decision-maker and other team members. That interview was more of a panel discussion, covering my resume, how I'd approach the wor…
Interview experiences · JOHNSON HEALTH TECH TRADING
JOHNSON HEALTH TECH TRADING Software Engineer interview: expected assessment
A recruiter contacted me after I applied, and the first exchange was quick and direct. I had a short phone conversation about my background and fit, and it sounded as though an assessment would follow. Then I stopped hearing anything for a while. The recruiter did not give much information about timing or the full length of the process. I waited without updates, and that uncertainty felt rough be…
Interview experiences · Johnson
Johnson Software Engineer interview: two virtual rounds with the decision-maker
I had two virtual interviews, moving directly from the first to the second. The employer or person responsible for the final decision was present in both. Other team members joined the second round, giving it a panel format. We focused on my background and fit. It was a structured conversation with several perspectives. Although the process was short in terms of rounds, I felt they were actively…
Interview experiences · Johnson
Johnson Software Engineer interview: unclear recruiter process
Recruiters contacted me after I applied, but the process was hard to understand from the beginning. Their conversations were direct and gave little detail about what to expect or how long things might take. After the interview, I stopped hearing anything about the role. I could not gauge whether I was progressing or whether another step was coming. It did not feel transparent, and the lack of upd…
Interview experiences · Jones Lang LaSalle
Jones Lang LaSalle Financial Analyst Interview Experience: a one-hour fit-focused meeting
After applying through the company portal, I was shortlisted and heard from HR fairly quickly. The face-to-face stage moved fast after that. HR scheduled an in-person interview with a finance manager and director. It took about an hour and felt straightforward rather than especially technical. Most questions were behavioral and tied to my past experiences. They wanted to understand how I had hand…
Interview experiences · Josh Technology
Josh Technology Frontend Engineer interview: JavaScript-heavy process
My first in-office round was DSA-oriented and firmly JavaScript-centric. It mixed aptitude questions with logic problems that had to be coded in JavaScript. The preassessment felt hardest because of graph and restriction-style prompts and the strict JavaScript requirement. After clearing it, I had more JavaScript machine-coding rounds and a final one-on-one technical interview. Arrays and common…
Interview experiences · Josh Technology Group
Josh Technology Group Frontend Engineer interview experience: JavaScript OA debugging
After a recruiter touchpoint, I went straight to an OA that was heavily focused on JavaScript. It opened with about 10 to 15 aptitude and reasoning questions, including blood relations and basic science or math. I had not prepared specifically for that part, but it did not feel like the blocker. The JavaScript portion had medium-to-hard HTML, CSS, and JS questions, plus debugging where I had to f…
Interview experiences · Josh Technology Group
Josh Technology Group Frontend Engineer interview: group web-template assessment
My process began with online rounds and, after I was shortlisted, became very in person and structured. After the recruiter step, about a week later I had a technical screen on DSA-style coding. The in-office sequence began with a coding round where I needed to solve 2 of 4 DSA questions. Then four candidates worked together in a small group to implement assigned features in a web-development tem…
Interview experiences · Josh Technology Group
Josh Technology Group Software Engineer interview: campus DSA sequence and five onsite interviews
The campus process had three rounds before anything moved onsite. First came object-oriented-programming concepts and logical reasoning. The second round combined an aptitude test with two DSA coding questions. The third had three more DSA problems. People who cleared those rounds were invited to an onsite sequence of roughly five technical interviews. Those conversations leaned heavily on data s…
Interview experiences · Josh Technology Group
Josh Technology Group Software Engineer interview: campus to office technical rounds
After clearing campus rounds, I was called to office interviews. The campus sequence began with MCQs on CS fundamentals and output prediction, then MCQs plus one coding question, then a coding-only round. At the office, I completed an OA with two coding questions at about the same difficulty as the final campus coding round. It was followed by three technical interviews and an HR interview. The t…