cswork / libraryOpen practice workspace

READ. UNDERSTAND. PRACTICE.

Interview experiences

Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.

3,669 resources · Page 153 of 153

  1. Interview experiences · Zoom Communications

    Zoom Communications Software Engineer interview: three months without closure

    The process lasted roughly three months and began to feel inconsiderate of my time. After the recruiter touchpoint, I went through several steps that kept being moved ahead, including a presentation that required real preparation and a VP interview. The conversations felt positive, but the gaps grew harder to tolerate and recruiters became difficult to reach. I had a strong VP call. They told me…

  2. Interview experiences · Zoom Communications

    Zoom Communications Software Engineer interview: WebRTC gap

    My recruiter arranged time with the hiring manager and five engineers, so I met a lot of people in a short, back-to-back stretch. Most conversations were fine. One engineer, though, seemed to have decided what he thought before we had really started. He used less than the allotted time and did not seem interested in my background. It felt as though he had not reviewed my resume. The loop eventual…

  3. Interview experiences · Zoom Video Communications

    Zoom Video Communications Account Executive interview: clear steps, delayed decision

    The multi-round process moved quickly without becoming chaotic. After an HR touchpoint, the scheduling and next steps were clear, and I was not left wondering where I stood. Everyone I spoke with was professional, and the communication felt constructive. The process kept momentum even though it was described as "length" at one point, and I felt I had handled each round well. The frustrating part…

  4. Interview experiences · Zoom Video Communications

    Zoom Video Communications Software Engineer interview: delays after a VP call

    I was drawn into a long hiring loop that took most of three months. After the recruiter stage, I prepared a presentation and then had a VP interview, with long delays between steps. I kept getting positive signals and being told I was advancing, but I also had to chase updates, and the recruiter and hiring manager were hard to reach when I needed clarity. The VP call gave me the most confidence.…

  5. Interview experiences · Zoom Video Communications

    Zoom Video Communications Software Engineer interview: WebRTC and CodeSignal

    A recruiter scheduled a hiring-manager conversation and four additional interviews. Most of those conversations went fine, but one engineer seemed to have decided what the interaction would be before it began. He used barely any of the expected time and did not appear interested in learning about my background. That conversation came down to WebRTC protocols. I covered SIP, RTP, the ICE framework…

  6. Interview experiences · ZoomInfo

    ZoomInfo Software Engineer interview on projects, debugging, and coding

    After a recruiter call involving the hiring manager, I had a technical screen that mostly covered my projects, the role, and resume alignment. A couple more technical conversations followed, mixing coding-style problem-solving and debugging with JavaScript, Java, and SQL. The feeling was practical: they were testing reasoning, not memorization. My background stayed central throughout. I repeatedl…

  7. Interview experiences · ZoomInfo Technologies

    ZoomInfo Technologies Software Engineer interview with VP conversation

    After a recruiter call, I had a technical screen with the hiring manager. A few days later I interviewed with the SWE manager on a coding question, then shifted to resume questions about how my experience fit what they needed. The process felt structured and standard. I could feel the difference between solving the coding problem and explaining background alignment. At a later stage, I had a casu…

  8. Interview experiences · Zoox

    Zoox Data Scientist Interview Experience — A Random Grab-Bag of Math and Estimation Questions

    Overall it wasn't too hard, and the interviewer was very friendly. The interviewer had a slide deck, and the questions were picked from it at random. A 15x20 foot floor — if you tile it with tiles that are 1 square yard each, how many tiles do you need? An account has $1,000 in it, doubling every year. How much money is there after 20 years? Sitting by a window looking at the moon, estimate your…

  9. Interview experiences · Zoox

    Zoox Robotics Engineer interview: validation-testing problem solving

    About a week after a recruiter conversation, I had a virtual interview with the hiring manager. I first walked through my background, then we discussed how I handle problems during validation testing: what I do when behavior is unexpected, how I debug, and how I decide which check to run next. It was a focused conversation rather than a puzzle marathon. The questions stayed close to my day-to-day…

  10. Interview experiences · Zoox

    Zoox Software Engineer interview: a written assignment and unclear evaluation

    The interview loop felt long and demanding. After a recruiter contacted me, I spoke with several hiring managers and moved into more technical work. The biggest commitment was an extensive assignment with a detailed written report and, if selected, a presentation to a panel. I felt the workload was disproportionate, especially when I couldn't see clearly how the work would be assessed. After fini…

  11. Interview experiences · ZScalar

    ZScalar Account Executive interview: mock cold-email exercise

    I had a recruiter call and, about a week later, entered a structured process that moved quickly. It began with a hiring-manager conversation and a mock cold-email exercise. That first stage showed they were testing both how I thought about the role and how I would communicate in a realistic sales motion. If I had advanced, the later steps would have included another account-executive interview, p…

  12. Interview experiences · Zscaler

    Zscaler Account Executive objection-handling role plays

    The process started with a recruiter screen, followed by a round with two interviewers at the same time. That middle stage was more hands-on. I had to work through an objection-handling role play, which forced me to focus on responding in the moment instead of polishing a perfect story. After that, I had another round with senior leadership and a new role-play scenario. The interviews focused on…

  13. Interview experiences · Zscaler

    Zscaler Software Engineer interview after an 8-month job hunt

    I came out of an 8-month job hunt, and once things started moving at Zscaler, they moved quickly. I had been working at Oracle as an SMTS (IC3) until I was laid off in September 2025. My application timeline ran roughly from November 2025 to May 2026. My path to the offer involved both outreach and applications. I used referral support and applied directly through the company's portal. I stayed i…

  14. Interview experiences · Zscaler

    Zscaler Software Engineer interview: DSA, OOPs, DBMS, and C++

    My process was compact. I had one technical interview followed by a project round. The technical discussion included an hour of general discussion and then two DSA questions. We also covered basic OOPs, database management system topics, and C++ fundamentals. The overall level felt easy, and the structure didn't overwhelm me with too many moving parts. I still didn't receive an offer. My lingerin…

  15. Interview experiences · Zscaler

    Zscaler Software Engineer interview: four DSA questions in an online assessment

    I went through an online assessment with four DSA questions covering easy, medium, hard, and more complex material. It felt like a filter: if I cleared that set, I'd move on to a video call. The process was tied to an off-campus program for the 2027 batch, so it felt structured around moving candidates through a pipeline rather than having a deep back-and-forth interview. I completed the set but…

  16. Interview experiences · Zscaler

    Zscaler Software Engineer interview: networking to system design

    After a recruiter touchpoint, I had a focused first technical round. It opened with networking questions, moved to two coding problems, and then shifted to an open-ended system-design prompt. The system-design part was the hardest to get my head around. The interviewer did not feel encouraging or helpful while I was trying to organize an approach. Compared with that, the coding portion was manage…

  17. Interview experiences · Zscaler

    Zscaler Software Engineer interview: online assessment, group discussion, and two interviews

    My process at Zscaler followed a pretty standard structure. It started with an Online Assessment covering aptitude, coding, and communication. After that, I went through a Group Discussion round, followed by two interview rounds focused on knowledge, problem-solving, and teamwork. The overall difficulty felt about average. Even with the group setting, the process stayed straightforward. The inter…

  18. Interview experiences · Zscaler

    Zscaler Software Engineer interview with a 75-minute DSA round

    After an online assessment, I went through pre-interview sessions about Zscaler's journey and the interview process. They helped me understand what the company was looking for and what the next steps would feel like. The technical interview lasted about 75 minutes and focused mainly on medium-level DSA and problem-solving. The interviewer was genuinely friendly, which helped me think more clearly…

  19. Interview experiences · Zscaler

    Zscaler Software Engineer interview with three to four DSA questions

    I was asked to take a coding test, and it ended up having roughly three to four questions. The main topics were the DSA areas I expected, including graphs, dynamic programming, and trees. I was also able to choose the language I wanted from Python, Java, or C++. I didn't get an offer, but the experience felt like an average-difficulty coding screen rather than something unusually tricky or obscur…

  20. Interview experiences · Zscaler

    Zscaler Software Engineer: role-focused questions and a poor interview experience

    The process was fairly simple and focused on the role. I saw more situation-based and role-based questions than anything overly abstract. What frustrated me was the way the interview was conducted. The upper-management participants seemed completely disinterested, which made the conversation feel less respectful than it could have been. I didn’t feel the warmth or cordial engagement I’ve come to…

  21. Interview experiences · Zscaler

    Zscaler Software Engineer Senior Staff SDE offer in May 2026

    I applied for a Senior Staff SDE role at Zscaler through a referral and direct portal applications. After I entered the pipeline, a recruiter reached out, and the process started to feel more organized. The process led to an offer in May 2026. The recruiter kept communication on track, which made it clear that the company was actively reviewing my profile. I accepted the offer for the Senior Staf…