Articles 🧠 Quiz ↗

Qualcomm — Camera Systems & Related Roles: Interview Experiences

Goal of this document: Collect ~50 real interview experiences for Qualcomm Camera Systems Engineer and closely related roles (Camera Software, ISP / Image Signal Processing, Multimedia / Video Codec, Computer Vision, plus adjacent Embedded / Systems / SWE / ASIC-DV roles that share the same interview loop), capturing questions asked, how the interview went, round structure, timings, and tricks/tips — each with its source URL.

Collected: 2026-06-27 · via Google search (Chrome) + page extraction. Search went to Google pages 3–4 for each term; search terms were revised as new role variants surfaced (ISP, multimedia, video codec, computer-vision, DV, ASIC).


Methodology & access notes (read this first)

Search terms used (10 core + revisions, each taken to Google pages 3–4): 1. Qualcomm camera systems engineer interview experience 2. Qualcomm camera software engineer interview questions experience 3. Qualcomm camera engineer interview experience rounds questions 4. Qualcomm ISP image signal processor engineer interview questions experience 5. site:reddit.com Qualcomm (camera OR ISP OR multimedia OR camx OR vision) interview 6. Qualcomm multimedia camx camera driver engineer interview experience 7. Qualcomm camera systems engineer interview glassdoor blind taro 8. site:reddit.com/r/qualcomm interview camera OR ISP OR feedback OR whiteboard 9. Qualcomm Camera ISP Architecture Engineer Role reddit chipdesign interview 10. Qualcomm "Computer Vision Systems" Modeling Engineer reddit interview

Revised/added during collection: video codec engineer, computer vision engineer, DV / design verification, ASIC image/video processing, whiteboard / hackerrank.

What was freely readable (full questions extracted): GeeksforGeeks, Medium, JoinTaro, NodeFlair, AmbitionBox, CleverPrep, InterviewBit, Foundit, CodingKaro, Naukri Code360, InterviewQuery, LeetCode Discuss.

What was login/bot-walled (handled separately, Part B): Reddit is hard-blocked on every non-authenticated route (direct fetch, redlib/libreddit mirrors, reader proxies all return 401/403/Anubis) — only Google-indexed snippets are quotable. Glassdoor shows per-role stats but walls the actual review text. Blind is login-walled (snippet only). For these, content below is the publicly-indexed snippet plus the source URL; full text would need a logged-in browser session (paste-in).


Summary

  • Total experiences collected: 75Part A: 62 detailed write-ups (with full question lists, rounds, timing, tips) + Part B: 13 restricted-site (Reddit/Blind/Glassdoor) snippet notes.
  • 21 of the Part A entries are tagged camera / ISP / display / video / computer-vision / audio-ML–specific (sorted to the top). The rest are adjacent embedded / systems / SWE / ASIC-DV loops, which Qualcomm runs through the same interview pipeline and question bank — directly relevant prep for camera roles.

Key patterns, timing & tricks (read before the entries)

Process shape - Camera / ISP / multimedia (US, e.g. San Diego/Santa Clara): recruiter screen (~30 min) → technical phone screen (~60 min, Senior Camera Engineer) → imaging/domain deep-dive (~60 min) → virtual onsite = 5 rounds, 5–6 hrs (image-processing+ISP architecture, C/C++ & embedded, camera driver+Android HAL, cross-functional w/ sensor/apps team, behavioral w/ Camera Eng Manager) → hiring-committee offer (1–2 weeks). - India systems / SWE / embedded (Hyderabad, Bangalore, Noida): often telephonic/screen + 3–5 technical rounds + HR/HM. Experienced candidates frequently get no online assessment, with the first 2 rounds back-to-back the same day. Freshers/campus usually start with an aptitude test (50–60 Q, negative marking).

Round durations: technical rounds run 45 min – 1.5 hrs (design/LLD rounds up to ~2 hrs); HR/HM rounds are short (10–30 min, sometimes finished early when feedback is already positive).

What gets asked (recurring across roles) - C/C++: pointers, dangling pointers, memory map, storage classes (auto/static), virtual functions/vtable/vptr, friend classes, struct vs class, inline, sizeof/memcpy (incl. overlap), endianness. - DSA: linked lists (reverse, detect/length of loop, merge k sorted, delete given node, reverse in k-groups), binary trees (max element, max path sum), bit manipulation, stack/queue, hashing, search/sort + complexity. - OS / embedded: processes vs threads, scheduling (incl. time-slicing), IPC, mutex/semaphore/deadlock, priority inversion, virtual memory/thrashing, watchdog, kernel↔user-space↔HAL, drivers. - Domain-specific: Camera/ISP — ISP pipeline (demosaic→denoise→color→tone-map), 3A (AF/AE/AWB), multi-frame HDR, noise reduction, green-tint debug, image interpolation, low-latency preview; Display — frame buffers, screen tearing / producer–consumer / reader-writer sync; Video — bit-rate control, codecs; CV/ML — backprop (dense + conv), ResNet/Inception/VGG, 1×1 conv, computer-vision pipeline. - Almost always: deep project / resume discussion ("be out-and-out clear on YOUR projects"), 1–2 puzzles (100 doors, chessboard rectangles/boxes, torch-and-bridge), and an HR/HM fit chat.

Tricks that candidates credit - Think aloud and collaborate (interviewers explicitly weight collaboration on whiteboard/ML rounds), ask clarifying questions, give multiple approaches + complexity, and explain visually before coding. - Be ready for open-ended design (Google Maps road-blocks, lift system, lottery machine, camera/driver architecture) with continuous cross-questioning and interviewer hints. - Nail the basics/memory ("almost everyone ignores basic topics"). On negative-marking aptitude, skip questions you're unsure of. - Ask the interviewer about the team/role — several candidates say it helped. Timing: next-round scheduling/feedback can come same day; some offers move fast (hire email next business day); India feedback sometimes clusters around specific dates.


Part A — Detailed individual experiences

(Sorted camera/ISP/display/video/CV/audio-ML first, then adjacent embedded/systems/SWE/ASIC-DV loops. Each entry: source URL · candidate context · rounds & how it went · timing · questions · tips.)

1. Camera Engineer (Spectra ISP / camera SW) — aggregated guide — CleverPrep

  • Source: https://www.cleverprep.com/companies/qualcomm/camera-engineer
  • Candidate / context: all levels; compiled from Glassdoor + LinkedIn + levels.fyi + candidate reports · San Diego / Santa Clara, US · guide reviewed Jun 2026 | Outcome: n/a (aggregated process guide, not one candidate) | camera/ISP/display-relevant
  • Rounds & how it went: Reported 5-stage process. (1) Recruiter screen — 30 min: camera/imaging background, driver or ISP experience, interest in mobile camera dev; recruiter explains the different camera teams (driver, ISP, algorithms, applications). (2) Technical phone screen — 60 min with a Senior Camera Engineer: image-processing fundamentals, camera system architecture, your camera project experience; expect C/C++ coding and systems questions. (3) Imaging deep dive — 60 min: ISP pipeline, image-processing algorithms, or camera-driver development depending on the role; discussion of your approach to image-quality optimization. (4) Virtual onsite (5 rounds, 5-6 hrs): (a) image processing + ISP architecture deep dive, (b) C/C++ and embedded systems programming, (c) camera driver + Android HAL discussion, (d) cross-functional interview with sensor or applications team, (e) behavioral with Camera Engineering Manager. (5) Offer decision — 1-2 weeks: hiring committee weighs imaging knowledge, embedded programming, and system-level debugging; ISP-tuning/computational-photography experience commands premium packages.
  • Timing: Recruiter 30 min; phone screen 60 min; imaging deep dive 60 min; virtual onsite 5-6 hrs (5 rounds); offer decision 1-2 weeks.
  • Questions asked:
  • Explain the ISP pipeline from raw sensor data to final image output.
  • How would you implement auto-exposure control for a mobile camera?
  • Design a noise reduction algorithm optimized for mobile processing.
  • Explain how multi-frame HDR works and its implementation challenges.
  • How would you debug a camera issue that causes green tint in images?
  • Design a camera driver architecture supporting multiple sensors.
  • Explain 3A (auto-focus, auto-exposure, auto-white-balance) algorithms.
  • How does computational photography enable night mode on smartphones?
  • Design a low-latency camera preview pipeline for real-time display.
  • Explain the trade-offs between image quality and processing speed.
  • [Behavioral] Tell me about a camera feature you developed that improved image quality.
  • [Behavioral] Describe a time you debugged a complex image quality issue.
  • [Behavioral] How do you approach trade-offs between latency and quality in camera?
  • [Behavioral] Tell me about your experience working with sensor vendors.
  • [Behavioral] Describe a project where you optimized camera power consumption.
  • [Behavioral] How do you approach debugging issues spanning sensor, ISP, and software?
  • Tips / tricks: Review ISP pipeline stages (demosaic, denoise, color correction, tone mapping). Understand camera system architecture sensor->ISP->driver->HAL->framework. Know 3A algorithms and implementation. Be ready to discuss mobile constraints (power, latency, thermal). Prepare image-quality debugging methodology. Research Spectra ISP. Understand Android camera architecture (Camera2 API, HAL3). Practice embedded C/C++. Hiring criteria: strong image-processing/ISP fundamentals; camera drivers + Android camera framework; embedded C/C++; sensors & image-quality metrics; debug skills; passion for computational photography.

2. Senior Engineer - Display team — LeetCode Discuss

  • Source: https://leetcode.com/discuss/post/5079058/qualcomm-senior-engineer-hyderabad-april-u7dw/
  • Candidate / context: 3.2 yrs; previously SDE-2 at a product-based MNC · Hyderabad · March 2024 (offer 1st week of April 2024) | Outcome: Offer (declined; took an Amazon counteroffer) | camera/ISP/display-relevant
  • Rounds & how it went: Applied via career page late Feb; recruiter call within 10 days; first two rounds scheduled back-to-back the same day; no written/online assessment. Round 1 - Coding 1 hr 10 min: intro + project discussion (10 min); C++/C fundamentals (45 min: processes, threads, dangling pointers; polymorphism types with examples and code; virtual and friend keywords; MCQ-style code output / compile-time vs run-time errors); Coding challenge: Merge k sorted lists, written fully on a shared whiteboard + time-complexity analysis + walkthrough. Round 2 - Design 2 hr 5 min: intro + project discussion (20 min); Q1 (1 hr) screen-tearing low-level design (CRT panel + SoC chipset sharing a single frame buffer; SoC=producer, panel=consumer; 120 FPS, 1 ms TAT; line-by-line display causes tearing) - design an algorithm to fix tearing, presented 3 solutions, discussion of synchronization like reader-writer problem; Q2 (30 min) another low-level design. Round 3 - Hiring Manager (scheduled 45 min, finished in 25 min): 100 doors puzzle (answer: perfect squares), divisibility rule of 11; positive verbal feedback.
  • Timing: Recruiter call within ~10 days of applying; Round 1 + Round 2 back-to-back same day; HM round scheduled 45 min but done in 25 min; hire email next business day; compensation finalized in 3-4 days.
  • Questions asked:
  • Merge k sorted lists (full solution on shared whiteboard + complexity).
  • Explain processes vs threads.
  • What is a dangling pointer?
  • Polymorphism - types, examples, and code samples.
  • Explain the virtual and friend keywords.
  • MCQ-style code output, compile-time vs run-time error questions.
  • Screen-tearing problem: CRT panel + SoC share one frame buffer (producer/consumer), 120 FPS, 1 ms TAT, line-by-line tearing - design an algorithm to fix it (reader-writer synchronization).
  • A second low-level design problem (30 min).
  • 100 doors puzzle - which doors remain open? (perfect squares).
  • Explain the divisibility rule of 11.
  • Tips / tricks: Display/multimedia systems loop leans on real hardware low-level design (frame buffers, producer/consumer, screen tearing, synchronization) plus solid C++ and one DSA whiteboard problem. No online assessment; rounds can be back-to-back same day; decisions come fast (hire email next business day).

3. Graphics Software Engineer — GeeksforGeeks

  • Source: https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-experience-set-9-experienced-linkedin-invite/
  • Candidate / context: experienced (1 year job experience in SAP BI, plus internship in Computer Vision) · Bangalore | Outcome: unknown | camera/ISP/display-relevant
  • Rounds & how it went: Reached out via LinkedIn invite; called for interview about 2 weeks after applying. Three rounds total. Round 1 (60 minutes): focused on the candidate's BE project (satellite image processing), data structures and algorithms, and OOP. Round 2 (30 minutes): focused on the candidate's Computer Vision internship and image processing concepts, plus hardware/software model design. Round 3 (30 minutes): a mix of C/C++ programming, scripting, data structures, SAP BI workflow, and logic/math puzzles.
  • Timing: Called for interview about 2 weeks after applying. Round 1: 60 minutes. Round 2: 30 minutes. Round 3: 30 minutes.
  • Questions asked:
  • Explain your BE project (Satellite image processing).
  • Explain graph traversal algorithms with code examples.
  • How do you detect a loop in a linked list?
  • Explain merge sort and quick sort with their complexity analysis.
  • How does the choice of pivot element impact quick sort complexity?
  • Implement binary search.
  • Explain OOP concepts: virtual functions, and overloading vs. overriding.
  • Find the intersection point of two linked lists (give two approaches: brute force and O(n log n)).
  • Tell me about your internship experience in the Computer Vision domain.
  • What are multidimensional images?
  • Explain masking operations.
  • Explain edge detection techniques.
  • Explain face detection methods.
  • Describe the general image processing workflow.
  • Explain image segmentation techniques.
  • How would you design a hardware simulation model?
  • How do you compare the output between hardware and software models?
  • What is the difference between malloc and calloc?
  • Write a Python script to find the number of occurrences of a word in a file.
  • Explain time complexity notations.
  • Write create and insert functions for a Binary Search Tree.
  • Explain access specifiers with examples.
  • Explain the steps in the SAP BI workflow.
  • Logic puzzle: Shape transformation with the minimum number of matchstick moves.
  • Math puzzle: Work completion timeline calculation.

