READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 114 of 153
Interview experiences · Rokt
Rokt Software Engineer interview with a full-day bar raiser
The later stage became the most memorable part of my process, and not in a good way. After the earlier rounds, I was brought into an Amazon-style bar raiser interview. The tone felt scripted and as if the decision had already been made. The interviewer began by asking me to walk through a specific period from my resume. They mostly stayed quiet and gave very little feedback while I spoke. There w…
Interview experiences · Rokt
Rokt Software Engineer interview with coding, system design, and behavioral rounds
My process dragged on much longer than it should have. Recruiters were difficult to reach and gave me incorrect information about what the interviews would involve. Some interviewers also came across as though they didn't want to be there. At times, the whole process felt cold and stressful instead of inviting. Communication problems kept making the process feel unreliable. In some interviews, th…
Interview experiences · Rokt
Rokt Software Engineer interview with onsite coding, design, and leadership rounds
My process started with online aptitude and personality testing, followed by a behavioral evaluation and a one-way video interview where I recorded answers to a prompt. After those early steps, I was invited to an in-person onsite sequence with multiple parts. In the later rounds, the technical work shifted toward live problem solving and deeper evaluation. I worked through standard algorithmic c…
Interview experiences · Rokt
Rokt Software Engineer process with a room exercise, one-way video, and take-home
My first step was a cognitive and personality-style evaluation. After that, I quickly reached rounds that felt more like assessments than engineering interviews. One memorable part was a room-based exercise that had nothing to do with building software. It was meant to see how I performed under pressure during an activity unrelated to day-to-day development. The process also included a one-way vi…
Interview experiences · RTX
RTX Software Engineer interview: manager conversation and fast offer
I had an hour-long Zoom meeting with a manager for a new-grad role. I expected it to be more intimidating, but it was smoother than I expected. She explained what the team did and asked behavioral questions along with a few technical questions linked to my experience. The conversation covered my background, why I wanted to work at RTX, and how my experience fit the job. An offer arrived within an…
Interview experiences · RTX
RTX Software Engineer interview: projects, circuits and technical depth
I expected a mostly behavioral interview, but it became more technical. I discussed my projects and problem-solving approach, then answered questions about diodes and impedance and calculated current in a simple resistor circuit. Even in the casual format, the interviewer seemed to be looking for understanding rather than buzzwords. I was also able to choose technical topics from my background. I…
Interview experiences · RTX
RTX Software Engineer interview: short hiring-event fundamentals check
I attended an RTX hiring event with interviews compressed into 30-minute slots. The process felt low-pressure and straightforward, and most of the discussion was behavioral. There were still a couple of technical questions to check programming proficiency, including how to find the least child in a binary tree. Because the time was short, the discussion stayed on basics and clear answers rather t…
Interview experiences · Rubrik
Rubrik Account Executive interview: several meetings in a few days
The process gained momentum quickly, with several stages packed into a few days. I had three face-to-face conversations and then a final session. Almost as soon as that last conversation began, I felt off balance. I was thrown by the first sentence and never quite recovered. The tone and pace left little room to reset. I didn't advance, but I received clear feedback and respected how direct they…
Interview experiences · Rubrik
Rubrik Intern Frontend Engineer Interview Experience — 90-Minute OA, Solved Just One of Three Problems
90 minutes, 3 problems. Felt like every problem was medium+ difficulty. I only managed to solve the first one, and even that had a TLE. LeetCode 2551 Given two vectors of equal length, for each index [i] there is guaranteed to be an edge between v1[i] and v2[i]. Within the same vector, earlier elements sit at a higher level and later elements sit at a lower level, and together they end up forming…
Interview experiences · Rubrik
Rubrik Software Engineer interview: coding depth and uneven later rounds
Recruiting contacted me early, then I had a direct technical screen: solve a medium-to-hard coding and data-structure problem with the interviewer on the call and explain my reasoning. The interviewer gave hints when I was stuck, but the question demanded real understanding of the data structure. I left feeling that problem was the main filter. Later rounds included system coding and concurrency.…
Interview experiences · Runway
Runway Machine Learning Engineer Interview Experience — Two Phone Screens, Rejected in ML System Design
Sharing an interview experience for a lesser-known company. It's a video generation startup that seems to be doing pretty well lately. I mass-applied to one position, but the recruiter contacted me about a different role instead. There were two phone screens total, both 45 minutes. Round 1 was coding: implement an ngram class with fit and generate methods. fit reads a file and counts ngrams, and…
Interview experiences · Safran
Safran Full Stack Engineer Interview Experience: a month-long structured process
I applied early in the month and first heard back about two weeks later for an HR interview. About two weeks after that, I had an in-person conversation, then waited another week for the decision. The whole process took about a month, which made the scheduling feel fairly smooth. The process itself felt structured. It began with a phone conversation about my academic and professional background,…
Interview experiences · Safran
Safran Software Engineer interview: written aptitude and technical test
I remember a fairly structured process. After an initial recruiter discussion, I later completed a short written test with aptitude and technical questions. I had only 45 minutes to finish the whole test. That was followed by two interviews. The first covered basic questions related to the field. The second was more application oriented and lasted about 30 to 45 minutes. The whole process felt me…
Interview experiences · Sage
Sage Software Engineer interview experience
After a recruiter call, I had a technical screen of about an hour and then an HR conversation of around 30 minutes. The atmosphere was calm and not overly intense. I never felt set up to fail. The technical discussion drew heavily on my background and resume projects, then covered OOP, web-development basics, some distributed-systems ideas, and a couple of AIML questions. The interviewers were kn…
Interview experiences · Salesforce
Salesforce Account Executive interview: demoralizing recruiter process
The recruiters made me feel as though my time was something I should be grateful to spend, and I did not feel heard. They seemed to move through checklists and pass me to other recruiters to see which openings existed. The process dragged with gaps in communication. I was asked whether I would take a lower role to get in, with the implication that others step back to join Salesforce. By the hirin…
Interview experiences · Salesforce
Salesforce Account Executive interview with a three-stage in-person panel and account strategy
The recruiter process was organized and supportive. I got guidance that made the next steps clearer, along with preparation materials that helped me understand the expectations. The flow appeared to have three stages, with the last round as an in-person panel. The interviews were structured and purposeful. Instead of asking the same behavioral questions repeatedly, each interviewer focused on a d…
Interview experiences · Salesforce
Salesforce Account Executive interview with Dublin relocation questions and mismatched rejection feedback
After a couple of early steps that felt fairly normal, the process broke down at the fourth stage. I had been told that the third interview would focus on my motivations and details around relocating to Dublin, so I prepared for that context and answered accordingly. When the rejection feedback finally arrived, it cited commercial skills that, as far as I understood, had never been asked about or…
Interview experiences · Salesforce
Salesforce Customer Success Engineer interview experience
After speaking with the recruiter, I had a technical round where I discussed my project experience and worked through a piece of provided code. I was asked to make the code more production-ready, and the coding-style questions connected back to OOP concepts. The later managerial round focused on customer work: how I would handle situations, manage relationships, and name a few Salesforce products…
Interview experiences · Salesforce
Salesforce Customer Success Engineer Interview Experience: HackerRank through techno-managerial
My process had three direct rounds. First came an online HackerRank coding session focused on problem-solving. Then I had a technical round that covered Stack versus Heap, debugging a snippet to find the cause of a NullPointerException, and HTTP methods. The final step was described as techno-managerial. That fit the overall process: I expected to show technical grounding while also explaining ho…
Interview experiences · Salesforce
Salesforce Member of Technical Staff Interview Experience — Three Rounds from Streaming Top K to Payment Design
Round 1 Find the top K most frequent elements in an infinite data stream. Convert a sorted doubly linked list in place into a balanced binary search tree without creating any new nodes. Round 2 I had to implement merge sort by hand: Implement merge sort from scratch. Explain its recursion tree in detail. I also had to implement operations involving set bits and find all anagrams. Round 3: System…
Interview experiences · Salesforce
Salesforce Senior AI Engineer Interview Experience — Onsite Coding Project, Offer the Next Day
My background: undergrad from University of Washington, CSE, with about 5 years of YOE. Timeline: Week 1: HR Screening Week 2: Three virtual interview rounds (HM + Project + AI Fundamentals) Week 3: On-site (Coding Project + System Design) One day after the on-site: HR was incredibly efficient and gave me a verbal offer right away. HR Screening Mainly talked about my current interest and my work…
Interview experiences · Salesforce
Salesforce Senior+ Software Engineer Interview Experience — Two OA Questions: String Segmentation and Power-of-Two Operations
Question 1: Minimum Segments with No Repeated Characters Given a string s, you need to perform the following operation exactly once, then compute the minimum number of non-overlapping, non-empty substrings with no repeated characters that the string can be split into: Choose any lowercase English letter, and delete every occurrence of it from the string. Constraints: 1 <= |s| <= 2 * 10^5 String s…
Interview experiences · Salesforce
Salesforce Senior+ Software Engineer Interview Experience — VP Chat, Four Rounds, Then Team Matching
Cross Cloud org. Round 1 was a chat with a VP. Round 2 was an OA; one of the questions was problem 443. Round 3 was two VOs, one coding and one system design. The coding was problem 460. The system design was to design a coffee shop order system. Round 4 was the onsite, same as above. The coding question was the same as the one in another thread on this forum — maybe a bit more complex, because y…
Interview experiences · Salesforce
Salesforce Software Engineer II Interview Experience — HM Screen, OA, and a GCP-Focused Final Round
A recruiter reached out in April and scheduled a video call to get a sense of my situation, and mentioned there would be a lot of openings coming up after that. In June I noticed a large number of Salesforce job postings, but the recruiter seemed to have forgotten about me, so I emailed to nudge them. Interviewing for SDE 2. First round: Hiring manager screening. Mainly asked about my background,…