Linux Stability and Debug Engineer, Sr Lead

<p><span>Looking for a candidate with 9+ Years of experience .As an Engineer for the Product Debug team, you will be driving software stability issues across Qualcomm SoCs. This role spans the product lifecycle—from pre-silicon validation to commercialization—requiring strong Linux/RTOS fundamentals, embedded systems knowledge, and a passion for debugging complex issues.</span></p><p></p><p></p><p><b><u>Key Responsibilities</u></b></p><p><b>Debug & Stability Analysis:</b><br />• Investigate and resolve complex system/software stability issues across multi-processor, Linux/multi-RTOS environments.<br />• Triage stability issues by coordinating with cross-functional teams (hardware, software, test, customer engineering).</p><p><b>Advanced Debug Techniques:</b><br />• Utilize tools such as JTAG, ETM, Trace32, GDB, and oscilloscopes for low-level debugging & instrument code in RDET/internal debug tools to improve system analysis.<br />• Perform code inspection, instrumentation, and log analysis to identify root causes.</p><p><b>Cross-Team Leadership:</b><br />• Represent the debug team in chip bring-up, stability scrums/reviews</p><p>• Drive improvements in debug processes via automation(RDET & internal tools), scripts, training material & developing/improving GenAI services( custom RAG based application on debug data sets)</p><p><b>Knowledge Development:</b><br />• Maintain expert-level understanding of Qualcomm SoC architecture, CPUSS architecture, DSP subsystems, and interconnects.<br />• Stay current on Linux kernel internals, device drivers, and embedded system trends.<br />• Expertise in Qualcomm DSP debugging.<br />• Deep understanding of Qualcomm Neural Network (QNN) model execution on DSPs, including performance optimization and troubleshooting.</p><p><b><u>Required Skills</u></b></p><p>• Strong analytical and problem-solving skills with ability to handle complex stability issues.<br />• Proficiency in C/C++ programming; familiarity with Assembly is a plus.<br />• Expert-level understanding of Linux internals (kernel, device drivers, memory management) and RTOS fundamentals (scheduling, synchronization).<br />• Solid understanding of ARM architecture and CPUSS architecture for system-level debugging and analysis.<br />• Ability to quickly adapt to new software stacks used in Auto, AI200 and Data Center, and effectively contribute to resolving issues.<br />• Hands-on experience with debugging tools (Trace32, GDB) and hardware/software interaction.<br />• Ability to prioritize tasks and work across multiple projects in a fast-paced environment.</p><p><b><u>Preferred Qualifications</u></b></p><p>Education:<br />o B.Tech/M.Tech in Electronics, Computer Science, or related field from a Tier-1 institute.<br />• Experience:<br />o 2–10 years in semiconductor or embedded systems domain with proven debugging expertise.<br />• Familiarity with ARM/Cortex/Hexagon/CPUSS architectures and bus systems (AHB, AXI, NoC).</p><p></p>

Back to blog

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...