JobsFirmware Engineer III, Wireless Data and Voice Path
Firmware Engineer III, Wireless Data and Voice Path
GoogleFirmware Engineer III, Wireless Data and Voice Path
GoogleLocation
Mountain View, CA
Type
Full-time
Posted
5/5/2026
Compensation
$138,000 - $198,000 per year
Undergraduate with 5+ Years of Experience
Approval 99%·Filings 5,616·New hires 2,898·
👑 Elite Sponsor
·FY 2025Job description
The Firmware Engineer III role focuses on optimizing modem data and voice traffic paths for Google's wireless technologies. As part of the Modem Protocol L2/Data team, you will enhance features related to LTE and 5G audio paths, ensuring efficient performance and user experience. This position involves collaboration with global carrier engineering teams and cross-layer teams to meet performance requirements. Your expertise will contribute to critical features for upcoming Pixel releases, driving advancements in wireless scheduling and data prioritization.
Requirements
- Bachelor's degree in Computer Science, Electrical Engineering, Computer Engineering, or a related technical field.
- 5 years of experience in modem protocol development, focusing on 3GPP LTE and 5G NR.
- 5 years of experience in coding with a general purpose programming language such as C/C++.
- Experience in wireless communications, mobile, and embedded systems.
Responsibilities
- Enhance modem data path and voice traffic path features to improve user experience.
- Optimize LTE and 5G related audio paths including JBM, RTP, PDCP/RLC and MAC in the wireless modem.
- Analyze, debug and fix modem protocol issues from the testing team, certification lab, and customers.
- Work and design with the global carriers engineering team to meet customer’s performance and features requirements.
- Collaborate with cross-layer teams, including layer 1 and Android audio related teams.
Benefits
- Employees at Google are often offered benefits like comprehensive health insurance, 401(k) matching, and flexible work arrangements, among other benefits.
Is this posting expired or inaccurate?
