READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 108 of 153
Interview experiences · Ramp
Ramp Account Executive interview experience: 45-minute presentation
The process was long. The recruiter kept me updated, but the timeline still stretched out to roughly six interviews. The biggest demand was a 45-minute presentation that took about 20 hours to prepare. I received positive feedback during the stages I completed, so I expected a clearer ending. Instead, I got a rejection email with almost no explanation. After putting in that much time, I wished th…
Interview experiences · RAMP Consulting Group
RAMP Consulting Group Account Executive interview: presentation round and email rejection
The process dragged on and felt more time-consuming than it needed to be, especially because the hardest parts came near the end. I started with the recruiter and went through several interviews that led to a presentation-heavy round. Although the feedback earlier in the process had been positive, the pressure grew as I prepared the materials. The presentation was the biggest challenge. I spent a…
Interview experiences · Ramp
Ramp Software Engineer interview: AI-assisted development screen
After a recruiter reached out, I had a short screen that was mostly about how I use AI day to day. We discussed what I had built or worked on with coding assistants and answered questions directly about AI-assisted development. The recruiter did not go deeply into much else, so the AI emphasis was clear. The next step was another technical conversation with a practical coding feel. It had two par…
Interview experiences · Ramp
Ramp Software Engineer Interview Experience — Four Onsite Rounds, No Offer
Coding (I'm posting the full original question) Given a list of flights: Part 1: get_user_with_most_flights() Part 2: get_user_location(time) The problem itself wasn't hard — a classic binary search question. But I had to figure out on my own how to import the file (the file and the test weren't even in the same folder), and I wasn't that familiar with writing tests in pytest, so I spent some tim…
Interview experiences · Ramp
Ramp Software Engineer Interview Experience — Recursive URL-Fetching Round Under Time Pressure
They give you a URL, and you have to call it. The response might contain a new set of URLs, or it might contain other data; then you keep calling whichever URLs come back, recursing/iterating like this until you finally get back "congrats". You don't need to return the path, just the final URL. The problem itself isn't especially hard, but overall it's pretty tedious and practical. During the int…
Interview experiences · Ramp
Ramp Software Engineer Interview Experience — URL Maze BFS Problem, Rejected Over a Debugging Miss
The question was the "URL maze, find the exit" problem that's already known on this forum. Right from the start we were just talking through it, testing the URL, then I wrote the program, and finally wrote a BFS solution that passed. The follow-up: they swapped in a different URL and had me run my Part 1 solution against it, and this time it didn't pass — I needed to handle status codes like 503…
Interview experiences · Ramp
Ramp Software Engineer Interview Experience — URL Maze BFS Tech Screen with Flaky 503s and a Silent Interviewer
Just finished my Ramp tech screen today, so here's the writeup. Process: one hour, one question, 5 minutes of Q&A at the end. Question: URL Maze (a classic that keeps showing up in past interview reports) You're given a start URL. Calling it returns JSON where the key is next_stops and the value is a list of paths. You append each path to the host and keep visiting, until some URL returns {"messa…
Interview experiences · Raytheon
Raytheon Software Engineer interview: resume-depth second round
The first interview was surprisingly laid-back. We spent a lot of time on OOP, including the classic four pillars, and broader software-engineering fundamentals. I explained how I thought about code, and it did not feel like they were trying to catch me out. The second round was a real step up. Several engineers and the hiring manager joined, and they examined the details behind what I had put on…
Interview experiences · Raytheon Technologies Corporate Headquarters
Raytheon Technologies Corporate Headquarters Software Engineer interview: C++ resume deep dive
After speaking with a recruiter, I had two back-to-back rounds. The first was easygoing and focused on how I thought about code, core OOP ideas, and software-engineering fundamentals. I walked through what I had built and how those concepts appeared in practice. The second conversation was tougher. I met the hiring manager and several engineers, and they went deeply into my resume. Surface-level…
Interview experiences · RBC
RBC Business Analyst interview: clear behavioral panels
RBC contacted me about two weeks after I applied. Once the interview was booked, the process moved quickly and stayed low stress. The early conversations were efficient, the timeline and expectations were clear, and I had time to ask questions at the end. Most of the interviews were behavioral and situational. I talked through past experience and then responded to scenarios about how I would hand…
Interview experiences · RBC
RBC Software Engineer interview: coding assessment and a project-focused final round
After speaking with a recruiter, I took a technical screen with LeetCode-style problems on a coding assessment. One felt easy and a couple were medium. A little later, I had further rounds combining deeper discussion with technical evaluation. The final part focused on what I'd built and how it worked. I discussed my projects and familiar tech stack, answered targeted technical questions and then…
Interview experiences · RBC
RBC Software Engineer Interview Experience: an easy behavioral interview without closure
The process was simpler than I expected. It started with a roughly 30-minute behavioral interview and situational questions that were not especially difficult. I was told I would hear about my application status within a week. Almost two weeks passed without an update, so I sent a follow-up email thanking them and asking about timing. That email was not answered either. I ended up without closure…
Interview experiences · Red Hat
Red Hat Software Engineer Interview Experience: four rounds disrupted by scheduling
A recruiter contacted me quickly after I applied, but reaching them afterward was frustrating. Once I was scheduled, the process became chaotic because scheduling was the biggest source of stress. I had four interviews: a hiring-manager call, two technical discussions, and a coding round. I had given availability for a week, and the schedule was set around it. Then my final-round interview was mo…
Interview experiences · Red Hat
Red Hat Software Engineer interview: system design, coding, and projects
My Red Hat loop followed the usual order: a screening round, a conversation with the hiring manager, and technical rounds. I reached a later technical stage but was not moved forward after it. The technical discussions covered system design and coding concepts. I also talked through my current projects and the design decisions behind them, which kept the interviews tied to how I actually work. Th…
Interview experiences · Reddit
Reddit Backend Engineer Interview Experience — Load Balancer Deep-Dive and a One-Week Offer
General coding 1: the Report Chain problem General coding 2: the Tennis Game problem — afterward the interviewer also chatted with me a bit about the strategy pattern Backend programming: the Load Balancer problem: It's split into four parts, and they give you a codebase. Part 1: The load balancer keeps getting error code 500. You need to find the cause — the cause is that the LB has the hostname…
Interview experiences · Reddit
Reddit Machine Learning Engineer Interview Experience — General Pooling and a Ranking Interview
I applied to a particular team while sending out lots of applications online. The first phone screen was a question from the forum: analyze a spent-hours dataset and predict clicks. Since I had prepared it, the interview went quite smoothly. A week after the interview, I still hadn't heard anything, so I logged into the candidate portal. The position I had applied for was gone, and the interview…
Interview experiences · Reddit
Reddit Machine Learning Engineer Interview Experience — Onsite with a Cat/Dog Comment-Tree Filter and a Comment-Likelihood ML Design
Coding: seems like a new question? I had AI rewrite it: You are given a dictionary of Reddit comments. Each comment contains: id parent_comment body cat: whether the comment is about cats dog: whether the comment is about dogs Example input: Comments form a tree using parent_comment. There are two user modes: CAT_PERSON: does not want to see dog-related comments DOG_PERSON: does not want to see c…
Interview experiences · Reddit
Reddit Machine Learning Engineer interview experience: two DSA rounds
The interview was straightforward: two data-structures-and-algorithms rounds along with machine-learning knowledge. The interviewers were kind and easygoing, and one of them in particular made the conversation feel comfortable. The format matched what I expected for the role. There were no strange surprises, just a clean sequence with a relaxed tone. I did not receive an offer, but the interview…
Interview experiences · Reddit
Reddit Software Engineer Interview Experience — A Word-Search Rule Clarified Too Late
The author reports an unsuccessful Reddit coding screen involving word search. After presenting the task, the interviewer remained quiet while the applicant worked. The author did not confirm the movement rules and implemented a more permissive search than the interviewer expected. A typo also consumed about ten minutes. Although the applicant’s own tests passed, the interviewer said near the end…
Interview experiences · Remitly
Remitly Frontend Engineer interview with a timed Canditech assessment
The process started with a recruiter screen, followed by a timed assessment on Canditech that lasted about an hour. The structure was rigid. Each section had its own time limit, and once I finished one, I couldn't return to it. There was no way to practice or get familiar with the platform beforehand, which made the pacing more stressful. I got thrown off immediately because I initially saw only…
Interview experiences · Remitly
Remitly Software Engineer interview: DFS screen and four-interview virtual onsite
I applied online and went straight to scheduling without a recruiter introduction. My first technical interview involved a simple DFS-style problem. I passed that round and was invited to a virtual onsite. The virtual onsite felt uneven. It included four interviews: two technical coding rounds, a manager round, and a product manager round. Some interviewers were engaged and seemed genuinely inter…
Interview experiences · Remitly
Remitly Software Engineer interview: live coding and power-day onsite
My process started with an HR phone call. I then had a fairly structured technical interview with a live coding problem and enough time to think through the approach, followed by a separate values and discussion segment. After that, I went through what felt like a larger "power day" onsite with multiple interviewers across different roles. Some rounds focused on my resume experience. The technica…
Interview experiences · Remitly
Remitly Software Engineer interview: two coding interviews and values-based behavioral round
After applying, I didn’t do anything especially elaborate up front. Everything took place online over Zoom, and the process focused heavily on values. The interviews seemed designed to assess how I’d show up, not just how I’d code. My interview day combined two technical coding interviews with a behavioral interview centered on the company’s core values. One interviewer gave me a clear framework…
Interview experiences · Remitly
Remitly Software Engineer interview with a disputed coding solution
After a recruiter reached out, I entered the process with a decent amount of momentum. I had one technical interview that combined Q&A with a whiteboard-style coding task. The conceptual part focused on DSA and time complexity. Even when the conversation became tense, I felt I understood what they were asking me to do. The process then moved into the loop. One technical interviewer kept insisting…