Engineer – Software Build & Integration

HireSetu's note

Judged on debugging depth

Qualcomm doesn't put a number on experience. Everything on the preferred list is knowledge and ability: embedded, Linux, Android or RTOS, analytical debugging, an appetite for learning across domains. Freshers and mid-career engineers both fit that description, so the thing that separates candidates is evidence of hard debugging.

Pick two bugs you can talk through properly: one you found in firmware, one that looked like software until you checked the hardware. Include how you measured it and what changed after the fix. Build scripts and merge requests show the least interesting part of this work.

Software build means system images

At a chip company, build and integration is kernel, firmware, middleware and subsystem interfaces stitched together and made to boot on new silicon programs. Automation and observability work sits alongside that, not at the centre of it.

If your background is release engineering for web services, the vocabulary overlaps and the job doesn't. Linux internals, board bring-up and reading a register dump are closer to the daily work, with C or C++ plus a scripting language as the toolkit.

Onsite, close to the boards

Bring-up and hardware-firmware-kernel debugging happen where the boards, rigs and instruments are, and this job is onsite in Hyderabad. Being in the same building as the hardware team matters when a bug crosses the boundary between a driver and a regulator.

Ask how the team splits bring-up, customer escalations and automation, and how much of that work happens at your site. Power, thermal and performance investigations need instrumented setups, so where those live tells you what a normal week looks like.

Drafted with AI from Qualcomm's job posting and checked by Prashanth Jakkula before publishing. See our Editorial Policy.