4. Senior Engineer — Medium

  • Source: https://medium.com/@sumitpardhiya/qualcomm-senior-engineer-interview-experience-436b0f0fbc46
  • Candidate / context: experienced (had previously interviewed for the Engineer role); background in C++ and Python, lacked video processing experience | Outcome: no-offer | camera/ISP/display-relevant
  • Rounds & how it went: Two phases: remote rounds followed by face-to-face rounds the following Monday. REMOTE INTERVIEW (3 rounds, ~3 hours total, Friday 2-5 PM). Round 1 (1 hour): introduction, AI/ML and basic image processing questions, a torch/bridge crossing puzzle, and a basic string coding question. Round 2 (1 hour): 7 coding questions total - 3 bitwise operations, 1 linked list, 1 graph, 2 binary search; candidate answered all confidently. Round 3 (1 hour): team/work discussion, deep project discussion, 3 bitwise coding questions (all answered), and a debugging question involving pointers (struggled). FACE-TO-FACE ROUNDS (Monday). F2F Round 1: image processing questions, 5 coding questions on bitwise operations (solved 4), a rope-burning puzzle (solved), and C++ questions on mutex and semaphore (couldn't recall). F2F Round 2 (Managerial): discussion of comfort level with video processing, career motivation questions, and a code review on paper (3 errors, candidate solved 1). The candidate did not clear all the rounds and received no offer.
  • Timing: Remote rounds: Friday 2-5 PM, 3 rounds of 1 hour each (3 hours total). Face-to-face rounds held the following Monday.
  • Questions asked:
  • 4 people with crossing times 1, 2, 5, and 8 minutes, only two can cross with one torch — find minimum time
  • Basic string coding question
  • 3 bitwise operations coding questions
  • 1 linked list coding question
  • 1 graph coding question
  • 2 binary search coding questions
  • 3 bitwise coding questions
  • Debugging question with pointers
  • Image processing questions
  • 5 coding questions on bitwise operations
  • Two 60-minute ropes — measure 45 minutes?
  • C++ questions: mutex, semaphore
  • AI/ML and basic image processing questions
  • Video processing comfort level discussion
  • Career motivation questions
  • Code review on paper (3 errors)
  • Tips / tricks: Make sure to revise: OS concepts, OOPS concepts, DSA (especially bitwise operations), C/C++ (especially pointers).

5. Computer Vision Engineer — Medium

  • Source: https://medium.com/@sumitpardhiya/%EF%B8%8F-qualcomm-my-interview-experience-34bbdb7f27c3
  • Candidate / context: experienced, 3+ years in Machine Learning · January 2025 | Outcome: rejected | camera/ISP/display-relevant
  • Rounds & how it went: Single interview of 2.5 hours total, split into five 30-minute sections completed in order: (1) Introduction & Behavioral Questions (30 min) covering background, work experience, handling challenges, strengths and weaknesses, and problem-solving under pressure; (2) DSA (30 min) with two problems, each finished in ~15 minutes, moved to the next section early due to strong performance; (3) Computer Vision (30 min) testing domain expertise on CNNs, R-CNN, YOLO and various object detection architectures; (4) AI/ML & Real-World Scenarios (30 min) discussing real-world problem scenarios, model selection, optimization, evaluation, and deployment challenges; (5) Project Discussion (30 min) walking through major projects from dataset preparation to deployment with justification of technical choices. The author performed well overall but was ultimately rejected because the position was filled before a decision was made.
  • Timing: Applied via LinkedIn then Qualcomm career portal; shortlisted within 2 days; requested and received a 2-day preparation period; interview conducted after the preparation period; the interview itself ran 2.5 hours (five 30-minute sections); decision received about 1 week post-interview.
  • Questions asked:
  • Discuss your background and work experience
  • How do you handle challenges?
  • What are your strengths and weaknesses?
  • How do you approach problem-solving under pressure?
  • Solve two DSA problems (data structures & algorithms)
  • Questions on CNNs, R-CNN, YOLO and various object detection architectures
  • Real-world scenario questions on model selection, optimization, evaluation, and deployment challenges
  • Walk through your major projects from dataset preparation to deployment and justify your technical choices
  • Tips / tricks: Align your resume with the specific job description requirements; strengthen DSA problem-solving skills; prepare in-depth project walkthroughs with technical rationale; practice explaining your thought process clearly; emphasize communication and clarity during technical discussions.

6. Senior Engineer (Display team) — CodingKaro

  • Source: https://www.codingkaro.in/jobs-internships/leetcode-interview-experience/Qualcomm
  • Candidate / context: senior, 3.2 YOE · Hyderabad · March 2024 | Outcome: offer | camera/ISP/display-relevant
  • Rounds & how it went: Interviewed for the Display team. Received an offer in April 2024 but declined it for an Amazon offer. Candidate background: previously SDE 2 at a product-based MNC. Rounds included Hard DSA, system design, and puzzle/math questions.
  • Timing: Offer received April 2024; posted April 27, 2024
  • Questions asked:
  • Merge k Sorted Lists (Hard DSA)
  • Design Algorithm to Address Screen Tearing (System Design)
  • Design a Text Editor with Undo/Redo (System Design)
  • Door Flip Puzzle (DSA)
  • Explain Divisibility Rule of 11 (Other)

7. Camera Engineer — JoinTaro

  • Source: https://www.jointaro.com/interviews/companies/qualcomm/experiences/camera-engineer-san-diego-ca-august-22-2023-accepted-offer-positive-1fc32442/
  • Candidate / context: San Diego, California · August 22, 2023 | Outcome: accepted | camera/ISP/display-relevant
  • Rounds & how it went: Six rounds total, each with a different engineer. One round was an HR round. The remaining rounds focused on basic questions about understanding of algorithms. The candidate described the overall process as smooth.
  • Questions asked:
  • HDR-related question
  • How to find interpolated image between two images

8. Video Codec Engineer — JoinTaro

  • Source: https://www.jointaro.com/interviews/companies/qualcomm/experiences/video-codec-engineer-bengaluru-karnataka-october-29-2025-no-offer-positive-7cb1a305/
  • Candidate / context: Bengaluru, Karnataka · October 29, 2025 | Outcome: no-offer | camera/ISP/display-relevant
  • Rounds & how it went: The interview process was smooth but had multiple rounds. The questions were targeted at applications of video, and the process was quite positive and encouraging. Specific count, duration, and breakdown of rounds were not provided.
  • Questions asked:
  • How can you control the bit-rate of video?

9. Qualcomm (general / unspecified engineering role) - generic article, not a personal candidate experience — foundit

  • Source: https://www.foundit.in/career-advice/qualcomm-interview-questions-to-help-you-prepare-for-your-interview-at-qualcomm/
  • Candidate / context: Article last updated 30th January 2025 (page header also shows '2026 UPDATED'); by Team foundit | Outcome: unknown | camera/ISP/display-relevant
  • Rounds & how it went: This is a generic prep article ('Most Asked Qualcomm Interview Questions'), NOT a personal candidate interview experience. It describes the typical Qualcomm interview process as: 1 telephonic round, 5 technical rounds, and 1 HR round. Each round is scheduled for approximately 45 minutes. The article notes the exact process can change based on job, level, and location. The FAQ restates the process: phone screen, followed by 5 technical interviews, then an HR round, each lasting about 45 minutes. No individual candidate, role, location, date, or outcome is given. Questions below are general SWE/embedded/systems/CS questions; none are camera/ISP/multimedia-specific.
  • Timing: Process described as 1 telephonic round + 5 technical rounds + 1 HR round; each round approximately 45 minutes. No overall multi-day/multi-week timeline or candidate-specific timing is given.
  • Questions asked:
  • Tell me the difference between stack and heap memory.
  • Describe a few deadlock avoidance schemes.
  • Implement the malloc() and free() operations. Describe only the strategy for doing so, not the code.
  • What is "I" in ACID properties?
  • Describe the virtual function in C++.
  • A window of size k is sliding from left to right in an array of size n. Find out the maximum number in the window at each window position.
  • What do you understand by clustering index?
  • Describe your final year project in detail. How would you describe your role in the same?
  • There is a program which inserts and deletes node in a sorted singly linked list. There is a bug in one of the modules. Give us a method of debugging it.
  • What are the various techniques by which fault tolerance can be ensured in systems? (Different redundancy techniques)
  • A pair of redundant systems is operating. Give us a method of ensuring that when one of them goes down, the other one will take over its operation.
  • Suppose a 4-inch cube is painted on all the sides. If this piece is cut into smaller cubes of side 1 inch each, how many cubes will be left unpainted at all?
  • Devise a program to check whether a binary tree is BST or not.
  • Supposing that two of the nodes of a Binary Search Tree (BST) are interchanged, give us a method to fix (or correct) this BST.
  • Out of given choices, pick out the Super Key from the lot.
  • Questions based on function pointers and its usage.
  • Devise an algorithm to check if there is a loop in a doubly linked list.
  • Considering GRANT is used to grant privileges to perform the queries, specify the command which is used to remove these permissions.
  • Write a program to delete a node, given only a pointer to the node in a circular linked list.
  • Questions on call back functions.
  • How would you define HADOOP? Describe the underlying principle of HADOOP and illustrate some of its features like Map Reduce?
  • Describe some salient features of the cloud?
  • Write a program to return a stream of bytes from a function.
  • What do you understand by the term cloud computing?
  • Describe the difference between a Public and Private cloud.
  • Write a code to reverse a single linked list.
  • Introduce yourself.
  • Can you describe yourself in three words?
  • Tell me about your family/Tell me about your family background.
  • What have been your highs and lows in the four years of college life?
  • Tell me one thing you hate the most.
  • What do you know about our competitors?
  • Why do you want to join Qualcomm?
  • Why should we hire you over other candidates?
  • You have been through the pre-placement talk. Tell us a few negatives about the presentation and how can we improve next time onwards.
  • We have undergoing projects all over India. Will it be feasible for you as an employee if your job profile requires regular travelling or relocation to a place away from your current city?
  • At Qualcomm you might have to do multiple tasks such as attend meetings related to your work as well as complete work for your client. How will you cope up with the same?
  • Logical or choice-based questions: You have a cake. Describe a method to divide it into eight pieces using only three lines.
  • How do you define your goals in life? Do you make plans and strategies for the future or grab opportunities as they come?
  • Would you be interested in changing your domain? If yes, why?
  • Why did you sit for the interviews for this company?
  • Describe a situation wherein you were asked to do something you didn't like? How did you handle it?
  • What do you expect from our organisation?
  • Will you be comfortable in relocating?
  • Has there ever been a situation wherein you weren't able to complete your task in time and therefore had to take a quick decision to manage the situation?
  • What extra-curricular activities are you involved in?
  • Tips / tricks: To clear Qualcomm interviews, work strongly on domain knowledge since the technical rounds heavily test subject knowledge. For technical rounds: review technical skills, practice coding problems, and study Qualcomm's technologies and products; be ready to discuss your projects. For HR rounds: reflect on professional experiences, practice common HR questions, and align responses with Qualcomm's values and culture. Be well-prepared and confident. Qualcomm values strong technical skills, problem-solving abilities, adaptability, teamwork, and a passion for innovation.

10. Computer Vision Engineer — CodingKaro

  • Source: https://www.codingkaro.in/jobs-internships/leetcode-interview-experience/Qualcomm
  • Candidate / context: experienced, 3 YOE · January 2025 | Outcome: unknown | camera/ISP/display-relevant
  • Rounds & how it went: A single 2.5-hour interview with five sections covering behavioral, DSA, Computer Vision, AI/ML, and project discussions.
  • Timing: 2.5 hours total; posted December 13, 2025
  • Questions asked:
  • Handling Challenges (Behavioral)
  • Strengths and Weaknesses (Behavioral)
  • Problem-Solving Under Pressure (Behavioral)

11. Machine Learning and System Engineer — GeeksforGeeks

  • Source: https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-experience-for-ml-and-system-engineer/
  • Candidate / context: fresher (on-campus) · India (on-campus / college recruitment) · October 2023 | Outcome: offer | camera/ISP/display-relevant
  • Rounds & how it went: Process began with a CV review followed by an online screening test, then two technical rounds and an HR round. Online Test (screening) had three sections: Aptitude, Basic C/C++ programming, and an Optional subject (ML / Signal Processing / CS). Technical Round 1 (~50-55 minutes): started with a 2-3 minute self-introduction, two C coding questions on trees and graphs, resume project explanation, internship discussion, then ML/deep-learning and computer vision questions. Technical Round 2 (~1 hour): focused on C/C++ proficiency, OS/kernel concepts, data structures and memory management, with coding tasks and a code-error identification task. HR Round (~10 minutes): role clarification, location preference and general questions.
  • Timing: Online test for screening, then Technical Round 1 ~50-55 minutes, Technical Round 2 ~1 hour, HR Round ~10 minutes. On-campus recruitment in October 2023.
  • Questions asked:
  • Tell me about yourself (self-introduction, 2-3 minutes)
  • Two C coding questions on trees and graphs
  • Explain a project from your resume
  • Back-propagation algorithm in Dense Network, Back-propagation in Convolution Network
  • Write a C program for Back-propagation in Conv Network
  • Tell me about your Computer Vision experience; architectures of Inception, VGG
  • Explain the architecture of ResNet? Advantages of ResNet?
  • How 1x1 Convolution reduces computation?
  • Write a program to find whether a number is a power of two
  • Explain Semaphore, mutex, locking, and threading
  • What is a deadlock in OS? What are the necessary conditions for a deadlock?
  • Write a program to find the intersection of two linked lists (in C)
  • Write a clean implementation of the stack (any method)
  • How is memory allocated in C during malloc and calloc?
  • How do you know whether a memory is in use or free?
  • What are dangling pointers?
  • Identify the error in the given code
  • What is a segmentation fault?
  • Tips / tricks: Use mnemonic variable/function names; modularize code; handle edge cases; explain your approach before coding; walk through your code aloud; address edge cases explicitly.

12. Associate Software Engineer (Off-Campus) — GeeksforGeeks

  • Source: https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-experience-for-associate-software-engineer-off-campus/
  • Candidate / context: fresher / entry-level · Last Updated July 23, 2025 | Outcome: offer | camera/ISP/display-relevant
  • Rounds & how it went: 4 virtual rounds conducted via Microsoft Teams. Round 1 (Technical Screening, 45 min): introduction followed by discussion of projects and internship experience, then two coding problems (linked-list focused) and OOP concepts. Candidate advanced to Round 2. Round 2 (Technical Assessment, 45 min): began 5 minutes after Round 1 on the same call; covered multithreading (based on candidate's project), inheritance and C++ concepts, procedural vs object-oriented programming, and resume-based questions (certifications, hobbies). Round 3 (Technical Deep Dive, 1 hour): began 5 minutes after Round 2; interviewer provided continuous hints throughout. Round 4 (Design Round, 1 hour): occurred after a 1-day gap; 2 open-ended design problems with continuous cross-questioning and interviewer hints, plus motivation/technology-interest questions.
  • Timing: 3 days total. Rounds 1, 2 and 3 occurred on the same day/call: Round 1 (45 min), then Round 2 began 5 minutes after Round 1 on the same call (45 min), then Round 3 began 5 minutes after Round 2 (1 hour). Round 4 (Design Round, 1 hour) occurred after a 1-day gap.
  • Questions asked:
  • Find the nth node from the end of a linked list (with expectation of multiple approaches)
  • Find the length of loop in a linked list
  • Object-oriented programming concepts: method overloading vs overriding, abstraction, static methods and variables
  • Print odd and even numbers sequentially using two different threads
  • Types of inheritance in C++ and resolution of ambiguity in multiple inheritance
  • Compare procedural and object-oriented programming with examples
  • Implementation of hash table
  • Implement your own immutable class
  • Difference in value manipulation when passing arrays and vectors to functions
  • Difference between static and dynamic binding
  • Multithreading memory structure, resource sharing, inter-process communication, deadlocks
  • Types of linked lists and their use cases
  • UML Association vs Aggregation vs Composition
  • Design a Lottery Machine: generate non-repeating random numbers from 1 to N, eliminate the corresponding lottery ticket holders, continue generation from the last eliminated person's position (circular queue treatment), continue until one winner remains, log all operations, and ensure modular, readable code
  • Design a Lift Management System (open-ended, with candidate discretion on defining actors, displays/console, operations, and switches)
  • Motivation for joining Qualcomm and technology interests
  • Tips / tricks: GFG archives is the key to crack it; questions follow a definite pattern and are mostly repeated. Use the 'Draw on Page' Chrome extension to better explain approaches. Believe in yourself.

13. Software Developer — Medium

  • Source: https://medium.com/@manishaagarwal/the-interview-story-experience-of-a-software-developer-part-1-qualcomm-90ad3a7a7d79
  • Candidate / context: fresher (2017 graduate, Electronics and Communication Engineering, NIT Durgapur) · Hyderabad (Qualcomm office) · 2017 (offer received December 20, 2017) | Outcome: offer accepted | camera/ISP/display-relevant
  • Rounds & how it went: Process started with an online screening test (aptitude, programming, operating systems and computer architecture; difficulty easy to medium, the main challenge being the length of the test rather than the complexity). After clearing it, an onsite interview was scheduled one week later, consisting of four interview rounds: rounds 1-2 focused on operating systems and computer architecture (candidate felt confident), and rounds 3-4 were more challenging (candidate uncertain). Lunch was provided between rounds (vegetable biryani and a chocolate donut). The candidate's profile was initially put on hold, then a second opportunity came via a phone interview (scheduled on a Thursday) focused on operating systems, computer architecture, DBMS and computer networking. Candidate was at Amdocs, Pune at the time. Offer was 15 lakhs INR per year (a 150% salary increase).
  • Timing: Online test was the initial screening round. Onsite interview scheduled one week after clearing the online test (four rounds in one day with lunch in between). After an initial profile hold, a phone interview was scheduled on a Thursday as a second opportunity. Offer received December 20, 2017; start date March 5, 2018.
  • Tips / tricks: Preparation resources used: GeeksforGeeks (operating systems, computer architecture, networking, and Qualcomm-specific questions), C/C++ programming refresher, data structures and algorithms, Linux and Git concepts, and W3Schools web development topics. Preparation timeline was one week of intensive study (waking at 7am, 1 hour of morning study, sneaking in study sessions at the office, and 3 hours of evening revision). Mindset advice: adopting a "worst case scenario is, I would be laughed out at the Interview" attitude helped overcome fear; persist through setbacks (the initial profile hold did not deter further attempts); and avoid excessive expectation-setting during waiting periods. No specific interview questions were detailed verbatim in the article.

14. Engineer — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer
  • Candidate / context: experienced (not specified) · Posted 11 Oct 2024 | camera/ISP/display-relevant
  • Rounds & how it went: Single one-on-one round. Interview experience rated 3/Average. Round 1 - One-on-one (1 question): tell me about the challenging project.
  • Timing: Process duration not specified
  • Questions asked:
  • Tell me about the challenging project

15. Software Engineer (kernel / embedded) — LeetCode Discuss

  • Source: https://leetcode.com/discuss/post/4972418/qualcomm-software-engineer-hyderabad-feb-d2yg/
  • Candidate / context: 1 yr 10 months; SDE-1 at MNC; based in Noida · Hyderabad · Feb 2024 (posted Apr 2024) | Outcome: Offer | camera/ISP/display-relevant
  • Rounds & how it went: 3 rounds over 2 days; no written/online assessment. Round 1 - Technical phone screen 1-1.5 hr (Day 1): intro + previous work (kernel bootloader issue debugging, code integration), project discussion, kernel debugging from logs, kernel drivers, kernel<->user-space comm, zygote, static keyword, friend classes, stack vs heap, malloc/calloc/realloc, multiply two numbers (many approaches), code-snippet outputs, time-slicing scheduling. Round 2 - Technical: dangling pointer + how to avoid, struct vs class, design patterns (why), pointer vs reference (which is better), kernel<->HAL comm, memory leaks (identify + prevent), Google Maps design (how to handle road blocks). HR called same evening to schedule Round 3 (positive feedback). Round 3 - Hiring Manager + Technical 30 min (Day 2): C language, kernel/pointers/memory management, kernel<->user-space, writing a user application on an embedded system that has no kernel.
  • Timing: Day 1: rounds 1 and 2; HR call same evening; Day 2: HM round (30 min). No online assessment.
  • Questions asked:
  • Delete a given node from a linked list (with code).
  • Count the occurrence of each letter in an array without extra space.
  • How do you debug kernel issues from logs?
  • How does the kernel communicate with user space?
  • What is the function of zygote?
  • When do we use the static keyword (and follow-ups)?
  • Friend classes and their use.
  • Difference between stack memory and heap memory.
  • malloc vs calloc vs realloc.
  • If you want to multiply two numbers, how would you do it? (discuss many approaches)
  • Code-snippet output questions.
  • Time-slicing scheduling; is time slicing a good choice for a game developer's scheduling algorithm?
  • 100 doors puzzle.
  • What is a dangling pointer and how to avoid it?
  • struct vs class.
  • What are design patterns and why use them?
  • Pointer vs reference - which is better?
  • How does the kernel communicate with the HAL?
  • What are memory leaks, how do you identify them in code, and how to prevent them?
  • How does Google Maps work / manage road blocks? If you were to design Google Maps, how would you identify and handle road blocks causing extra time?
  • How would you write a user application on an embedded system that has no kernel?
  • Tips / tricks: Loop is kernel/driver/embedded heavy (kernel<->user-space/HAL, memory management, scheduling) plus standard C/C++ and DSA; expect an open-ended system design (Google Maps). Feedback and next-round scheduling can happen same day.

16. System Software Engineer — Medium

  • Source: https://medium.com/@PranabNandy/qualcomm-interview-experience-2e0edc562d42
  • Candidate / context: fresher · NIT K, Surathkal (on-campus) · April 16, 2023 | Outcome: offer | camera/ISP/display-relevant
  • Rounds & how it went: 4 rounds total: 1 written test, 2 technical interviews, and 1 HR round. Written Test (video proctored on HirePro): Section 1 was an Aptitude Section (20 questions), Section 2 was a C/C++/OOPS/Java Section (20 questions), and Section 3 had 20 questions (topic unspecified). Scoring was +1 for correct and -0.25 for wrong; the candidate attempted 52 of 60 questions. About 55 students were shortlisted from roughly 500 applicants. First Technical Round was conducted over Microsoft Teams/HackerRank and covered memory hierarchy, cache memory, CPU functions, cache coherence in multiprocessor systems, multithreading vs. multiprocessing, how a program is executed by the OS, critical sections, synchronization, race conditions, and binary semaphores vs. mutexes. Second Technical Round covered project explanation with cross-questioning, DSA (array and string questions), a focus on the preprocessor, bitset usage and questions, and OS topics including paging, virtual memory, and synchronization. HR Round was conducted via phone call around 7:00 PM with formal questions. Final results: 8 total placements (4 software + 4 hardware positions).
  • Timing: First Technical Round: 45 minutes. Second Technical Round: 45 minutes. HR Round: phone call around 7:00 PM. Interview date April 16, 2023. ~55 students shortlisted from ~500 applicants after the written test.
  • Questions asked:
  • Implement memcpy function
  • Implement binary semaphore (with follow-up questions)
  • 2 threads are there where one is printing odd number and other one is printing even number and use mutex to synchronize
  • check whether a number is power of 2 or not within O(1) time complexity without using pow,log2 inbuild functions
  • Tips / tricks: Written test scoring penalizes wrong answers (-0.25), so be selective when unsure. Be strong in OS fundamentals (memory hierarchy, cache, synchronization, semaphores vs mutexes, paging, virtual memory), C/C++ implementation (memcpy, binary semaphore, thread synchronization with mutex), bit manipulation, and the preprocessor. Be ready for project cross-questioning and DSA array/string problems.

17. SDE-1 (Software Development Engineer) — Medium

  • Source: https://medium.com/@barath_natarajan/qualcomm-sde-1-interview-experience-c5fcbec3314e
  • Candidate / context: fresher with 8 months of experience; B.E. Electronics from Anna University Guindy · Chennai, India (Qualcomm Chennai) · February 25, 2024 | Outcome: offer | camera/ISP/display-relevant
  • Rounds & how it went: Two rounds total - one online and one in-office at Qualcomm Chennai. Round 1 (Online, 1 hour): three coding problems followed by questions on personal projects and previous work experience; candidate provided optimal solutions. Round 2 (In-office, ~2 hours): a DSA question, Docker/Kubernetes hands-on written on paper, theory on Kubernetes and computer networks, a system design discussion of a previous C++ product, SQL vs NoSQL plus a SQL query (candidate struggled here), database key concepts, project deep-dives, rapid-fire behavioral scenarios, and personal questions. Candidate performed well overall except the SQL problem but was still selected.
  • Timing: Two rounds. Round 1 online lasted 1 hour. Round 2 in-office lasted approximately 2 hours. Interview date February 25, 2024.
  • Questions asked:
  • Single Number problem (LeetCode)
  • Count Array Pairs Divisible by K problem
  • String compression: given a string say AABCCC, return it as 2A1B3C, with constraint that 13 A's should print as 9A4A
  • Maximise the number of toys that can be purchased with amount K (DP approach similar to coin change)
  • Write a Dockerfile for a Python app, build image commands, container run commands, and local Kubernetes deployment (written on paper)
  • Kubernetes theory questions
  • Computer networks questions
  • Explain your previous C++ product, your contributions, and the development lifecycle
  • SQL vs NoSQL comparison and write a SQL query
  • Difference between Primary Key and Foreign Key
  • Node.js and Python project discussions
  • Behavioral (rapid-fire): how do you handle deadline conflicts?
  • Behavioral (rapid-fire): describe your problem-solving approach
  • Behavioral (rapid-fire): how do you handle unfamiliar tasks?
  • Behavioral (rapid-fire): how do you handle urgent customer requests?
  • Personal questions about hobbies and family
  • Tips / tricks: Be prepared to give optimal solutions to coding problems and to discuss your personal projects and prior work experience in depth. Expect practical DevOps (Docker/Kubernetes written on paper) and computer networks theory. Brush up on SQL/NoSQL and SQL query writing (a noted weak spot). Be ready for rapid-fire behavioral scenario questions. Note: the candidate struggled with the SQL question but was still selected, suggesting overall performance matters.

18. Software Engineer (Campus Placement, full-time) — GeeksforGeeks

  • Source: https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-experience-2/
  • Candidate / context: fresher · Last updated July 14, 2025 | Outcome: offer | camera/ISP/display-relevant
  • Rounds & how it went: Round 1 - Online Assessment (90 minutes): 3 sections of 20 questions each, 30 minutes per section, scoring +1 for correct and -0.25 for wrong. Section 1: quantitative aptitude, logical reasoning, data interpretation, verbal (medium-hard). Section 2: programming - pointers, structures, memory, bit manipulation (easy-medium). Section 3: computer science - DBMS, operating systems, networks (easy-medium). Round 2 - First Technical Interview: covered structures/unions, memory allocation, processes, threading, OS concepts, bit manipulation, a DSA problem, and a logic puzzle. Round 2 - Second Technical Interview: resume-based and ML project discussion, system calls, OS internals, compiler phases, libraries, cache, scheduling, unions, and a linked-list problem. Round 3 - HR Interview (20 minutes): self-introduction, motivation, background, and relocation preferences. Overall 22 candidates were selected for full-time roles.
  • Timing: Online Assessment: 90 minutes total (3 sections x 30 minutes). HR Interview: 20 minutes. Other round durations not specified.
  • Questions asked:
  • concept of padding in structures
  • How memory is allocated using calloc and malloc functions
  • How is free keyword different from delete
  • How does free() know the size of memory to be deallocated?
  • difference between global variables and static variables
  • extern keyword (variable scopes)
  • Void pointers
  • Threading and pThread concepts
  • Page fault and steps followed to handle it
  • How to check if a given number is a power of 2, only using bitwise operators
  • N meetings in a room problem
  • Three boxes, one contains only apples, one contains only oranges, one contains both. Opening just one box, and without looking in the box, you take out one piece of fruit. By looking at the fruit, how can you immediately label all of the boxes correctly?
  • Resume-based questions
  • Machine Learning project explanation
  • Different System calls and why do we use them
  • Difference between Kernel and Operating System
  • Different phases of Compiler and in-detail explanation
  • How compiler does intermediate code optimization?
  • What are Static and Dynamic Libraries?
  • Why do we use Cache Memory?
  • What is Cache Coherence Protocol
  • Difference between Scheduler and Dispatcher
  • Union applications and problems
  • How to detect and remove the loop from the Linked List
  • Brief self-introduction (HR)
  • Motivation for joining Qualcomm
  • Location/relocation preferences
  • Tips / tricks: In the online assessment, try to answer only the questions you know (due to negative marking of -0.25 per wrong answer).

19. Software Engineer (FTE, On-Campus) — GeeksforGeeks

  • Source: https://www.geeksforgeeks.org/interview-experiences/qualcomm-fte-interview-experience-for-software-engineer-on-campus/
  • Candidate / context: fresher · On-campus (virtual due to college closure) · August 14, 2021 | Outcome: offer | camera/ISP/display-relevant
  • Rounds & how it went: Eligibility: circuit branches (CSE, ECE, EEE), B.Tech and M.Tech, minimum CGPA 6.9. Selection funnel: 250+ applications -> 45 selected for technical rounds -> 12 final selections. Round 1 (Online Test/Screening): MCQ-based, video-proctored on HirePro platform, covering C/C++ code outputs, data structures, debugging, Operating Systems, OOP, and Combinatorics; difficulty medium-hard; 45 students advanced. Round 2 (Technical Interview 1): conducted on Microsoft Teams with HackerRank CodePair, ~1 hour 10 minutes; began with self-introduction and discussion of Samsung summer internship project, then OS questions, C++ in-depth questions, and DSA coding problems; candidate also asked the interviewer questions about working at Qualcomm, Snapdragon, and Qualcomm's leadership in wireless/4G/5G. Round 3 (Technical Interview 2): on Microsoft Teams, ~1 hour 50 minutes; thorough resume discussion, leadership/soft-skills questions, Computer Networks, IPC and Socket Programming (candidate highlighted experience and was asked to elaborate on building a chat system using IPC), Operating Systems, Computer Architecture, and several DSA/C++ coding problems on CodePair plus a puzzle. Round 4 (HR Call): after about an hour of waiting; formal HR questions, no additional technical rounds, immediate offer communication; selection confirmed after ~1 hour. Note: technical rounds were variable (2-4 per candidate); this candidate had 2 technical rounds. Total selected: 12 candidates.
  • Timing: Round 2 (Technical Interview 1): approximately 1 hour 10 minutes. Round 3 (Technical Interview 2): approximately 1 hour 50 minutes. Round 4 (HR Call): began after about an hour of waiting; selection confirmed after approximately 1 hour. Overall flow: Online test -> 45 candidates to technical rounds -> technical rounds (variable 2-4 per candidate; this candidate had 2) -> HR call -> 12 candidates finally selected.
  • Questions asked:
  • Introduce yourself
  • Discuss your summer internship project (Samsung)
  • Why is Disk Scheduling needed and what are different types of Disk Scheduling algorithms
  • Implement the best disk scheduling algorithm and discuss its efficiency
  • What are different types of memories present in a Computer system?
  • Follow-up on cache working, cache types, and LRU cache data structures
  • What are different types of pointers?
  • Volatile Keyword
  • Memory allocation of a c++ program
  • Create a Singleton Class (using private destructor, static object creation)
  • new and delete keywords (Dynamic Memory Allocation)
  • Given a sentence in the form of a string, reverse the words in it and print the sentence
  • Create a linked list and sort the list containing integers (discussion of merge sort vs. quick sort for linked lists)
  • Discussion on recursion and memory allocation done during recursion (call STACK memory) and about Dynamic Programming
  • OSI Model and about all the 7 layers with examples
  • TCP/IP Model and many follow-up questions on it
  • What are a switch, hub, and router? What layer of the TCP/IP model are they related to?
  • What is Port addressing?
  • Difference between IP Address and MAC Addresses, how they help in communication between 2 different networks
  • Inter Process Communication and follow-up questions like pipes, fifos, message queues, semaphores, and some codes on them about creation and working
  • Elaborate on creating a chat system using IPC
  • What are Deadlocks, Spinlocks, and their differences?
  • Difference between Mutex locks and Semaphores
  • Threads and asked to write pseudocode to implement deadlocks on threads
  • Difference between a process and program
  • Thread memory allocation in a multi-threaded process
  • Memory Management and why paging was needed (fragmentation discussion)
  • What are different Endians in a computer system? Write a c++ code to show if our system's endianness is big or little
  • What are buses and their types in a computer system?
  • Allocate memory dynamically (Heap memory) and then differences between stack memory and heap memory
  • Write a C++ code to implement stack overflow and heap memory overflow
  • What is pass-by value and pass-by reference? Write a code to implement it and explain the memory level working of it
  • Given a string remove the extra spaces and reverse the odd positioned words in the string
  • Given a linked list for example 1->2->3->4->------>n change the last node to first node and then return the list. i.e return n->1->2->3->---->n-1
  • Given a linked list of names represented in the form of names and is arranged in dictionary order, insert a new name at the correct position in the list of names
  • Given a encoded string in the binary form convert it into decimal form. For example if the string is "a10101b001c11" then the output should be "a21b1c3" as 10101 = 21, 001 = 1 and 11 = 3 in decimal forms
  • Given a Preorder array of a Binary Search Tree how many other permutations of the given bst will form the same BST as the given preorder (Example: preorder "4, 1, 3, 2, 5, 7, 6, 8, 11, 10" with answer "(n-1)p(elements < pre[0])" or "9p3")
  • 3 bulbs and 3 switches puzzle - find correct pairing
  • Tips / tricks: Confidence is the key. Had very little time to prepare due to ongoing internship, so used time efficiently, worked hard to thoroughly revise all concepts, and practiced coding. Talking to the interviewers helps a lot. Don't bluff in the interviews, it won't help. Be thorough with the resume. Discuss with your friends while preparing - that will help a lot. Focus on concept revision rather than cramming.

20. Software Engineer (SDE) — GeeksforGeeks

  • Source: https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-experience-for-sde-off-campus-2023/
  • Candidate / context: experienced, 1.5 years · Chennai · 2023 | Outcome: offer | camera/ISP/display-relevant
  • Rounds & how it went: Off-campus process with four technical rounds; rounds 1-2 were initial technical screens and rounds 3-4 were conducted on-site. Round 1 covered background on previous company/role, C programming fundamentals, bit manipulation, data structures (linked lists), and logic puzzles. Round 2 covered academic projects, string and linked list manipulation, OS concepts, sorting algorithms, and puzzles; candidate was shortlisted for the on-site after this round. Round 3 was a managerial/on-site round covering behavioral competencies, project discussion, advanced OS concepts, data structure design, bit manipulation, and system-level knowledge. Round 4 covered project discussion, string manipulation, algorithm optimization, concurrency/synchronization, and system calls. Candidate was selected.
  • Timing: Four technical rounds total; rounds 1-2 initial technical screens, rounds 3-4 on-site. No specific per-round durations or overall timeline given on the page.
  • Questions asked:
  • Write a C program to get the size of variable without using sizeof()
  • How to divide a number with 4 without using division operator?
  • What are the different types of Linked Lists?
  • Create a Linked List and insert a Node at given position
  • Various puzzle questions (Round 1)
  • Write a program to Reverse a String
  • Write a program to Reverse a Linked List
  • Write a program to Reverse a Doubly Linked List
  • What is process? What is Thread? Difference between Process and Thread?
  • What are Software Interrupts? Explain different types of interrupts?
  • Implement MERGE SORT
  • Various puzzle questions (Round 2)
  • What is your greatest Achievement?
  • Define a data structure for storing 12 bits of data
  • What is process?
  • What is context switching?
  • What are different types of scheduling algorithms?
  • Working of Round Robin Algorithm
  • How Process is created?
  • What is process table? What is PCB (Process Control Block)? What are different types of attributes in PCB?
  • How does OS perform context switching?
  • What happens when we press a keyboard key? (covering hardware, OS, and CPU levels)
  • What is system call?
  • What is User space and kernal space?
  • Explain the memory layout of process
  • Insert a Node at given position in a Linked List?
  • Count the number of set bits in a given number
  • Puzzle requiring C programming solution (Round 3)
  • Given an input string s, reverse the order of the words. A word is defined as a sequence of non-space characters...
  • Given arrival and departure times of trains reaching a station, find the minimum platforms needed so no train waits
  • What is mutex?
  • What is spin lock?
  • What is Critical Section?
  • Given 2 resources and 4 threads. One thread locked the CS. How do other threads acquire the CS?
  • What are System Calls? Different types of system calls?
  • Tips / tricks: Focus preparation on: Core DSA (linked lists, string manipulation, sorting algorithms); low-level C (sizeof alternative approaches, bit manipulation); Operating Systems (processes, threading, context switching, scheduling, PCB, system calls, memory layout); Concurrency (mutex, locks, critical sections); and problem-solving via logic puzzles and system-level thinking.

21. Audio ML / Speech ML Engineer (role assumed by author from the questions; not explicitly stated) — Medium

  • Source: https://medium.com/@k25296858/qualcomm-interview-experience-02c701880080
  • Candidate / context: Dec 11, 2025 (article publication date) | Outcome: unknown | camera/ISP/display-relevant
  • Rounds & how it went: The article describes a single technical interview round focused on machine learning fundamentals, deep learning, audio/speech processing, transformers, CNN training, and ASR architectures. It is written as a summary of the topics/areas the interviewer evaluated rather than a round-by-round transcript. No number of rounds, interviewer count, or per-round flow beyond this technical discussion is given.
  • Timing: Not provided. No per-round durations or overall timeline given in the article.
  • Questions asked:
  • Explain the end-to-end training pipeline for a neural network (data preparation, augmentation, feature extraction, batching, loss functions, optimizers, and evaluation)
  • How would you use a CNN for audio, taking spectrogram inputs and CNN feature learning, for Alexa wake-word recordings?
  • How would you augment clean Alexa audio (e.g., with noise, reverb, pitch shift, time stretch)? (MUSAN datasets, SNR mixing, SpecAugment)
  • Explain the Adam optimizer (first/second moments, bias correction, typical hyperparameters such as lr=1e-3, betas=(0.9, 0.999))
  • Explain the Whisper architecture (encoder-decoder design with convolutional front-end and transformer components)
  • Explain an encoder-decoder translation / seq2seq architecture with cross-attention mechanisms
  • Compare LSTM vs Transformer (computational requirements and parallelization differences)
  • Explain audio processing from STFT to mel-scale conversion via filter bank multiplication
  • How would you handle wake-word detection false positives (e.g., 'Alex' vs 'Alexa')?
  • Tips / tricks: Preparation tips from the article: Prepare a concise ML training pipeline script; memorize the Whisper architecture flow; write a small CNN training template; prepare examples of audio augmentations; prepare an LSTM vs Transformer comparison; prepare a mel filter bank explanation with matrix shapes.

22. Embedded SW Application Developer — GeeksforGeeks

  • Source: https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-set-2/
  • Candidate / context: experienced (telecom domain, C/RTOS/Data structures) · Qualcomm office | Outcome: rejected (rejected for this position but considered for another role)
  • Rounds & how it went: First interview process consisted of 1 Telephonic + 5 Technical + 1 HR round, each lasting 40 min to 1 hr. Telephonic round first, then on-site within 2 days. Telephonic: CV discussion, lots of questions on project and how it actually works, OS concepts with real examples, deadlock situations, software watchdog timers, OS schedulers, error handling/core dumps, memory management, IPC, mutex/critical section/semaphores; all asked in depth, candidate needed to convince the interviewer. Round 1: basics of C, memory map of program, storage classes and mapping, variable storage when exceeding registers, IPC signal implementation, code snippets to debug. Round 2: basic C, linked list and pointer programs. Round 3: generic project questions, SIM card/embedded memory handling, OS priorities, process vs thread, void pointers. Round 4: string/linked-list programs, software development process, project and career questions. Round 5: endianness, memory questions, memcpy implementation, library vs system call, priority inversion. Round 6 (HR): aspirations, culture fit, casual discussion with feedback on performance.
  • Timing: Telephonic round, then on-site within 2 days. 1 Telephonic + 5 Technical + 1 HR round, 40 min to 1 hr each.
  • Questions asked:
  • OS concepts with real examples
  • Deadlock situations (detection, prevention)
  • Software watchdog timers
  • OS schedulers and algorithms
  • Error handling, core dumps
  • Memory management concepts
  • IPC communications
  • Mutex/critical section/semaphores
  • Basics of C programming
  • Memory map of program, storage classes and their mapping
  • Variable storage when exceeding available registers
  • IPC (signal implementation); code snippets to debug with output identification
  • Write a program to Delete a node, given only a pointer to the node in a Circular linked list
  • Accessing data in called functions after return (auto variables limitation)
  • Write a program to return a stream of bytes from a function
  • Function pointers (how, usage, examples)
  • Generic project questions (market values, upcoming products)
  • Memory handling in SIM cards/embedded applications
  • Priorities of OS programs, process and thread differences
  • Handling generic functions with void pointers
  • Write a own program for strstr function, optimal way
  • Write a program to convert a given single Linked list to BST
  • Software development process and product development approach
  • Career aspirations (1-year outlook)
  • Big & Little endian – definitions, representations, write it down, swap them, etc
  • Write a program to implement memcpy() on your own (including overlap situations)
  • Difference between library call and a system call
  • Priority inversion in a RTOS and its solutions
  • Qualcomm aspirations and culture fit
  • Tips / tricks: Be out and out clear with your projects and CV. All interviewers will explain about the position you have applied for and it is good if you ask more questions on what exactly they do and how it works.

23. Embedded/Systems SW position (unspecified, candidate's dream company) — GeeksforGeeks

  • Source: https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-set-2/
  • Candidate / context: experienced · Qualcomm | Outcome: offer (received offer; candidate states it was their dream company)
  • Rounds & how it went: Second interview process (within 1 month of the first rejection) consisted of 3 Technical rounds. Round 1: networking, OS schedulers, code-writing for a timer module handling timeouts/handlers for clients, callback functions, function pointers, linked-list programs, and code error detection. Round 2: in-depth project details, IPC, OS schedulers, prioritized processes/weighted round robin, software watchdog, memory management, memory leaks and tools, buffer overflows, deadlock prevention, semaphore/mutex/busy wait, memcpy with error scenarios. Round 3: stack corruption, stack smashing, program debugging, priority inversion, race conditions, semaphore/mutex, strcmp program, arbitrary linked list program, memcpy with overlapped memory, a small DI puzzle, and pointer subtraction.
  • Timing: Second process occurred within 1 month of the first rejection; 3 technical rounds.
  • Questions asked:
  • Network traffic measurements
  • Udp vs tcp, diff
  • OS schedulers
  • Timer module code // you need to write code for the timer module which actually handles timeout functionality for all clients and execute handlers of client at timeout
  • Callback functions
  • Function pointers
  • Program to Reverse a single linked list
  • Program to Detect loop in a single linked list
  • Error detection in code: int main(void) { char *p; while(i<50) p++; return p; }
  • Project details (in depth)
  • Ipc, os schedulers
  • Prioritized processes, weighted round robin
  • Software watchdog
  • Memory management
  • Mem leaks & corresponding tools
  • Buffer overflows and impacts/problems from that
  • Deadlock, methods to avoid, prevent, etc
  • Semaphore, mutex, busy wait
  • Memcpy code covering all error scenarios
  • Stack corruption
  • Hacking through stack smashing
  • Program debugging
  • Priority Inversion, ex
  • Race conditions, ex
  • Semaphore, mutex, ex
  • Strcmp, pgm
  • Arbitrary linked list program
  • Memcpy with overlapped memory address copy
  • Small general DI puzzle
  • Pointer subtraction
  • Tips / tricks: Sincerely thanks GeeksforGeeks as very helpful in preparation; hopes the experience is useful for other aspirants.

24. Qualcomm Technical Profiles (general; not a single named candidate experience) — GeeksforGeeks

  • Source: https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-questions-and-answers-for-technical-profiles/
  • Candidate / context: — | Outcome: unknown
  • Rounds & how it went: This page is a general 'Qualcomm Interview Questions and Answers for Technical Profiles' Q&A article, NOT a personal interview experience. It does not describe specific rounds, candidate names, dates, locations, outcomes, durations, or a timeline. It is a curated list of 35 commonly-asked technical interview questions (with linked answers) grouped by topic: Data Structures & Algorithms, Operating Systems, Database & ACID, Computer Architecture, Object-Oriented Programming, Memory Management, Networking, APIs & Tools, and C/C++ Programming. The page references a separate link to actual Qualcomm interview experiences, but those experiences are not present on this page.
  • Questions asked:
  • What is a pointer and types of pointers?
  • Difference between malloc() and calloc() in C
  • What is linked list and its types?
  • What is Binary Search Tree?
  • What is LRU Cache?
  • What is LFU cache?
  • What's the difference between Function overloading and function overloading?
  • What is the difference between Hashing and Hash Tables?
  • Find first and last positions of an element in a sorted array
  • Find position of an element in a sorted array of infinite numbers
  • Pairwise Swap Nodes of a given Linked List
  • What's the difference between BFS and DFS?
  • Left View of Binary Tree
  • Longest Palindrome in a String
  • Topological Sorting
  • Length of the longest substring without repeating characters
  • Check if a Binary Tree is BST or not
  • Merge Sort
  • Difference between Process and Thread
  • What is process synchronization in operating system?
  • What's the difference between mutex and semaphore?
  • What is Memory management?
  • What is Deadlock?
  • What's the difference between internal and external fragmentation?
  • What are overlays in OS?
  • What Race Condition Vulnerability?
  • ACID Properties
  • Difference between Normalization and Denormalization?
  • What is Cache Memory in Computer Organization?
  • What are 4 main features or pillars of oops?
  • What is the difference between heap and stack memory?
  • What's the difference between TCP and UDP?
  • What is a firewall in computer network and how does it work?
  • What is an API
  • Write your own memcpy() and memmove()
  • Tips / tricks: The article is structured as preparation material grouped by topic (DSA, OS, DBMS/ACID, computer architecture, OOP, memory management, networking, APIs, C/C++). Candidates preparing for Qualcomm technical roles should be ready across these areas. No camera/ISP/multimedia-specific content is present; the questions are general CS fundamentals plus coding problems. The page links out to actual Qualcomm interview experiences for further reading, but those are not on this page.

25. Sr Engineer / Sr Lead (Generative AI) — Medium

  • Source: https://medium.com/interview-preparation/my-qualcomm-interview-experience-for-sr-engineer-sr-702e8156d2d1
  • Candidate / context: experienced/senior · Qualcomm office (face-to-face / in-person) · Article published June 1, 2025; actual interview date not specified | Outcome: unknown
  • Rounds & how it went: The article describes Round 1: 'Coding, Puzzles, and GenAI Concepts.' This round had three components: a coding problem, a puzzle, and a few rapid-fire questions on Generative AI. The coding problem was a pair-sum-divisible-by-k problem. The author notes the key insight for the coding problem is the mathematical trick that (a + b) % k == 0 implies a % k + b % k == k. The puzzle and the specific GenAI rapid-fire questions are mentioned but not detailed in the available content. Subsequent rounds were not covered in the fetched excerpt.
  • Timing: Timing/durations of rounds and overall timeline not specified in the available content
  • Questions asked:
  • Given a list of integers and a number k, find the number of pairs (a, b) such that the sum of the pair is divisible by k. Example: List = [2, 4, 1, 8, 7], k = 3. Valid pairs: (2, 4), (2, 7), (1, 8), etc.
  • A puzzle (specific puzzle not detailed in the available content)
  • A few rapid-fire questions on Generative AI (specific questions not detailed in the available content)
  • Tips / tricks: Key insight shared for the coding problem: use the mathematical trick that (a + b) % k == 0 is equivalent to a % k + b % k == k (i.e., group numbers by their remainder mod k).

26. System Engineer — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/system-engineer
  • Candidate / context: Interviewed Feb 2026 (review posted 3 Mar 2026) | Outcome: Not Selected
  • Rounds & how it went: Posted by Anonymous. Interview experience rated 5/5 (Excellent). Difficulty level: Moderate. The candidate appeared for an interview in Feb 2026 and was asked a set of embedded/systems questions (single listed question set, no per-round breakdown given on the page).
  • Timing: Process Duration: Less than 2 weeks.
  • Questions asked:
  • What is isr
  • What is deadlock
  • Basic pointers qus
  • Explain about smart pointer
  • How to check processor is little endian or big endian?

27. System Engineer — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/system-engineer
  • Candidate / context: Interviewed Dec 2023 (review posted 13 Jan 2024) | Outcome: Selected
  • Rounds & how it went: Posted by Anonymous. Applied via Qualcomm Careers. Interview experience rated 5/5 (Excellent). Difficulty level: Hard. There were 4 interview rounds (Technical-1, Technical-2, Technical-3, HR). Round 1 - Technical (1 question): Managerial introduction and alignment with the job role. Round 2 - Technical (1 question): Technical Hardware Questions. Round 3 - Technical (1 question): Technical Software/Scripting Questions. Round 4 - HR (1 question): General HR discussions.
  • Timing: Process Duration: 2-4 weeks.
  • Questions asked:
  • Managerial Introduction and alignment with the job role.
  • Technical Hardware Questions
  • Technical Software/Scripting Questions
  • General HR discussions
  • Tips / tricks: Make sure you fit well with the requirements and have your fundamental understanding pretty strong. They will chain questions and keep going, make sure you have the thinking stamina to keep on going for 2 hours continuously.

28. System Engineer — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/system-engineer
  • Candidate / context: Interviewed Dec 2023 (review posted 13 Jan 2024) | Outcome: Selected
  • Rounds & how it went: Posted by Anonymous (this is a second listing of the same Dec 2023 experience as it appears separately on the page). Applied via Qualcomm Careers. Interview experience rated 5/5 (Excellent). Difficulty level: Hard. There were 4 interview rounds (Technical-1, Technical-2, Technical-3, HR). Round 1 - Technical: Managerial introduction and alignment with the job role. Round 2 - Technical: Technical Hardware Questions. Round 3 - Technical: Technical Software/Scripting Questions. Round 4 - HR: General HR discussions.
  • Timing: Process Duration: 2-4 weeks.
  • Questions asked:
  • Managerial Introduction and alignment with the job role.
  • Technical Hardware Questions
  • Technical Software/Scripting Questions
  • General HR discussions
  • Tips / tricks: Make sure you fit well with the requirements and have your fundamental understanding pretty strong. They will chain questions and keep going, make sure you have the thinking stamina to keep on going for 2 hours continuously.

29. System Engineer — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/system-engineer
  • Candidate / context: Interviewed before Oct 2023 (review posted 2 Oct 2024) | Outcome: Selected
  • Rounds & how it went: Posted by Anonymous. Applied via Referral. Interview experience rated 4/5 (Good). Difficulty level: Hard. There was 1 interview round - a One-on-one round with 2 questions (signal-processing / wireless / probability focus).
  • Timing: Process Duration: 2-4 weeks. (1 interview round)
  • Questions asked:
  • What will variance of sum of two iid random variables
  • Different type of fading channels in wireless system
  • Tips / tricks: Go through deep study.

30. System Engineer — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/system-engineer
  • Candidate / context: Interviewed before Oct 2022 (review posted 25 Oct 2023) | Outcome: Selected
  • Rounds & how it went: Posted by Anonymous. Applied via Company Website. Interview experience rated 5/5 (Excellent). Difficulty level: Moderate. There were 2 interview rounds. Round 1 - Resume Shortlist. Round 2 - One-on-one round with 4 questions focused on C and DSP (the candidate noted it was 3-4 rounds of C and DSP questions).
  • Timing: Process Duration: Less than 2 weeks. (2 interview rounds)
  • Questions asked:
  • 3-4 rounds of c and DSP questions.
  • Fourier transform
  • Digital filtering
  • C coding and basics
  • Tips / tricks: Have C and DSP concepts handy. Some tricky coding and fundamentals are a necessity.

31. Engineer (C++) — CodingKaro

  • Source: https://www.codingkaro.in/jobs-internships/leetcode-interview-experience/Qualcomm
  • Candidate / context: experienced, 1 YOE · June 3, 2025 | Outcome: offer
  • Rounds & how it went: Three elimination-based rounds: two technical rounds plus one hiring manager round. Candidate background: BE in ETCE from a Tier 1 college, previously at a top EDA company.
  • Questions asked:
  • Binary Tree Maximum Path Sum (Hard DSA)
  • Asteroid Collision (Hard DSA)
  • LRU Cache Implementation (Hard DSA)
  • Reverse Nodes in K Group (Hard DSA)

32. ML Systems Engineer — CodingKaro

  • Source: https://www.codingkaro.in/jobs-internships/leetcode-interview-experience/Qualcomm
  • Candidate / context: fresher, 0 YOE (on-campus) · Bengaluru · May 25, 2025 | Outcome: offer
  • Rounds & how it went: Online assessment followed by two technical rounds. Candidate background: MTech from IIT (CSE). Compensation reported: Rs 19.50L base + Rs 9.6L joining bonus + Rs 1.90L performance bonus + $16K stock.
  • Questions asked:
  • Leetcode Medium-Hard Problem (DSA)

33. Entry Level SWE — CodingKaro

  • Source: https://www.codingkaro.in/jobs-internships/leetcode-interview-experience/Qualcomm
  • Candidate / context: March 29, 2025 | Outcome: unknown
  • Rounds & how it went: A 6-round process covering problem-solving, system design, and behavioral.
  • Questions asked:
  • Number of Islands (DSA)
  • Secure Password Generator (DSA)
  • Design 5-star React Rating Component (System Design)
  • Generate Valid Sentences from Words (DSA)
  • Match Report and Player Statistics from API (Other)
  • Dealing with Strict Manager (Behavioral)
  • Handling Strict Deadlines and Unclear Instructions (Behavioral)
  • Propagate Failures in Dependency Graph (DSA)

34. Applications Engineer (Qualcomm) — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/applications-engineer
  • Candidate / context: Interviewed Jul 2024 (review posted 16 Aug 2024) | Outcome: no-response
  • Rounds & how it went: 1 interview round total. Applied via LinkedIn. Round 1 - Technical (2 questions): focused on DSA and bitwise operations, and GPU architecture. Difficulty level rated Moderate; overall interview experience rated 4/5 (Good).
  • Timing: Process Duration: Less than 2 weeks. Interviewed in Jul 2024.
  • Questions asked:
  • DSA, bitwise operations
  • Gpu architecture
  • Tips / tricks: Interview preparation tips - Prepare DSA, Bitwise operators, Parallel programming, GPU architecture.

35. Engineer (Experienced) — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer/experienced-candidates
  • Candidate / context: experienced · 13 Aug 2024 | Outcome: offer
  • Rounds & how it went: 3 rounds, all Technical (Technical-1, Technical-2, Technical-3). Interview experience rated 5/5 (Excellent). Result: Selected. Round 1 (Technical) - 2 questions: linked list merge and bitwise. Round 2 (Technical) - 2 questions: reverse words in string and inter-process communication theory. Round 3 (Technical) - 4 questions covering Linux kernel internals, motivation, dynamic 2D array multiplication, and Linux module development. Skills evaluated: Algorithms, Data Structures, Operating Systems.
  • Timing: Process duration not specified. 3 technical rounds.
  • Questions asked:
  • Merge two sorter linked list (Merge two sorted linked lists)
  • Bitwise questions easy to medium
  • Reverse words in String
  • Inter process communication theory
  • Why linux kernel ? And About how to compile linux kernel?
  • Why this role ?
  • Dynamic 2d array multiplication
  • Linux Module development
  • Tips / tricks: Interview preparation tips: Prep OS. Prep Embedded Linux. Prep Bitwise and Linked list Problems (easy to medium). Prep Array and String w.r.t to dynamic memory allocation. Prep Pointer Arithmetic.

36. Engineer (Experienced) — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer/experienced-candidates
  • Candidate / context: experienced · 12 Jun 2024 | Outcome: unknown
  • Rounds & how it went: 3 rounds: Coding Test-1, Coding Test-2, HR. Interview experience rated 5/5 (Excellent). Result: not specified. Round 1 (Coding Test): reverse a linked list. Round 2 (Coding Test): difference between structure vs union. Round 3 (HR) - 2 questions: salary expectation and tell me about yourself.
  • Timing: Process duration not specified. 3 rounds (2 coding tests + HR).
  • Questions asked:
  • Reverse a LinkedIn list (Reverse a Linked list)
  • Difference between Structure vs union
  • Salary expectation
  • Tell me about yourself

37. Engineer (Experienced) — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer/experienced-candidates
  • Candidate / context: experienced · 20 Apr 2022 | Outcome: unknown
  • Rounds & how it went: Applied via 'Approached by Company'; interviewed in Oct 2021. 4 interview rounds: Resume Shortlist, then three One-on-one rounds. Round 1 - Resume Shortlist. Round 2 - One-on-one (1 question): array manipulation questions. Round 3 - One-on-one (1 question): linked list questions, bit manipulation and C basics, C++, OOPs. Round 4 - One-on-one (1 question): C basics, recursion, stack and queue questions, reverse linked list in pairs.
  • Timing: Interviewed in Oct 2021. 4 rounds total (1 resume shortlist + 3 one-on-one).
  • Questions asked:
  • Array manipulation questions
  • Linkedlist questions, bit manipulation and C basics. C++,OOPs
  • C basics, recursion, stack and queue questions. Reverse linked list in pairs.
  • Tips / tricks: Interview preparation tips: Be confident with C and C++ and practice data structures such as stack, queue and linked lists.

38. Engineer (4G/5G modem system) (Experienced) — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer/experienced-candidates
  • Candidate / context: experienced · 13 Mar 2020 | Outcome: unknown
  • Rounds & how it went: Personal Interview. Interview Questionnaire - 1 question. Interviewed for 4G/5G modem system role. Topics that generally come in these types of interviews: communication systems basics in detail, modulation techniques in detail, wireless channel in detail (multipath etc.).
  • Timing: Not specified.
  • Questions asked:
  • I was interviewed for 4G/5G modem system. Topics that generally comes in these types of interview: Communication systems basics in detail, modulation techniques in detail, wireless channel in detail like m... (multipath etc.)

39. Engineer (Experienced) — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer/experienced-candidates
  • Candidate / context: experienced · 28 Jun 2017 | Outcome: unknown
  • Rounds & how it went: Appeared for an interview before Jun 2016. Rounds: Aptitude Test, Technical, HR (and 'Other'). Round (Test): basic questions testing normal knowledge, total 50 questions. Round (Technical Interview): 20 minutes, 5 questions on Scheduling, real-time OS, and file system; in-depth questions on file-handling in Linux; C++ from IBM site tutorials, C-FAQ for C coding tutorials; one puzzle regarding number of rectangles on a chessboard, plus typical technical questions. Round (HR Interview): family and educational background, tell me about yourself, went in-depth into Linux; main concern was whether candidate will join or not.
  • Timing: Aptitude Test: 50 questions. Technical Interview: 20 minutes, 5 questions. Appeared before Jun 2016.
  • Questions asked:
  • Scheduling, real-time OS, and file system based questions
  • In depth questions about file-handling in Linux
  • One puzzle, regarding number of rectangles on a chessboard
  • Family and educational background
  • Tell me about yourself
  • Went a little in-depth into Linux
  • Main concern: will you join or not
  • Tips / tricks: Overall preparation in C, DSP course, OS and a course in networking helps. For HR interview, know about the company, PPT and website.

40. Associate Software Engineer — GeeksforGeeks

  • Source: https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-experience-set-8-experienced/
  • Candidate / context: experienced, 1 year · Hyderabad · January 7, 2017 | Outcome: unknown
  • Rounds & how it went: Five rounds total. Round 1 was telephonic (70 minutes, 2 interviewers) covering project discussions from company and college, and Operating Systems concepts (memory management, CPU scheduling, deadlock with real-time examples, inter-process communication methods), plus coding. Round 2 was face-to-face (120 minutes) covering project history/work experience, memory overflow and crash handling scenarios, big and little endian concepts (notation, OS-specific implementations, writing code that works on both endian systems using macros), a string/word-counting coding problem, 10 pointer-based output prediction questions, and header file inclusion scenarios across x.h, y.cpp, z.h, a.cpp. Round 3 was face-to-face (80 minutes) covering process vs thread differences, two threads accessing same MAP with mutex/locking systems, storage classes in C, coding questions with call stack analysis, stack and queue data structures, stack vs heap memory differences, and function pointers and usage. Round 4 was face-to-face (80 minutes) covering inline functions (when they don't work, internals, performance benefits), relationship between function pointers and inline functions, static variables and static functions, pointer fundamentals and memory access, plus coding. Round 5 was the Manager/HR round (20-30 minutes) covering previous company and projects, position explanation, joining timeline and interest level, salary expectations and relocation willingness.
  • Timing: Round 1 (telephonic): 70 minutes. Round 2 (F2F): 120 minutes. Round 3 (F2F): 80 minutes. Round 4 (F2F): 80 minutes. Round 5 (Manager/HR): 20-30 minutes. Interview date January 7, 2017.
  • Questions asked:
  • Reverse a linked list
  • Print left view of a binary tree
  • Implement custom memcpy function
  • Find the word "is" in the paragraph: "This is my island of love and it is meant for kids of 10 years" (count: 4) - solutions using strcmp and custom logic, HashMap and word-searching approaches
  • 10 pointer-based output prediction questions
  • Header file inclusion scenarios across x.h, y.cpp, z.h, a.cpp
  • Process vs. thread differences
  • Two threads accessing same MAP, mutex, locking systems
  • Storage classes in C
  • Reverse the bits of a number
  • Min distance between two given nodes of a Binary Tree (call stack analysis requested)
  • Stack and queue data structures
  • Stack vs. heap memory differences
  • Function pointers and usage
  • Inline functions, when they don't work, internals, performance benefits
  • Relationship between function pointers and inline functions
  • Write your own sizeof operator
  • Static variables and static functions
  • Pointer fundamentals and memory access
  • Program to Detect loop in a circular linked list
  • Reverse the bits of a number and count the number of set bits
  • Memory overflow and crash handling scenarios
  • Big and little endian concepts, notation, OS-specific implementations, writing code that works on both endian systems using macros
  • Memory management
  • CPU scheduling
  • Deadlock and real-time examples
  • Inter-process communication methods
  • Tips / tricks: One must be clear with pointers and memory management and DS questions. Basics of C are heavily asked.

41. Embedded System (Embedded Software / Embedded Systems Engineer) — GeeksforGeeks

  • Source: https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-experience-for-embedded-system/
  • Candidate / context: fresher/entry-level (appears to be internship/entry-level based on context) · Last Updated 23 Jul, 2025 | Outcome: offer
  • Rounds & how it went: Two rounds. Round 1 had four distinct sections covering fundamentals: (1) Computer Organization/Architecture, (2) Data Structures, (3) Programming Logic & C, and a coding task on an online compiler. Round 2 had three questions including a C pattern-printing program, a chessboard box-counting problem, and a logic puzzle. The interview emphasized core/basic fundamentals, especially memory-related topics.
  • Timing: Not specified
  • Questions asked:
  • Computer Organization/Architecture: Signed and unsigned integer ranges
  • Memory-related questions
  • Memory hierarchy ordering (main memory, secondary memory, cache — proximity to the processor)
  • Program storage locations (where a program is stored)
  • Dynamic memory allocation usage
  • Given unsorted elements, for searching an element which Data Structure is best suited (with complexity analysis)
  • Binary search time complexity across different scenarios
  • HashMap, Stack, Binary Tree questions and complexity analysis
  • Find the missing element if you have been given an unsorted list from 1 - n elements (optimal approach)
  • Searching and sorting theory with complexity
  • Rotate k-elements to the right in an array (done on an online compiler)
  • Round 2: Pattern printing in C
  • Round 2: Chessboard box counting problem (count boxes of sizes 2x2 through 7x7)
  • Round 2: Logic puzzle (Torch and Bridge)
  • Tips / tricks: Focus on topics related to memory and the basics (almost everyone tends to ignore basic topics).

42. Intern + Full Time Employee (FTE) — GeeksforGeeks

  • Source: https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-experience-set-4-intern-full-time-employee/
  • Candidate / context: intern · Last Updated 23 Jul, 2025 | Outcome: offer
  • Rounds & how it went: Three rounds. Round 1 - Aptitude Test: 60 aptitude questions with negative marking; the candidate attempted around 48 questions, deliberately avoiding ones they were unsure of due to the penalty for wrong answers, and passed the round. Round 2 - Technical Interview: the longest round in the panel at roughly 1.5 hours; started with an introduction covering background, education and projects, followed by a project discussion that felt 'more of a conversation', then data structures questions. The candidate explained the linked list reversal visually before coding, implemented the stack well, and asked multiple clarifying questions. Round 3 - HR Interview: scenario-based behavioral questions and discussion of professional development; the interviewer questioned the candidate's English course completion. The candidate gave reasoning for their decisions, backed up weaknesses with mitigation plans, and asked 5-7 company-specific questions.
  • Timing: Round 2 (Technical) was approximately 1.5 hours, noted as the longest in the panel. Round 1 (Aptitude) and Round 3 (HR) durations not specified.
  • Questions asked:
  • Write a program to reverse a linked list
  • Write a working program for all operations in a stack
  • What is a stack, its use, etc?
  • Tips / tricks: Ask substantive, company-specific questions during the HR round (candidate asked 5-7). Provide clear reasoning for all answers and back weaknesses with mitigation plans. Use visual explanations to strengthen technical communication (e.g., explaining linked list reversal visually before coding). On the aptitude test with negative marking, avoid attempting questions you are uncertain about.

43. Software/Engineering (On-Campus, unspecified team) — GeeksforGeeks

  • Source: https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-experience-set-6-on-campus/
  • Candidate / context: fresher (on-campus student) · Last updated July 23, 2025 | Outcome: unknown
  • Rounds & how it went: On-campus recruitment process. Two interview panels conducted the interviews. Panel 1 was a technical panel covering a mix of HR-style and technical questions (programming, data structures, computer organization, and OS). Panel 2 was an HR panel covering background, project, and preference questions. Panel 1 questions: Tell me about yourself; How many interviews did you attend; Reasons for rejection in interviews; How you dealt with rejections; Swapping two numbers without a third variable; Deleting a node in a binary tree; Draw and explain the block diagram of a computer; Process states in OS. Panel 2 (HR) questions: Tell me about yourself; Strengths and weaknesses; About my project; Which location preferred; About my family. Round durations, overall timeline, and final outcome were not provided on the page.
  • Timing: Not provided on the page.
  • Questions asked:
  • Tell me about yourself.
  • How many interviews did you attend?
  • Reasons for your rejection in the interviews?
  • How did you deal with those rejections?
  • Swapping two numbers without the third variable.
  • Deleting a node in binary tree?
  • Draw the block diagram of a computer and explain?
  • Process states in OS?
  • Tell me about yourself?
  • Strengths and weaknesses.
  • About my project.
  • Which location I preferred?
  • About my family?
  • Tips / tricks: Not provided on the page.

44. Software / Systems Engineer (off-campus) — GeeksforGeeks

  • Source: https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-experience-off-campus-2021/
  • Candidate / context: fresher · Hyderabad · 2021 | Outcome: offer
  • Rounds & how it went: Three rounds. Round 1 - Online Test on the HirePro platform: MCQs with negative marking, divided into three sections of 30 minutes each (90 minutes total), each section containing 20 questions. Sections were (1) Aptitude, (2) Programming Questions, (3) Operating System, Computer Networks, Computer Architecture, Data Structures & Algorithms. Round 2 - Technical Interview over MS Teams using Hackerrank Codepair for code sharing; covered C/C++ language internals, a coding problem, and Operating System concepts. Round 3 - Aptitude & Coding round done in pseudocode, mostly DSA (linked lists, geometry, classic puzzles). The candidate was a fresher from IIIT Hyderabad and was selected.
  • Timing: 3 rounds in 2021. Round 1 online test: 90 minutes total, 30 minutes per section across 3 sections. Round 2 and Round 3 durations not specified on the page.
  • Questions asked:
  • C program execution flow
  • Difference between memcopy and mommove (memcpy and memmove)
  • Implement memcopy without temporary array
  • Content of executable C files
  • Stack growth direction
  • Volatile keyword
  • malloc(0) behavior
  • How free() determines memory to clear
  • Maximum allocatable memory
  • Find Count of Palindromic sub-string
  • Process vs Thread
  • Mutex vs Binary Semaphore
  • Virtual Memory
  • Virtual to physical address conversion (MMU)
  • Cache functionality
  • Cache, RAM, secondary memory speed comparison
  • Page table location
  • Priority Inversion
  • Check two Rectangle are overlapping or not
  • Trapping Water problem
  • 100 bulb problem
  • Linked List insert at beginning
  • Linked List insert at kth location
  • Detect Loop in linked List
  • Find middle of linked list
  • Tips / tricks: Overall interview process is focused on fundamentals of Computer Science. The candidate prepared core subjects from GATE notes and GeeksforGeeks. Advice: 'Always discuss approach first with interviewer then only write code so that he could help you if you are going wrong.'

45. Software Engineer (University graduate) — Medium

  • Source: https://kanwar7svastik.medium.com/qualcomm-software-engineer-interview-experience-3490052f1a03
  • Candidate / context: fresher, 0-1 year · 2025-11-14 | Outcome: offer
  • Rounds & how it went: Applied via referral. Round 0 - Online Assessment: 90 minutes covering CS fundamentals and aptitude questions with mixed difficulty levels. Round 1 - Technical (1 hour), conducted immediately after the online assessment: started with project introduction, then deep low-level/embedded questions on C storage classes, memory (stack/heap), fragmentation, dynamic memory allocation internals, enums, unions, memory leaks/stack overflow, mutex vs semaphore, plus coding (custom memcpy, linked list, struct padding). Round 2 - Technical (1 hour), scheduled 5 minutes after Round 1 completion: concurrency (priority inversion/inheritance, race conditions), bit manipulation, string problems, custom sizeof, linked list loop detection, storage classes revisited, pass-by-reference vs pass-by-value. Round 3 - HR + Technical (15 minutes): an aptitude/puzzle question, code output prediction, and OS systems concepts. Got verbal offer and then offer letter 5 days after the verbal offer.
  • Timing: Round 0 (Online Assessment): 90 minutes. Round 1 (Technical): 1 hour, immediately after the online assessment. Round 2 (Technical): 1 hour, started 5 minutes after Round 1. Round 3 (HR + Technical): 15 minutes. Offer letter received 5 days after the verbal offer.
  • Questions asked:
  • Introduce/explain your project
  • Explain C storage classes (extern, register, static, auto) and their impact on variable lifetime, scope, and visibility
  • Explain stack and heap memory in detail
  • What is internal vs. external fragmentation?
  • How do malloc, calloc, realloc, and free work internally?
  • How are enums implemented and how does enum indexing behave?
  • Explain the union data type and memory sharing
  • What are the conditions for a memory leak and a stack overflow?
  • What is the difference between mutex and semaphore and their use cases?
  • Implement a custom memcpy()
  • Write code for a linked list
  • Explain struct padding and calculate struct sizes
  • Explain the priority inversion problem and the priority inheritance solution
  • Identify thread race conditions in pseudocode
  • Bit manipulation: flip the Kth bit from the right
  • Validate whether a string is a palindrome
  • Convert a string to an integer
  • Implement a custom sizeof()
  • Detect a loop in a linked list using the slow/fast pointer technique
  • Explain storage classes (revisited)
  • Explain pass-by-reference vs pass-by-value with struct examples
  • What is the angle between the hour and minute hands at 3:15? (Answer: 7.5 degrees)
  • Predict the output of code involving malloc in a loop
  • What are system calls?
  • What are the memory management system calls?
  • Explain user mode and kernel mode concepts
  • Tips / tricks: Interview heavily emphasized low-level/embedded programming concepts: C storage classes, memory management fundamentals (stack/heap, fragmentation, malloc family internals, struct padding), and concurrency theory (mutex vs semaphore, priority inversion/inheritance, race conditions). Be ready to write implementations of standard library functions (memcpy, sizeof) and classic linked list / string / bit-manipulation problems. Also brush up on OS concepts (system calls, user vs kernel mode) and basic aptitude/puzzle questions for the HR round.

46. Engineer — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer
  • Candidate / context: experienced (not specified) · Posted 13 Aug 2024 | Outcome: Selected
  • Rounds & how it went: Three technical rounds (Technical-1, Technical-2, Technical-3). Interview experience rated 5/Excellent. Round 1 (Technical, 2 questions): merge two sorted linked lists; bitwise questions easy to medium. Round 2 (Technical, 2 questions): reverse words in string; inter-process communication theory. Round 3 (Technical, 4 questions): Linux kernel and compilation, why this role, dynamic 2D array multiplication, Linux module development. Skills evaluated: Algorithms, Data Structures, Operating Systems.
  • Timing: Process duration not specified
  • Questions asked:
  • Merge two sorted linked lists
  • Bitwise questions easy to medium
  • Reverse words in String
  • Inter process communication theory
  • Why linux kernel? And about how to compile linux kernel?
  • Why this role?
  • Dynamic 2d array multiplication
  • Linux Module development
  • Tips / tricks: Prep OS. Prep Embedded Linux. Prep Bitwise and Linked list Problems (easy to medium). Prep Array and String w.r.t to dynamic memory allocation. Prep Pointer Arithmetic.

47. Engineer — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer
  • Candidate / context: experienced (not specified) · Posted 11 Aug 2025; appeared for interview in Jul 2025 | Outcome: Selected
  • Rounds & how it went: Single round of questions. Interview experience rated 5/Excellent. Difficulty: Easy. Asked a program on pthreads and to reverse a linked list. Skills evaluated: Data Structures.
  • Timing: Process duration: Less than 2 weeks
  • Questions asked:
  • Program on pthreads
  • Reverse a linked list

48. Engineer — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer
  • Candidate / context: fresher (campus placement) · Posted 5 Nov 2024
  • Rounds & how it went: Applied via Campus Placement. Two rounds. Interview experience rated 5/Excellent. Round 1 - Aptitude Test: Aptitude, Programming, Communication. Round 2 - Technical (1 question): Detection & Estimation, Communication and Signal Processing.
  • Timing: Process duration not specified
  • Questions asked:
  • Aptitude, Programming, Communication (Aptitude Test round)
  • Detection & Estimation, Communication and Signal Processing

49. Engineer — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer
  • Candidate / context: experienced (not specified) · Posted 26 Jul 2024
  • Rounds & how it went: Single technical round. Interview experience rated 4/Good. Round 1 - Technical (2 questions): signal processing based questions; detection and estimation question.
  • Timing: Process duration not specified
  • Questions asked:
  • Signal Processing based questions
  • Detection and estimations question

50. Engineer — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer
  • Candidate / context: experienced (not specified) · Posted 7 Feb 2024
  • Rounds & how it went: Single one-on-one round. Interview experience rated 4/Good. Round 1 - One-on-one (5 questions) focused mostly on C, OS and wireless communication fundamentals. Skills evaluated: Operating Systems, Data Structures, C, RTOS.
  • Timing: Process duration not specified
  • Questions asked:
  • What does malloc return?
  • What is RTOS and how does it differ from OS?
  • Why not to use malloc?
  • What happens at stack/memory level when a null ptr is dereferenced?
  • Mostly on C, OS and wireless comm fundamentals.

51. Engineer — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer
  • Candidate / context: experienced (not specified) · Posted 10 Dec 2024; appeared for interview before Dec 2023 | Outcome: Selected
  • Rounds & how it went: Two rounds (Technical, Coding Test). Interview experience rated 4/Good. Difficulty: Moderate. Round 1 - Technical (5 questions): count elements in array in Python, merge two arrays in sorted order, difference between list and tuple, OOPs concepts, one regex and one file handling question in Python. Round 2 - Coding Test: pseudo code of binary search and some OOPs concept. Skills evaluated: Algorithms.
  • Timing: Process duration: Less than 2 weeks
  • Questions asked:
  • Count number of elements in an array in python.
  • Merge two arrays in sorted order.
  • Difference between list and tuple
  • OOPs Concepts: Abstraction, Encapsulation, Inheritance, Polymorphism
  • One regex question and one file handling question in python
  • Psuedo code of binary search. and some OOPs concept. (Round 2 - Coding Test)
  • Tips / tricks: Managerial round covered: any offers in hand, previous companies, and family backgrounds.

52. Engineer — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer
  • Candidate / context: experienced (not specified) · Posted 10 Oct 2024; interviewed in Apr 2024 | Outcome: Selected
  • Rounds & how it went: Applied via 'Approached by Company'. One technical round. Interview experience rated 5/Excellent. Difficulty: Easy. Round 1 - Technical (3 questions): problem solving, coding questions, XR related questions and OOPS programming.
  • Timing: Process duration: Less than 2 weeks; 1 interview round
  • Questions asked:
  • Problem solving
  • Coding questions
  • XR Related questions, OOPS programming

53. Engineer — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer
  • Candidate / context: experienced (not specified) · Posted 3 Apr 2024
  • Rounds & how it went: Three technical rounds (Technical-1, Technical-2, Technical-3). Interview experience rated 4/Good. Round 1 - Technical (1 question): OS, DBMS, coding questions. Round 2 - Technical (1 question): C, C++, OS questions. Round 3 - Technical (1 question): project, coding questions.
  • Timing: Process duration not specified
  • Questions asked:
  • Os, dbms, coding qs
  • C, c++, c os questions
  • Project, coding qs
  • Tips / tricks: Good

54. Engineer — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer
  • Candidate / context: experienced (not specified) · Posted 13 May 2025; appeared for interview before May 2024 | Outcome: Selected
  • Rounds & how it went: Interview experience rated 5/Excellent. Difficulty: Moderate. Asked about projects done in previous company and bit manipulation.
  • Timing: Process duration: Less than 2 weeks
  • Questions asked:
  • Projects done in previous company
  • Bit manupulation

55. Engineer — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer
  • Candidate / context: experienced (asked 9 months ago) · Asked ~9 months ago (relative to page update 16 Sep 2025) | Outcome: unknown
  • Rounds & how it went: Standalone asked question (not a full structured experience): write a program using pthreads.
  • Questions asked:
  • Write a program using pthreads.

56. Engineer — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer
  • Candidate / context: experienced (asked 9 months ago) · Asked ~9 months ago | Outcome: unknown
  • Rounds & how it went: Standalone asked question: reverse a singly linked list.
  • Questions asked:
  • Given the head of a singly linked list, reverse the list, and return the reversed list.

57. Engineer — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer
  • Candidate / context: experienced (asked 10 months ago) · Asked ~10 months ago | Outcome: unknown
  • Rounds & how it went: Standalone asked question: procedure to reverse a linked list.
  • Questions asked:
  • What is the procedure to reverse a linked list?

58. Engineer — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer
  • Candidate / context: experienced (asked 10 months ago) · Asked ~10 months ago | Outcome: unknown
  • Rounds & how it went: Standalone asked question: replacing occurrences of 'a' with 'ab' in a string.
  • Questions asked:
  • What is the process for replacing occurrences of 'a' with 'ab' in a string?

59. Engineer — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer
  • Candidate / context: experienced (not specified) | Outcome: unknown
  • Rounds & how it went: Standalone asked question: counting elements in an array using Python.
  • Questions asked:
  • How do you count the number of elements in an array using Python?

60. Engineer — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer
  • Candidate / context: experienced (not specified) | Outcome: unknown
  • Rounds & how it went: Standalone asked question: Merge Two Sorted Arrays (merge nums1 and nums2 in-place into nums1).
  • Questions asked:
  • Merge Two Sorted Arrays Problem Statement: Given two sorted integer arrays nums1 and nums2, merge them into a single sorted array nums1. The merge must be done in-place and you are allowed to modify nums1.

61. Engineer — AmbitionBox

  • Source: https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer
  • Candidate / context: experienced (not specified) | Outcome: unknown
  • Rounds & how it went: Standalone asked question: difference between a list and a tuple.
  • Questions asked:
  • What is the difference between a list and a tuple?

62. Engineer (C++) — LeetCode Discuss

  • Source: https://leetcode.com/discuss/post/6806397/qualcomm-engineer-interview-experience-b-6ndk/
  • Candidate / context: ~1 YOE; BE in ETCE from a Tier-1 college; previously at a top EDA company · India · Posted Jun 2025 | Outcome: Selected
  • Rounds & how it went: 3 elimination-based rounds (2 technical + 1 hiring manager). Round 1 (medium-to-hard DSA): find the maximum element in a binary tree; then a problem like Binary Tree Maximum Path Sum; solved both in ~30 min so given another like Asteroid Collision. Round 2 (hard, senior engineer): started with OS concepts - defragmentation, thrashing, virtual memory, memory management (deep dives); then C++ - auto storage class, explain virtual functions with an example and use case; then a twisted version of LRU Cache (explain logic + write pseudo-code, detailed follow-ups on each part); finally a problem like Reverse Nodes in K-Group (approach + pseudo-code, short on time). Round 3 (medium, hiring manager): asked how previous rounds went; resume/project deep-dive (role and contributions to runtime improvements via code changes); object-oriented design - Singleton class, ensuring thread safety, write the code; deep dive on abstraction, virtual classes, vtable, vptr.
  • Timing: 3 elimination-based rounds (each gates the next).
  • Questions asked:
  • Find the maximum element in a binary tree.
  • Binary Tree Maximum Path Sum (similar).
  • Asteroid Collision (similar).
  • Explain defragmentation, thrashing, virtual memory and memory-management concepts.
  • Explain the auto storage class in C++.
  • Explain virtual functions with an example and describe the use case.
  • Twisted version of LRU Cache (logic + pseudo-code).
  • Reverse Nodes in K-Group (similar).
  • Implement a Singleton class and make it thread-safe (write the code).
  • Explain abstraction, virtual classes, vtable, and vptr.
  • Tips / tricks: Rounds are strictly elimination-based. Strong coverage of DSA (binary tree, linked list, stack/asteroid), OS memory internals (thrashing, virtual memory, defragmentation), and C++ OOD (singleton + thread safety, vtable/vptr).

Part B — Restricted sites (Reddit / Blind / Glassdoor): Google-indexed snippets

These are partial (snippet-level) — they reliably give role, round count, timing and "how it went," but the specific question lists are usually truncated by the source. Source URLs included so you (logged in) can open the full thread.

B1 · Camera Engineer — r/qualcomm

  • Source: https://www.reddit.com/r/qualcomm/comments/1axnc8h/qualcomm_camera_engineer_interview/ (2 comments, ~2 yrs old)
  • Role: Camera Engineer (received interview call).
  • How it went / notes: OP: "I've recently received an interview call for a camera engineer position from Qualcomm. Unfortunately, I don't have a lot of background in camera systems." — thread is the candidate asking how to prepare for a camera-systems-focused loop without prior camera background. (Comment advice truncated in index.)

B2 · Camera ISP Architecture Engineer — r/chipdesign

  • Source: https://www.reddit.com/r/chipdesign/comments/1qku6xa/qualcomm_camera_isp_architecture_engineer_role/ (4 comments, ~5 mo old)
  • Role: Camera ISP Architecture Engineer.
  • What to expect (commenter advice): "expect questions about digital design fundamentals, timing constraints, pipeline architectures, and potentially some [HDL/RTL]…" — i.e. the ISP-architecture loop leans on digital-design + pipeline/architecture reasoning, not just DSA.

B3 · Camera ISP Architecture Engineer — Blind (teamblind.com)

  • Source: https://www.teamblind.com/post/qualcomm-camera-isp-architecture-engineer-role (posted 23 Jan 2026)
  • Role: Camera ISP Architecture Engineer. Candidate: 3 YOE (1 yr internship + 2 yr full-time).
  • Notes: "received an interview call from QC for the above mentioned role … currently working as …" — candidate seeking prep guidance for the ISP architecture loop. (Full text login-walled.)

B4 · Computer Vision Systems & Modeling Engineer — r/csMajors

  • Source: https://www.reddit.com/r/csMajors/comments/1p0ql7m/qualcomm_computer_vision_systems_modeling/ (4 comments, ~7 mo old)
  • Role: Computer Vision Systems & Modeling Engineer.
  • Notes: OP had first round of interviews for this role and crowd-sourced what to expect. (Details truncated in index.)

B5 · GPU Engineer (onsite) — r/csMajors

  • Source: r/csMajors "Qualcomm GPU Engineer Onsite Interview tips" (2 comments, ~4 mo old)
  • Role: GPU Engineer (onsite) — adjacent multimedia/graphics loop.
  • What to expect (commenter): "Expect to be asked about design some change to ISA, for XYZ system, or how would you implement some system for handling xyz bandwidth to do zyx." — open-ended systems/architecture design questions.

B6 · ASIC Design Engineer, image/video processing blocks — r/chipdesign

  • Source: r/chipdesign "Seeking Advice: Preparing for My First Interview at Qualcomm (Hardware Design Role)" (5 comments, ~1 yr old — post since deleted; cached description only)
  • Role: ASIC Design Engineer — "designing image and video processing blocks … micro-architecting HW for multimedia and camera." Directly camera/multimedia-adjacent hardware loop.

B7 · Interview feedback — embedded test role — r/qualcomm

  • Source: https://www.reddit.com/r/qualcomm/comments/1q29zsf/qualcomm_interview_feedback/ (30+ comments, ~5 mo old)
  • Round structure / timing: "Recently I had completed 3 rounds of Technical interview in qualcomm for embedded test role. Last round with manager …" — 3 technical + manager; thread is about waiting on feedback timing.

B8 · "Worst interview experience" (virtual loop) — r/qualcomm

  • Source: https://www.reddit.com/r/qualcomm/comments/1spid3l/worst_interview_experience/ (40+ comments, ~2 mo old)
  • Round structure / timing: "The interview was virtual. In total I had to go through 5 technical rounds and there was 1 director round at the end. They asked me c++ …" — 6 rounds total; heavy C++.

B9 · Whiteboard / HackerRank interview guidance (DV & ML) — r/qualcomm

  • Source: https://www.reddit.com/r/qualcomm/comments/1ql1mwy/qualcomm_whiteboard_interview_guidance/ (8 comments, ~5 mo old)
  • Notes: Asker: "What type of questions are asked on a hackerrank whiteboard interview which is for a design verification position?" Trick (top advice, for ML whiteboard): "focus more on collaboration rather than question and answers only" — interviewers weight how you think out loud / collaborate.

B10 · Senior Engineer, Audio Team (offline drive) — r/qualcomm

  • Source: https://www.reddit.com/r/qualcomm/comments/1s1ljnm/qualcomm_interview_for_senior_engineer_role_in/ (3 comments, ~3 mo old)
  • Round structure: "interview for senior engineer role in audio team … attended the offline drive and all interviews …" — multimedia-adjacent (audio); single-day offline drive format.

B11 · Device Driver role (2 online rounds) — r/qualcomm

  • Source: r/qualcomm "Recent interview no feedback" (5 comments, ~6 mo old)
  • Round structure: "applied … on LinkedIn for device driver role and got call for online 2 rounds of interviews …"

B12 · 6-round loop (screening + 5 technical) — r/qualcomm

  • Source: r/qualcomm "After 6 interview rounds, no update for 10 days — HR said…" (10+ comments, ~3 mo old)
  • Round structure / timing: "one screening round, followed by 5 technical" (6 total). Timing trick (top answer): for India-based roles, feedback often clusters around specific dates — "wait for 23rd–24th of March … this week is not that productive."

B13 · Glassdoor — Camera Systems Engineer (aggregate stats)

  • Source: https://www.glassdoor.co.in/Interview/Qualcomm-Camera-Systems-Engineer-Interview-Questions-EI_IE640.0,8_KO9,32.htm (1 interview report, updated 13 Mar 2017)
  • Stats (review text login-walled): Difficulty 3/5; 100% positive experience; ~1 day from application to hire (vs 11-day Qualcomm average); stages: 50% phone interview + 50% one-on-one; sourced via recruiter.

Appendix — All sources

A. Accessible sources (full text extracted → Part A)

  • AmbitionBox (1 exp) — https://www.ambitionbox.com/interviews/qualcomm-interview-questions/applications-engineer
  • AmbitionBox (17 exp) — https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer
  • AmbitionBox (5 exp) — https://www.ambitionbox.com/interviews/qualcomm-interview-questions/engineer/experienced-candidates
  • AmbitionBox (5 exp) — https://www.ambitionbox.com/interviews/qualcomm-interview-questions/system-engineer
  • CodingKaro (5 exp) — https://www.codingkaro.in/jobs-internships/leetcode-interview-experience/Qualcomm
  • GeeksforGeeks (1 exp) — https://www.geeksforgeeks.org/interview-experiences/qualcomm-fte-interview-experience-for-software-engineer-on-campus/
  • GeeksforGeeks (1 exp) — https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-experience-2/
  • GeeksforGeeks (1 exp) — https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-experience-for-associate-software-engineer-off-campus/
  • GeeksforGeeks (1 exp) — https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-experience-for-embedded-system/
  • GeeksforGeeks (1 exp) — https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-experience-for-ml-and-system-engineer/
  • GeeksforGeeks (1 exp) — https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-experience-for-sde-off-campus-2023/
  • GeeksforGeeks (1 exp) — https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-experience-off-campus-2021/
  • GeeksforGeeks (1 exp) — https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-experience-set-4-intern-full-time-employee/
  • GeeksforGeeks (1 exp) — https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-experience-set-6-on-campus/
  • GeeksforGeeks (1 exp) — https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-experience-set-8-experienced/
  • GeeksforGeeks (1 exp) — https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-experience-set-9-experienced-linkedin-invite/
  • GeeksforGeeks (1 exp) — https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-questions-and-answers-for-technical-profiles/
  • GeeksforGeeks (2 exp) — https://www.geeksforgeeks.org/interview-experiences/qualcomm-interview-set-2/
  • JoinTaro (1 exp) — https://www.jointaro.com/interviews/companies/qualcomm/experiences/camera-engineer-san-diego-ca-august-22-2023-accepted-offer-positive-1fc32442/
  • JoinTaro (1 exp) — https://www.jointaro.com/interviews/companies/qualcomm/experiences/video-codec-engineer-bengaluru-karnataka-october-29-2025-no-offer-positive-7cb1a305/
  • Medium (1 exp) — https://kanwar7svastik.medium.com/qualcomm-software-engineer-interview-experience-3490052f1a03
  • Medium (1 exp) — https://medium.com/@PranabNandy/qualcomm-interview-experience-2e0edc562d42
  • Medium (1 exp) — https://medium.com/@barath_natarajan/qualcomm-sde-1-interview-experience-c5fcbec3314e
  • Medium (1 exp) — https://medium.com/@k25296858/qualcomm-interview-experience-02c701880080
  • Medium (1 exp) — https://medium.com/@manishaagarwal/the-interview-story-experience-of-a-software-developer-part-1-qualcomm-90ad3a7a7d79
  • Medium (1 exp) — https://medium.com/@sumitpardhiya/%EF%B8%8F-qualcomm-my-interview-experience-34bbdb7f27c3
  • Medium (1 exp) — https://medium.com/@sumitpardhiya/qualcomm-senior-engineer-interview-experience-436b0f0fbc46
  • Medium (1 exp) — https://medium.com/interview-preparation/my-qualcomm-interview-experience-for-sr-engineer-sr-702e8156d2d1
  • foundit (1 exp) — https://www.foundit.in/career-advice/qualcomm-interview-questions-to-help-you-prepare-for-your-interview-at-qualcomm/
  • CleverPrep (1 aggregated camera guide) — https://www.cleverprep.com/companies/qualcomm/camera-engineer
  • LeetCode Discuss (1 exp) — https://leetcode.com/discuss/post/4972418/qualcomm-software-engineer-hyderabad-feb-d2yg/
  • LeetCode Discuss (1 exp) — https://leetcode.com/discuss/post/5079058/qualcomm-senior-engineer-hyderabad-april-u7dw/
  • LeetCode Discuss (1 exp) — https://leetcode.com/discuss/post/6806397/qualcomm-engineer-interview-experience-b-6ndk/

B. Restricted sites (snippet/stats only → Part B; full text needs a logged-in session)

  • Reddit r/qualcomm — Camera Engineer Interview — https://www.reddit.com/r/qualcomm/comments/1axnc8h/qualcomm_camera_engineer_interview/
  • Reddit r/chipdesign — Camera ISP Architecture Engineer Role — https://www.reddit.com/r/chipdesign/comments/1qku6xa/qualcomm_camera_isp_architecture_engineer_role/
  • Reddit r/csMajors — Computer Vision Systems & Modeling Engineer — https://www.reddit.com/r/csMajors/comments/1p0ql7m/qualcomm_computer_vision_systems_modeling/
  • Reddit r/qualcomm — Interview feedback (embedded test) — https://www.reddit.com/r/qualcomm/comments/1q29zsf/qualcomm_interview_feedback/
  • Reddit r/qualcomm — Worst interview experience — https://www.reddit.com/r/qualcomm/comments/1spid3l/worst_interview_experience/
  • Reddit r/qualcomm — Whiteboard interview guidance — https://www.reddit.com/r/qualcomm/comments/1ql1mwy/qualcomm_whiteboard_interview_guidance/
  • Reddit r/qualcomm — Senior Engineer, Audio Team — https://www.reddit.com/r/qualcomm/comments/1s1ljnm/qualcomm_interview_for_senior_engineer_role_in/
  • Reddit r/csMajors — GPU Engineer Onsite tips (referenced)
  • Reddit r/chipdesign — ASIC for image/video/camera blocks (post deleted; cached)
  • Blind (teamblind) — Camera ISP Architecture Engineer role — https://www.teamblind.com/post/qualcomm-camera-isp-architecture-engineer-role
  • Glassdoor — Camera Systems Engineer interviews — https://www.glassdoor.co.in/Interview/Qualcomm-Camera-Systems-Engineer-Interview-Questions-EI_IE640.0,8_KO9,32.htm
  • Glassdoor — Camera Engineer interviews — https://www.glassdoor.com/Interview/Qualcomm-Camera-Engineer-Interview-Questions-EI_IE640.0,8_KO9,24.htm
  • Glassdoor — Computer Vision Engineer interviews — https://www.glassdoor.com/Interview/Qualcomm-Computer-Vision-Engineer-Interview-Questions-EI_IE640.0,8_KO9,33.htm

C. Attempted but blocked / empty (no usable content)

  • NodeFlair camera-systems/camera-software/camera-engineer pages — JS shells, no real experiences.
  • AmbitionBox software-engineer / design-engineer / senior-engineer pages — intermittently bot-walled.
  • Naukri Code360, InterviewQuery, InterviewBit — bot-walled / no candidate experiences.
  • Reddit — every non-logged-in route (direct, redlib/libreddit mirrors, reader proxies) returned 401/403/Anubis; only Google-indexed snippets were quotable.

Compiled 2026-06-27 via Google search (Chrome) + page extraction (WebFetch for static sites, browser DOM extraction for JS-rendered LeetCode, Google-indexed snippets for Reddit/Blind/Glassdoor). Experiences are reproduced/condensed from the cited public sources; wording of questions preserved where possible.