READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 113 of 153
Interview experiences · Roblox
Roblox Software Engineer interview: challenging but relaxed Superday
After applying online, I took an online assessment built around game-style problem solving. The Superday itself was tough, though most interviewers were laid back and friendly. The technical side leaned heavily on numerous LeetCode-style questions in the medium-to-hard range. The behavioral questions were not just warmups. They were difficult enough that I had to be specific about how I would han…
Interview experiences · Roblox
Roblox Software Engineer Interview Experience — 2027 Intern/New Grad OA Games and Coding
My Roblox OA from a month ago. Round 1: Cognitive Games, three mini-games Robots: Assemble tools to cross different terrain. Try different assemblies to reach the finish. Factory: Optimize the production-line network, identify bottleneck stations, and maximize cash flow on the high-profit lines. Mars: Outpost: Modular programming. Watch out: only functions packaged during the testing phase can be…
Interview experiences · Roblox
Roblox Software Engineer Interview Experience — A Robot Navigating a Laser-Covered Grid
The interview experience was good overall, and the interviewer was very friendly. This time I got a classic grid graph search/simulation question. The problem statement was quite long and needed careful reading. The original question follows: Problem description: Imagine a board of size numRows × numColumns with some lasers on it. These lasers are located in the two-dimensional array laserCoordin…
Interview experiences · Roblox
Roblox Software Engineer Interview Experience — A Shared To-Do List Design and a Kafka Mistake
The system design question was the shared to-do list problem from the question bank. Unfortunately, I had not had time to prepare for it. This was also my first system design interview, so I did not perform very well. I made one critical mistake by adding a Kafka queue. That made the system asynchronous and would affect the speed of the synchronous flow. The interviewer still interacted with me t…
Interview experiences · Roblox
Roblox Software Engineer Interview Experience — Digit-Grid Phone Screen, Then Resource Loader and Pub/Sub System Design Onsite
Engine-related role — all the questions were things I'd never seen anywhere on this forum before. Phone Screen: Phase 1 was an m*n grid where each cell holds a digit from 0-9. I had to collect every horizontal or vertical run of 3 or more matching digits and record each one in a results array, in the format [position, length], with the results ordered top-to-bottom and left-to-right. Phase 2 buil…
Interview experiences · Roblox
Roblox Software Engineer Interview Experience — Hat Assignments in an Early-Career Onsite
The author reports two coding interviews during a Roblox early-career virtual onsite. One problem asked for the number of valid hat assignments and the highest score obtainable when hats carry point values. The author considered dynamic programming or backtracking, noting that the smaller input size might permit the latter. The second problem was identified only as a Candy Crush exercise, without…
Interview experiences · Roblox
Roblox Software Engineer Interview Experience — One Technical Screen, a Rare Trie/Heap Question, No Offer
A bit unlucky — I ran into an interviewer for this round. At first I was pretty happy, thinking we might have something in common, but then I got the lowest-frequency, hardest question in the database, and I didn't finish it. I ended up failing. I'm not sure whether it was because of the coding, or my resume, or maybe just because I didn't finish the coding — either way, my feedback didn't stack…
Interview experiences · Rocket Lab
Rocket Lab Cloud Engineer interview, onsite trivia questions
I arrived enthusiastic for the onsite, but the experience felt misaligned from the start. The interview moved away from the role and into trivia-style questions from other disciplines and roles, including questions from panelists who joined remotely. Instead of evaluating my software engineering fit as a whole, it became a cross-functional Q&A where the questions didn’t feel relevant to the job d…
Interview experiences · Rocket Lab
Rocket Lab Software Engineer interview: large take-home project
My process was fairly condensed and involved only a few steps. I had a screening call, followed by a take-home project and a technical interview with the team to discuss what I had submitted. The take-home wasn't a nightmare, but it was on the larger side for an interview assignment. The technical discussion focused on clarifying the work and talking through what I had built. There wasn't much ra…
Interview experiences · Rocket Lab
Rocket Lab Software Engineer interview: technical-project presentation
A recruiter scheduled the interview, which began with a presentation about my strongest technical project. The rest was a conventional mix of technical and behavioral conversations about my engineering experience. The process seemed designed to connect what I had built with how I solve day-to-day problems. There were no extreme gotchas, just steady evaluation of my technical approach and team fit…
Interview experiences · Rocket Lab
Rocket Lab Software Engineer interview: technical rounds, presentation and an onsite tour
The process lasted a little over a month. After a recruiter call, I waited a week or two for a virtual hiring-manager interview, then had a technical interview with an engineer on the team. Those conversations followed a similar pattern: my resume, how I'd handled previous work and engineering fundamentals such as debugging and problem solving. The later stages were more demanding. I needed to de…
Interview experiences · Rocket Lab
Rocket Lab Software Engineer interview with a one-hour presentation and site tour
The process began when a recruiter asked about my availability, and the team moved quickly to arrange the next stages. I had a virtual screening with the hiring manager and engineers from the team, followed by an onsite interview by the end of the month, about three weeks after the initial screening. The onsite was long and structured. It included a one-hour presentation, several interview panels…
Interview experiences · Rocket Lab
Rocket Lab Systems Engineer interview with a ground-systems project presentation
The interview started cleanly. I spoke with a recruiter first about my background and motivation, then met with the team's manager. The next step was a presentation on an engineering project, which led directly into technical questions. The conversation stayed easygoing rather than adversarial. The technical discussion focused on engineering fundamentals and problem-solving. We talked about how I…
Interview experiences · Rocket Lab
Rocket Lab Systems Engineer interview with four rounds and a technical coding assessment
I had a fairly straightforward interview process. The steps felt organized, even though the timeline varied. It started with a recruiter conversation about behavioral topics and my background. The later rounds followed a simple structure. Overall, it seemed to involve four rounds, and there wasn't a self-style presentation unless you were interviewing for an internship track. The technical portio…
Interview experiences · Rockstar Games
Rockstar Games QA Engineer Interview Experience: realistic testing role discussion
After applying, I had an HR-led process that walked through my resume, experience, and fit. The tone was relaxed but professional. We talked about why I was drawn to testing, what kept me interested in gaming, and the background relevant to the role. They also made sure I understood that QA did not mean playing games all day. Scheduling was slow, but the recruiter stayed in touch and felt approac…
Interview experiences · Rockstar Games
Rockstar Games Software Engineer interview: coding track and logistics
The process opened with a recruiter screen and moved directly into a technical track. In one version, the initial coding test covered basic Java, Spring Boot, SQL, and some problem solving. After that, I had a focused, practical screening or technical discussion with senior people. Later stages included a live CoderPad-style assessment with problems described as similar to LeetCode, followed by a…
Interview experiences · Rockstar Games
Rockstar Games Software Engineer interview: FiveM and RedM community assessment
My recruiter conversation covered my background, experience and interest in Rockstar. A little later, I met members of the Community team for a deeper interview about community management and creator relationships. We worked through ways to handle issues in the FiveM and RedM communities. The next step was a timed written assessment on CoderPad. It covered more than coding: I responded to communi…
Interview experiences · Rockstar
Rockstar QA Engineer Interview Experience: resume, gaming, and QA fit
I began with HR going through my resume step by step. We discussed prior work, why I wanted QA, and my interest in gaming and testing. The interviews stayed friendly and professional. The questions covered my familiarity with Rockstar titles, how I found issues, and why I fit the role. Talking naturally about gaming helped because it kept returning as a theme. Responses sometimes took longer than…
Interview experiences · Rockstar
Rockstar Software Engineer interview: community scenarios and an eleven-week process
After speaking with a recruiter, I moved into interviews focused on the community side of the role. The first deeper conversation was with the Community team. We discussed community management and creator relations, including what I'd do when situations didn't go as expected and how I'd maintain relationships with creators and the wider audience. Next, I completed a timed written assessment on Co…
Interview experiences · Rockstar
Rockstar Software Engineer interview: Java, Spring Boot, and SQL
I started with a coding test covering Java, Spring Boot, SQL, and some problem-solving prompts. It was a practical check across the stack, so I had to do the work rather than simply talk through what I might do. After that came a screening step and then a technical discussion with senior people. That conversation was more about how I approached problems and reasoned through solutions than about w…
Interview experiences · Rokt
Rokt Account Executive interview with two CCAT assessments and HireView
After applying, I went through a fast-moving assessment sequence centered on CCAT-style cognitive testing. I took two different CCAT versions, which felt a little odd and even useless to me, although the tests themselves weren’t especially hard. After reviewing my results, the recruiter scheduled a HireView step. It was short and not difficult, but I found the format oddly off-putting. I then mov…
Interview experiences · Rokt
Rokt Software Engineer aptitude assessment with 40 questions in 30 minutes
I started with an aptitude-style assessment to qualify for the initial screening. It was a timed, third-party test with 40 questions, and I had to finish it in under 30 minutes. The questions felt focused on puzzles and patterns, with some mental math mixed in. After I completed it, I never got the sense that there had been a meaningful conversation behind the scenes. My application moved to a ti…
Interview experiences · Rokt
Rokt Software Engineer interview: aptitude screen, LeetCode, and onsite rounds
I went through an assessment-heavy funnel that felt disconnected from actual software work. After applying, I completed a cognitive aptitude and personality-style screen, followed by a one-way video interview where I recorded responses to behavioral prompts. By then, the process already felt automated and generic. The later stages followed a more traditional technical path, but the pacing and com…
Interview experiences · Rokt
Rokt Software Engineer interview: CCAT, personality test, and one-way video
After applying, I was put through an automated sequence. First came the Criteria Cognitive Aptitude Test and the Employee Personality Profile. The CCAT was a timed, IQ-style block with pattern-recognition and math-style items. The personality portion took about 10 to 12 minutes and had no time limit. Some prompts were straightforward enough that it did not feel like a serious gatekeeping exercise…